Checking for Incompatibilities between Version 10 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.

There are no incompatibilities, as the upgrade version works with the existing INI file. However, as the new parameters are not included in the existing INI files, they cannot be configured manually.

Add the new parameters to the existing INI files so that they can be configured properly.

The following parameters are new in the REST section:

• corsSupportEnabled
• corsAccessControlAllowOrigin
• gzipSupportEnabled
• minPoolSize
• maxPoolSize
• idleTimeout

You can copy these parameters from the default INI file shipped with the new AE version.

You do not have to change their default values if there is no explicit reason to do so.

A new parameter has been added to the UC_SYSTEM_SETTINGS:

SMGR_SUPPORT_LEGACY_SECURITY = Y/N

Y = Not secure communication with legacy ServiceManagers still supported by the AE

This is the default setting during upgrades from versions < 12.2.0.

N = Only secure communication (TLS 1.2) between the AE and ServiceManagers is supported.

This is the default setting for new installations and the recommended setting after a successful upgrade from versions < 12.2.0 and roll out of CAPKI on all concerned computers.

All components are backwards compatible. The SM-Dialog indicates whether a connection is a secure one or not.

Important! Secure communication mode currently not available for components running on:

• Linux 32 Bit

• Linux PowerPC BE

CAPKI must be installed in all computers where either a Service Manager, or one of its clients is supposed to run, see CAPKI - Securing the ServiceManager.

When creating a task, the Status in the Time & Dependencies tab of the task properties is undefined (blank) by default. It no longer is set to ANY_OK.

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

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

AE supports up to 500k agents:

• changed default for srvquery (ucsrv.ini) from 0 to 1, but has no impact on the AE
• CP writes job reports directly into the database

• The new PS agent supports JVM 64 bit
• It is built on Java (not on C like the old one).
• It doesn't support the "native interface"(only the CA Automic-specific one) anymore (PS agents configured to use the "native interface" do not start up and an according message is written to the agent log).

• If a PS job uses the "native interface" it has to be changed to use the CA Automic-specific interface instead.
• There is no need to use JVM 32 bit anymore
• The installation/upgrade of a PS agent replaces previous versions entirely

Java Workprocess (JWP)

Installation of JWP(s) is mandatory for several functions in Automation Engine and AWI.

N/A

Install JWP(s)

UserInterface

The UserInterface has been replaced by the Automic Web Interface.

The new features for v12 have been implemented for the AWI exclusively.

N/A

N/A

Change of script function behavior:

• PREP_PROCESS_FILENAME
• PRE_PROCESSS_FILE
• PREP_PROCESS
• GET_FILESYSTEM

In connection with the new feature Centralized Agent Upgrade (CAU) the behavior of these script functions has been changed.

They do not abort anymore, if an agent is not available but stay in "Waiting for host" instead.

N/A

N/A

All ServiceManager actions require a password.

The password defined in the ServiceManager settings is now required for all possible actions in the ServiceManager.

You will be prompted for a password when:

• moving an entry up or down
• opening properties
• editing/deleting/duplicating an entry

Enter the correct password when prompted.

DB Load and upgrade on SQL-Server

If the parameter in the SQL database READ_COMMITED_SNAPSHOT = FALSE then:

• The upgrade has to be done by a user who has dbowner rights.
• During the database upgrade no additional users besides DB Load are allowed.

Therefore in such cases the Zero Downtime Upgrade (ZDU) is not available.

N/A

Set READ_COMMITTED_SNAPSHOT = TRUE

Make sure that the permissions specified in the z/OS agent installation are granted, see Installing the Agent for z/OS.

Workaround: Set parameter ft_thread_level_security=no in the INI file of the z/OS agent at the (GLOBAL) section, see Agent z/OS.

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

Service Level Management (SLM)

The Service Level Management via the Service Level Objective objects (SLOs) is a new function as of v12.
The general Automation Engine behavior has not changed but the SLOs' monitoring may affect system performance.

The monitoring has been implemented by checks via CPs and JWPs.

N/A

N/A

Zero Downtime Upgrade in AWI

