Checking for Incompatibilities between Version 21.0.7 and 21.0.8

As a system administrator, you need to check incompatibilities between consecutive versions before upgrading your system. Check the compatibility matrix to find the relevant information on supported versions, setup, or prerequisites. For more information, see Compatibility Information.

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

This page includes the following:

Compatibility Issues

Automic Automation

Behavior Change

Topic	Changed Behavior	Possible Incompatibilities	Actions/Countermeasures
Agent re-connection behavior during a network outage	In v12.3, the Agents started up and tried to connect to a CP. If there was no CP running to establish the connection, the Agent remained running and retried to connect indefinitely in the interval defined in the RECONNECT_TIME system setting. In version 21, the Agents behave differently and, if there are no JCP available to connect to, the Agents shut down.	None.	Make sure you read the updated INI file documentation, see: Agent Unix INI file Agent Windows 64-bit INI file

Topic

Changed Behavior

Possible Incompatibilities

Actions/Countermeasures

Agent re-connection behavior during a network outage

In v12.3, the Agents started up and tried to connect to a CP. If there was no CP running to establish the connection, the Agent remained running and retried to connect indefinitely in the interval defined in the RECONNECT_TIME system setting.

In version 21, the Agents behave differently and, if there are no JCP available to connect to, the Agents shut down.

None.

Make sure you read the updated INI file documentation, see:

Agent Unix INI file
Agent Windows 64-bit INI file

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.	Check and adapt relevant SQL/SQLI/SQLJOBS objects accordingly Check and adapt relevant DB queries used in external tools/programs

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.

Check and adapt relevant SQL/SQLI/SQLJOBS objects accordingly
Check and adapt relevant DB queries used in external tools/programs

Automic Automation Kubernetes Edition

Advisory

Topic	Changed Behavior	Possible Incompatibilities	Actions/Countermeasures
Secure connections to PostgreSQL DB	As of this version, it is possible to use TLS-secured connections to PostgreSQL databases.	The ae-db Kubernetes service of type ExternalName is no longer created and used during the AAKE deployment, but, if it already exists, it is not deleted for compatibility reasons.	None because the service is not deleted after the upgrade. In case of a new installation, the service is not created.