Checking for Incompatibilities between Version 21.0.8 and 21.0.9

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
Enhanced Security	When HTTPS is enabled, the JCP and REST endpoints of the Automation Engine accept TLS v1.2 or higher.	Older third-party HTTPS clients that do not support TLS v1.2 can no longer connect to the respective AE endpoints when HTTPS is enabled.	Make sure you use updated third-party HTTPS clients.
New FTP Agent Going forward, new development will occur only in this new FTP Agent, although the "old" RA FTP Agent remains compatible with the newer Automic Automation versions.	The new FTP Agent installation does not require neither loading files to the database (DBLoad) nor creating an Agent object in Client 0, which simplifies the installation process. After the new Agent is installed, you can use the existing INI file to keep the Agent's configuration. For more information, please see the FTP Agent integration documentation at Integration FTP Agent.	UI panels of FTP jobs are not displayed properly. Also, there might be different Java version requirements.	In Client 0, remove the old FTP UI panels (ECC-AE-SHEET-RA-FTP) from the Storage object UC_ECC_PLUGINS. Make sure you check the Compatibility Matrix for further information.

Topic

Changed Behavior

Possible Incompatibilities

Actions/Countermeasures

Enhanced Security

When HTTPS is enabled, the JCP and REST endpoints of the Automation Engine accept TLS v1.2 or higher.

Older third-party HTTPS clients that do not support TLS v1.2 can no longer connect to the respective AE endpoints when HTTPS is enabled.

Make sure you use updated third-party HTTPS clients.

New FTP Agent

Going forward, new development will occur only in this new FTP Agent, although the "old" RA FTP Agent remains compatible with the newer Automic Automation versions.

The new FTP Agent installation does not require neither loading files to the database (DBLoad) nor creating an Agent object in Client 0, which simplifies the installation process.

After the new Agent is installed, you can use the existing INI file to keep the Agent's configuration.

For more information, please see the FTP Agent integration documentation at Integration FTP Agent.

UI panels of FTP jobs are not displayed properly.

Also, there might be different Java version requirements.

In Client 0, remove the old FTP UI panels (ECC-AE-SHEET-RA-FTP) from the Storage object UC_ECC_PLUGINS.

Make sure you check the Compatibility Matrix for further information.

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
Shipment of standard libraries for UNIX systems	The standard libraries (libstdc++.so and libgcc_s.so) are no longer part of the Agent, Service Manager nor Utilities .tar balls. Now, they can be found in the offering under External.Resources/unix_libraries/unix_libraries.tar.gz.	The relevant component does not start properly, if the libraries are not installed properly.	Make sure that all standard libraries are available so that the relevant component can used them. To do so, first, untar the component's (Agent, Service Manager, Utilities, and so on) .tar file. Then, untar the libraries' tar file and copy the files relevant for your Operating System to the component's bin folder. Additionaly, use the ln -s ./libstdc++.so.6 command to create symbolic links for the libraries in the bin folder.

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

Shipment of standard libraries for UNIX systems

The standard libraries (libstdc++.so and libgcc_s.so) are no longer part of the Agent, Service Manager nor Utilities .tar balls.

Now, they can be found in the offering under External.Resources/unix_libraries/unix_libraries.tar.gz.

The relevant component does not start properly, if the libraries are not installed properly.

Make sure that all standard libraries are available so that the relevant component can used them.

To do so, first, untar the component's (Agent, Service Manager, Utilities, and so on) .tar file. Then, untar the libraries' tar file and copy the files relevant for your Operating System to the component's bin folder. Additionaly, use the ln -s ./libstdc++.so.6 command to create symbolic links for the libraries in the bin folder.