Checking for Incompatibilities between Version 21.0.10 and 21.0.11
As a system administrator, you need to check incompatibilities between consecutive versions before upgrading your system.
Each page lists the possible incompatibilities between two consecutive versions. If you are skipping one or more versions when upgrading, make sure you go through all the relevant pages. For example, if you upgrade from 24.0 to 24.3, you must read the pages for the 24.0 to 24.1, 24.1 to 24.2 and 24.2 to 24.3 pages.
The tables below lists new features that might lead to compatibility issues or should be taken care of when upgrading; they do not list all new features of this AE version. New features are described in full in the Release Highlights and Release Notes.
More information:
To provide a better overview, the tables are categorized by the severity of the issue. There are three different categories:
- Critical: Issues that must be addressed, otherwise the system will not work
- Behavior change: Functionality changes in existing features that might have an impact on your system
- Advisory: Different issues you should be aware of but might not have an impact on your system
The columns display the following information:
- Topic: Name of the general topic or new feature
- Changed behavior: What has been changed
- Possible incompatibilities: Impact the change may have
- Actions/Countermeasures: What can be done to identify and/or remove possible incompatibilities
This page includes the following:
Compatibility Issues
Automic Automation
Critical
|
Topic |
Changed Behavior |
Possible Incompatibilities |
Actions/Countermeasures |
|---|---|---|---|
| Mitigation of timeout issues for Agents |
The timeout for the connection between a TLS/SSL Agent and the Automation Engine for each Agent is no longer defined in the WEBSOCKET_TIMEOUT parameter in the UC_SYSTEM_SETTINGS. A new WEBSOCKET_TIMEOUT parameter has been added to the UC_HOSTCHAR_DEFAULT variable for this purpose. |
The existing WEBSOCKET_TIMEOUT parameter in the UC_SYSTEM_SETTINGS no longer applies to the timeout of TLS/SSL Agents and refers only to the connection timeout of the Java API or AWI and the corresponding Java communication process. If you used the WEBSOCKET_TIMEOUT parameter in the UC_SYSTEM_SETTINGS to define Agent timeout intervals, it will no longer work. |
Make sure you define the relevant TLS/SSL Agent timeout intervals using the new WEBSOCKET_TIMEOUT parameter in the UC_HOSTCHAR_DEFAULT variable. You can do so in the variable in Client 0, in which case the definition applies to the entire system or you can duplicate the variable and move it to the relevant Client to define an individual interval for a specific Agent. For more information, see UC_HOSTCHAR_DEFAULT - Host Characteristics. |
Advisory
|
Topic |
Changed Behavior |
Possible Incompatibilities |
Actions/Countermeasures |
|---|---|---|---|
|
General DB change Note: Information and the checking instructions apply to all versions, between your existing installation and the latest you want to upgrade to, respectively. |
The DB schema/structure has been changed. | Custom SQL queries on the AE database might not work after a change in the database schema/structure. |
|