Checking for Incompatibilities between Version 12.2 and 12.3

(J)WP and (J)CP - Process number to port range mapping

Note: When updating to this version, please check the new port definition for all types of server processes in the INI file of the Automation Engine.

More information:

• Types of Server Processes
• Automation Engine INI file

PWP: The PWP is the only WP that must have a port assigned. You do so in the pwpPort= parameter in the [TCP/IP] section of the INI file of the AE.

WPs: WPs connect to the PWP and to the CPs. Therefore, you do not have to assign ports for WPs in INI file of the AE.

CPs: The ports assigned to CPs are defined in the CP.PORTS= parameter in the [PORTS] section of the INI file of the AE.

JWP: The JWP is contacted by other WPs to carry out sync calls. JWPs can connect to any available port but you can define specific ports in the JWP.SYNC.PORTS= parameter in the [PORTS] section of the INI file of the AE.

JCP: The ports assigned to the JCP are defined in the JCP.PORTS= parameter in the [PORTS] section of the INI file of the AE.

The ports assigned to CPs, JWPs and JCPs can be defined in different ways:

• as single ports separated by semicolons
• as a port range
• as a combination of single ports and a port range

All process numbers assigned reflect the order in which the respective process starts.

None. However, pay special attention when performing a ZDU to this version.

If CP.PORTS are defined, these values are used. If not, the previous port definition is used.

If JWP.SYNC.PORTS are defined, these values are used. If they are not defined but the previous WP*=Port pairs are defined, the JWP consumes these ports. If none of these are defined, the JWP binds to any port available.

If JCP.PORTS are defined, these values are used. If they are not defined but the previous CP*=Port pairs are defined, the JCP consumes these ports in reverse order. f none of these are defined, the JCP binds to any port available.

It is recommended to migrate to the new port definitions as soon as possible.

Important! Pay special attention when old processes (12.2) are started after new ones (12.3) have been introduced into the system. You need to check the port numbers listed in the Processes & Utilization page (see Processes and Utilization) and adapt the INI file of the base version so that the processes use port numbers that are not being used already.

The forecast calculation only considers the days in which these tasks are planned and not the days for which the definition of the Calendar (CALE) object is not relevant.

Forecast and autoforecast items are differentiated internally by using two different object types and not one. This allows the system to request forecast and autoforecast data separately through the AE REST API.

The classes of the old forecast have been removed from the Java API.

Forecast data that was generated with the previous forecast functionality (thus using only one object type) does not support the new type.

Applications using the forecast classes of the old Java API will not find them anymore.

No action required.

When you upgrade your system, the existing forecast data is deleted automatically. If required, recalculate all relevant forecasts after a version upgrade.

Note: Do not perform any forecast calculation during a version upgrade, either manually or using the ZDU.

This variable is not used anymore.

If the variable still exists after an upgrade, the system ignores it. If the variable did not exist before the upgrade, it is not be created in the new version.

None.

No action required.

The obsolete variable can be deleted.

Agents with long passwords can be used as of version 12.1, not with older versions.

Note: The CAPAM A2A client is not compatible with Java 11 yet.

Use long passwords for agents only as of version 12.1 or higher. Shorter passwords can still be used.

The ServiceManager supports three different access levels:

1. Read: allows you to monitor the status of the services

2. Read and Execute: Allows you to execute commands, such as start and stop services, and monitor the status of the services.

3. Read, Execute, and Administrate: Allows you to edit the configuration of the ServiceManager, to execute commands, and to monitor the status of the services.

Unlike previous versions of the ServiceManager, the passwords are not encrypted but stored as a hash in the INI file of the Service Manager. On upgrade, an existing single password is migrated automatically and used initially for all three levels.

No action required.

However, it is recommended to assign different passwords for each level.

The message structure of the initial login message has changed with V4.

If UCXBM25C is an ALIAS (link) that points to UCCALL3I, change it to point to UCCALL4.

Example

//UCCALL EXEC PGM=UCXBM25C,REGION=65M,

change to:

//UCCALL EXEC PGM=UCCALL4,

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

None, since this is an additional, optional setting to increase security.