As of v12 the ZDU is available in the AWI.

Take care not to conduct the ZDU steps using UI and AWI alternately.

Perform the ZDU either via AWI or UI exclusively.

N/A

N/A

Rapid Automation (RA) agent solutions

In order to edit RA objects in the AWI, you must upgrade your RA agent solutions to versions that support the AWI. The latest version of most, but not all, RA solutions support the AWI. For information on specific RA solutions, see the Automic Compatibility Matrix. For more information, see Compatibility Information.

N/A

Contact Files to Aid Technical Support.

Web Service agent changes

New versions of the Web Service agent were split into separate RA solutions for SOAP (4.0.0) and REST (4.0.0).

Existing objects of version 3 are not automatically migrated to objects of version 4.

To migrate existing jobs from version 3 to 4 do the following :

• For SOAP migrate objects manually.
• For REST use the migration assistant.

CP/WP routing 

FORMS request routing toRapid Automation agents has been changed.

When you edit Rapid Automation connection objects, a corresponding Rapid Automation agent has to be active in the same client to retrieve data.

Assign a Rapid Automation agent for relevant clients.

Doubled MQ tables

MQ tables have been doubled and renamed.

MQ tables might not be considered when you use DB Reorg and existing scripts might fail due to changed table names.

Adapt DB Reorg scripts.

Proxy INI file extensions

Parameters and the format of some parameter values have been changed in the INI file due to functionality improvements.

You will not be able to reuse INI files of Proxy versions prior to v2 without adaptions.

Adapt INI file parameters according to the Proxy user documentation.

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

Release Packaging

The Release Packaging (zip files, folder structure and its content) have been changed.

The following files and folders have been removed:

• Folder ./11/ (the content, e.g. UserInterface, AutomationEngine) are now directly in the base directory and no longer in the sub folder.
• The uc4setup files and the CD image files have been removed.
• There is a new installer available for single box installation in the product bundles.

Possibly automated installation routines using release images will not work.

If there are scripts relying on the old package structure, you have to adapt the paths.

Third party monitoring via External Monitoring Interface

The new state-of-the-art JMX interface EMI (External Monitoring Interface) has been introduced.

The existing SNMP interface is still available, but the third party integration with BMC Patrol, HP OpenView, and Tivoli has been de-supported.

There is no incompatibility, but the integration with BMC Patrol, HP OpenView, and Tivoli is not available anymore.

Integrate third party monitoring systems via the new EMI instead.

Text variable values

• 1024 character limit for text based fields/variables has been removed
• Data type of DB fields has been changed from VARCHAR (1024) to CLOB (unlimited)

• Oracle DBMS_LOB Package must be installed to handle CLOB  
• Results on string based operations can exceed 1024 characters instead of string truncation or output error messages
• Queries of SQL/SQLI objects might operate on tables with text fields of changed data types

Check queries on tables with changed fields (VARCHAR -> CLOB)

such as search for "OVW_Value1": SELECT OH_Name FROM OH WHERE OH_Idnr IN (SELECT OVD_OH_Idnr FROM OVD WHERE OVD_SQL like '%OVW_Value1%' OR  OVD_SQLOra like '%OVW_Value1%' OR OVD_SQLDB2 like '%OVW_Value1%')

Script function GET_OH_IDNR

The second parameter client was removed from this Automation Engine scripting language function due to security reasons.

Objects using this script function with a specified parameter client that is different than the current client will write a warning to the message window, and return an invalid OH_IDNR.

Check all script tabs for this function and remove the parameter / correct the function call.

Login Objects required for file events on Windows, Unix

The new privilege File event: Start without Login object specified has been introduced for User objects

New privilege is checked and used per default after Automation Engine version upgrade but the file event still requires a Login object.

• To remain compatible to previous releases, set ANONYMOUS_FE=Y in the system variable UC_HOSTCHAR_DEFAULT, see ANONYMOUS_FE, ANONYMOUS_FT, ANONYMOUS_JOB
• If user objects are loaded via Transport Case or XML data is imported for example, this privilege may not be set. It must be set manually, if necessary.

