Enterprise production deployments of HxGN NetWorks Comms often involve hundreds, or even thousands, of users running several different client applications (for example, desktop, web, and mobile). Upgrading all users simultaneously to a new version can be challenging for a company’s IT organization and business operations. When new versions of HxGN NetWorks Comms are made available, compatibility of client applications with previous maintenance releases of the same release version and previous release versions (when possible) are maintained. This allows flexibility in making upgrade roll-out plans for client users.
The utmost effort is applied to have newer versions compatible with lower versions of other HxGN NetWorks Core client applications. However, version compatibility is not always possible due to factors such as adoption of new technologies or architectures. For example, new capabilities that have been added to a newer version of HxGN NetWorks Comms applications are not available to prior versions of the HxGN NetWorks Comms applications. If mixed-version compatibility is not possible, users are informed in the HxGN NetWorks Comms Release Notes documentation delivered with the product and posted to the Support page when the new software is made publicly available.
Any new functionality available in a new release might not function in a mixed-version
environment.
The following sections provide specifics of mixed-version compatibility support with various combinations of HxGN NetWorks Comms products.
The term database in these sections refers to the metadata structure, as well as the database packages and procedures. The packages and procedures support metadata and HxGN NetWorks Comms operations like LTT, trace, and job management.
If you upgrade the database, the administrative users must operate with that same version of software to use metadata or to use API functions provided in the release.
In the table below, the term "viable" means that there are no known issues with the combination of software and database being represented. However, if any combination specific issues are identified, they can be resolved by upgrading one or more parts of the system.
Database to Comms all products
|
Database Version |
Software |
|||||
|---|---|---|---|---|---|---|
|
10.03 |
10.04.1812 |
10.04.2003 |
11.01.2201 |
11.01.2301 |
11.01.2401 |
|
|
10.03 |
Compatible |
Compatible |
Compatible |
Not Compatible |
Not Compatible |
Not Compatible |
|
10.04.1812– 10.04.1912 |
Compatible |
Compatible |
Compatible |
Not Compatible |
Not Compatible |
Not Compatible |
|
10.04.2003– 10.04.2112 |
Not Compatible |
Not Compatible |
Compatible |
Not Compatible |
Not Compatible |
Not Compatible |
|
11.01.2201–11.01.2202 |
Not Compatible |
Not Compatible |
Not Compatible |
Compatible |
Not Compatible |
Not Compatible |
|
11.01.2301–11.01.2302 |
Not Compatible |
Not Compatible |
Not Compatible |
Not Compatible |
Compatible |
Not Compatible |
|
11.01.2401 |
Not Compatible |
Not Compatible |
Not Compatible |
Not Compatible |
Compatible |
Compatible |
|
11.01.2402 |
Not Compatible |
Not Compatible |
Not Compatible |
Not Compatible |
Compatible |
Compatible |
For more information, see HxGN NetWorks Core Database-Software Version Compatibility.