Checking for Incompatibilities between Version 12.0 and 12.1
As a system administrator, you need to check incompatibilities between consecutive versions before upgrading your system.
The tables below list 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
|
Topic |
Changed Behavior |
Possible Incompatibilities |
Actions/Countermeasures |
|---|---|---|---|
| Java Communication Process (JCP) | Installation of JCP(s) is mandatory for AE operations. | JCP/REST API is a required component as of 12.1 but it is not installed. | Install JCP(s) |
| Java >= 1.8 required | As of version 12.1 all components using Java (except Rapid Automation solutions) have been lifted from Java 1.7 up to 1.8 compile compatibility. | Java components will not run on computers with Java Version 1.7 or lower. | Upgrade Java Runtime to version >= 1.8.0. |
Behavior Change
|
Topic |
Changed Behavior |
Possible Incompatibilities |
Actions/Countermeasures |
|---|---|---|---|
| Access rights prevent objects being found in search | To access an object a user needs to have read access to the containing folder as well. | Objects are not found in the search. Objects (such as Login objects) are not displayed in the Process Assembly perspective | Adapt authorizations for users |
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. |
|
| IPv6 | Support for IPv6 | None | The system runs either in IPv4/IPv6 only environment, or a dual-stack environment where both is allowed. |
| 500k agent support |
AE supports up to 500k agents:
|
CPs now write job reports directly into the report tables within the AE database instead of passing it to the RWP. The load on CP side will therefore increase, but poses no problem at all. | If the customer experiences a performance drop due to this change of behavior, it is best to start more CPs to distribute the load. |
| Remove deprecated ResourceAdapter from AE.ApplicationInterface | ResourceAdapter is no longer supported after being deprecated. | ResourceAdapter no longer available. | N/A |
| AE REST API introduced | The completely new AE REST API is introduced. Some of its functional parts replace existing functions (e.g. object search). If the JCP does not work properly, the user will not be able to use specific functions. | If the new JCP is not set up and configured properly, AWA will not work as expected after an upgrade. | JCP has to be installed. Its INI file has to be configured properly (Object Search, REST WS). |
| New PS Agent | The tech stack of the PS agent has been changed to Java and some new functions have been added (as of V12.0.1). The new agent works with existing/old PS jobs and INI files without incompatibilities. |
|
|