Checking for Incompatibilities between Version 11.1 and 11.2
As a system administrator, you need to check incompatibilities between consecutive versions before upgrading your system.
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
Compatibility Issues
Critical
There are no critical issues when upgrading from version 11.1 to version 11.2.
Behavior Change
Topic |
Changed Behavior |
Possible incompatibilities |
Actions/Countermeasures |
---|---|---|---|
CP/WP routing |
FORMS request routing toRapid Automation agents has been changed. |
When you edit Rapid Automation connection objects, a corresponding Rapid Automation agent has to be active in the same client to retrieve data. |
Assign a Rapid Automation agent for relevant clients. |
Doubled MQ tables |
MQ tables have been doubled and renamed. |
MQ tables might not be considered when you use DB Reorg and existing scripts might fail due to changed table names. |
Adapt DB Reorg scripts. |
Proxy INI file extensions |
Parameters and the format of some parameter values have been changed in the INI file due to functionality improvements. |
You will not be able to reuse INI files of Proxy versions prior to v2 without adaptions. |
Adapt INI file parameters according to the Proxy user documentation. |
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 scheme/structure has been changed. |
Custom SQL queries on AE DB do not work anymore. |
|
Release Packaging |
The Release Packaging (zip files, folder structure and its content) have been changed. The following files and folders have been removed:
|
Possibly automated installation routines using release images will not work. |
If there are scripts relying on the old package structure, you have to adapt the paths. |
Third party monitoring via External Monitoring Interface |
The new state-of-the-art JMX interface EMI (External Monitoring Interface) has been introduced. The existing SNMP interface is still available, but the third party integration with BMC Patrol, HP OpenView, and Tivoli has been de-supported. |
There is no incompatibility, but the integration with BMC Patrol, HP OpenView, and Tivoli is not available anymore. |
Integrate third party monitoring systems via the new EMI instead. |