Checking for Incompatibilities between Version 24.0.0 and 24.1.0

As a system administrator, you need to check incompatibilities between consecutive versions before upgrading your system.

Important!

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:

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.

Behavior Change

Topic

Changed Behavior

Possible Incompatibilities

Actions/Countermeasures

Changed the default value of Usage in :ATTACH_RES from C to T.

The default value for the optional Usage parameter has been unified so that it is T everywhere.

Now, if you leave the Usage parameter value for the :ATTACH_RES script statement empty (for example, :ATTACH_RES STORE_OBJECT, RESOURCE,,N) the default is T.

Scripts with :ATTACH_RES where Usage is empty have a different default value. Check the scripts where :ATTACH_RES is used without specifying a Usage value.
Changes to User Privileges

  • Users with the right to define privileges for other Users will not be able to grant privileges that they do not have themselves.

  • The previous Execute system upgrades privilege has been enhanced to include the right to start and stop processes too. This privilege has been renamed and it is called Upgrade system, start and stop processes now.

  • The previous Create diagnostic information privilege has been enhanced to include the right to define AWI's log level.

  • So far, the Execute system upgrades privilege (now renamed to Upgrade system, start and stop processes) included the ability to upgrade Agents automatically using the Centralized Agent Upgrade (CAU) solution. Now this privilege DOES NOT include the right to upgrade the Agents.

    A new privilege called Upgrade Agents (CAU) is now available for this purpose.

    Important! If you upgrade from 24.0.0 to 24.1.0, all the Users that had the Execute system upgrades privilege will automatically get the new Upgrade Agents (CAU) privilege too.

  • Administrators who have created Users with more privileges than themselves will be able to view those Users, provided they have the necessary rights, but they will not be able to modify them.

  • To be able to start and stop processes (both from the UI and through scripts), a User must have the Upgrade system, start and stop processes privilege. The following script functions are affected by this change: :SHUTDOWN, :TERMINATE and MODIFY_SYSTEM.

  • To be able to configure AWI's log level and tracing (both from the UI and through scripts), a User must have the Upgrade system, start and stop processes privilege. The following script functions are affected by this change: :SHUTDOWN, :TERMINATE and MODIFY_SYSTEM.

  • Administrators need the new Upgrade Agents (CAU) privilege to upgrade Agents though the CAU: If you create new administrator Users, you will have to grant this new privilege manually.

Check the definition of Users who have the privilege to create other Users and modify their definition accordingly.

Check the definition of Users who used to be able to start and stop processes and to configure logs and traces. Modify their definition accordingly.
Changed the message numbers printed in File Trasfer reports

Until now, when the source Agent of a File Transfer was the Java OS Agent on Windows, the following messages were printed to the report:

  • 11124

  • 11125

  • 11126

As of now, the Java OS Agent uses the following messages instead:

  • 63087

  • 63088

  • 63089

The old and new messages map as follows:

  • 11124 > 63087

  • 11125 > 63088

  • 11126 > 63089

Check the post processing of File Transfer reports for occurrences of old numbers.

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

Automic Automation Kubernetes Edition

Behavior Change

Topic

Changed Behavior

Possible Incompatibilities

Actions/Countermeasures
AAKE/Automic SaaS : Deployment and upgrade without the Automic Helm plugin The Automic Helm plugin has been removed and is no longer required to install and upgrade AAKE. None In case it is already integrated in a CI/CD pipeline, the plugin can be removed, but the database backup needs to be done before starting an upgrade.
Disabled privileged containers

As of this version you can restrict pod security policies for AAKE.

AAKE containers run in non-privileged/restricted mode and are no longer started with the root user

 If you use PVCs to mount the logs to files, the permissions of the folder on the storage will have to be changed accordingly: chown -R 1000 <logs_folder> and chmod 775 <logs_folder> Make sure you change the folder permissions as needed.