zOS: Replacing Job line in JCL

The value of attribute MVS_JOBTYPE has been deprecated.

Currently no incompatibility, the old value is still compatible.

No checks/adaptions needed

XML Variables (VARA.XML)

• The "Oracle Instant Client" is no longer supported.
• "Oracle XML DB Package" has to be installed.

• The "Oracle Full Client" must be installed (instead of "Oracle Instant Client").
• The "Oracle XML DB Package" must be installed.

No checks/adaptions needed, part of the AE DB installation

FAULT_OTHER tasks

Deactivation behavior of tasks with status  FAULT_OTHER has been changed.

• In previous AE versions, tasks have been deactivated in activities list by default. As of v11 their deactivation is bound to the deactivation options of the task.
• Consequently more tasks will remain in Process Monitoring, than in previous AE versions.

Check deactivation options accordingly.

(If needed, they can be set to archive the behavior of previous AE version)

Script functions GET_ATT and GET_ATT_SUBSTR(call_text)

In previous AE versions, at least a blank was returned. As of v11, no value in case of missing call text is returned.

Error occurs on empty call text.

N/A

From v9 SP4 to v10 SP4, GET_VAR resolves recursively. This means, if a value contains an "&", the script processor tries to resolve this. This has been changed.
Example:
Static variable 'MYVAR', Key = 1 Value = 'Schmidt&Partners'
Script
:set &partners = 'no'
:set &value# = get_var('MYVAR','1')

The variable &value# will contain therefore:
v9 SP4 to v10: Schmidtno
V11 : Schmidt&Partners

With v10 SP4 HF1 the behavior was configurable (key RESOLVE_GET_VAR in UC_SYSTEM_SETTINGS).

In v11 the configuration option was removed. As a conclusion all variable values, that should be resolved recursively, must use the Script function RESOLVE_VAR.

Potentially all scripts that use GET_VAR and a variable value that contains "&" characters, are affected.
Affected scripts/variables are not easy to determine, especially with dynamic variables.
It is recommended to apply comprehensive tests.

To determine affected Variable objects, you may use this SQL query:

select oh_client, oh_name from oh where oh_idnr in
(select ovw_oh_idnr from ovw where
ovw_value1 like '%&%'
or OVW_Value2 like '%&%'
or ovw_value3 like '%&%'
or ovw_value4 like '%&%'
or ovw_value5 like '%&%'
) order by OH_Client, OH_Name asc

The Script function RESOLVE_VAR may be used to recursively resolve a static Variable object, see RESOLVE_VAR.

Message numbers

(For detailed information on individual possible impact, see Message Number Changes.)

Message numbers are now eight digits long, instead of seven.

Old format: Unnnnnn
New format Unnnnnnn

Filtering on Unnnnnn numbers won't work with

• PREP_PROCESS_REPORT
• PREP_PROCESS_FILE
• Output scan filter
• Log scan scripts or custom tools
• Job reports of old java-based agents contain 7 and 8 digit messages
• Agents of older versions send/log 7 digit message numbers

• Find out script functions PREP_PROCESS_REPORT and PREP_PROCESS_FILE in scripts via search function such as change PREP_PROCESS_REPORT(,,’ACT’,’*U1234567*’) to PREP_PROCESS_REPORT(,,’ACT’,’*U01234567*’) 
• Check filter objects manually or use a SQL statement such as SELECT OH_Name FROM OH,OFC WHERE OH_Idnr=OFC_OH_Idnr AND OFC_Filtertext LIKE 'U001%' AND OH_DeleteFlag = 0

Rapid Automation (RA) agents

Shared third party libraries were removed from the RA agent core.

You have to obtain all needed shared third party libraries and ensure that they are installed properly.

Download Oracle JDBC driver and copy it to the lib directory of the RA core.

Note: This is only required for an RA agent that needs an Oracle DB connection (via JDBC) - such as RA Banner Agent, RA Oracle E-Business Suite Agent, RA JD Edwards Agent, or RA Oracle Retail Agent.