Release Notes - AE Version 11.1

Message numbers

(For detailed information on individual possible impact see also the topic Message number changes)

Filtering on Unnnnnn numbers won't work with

• PREP_PROCESS_REPORT
• PERP_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 e.g. change PREP_PROCESS_REPORT(,,’ACT’,’*U1234567*’) to PREP_PROCESS_REPORT(,,’ACT’,’*U01234567*’) 
• Check filter objects manually or use a SQL statement such as
  e.g. SELECT OH_Name FROM OH,OFC WHERE OH_Idnr=OFC_OH_Idnr AND OFC_Filtertext LIKE 'U001%' AND OH_DeleteFlag = 0

Script function ACTIVATE_UC_OBJECT

Script variables have been changed to unlimited length.

You can use GET_VAR to check for a non-existing key, which returns a blank, as shown in this example:
:SET &test# = GET_VAR(‚VARA.TEST‘,‘KEY_DOES_NOT_EXIST‘)

If you use STR_MATCH() following on this, with an empty string for the script variable &test#, like this:
:SET &true# = STR_MATCH(&test#,"")

in v10 of the Automation Engine the return value for &true# will be "Y"
In V11 it will be "N".

Explanation:
In STR_MATCH() a variable of length 0 is expected (""). Since the variable &test# contains a blank (" "), the return value for &true# is "N".

The v11 behavior thus is correct.

Grouping Criteria in the Activity Window

A new Grouping field is available in the left section of the Activity window. You can use this field to select a grouping criterion. Various items will be listed directly below for you to filter the activities list, depending on the option selected in the combo box.

The Queues, Agents, and Status grouping criteria are available by default. If you choose the Agents option, for example, the agents that are available in the client will be listed in the left section of the window. If you select an agent, the activities list (in the right section of the window) will only show the tasks that are executed on that agent.

In addition, you can also define your own grouping criteria for activities. The new UC_CUSTOM_ATTRIBUTES variable is used for this. You can allocate user-defined grouping criteria to an executable object on the Header tab (new section: Custom metadata).

The values of user-defined grouping criteria are used for filtering in the Activity window and originate from a reference variable object. When allocating grouping criteria on the Header tab, you do not necessarily have to select one of the reference values for a grouping criterion; you can also enter a value of your choice manually.

Since Version 9, only the list of queues has been available for direct filtering in the left area of the Activity window.

New Column 'Status within Parent' in Activity Window

A new column is available in the activity window, called "Status within parent". It shows the current state of a task that is child to another (for example a job inside a workflow).

Display of FAULT_OTHER Jobs in Activity Window - New Function Key

The key DEACT_FAULT_OTHER may be set in the system variable UC_CLIENT_SETTINGS. This key has two values which determine, if a job with status FAULT_OTHER should be kept in the Activity Window or not.

New Key SEND_MAIL_DEFAULT

In the system variable UC_CLIENT_SETTINGS the new optional key SEND_MAIL_DEFAULT may now be used. It allows the setting of the parameters Agent and Login, which define the Login object and agent to be used for sending emails.
Settings in the optional key SEND_MAIL_DEFAULT will override individual SEND_MAIL script settings anywhere throughout the respective client.

New Method: Adaptive ERT Calculation

The new "adaptive" ERT calculation method calculates the expected runtime in an intelligent and anticipatory way. By default, the following factors are considered:

• Parent alias
• Parent name
• Agent (in a file transfer: the source and target agent)
• Start time

You can also define other factors by using the new setting ERT_ADAPTIVE_DEFAULT_CONTEXT (variable UC_CLIENT_SETTINGS).

A new Java-based work process (=JWP) is required for calculating the adaptive ERT because no other work process can perform this kind of calculation. Note that you cannot make an adaptive ERT calculation if there is no available JWP.

New settings in the variable UC_CLIENT_SETTINGS:

• ERT_ADAPTIVE - Activates/deactivates the adaptive ERT calculation for the entire client.
• ERT_ADAPTIVE_DEFAULT_CONTEXT - Defines additional factors that have to be considered for the adaptive ERT calculation.
• ERT_ADAPTIVE_FALLBACK_METHOD - This is an alternative ERT calculation method for when you cannot use the adaptive calculation because there is no available JWP.

New setting in UC_SYSTEM_SETTINGS:

• ERT_ADAPTIVE_JWP_TIMEOUT - Time in seconds that the system waits after a system start until a JWP is available. After this period of time, it will use the alternative ERT calculation method (UC_CLIENT_SETTINGS: ERT_ADAPTIVE_FALLBACK_METHOD) until a JWP is active.

The setting ERT_METHOD (UC_CLIENT_SETTINGS) includes the new option "ADAPTIVE".

The Variables & Prompts tab of executable objects has been extended. The new column Use for adaptive ERT as is now available. Use this to define object variables as factors that should be considered in the adaptive ERT calculation.

Java-based Work Process (JWP)

There is a new Java-based work process (JWP) which is required for the following functions:

• Adaptive ERT calculation
• Single Sign-On using KDC

The JWP can initially only run the listed processes. It cannot run the processes of other WPs.

The JWP installation instructions can be found in the Administration Guide under "New installation".

Single Sign-On

Single Sign-On can now be configured via Kerberos KDC (Key Distribution Center) for an Automation Engine system. If Single Sign-On is selected, users can log in to the system without having to enter login details. Authentication takes place via a Service Directory (for example: Microsoft Active Directory).

There also is the new configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. variable UC_KDC_SETTINGS, which provides a range of different settings.

The instructions for Setting up Single Sign-On can be found in the Administration Guide.

As part of Single Sign-On, the Login dialog (UserInterface, Enterprise Control Center) has also been extended with additional options: "Use integrated authentication" and "Enable autologin". If you select these options, log-on will be performed via Single Sign-On. The fields for the login details (user, passwordA secret combination of characters for a Automation Engine user., departmentDepartment name to which the Automation Engine user belongs.) are deactivated in this case.

In addition the System variables UC_SYSTEM_SETTINGS and UC_CLIENT_SETTINGS have been extended to set or enable authentication via KDC.

The new Single Sign-On mechanism is completely independent from the previous one (UC_USER_LOGON) but does not replace it.

Execution of Deployment Workflows

You can now start Deployment Workflows directly in the UserInterface with the required values and parameters being retrieved from Application Release Automation (ARA). Deployment Workflows are defined in the ECC or the UserInterface. Previously you could only activate them in ARA.

For more details about requirements and handling refer to the chapter Application Integration.

Clustered indexes on MS SQL Servers

Only relevant on MS SQL Servers used as the Automation Engine database.

If deadlocks occasionally occur when accessing the MELD, AH, RH, RT, or UC_TEMP* tables, there is an option to convert the database to clustered indexes.
To do so, open the file IMAGE:/DB/GENERAL/11.0/CLUSTERED_INDEX.TXT using the utility AE.DB Load. Alternatively, you can run the file IMAGE:/DB/SQL_9/11.0/STEPS/CLUSTERED_INDEX.SQL directly in the database.

New Export Function for Folder Structures

You may now export and import folder structures, including linked external objects, folder and non-folder objects. The UserInterface and the script elements EXPORT and IMPORT have been modified accordingly.

Message Numbers - Now Eight Digits

The number of message digits has been changed. Message numbers are now eight digits long, instead of seven.

Default Password for New Users Defined Without a Password

You can now define a custom default password in a client using the PWD_DEFAULT setting in the UC_CLIENT_SETTINGS variable. This setting specifies the default password for new users defined without a password. You might want to use this setting to specify a default password that complies with your configured password policy. When a password is specified with this setting, the user will use this password when logging into the client for the first time. They will then be prompted to change their password.

Documentation - Selecting a Guide during a Search

A new combo box is available for use in the WebHelp during a search. You can use the combo box to select a specific manual. For example, when you select User Manual in the combo box, only documents from the User Manual will be included in your search.

Application Interface - New Library for .NET Programs

Automic now provides a new DLL library which allows you to use the ApplicationInterface for .NET programming languages.

PromptSet - Multi-Line Function for Text Fields

There is a new option for text fields in PromptSet objects to add multiple lines to a text field. An Editor dialog box is available for multi-line text fields. You can open the Editor by clicking a new button in the top right corner.

Activity Window "Selection" New Activation Tab

A new Activation tab is available on which you can define a time frame (dialog for filtering the Activity Window).

New Script Elements

• :ATTACH_RES - Specifies the resources to be attached to the Storage object, for use with the UNIX or Windows agent.
• :BEGIN_EXT_INTERPRETERS ..:END_EXT_INTERPRETERS - Defines the beginning and end of the external interpreter script in Job objects (JOBS, Windows and UNIX).
• PREP_PROCESS_VAR_XML - Used exactly like PREP_PROCESS_VAR, but only in conjunction with the new Variable object XML.
• :PUT_VAR_PROCESS - Writes the contents of a data sequence to a static Variable object.
• :REGISTER_VARIABLE - Used with the :BEGIN_EXT_INTERPRETERS and :END_EXT_INTERPRETERS script statement to use the values of a user defined variable together with an external interpreter script.
• XML_APPEND_BEFORE - Shifts an XML element to before another element.
• XML_APPEND_CHILD- Adds a sub-element to an XML element.
• XML_APPEND_CLONE - Duplicates an XML element and appends it to another element.
• XML_APPEND_ELEMENT - Appends an existing XML element to another element.
• XML_CLONE_AND_RENAME - Duplicates an XML element and renames it.
• XML_DELETE_NODE - Removes a specific XML element.
• XML_DOM_TO_PROCESS - Creates a data sequence that is based on a certain XML document.
• XML_INSERT_BEFORE - Creates a new XML element and inserts it before another element.
• XML_PROCESS_TO_DOM - Creates an XML document from a data sequence.
• XML_REMOVE_CHILDREN - Removes all sub-elements of an XML element.
• XML_SET_ATTRIBUTE- Adds a new attribute to an XML element or modifies an existing one.
• XML_SET_NODE_TEXT - Modifies or sets the value of an XML element.
• XML_TO_STRING - Returns the XML of a specific element as text.
• DELETE_FORECAST - Deletes any number of or given Forecasts stored in the Automation Engine database.

Extended Rollback / Backup

• File-based backup/rollback of non-existing directories:
  You can now specify a backup path that does not exist for file-based rollbacks. When you run a file-based backup from a non-existing file path, it will be deleted during the rollback process provided that it has previously been created when the job or file transfer has been processed.
• Closing / or \ characters no longer required when a path is specified for the backup path:
  A verification process in the target system now checks whether a directory or a file is involved. Previously, you had to specify either a directory or a file. For directories, you had to identify directories with closing / or \ characters. This is no longer necessary.
• File-based backup: Including empty directories
  By defining the value "1" in the object variable &RB_FBACKUP_COPY_EMPTY_DIR#" within the task (Variables & Prompts tab) you can activate the behavior that empty sub-directories are included in file-based backups. Sub-directories that are not empty are by default included in backup processes.
• User-defined rollback:
  When you start the backup task, the new object variable &RB_CBACKUP_RUNID# will now automatically be created within the parent task. This variable stores the RunID of the backup task.

Extended JCL Exit for z/OS Jobs

The JCL Exit is a user-defined module which the agent calls when z/OS jobs start in order to change the job JCL before the job is processed.

Previously, the JCL Exit had to be written in Assembler. Now you can also create such modules in the programming language C. The following new parameters are available in the z/OS agent's INI-file (section (JCL Exit)):

• ExitModul=
  The name of the DLL file of the exit module. If not otherwise specified, no module is loaded and the JCL Exit function is deactivated.
• ExitFunction=
  The name of the function within the module, which implements the JCL Exit.
• InitFunction=
  The function that is called when the agent starts (optional).
• CloseFunction=
  The function that is called when the agent ends (optional).

The Utility AE DB Load has a New Parameter -F for Folder Handling

The new parameter defines the behavior of AE DB Load concerning folders, when used as part of the Start Parameters. You may now choose between replacement of data of objects and linked objects or preservation of the data in the Automation Engine database.

Internal Webservices Available on Tomcat

The Automation Engine webservices are now also available on Tomcat. Detailed installation instructions are supplied in "Installing the AE Internal Webservice (Tomcat)"

SAP FCC 2.0 Add-on and SAP Business Add Ins now Available

The SAP FCC 2.0 Add-on may now be integrated in the Automation Engine system. You also may use SAP Business Add Ins (BAdI) with Automation Engine.

LDAP over SSL

For LDAP synchronization now also Oracle Directory Server is supported.

In the system variable UC_LDAP_EXAMPLE the three new keys, SYNC_LOGIN, VERSION and TLS are now available.
VERSION and TLS determine the use of an SSL connection to the respective LDAP server.
The key SYNC_LOGIN is optional and may be used to define one special UC_LDAP_Domain variable, in case a Login object shall be used for technical user credentials that enable the synchronization of LDAP data for users whose permissions are not sufficient.

In addition the User object has a new field to set the Distinguished name and user information, which is visible in case LDAP over SSL has been activated by the system administrator.

As the use of LDAP over SSL requires a Java based Work Process (JWP), the JWP Installation procedure has been complemented with information about adding the necessary certificates for SSL.

New Privilege in System Variable UC_HOSTCHAR_DEFAULT

The System variable UC_HOSTCHAR_DEFAULT has a new privilege, called ANONYMUS_FE. It may be used for FileEvents and has the same functions as ANONYMUS_FT and ANONYMUS_JOB.

Trace Added for the AE DB Change and AE DB Unload Utilities

You can now set the trace level for the program flow of the utility in the:

• UCYBCHNG.INI file for AE DB Change.
• UCYBDBUN.INI file for AE DB Unload.

ServiceManager Utility for UNIX No Longer Needs to Be Started with SetUID Bit

Due to a fix added to AE 11.2.0, 11.1.2, 10.0.6, and 9.13.0, the ServiceManager utility for UNIX no longer needs to be started with SetUID Bit.

Specifying Whether Sync Objects Are Checked When Restarting a Canceled Job Without an Abend Action

The new key SYNC_CHECK_RESTART in the UC_SYSTEM_SETTINGS variable determines whether Sync objects are checked when restarting a canceled job without an Abend action. It defaults to Y for yes to keep with the v9 behavior.

This setting was added to Automation Engine 10.0.6 SP6 and Automation Engine 11.1.1. There were some releases where this variable did not exist and the behavior was that the Sync object was not checked and jobs were restarted immediately.

UNIX Agent: Support of PAM

Previously, PAM (Pluggable Authentication Modules) were only supported for Solaris agents. Now, PAM support is also provided for Linux and AIX agents.

New Parameter for z/OS Agent INI

A new parameter has been introduced: jobSubmitContext=.
The job card in the JCL thus may either contain the user information of the Job's Login object, or the credentials won't be generated into the job card and the Job will be submitted to the host with the user credentials used with the agent.

Additional Database Support for SQL Agent

As of version 11 the databases PostgreSQL and EXASOL are being supported.

New IP Binding Function for SQL Agent in DB Service Mode

For the SQL agent a new function is available: In the section DB_SERVICE of the Automation Engine's INI file, the new parameter cp= has been introduced, whose value may be either a specific IP address or hostname. Which may than be used by the SQL agent to connect to an external CP in DB service mode.

UNIX Agent now may Execute FileEvent with User Specified in Login Object

As of version 11.1 the FileEvent object may be run by the UNIX agent with the user defined in a Login object, which is specified in the FileSytem tab of the FileEvent object. In order to be able to use this new function, in the system variable UC_HOSTCHAR_DEFAULT set the value for the key FE_VERSION to "2" (default).

New Object Type Storage

The new object type Storage  (short name: STORE) can be used to store binary data (entire files) centrally in the Automation Engine database.

Version 11 only prepares the infrastructure for this object type. In this release, you can neither create Storage objects manually in the UserInterface nor manipulate or display their binary data.

With this extension, the setting maxMsgSize= in the supplied Automation Engine's INI file (usrv.ini) has been set to 30 MB. The default value of 3 MB for this setting has not been changed. Automic recommends setting maxMsgSize= to 30 MB because this is the relevant limit for Storage objects.

VARA Objects: Limit for Values Removed

The limit of 1023 characters (data type: text) has been removed for the values of static and dynamic VARA objects.

It is still possible to define a maximum text limit (1 to 1024 characters) on the Attributes tab. However, this will only apply to the first value column (for both static and dynamic VARA objects).

VARA Objects (static) - Editor for the Contents of Value Columns

An Editor is available for the value columns of static VARA objects. To open the Editor, click the new pencil icon that is displayed at the right edge of each cell in which the text cursor is located.

VARA Objects (dynamic) - New Variable Object VARA.EXEC

A new dynamic Variable object is now available: VARA.EXEC. It is used to read out and save or transfer values from executable objects, which are either being executed or have been executed successfully.

VARA Objects (static) - New Variable Object VARA.XML

The new static Variable object XML may be used to store and transfer XML data. Thus even large XML data structures may be used throughout the Automation Engine system.
You also may use the VARA.XML as data reference in a PromptSet control and use AE variables there as attributes of the two keys "XPath" and "Key". Depending on the database the Automation Engine system is being used with, individual XPath expressions may work differently. In such cases please check with the database's vendor.

New Include Objects for External Interpreter Scripts

The two new Include objects (REGISTER_VARIABLE.WINDOWS and REGISTER_VARIABLE.UNIX) should be used to define external interpreters and their scripts.

New Login Object Field in File System Event Object

A new definition has been created for the File-System Event object EVNT.FILE in order to enable the integration of Login objects. Therefore, an additional control has been added to the File-System Event object's Attributes tab as a new field.

New Login Object Field in File System Event Object for IFS (Integrated File System, OS/400)

A new definition has been created for the File-System Event object EVNT.FILE in order to enable the integration of Login objects. Therefore, an additional control has been added to the File-System Event object's Attributes tab as a new field. This new login field is now also available on the integrated file system.

User Object has New Privileges

The User object has new privileges: They enable Windows, z/OS, and UNIX agents to run file events by using specific credentials in order to check access restricted files and directories.

New Job object type - Generic

The new Job object type Generic is now available where the agent the job shall run on may be defined in two ways: Through the Variables&Prompts tab of that object and the Script variables &OVERWRITE_AGENT# or &AGENT# respectively, or by using PromptSet elements. The agent may be any platform agent except the Rapid Automation agent.

Object Variables - Maximum Size Removed

The values of object variables are no longer restricted. Furthermore, an Editor is now available on the Variables & Prompts tab for editing the values of object variables. The Editor allows you to edit contents in a clear and easy manner.

Script Variables: Limits have been removed

The maximum size of script variables (1024 characters) has been removed. There are no limits anymore for the values of script variables.

JCL lines are no longer limited. Note that the limit for regular script lines (1024) still applies.

New System Variable to Register External Interpreters

The new system variables UC_EXT_INTERPRETERS_WINDOWS and UC_EXT_INTERPRETERS_UNIX are now available on Windows and UNIX to specify external interpreters, which then may be used in the Process tab of a Job object (JOBS, on Windows and UNIX). You replace the asterisk with the respective short version of the OS, as explained in the documentation topic.

Limit Access to System Client Objects - New System-Wide Setting

To limit the access to objects of the System client from other clients (e.g via context menu on object names in script tab) a new system setting was introduced in the System variable UC_SYSTEM_SETTINGS called OBJECT_ACCESS_CLIENT_ZERO=. With this setting you may determine, if users in other clients of the system have permission to objects of the system client.

Action "Export Authentication Package" Restricted

The action "Export Authentication Package" has been restricted to users in the System client 0. Additionally a user needs the "W" permission for the Agent object to be able to export an authentication package.

PromptSets - Text Fields

The limit for the text fields of PromptSets (maximum 950 characters) has been removed. Text fields are now unlimited.

SQL Variables - Trailing Spaces

The Automation Engine does not truncate trailing space characters from the end SQL variable values as it did in previous releases.

Script Function GET_OH_IDNR - Available Parameters Restricted

The script function GET_OH_IDNR has been changed and will have one parameter available instead of two. Trying to use more than one parameter will result in an error message.

Script Element MODIFY_TASK Extended by Parameter VALUE

The Script function MODIFY_TASK has been extended by the new parameter VALUE. With this new parameter you may modify or create values of Object Variables or of PromptSet controls.

Script Function SEND_MAIL Extended

The Script function SEND_MAIL has been extended with two new optional parameters: The parameter Agent allows to specify the agent to be used for the sending of a message.
The Login parameter lets you set a Login object, which has to be defined for file access to files you want to send as attachments, for example.
Settings in the new optional key SEND_MAIL_DEFAULT will override individual SEND_MAIL script settings anywhere throughout the respective client.

Changes in Windows HEADER/TRAILER in Client 0 for Powershell Integration

Changes in Windows HEADER/TRAILER in Client 0 allow users integrate the Powershell scripts with Automation Engine. This means that users can check for exceptions in script and have the possibility to return from processing so that Automation Engine update the return code set by user. An example is shown in Windows BAT and Powershell Examples.

Powershell Set as Default Interpreter for Windows Jobs

Windows Powershell is entered by default as the interpreter using the parameters ECPEXE= and EXPEXT= in the affected Windows agent's INI file([GLOBAL] section).

"Access to selective statistics" Privilege Required to Get Statistics of an Object via JavaAPI

Starting with v11.1, getting statistics of an object via the JavaAPI requires the user privilege "Access to selective statistics".

The Function "Deactivation Delay" is now Available for Additional Objects for Automatic Deactivation

This function has been added for the executable objects Group, Notification, Script and Event. In addition the Automation Engine variable UC_CLIENT_SETTINGS now provides the key "DEACTIVATION_DELAY_TIME".

Default Value "-c" Changed for UNIX Job object

As of v11, selecting a self-defined external interpreter (set in UC_SHELL_UNIX) from the drop-down list in the UNIX tab of a UNIX Job object will leave the options empty, if you do not enter a value in the options field.

XML Import File Size Extended

The allowed file size for the import of XML files is now 30720 KB (30 MB).

Dependent PromptSet Controls Introduced

Now it is possible to activate dependencies for controls in the Designer tab of a PromptSet object. Dependencies for the following elements may be set: Text, Combo box, Checkbox and Checklist.

Job Object z/OS (JOBS) - Interface Updated - JCL Job Card Replacement Changed

For the Job object on z/OS the UserInterface has been updated. In the Host Attributes Tab the section "Type" now contains the option "Automation Engine (AE)" as a radio button, instead of the previously used "UC4".
The second option of this section, "z/OS JCL" works now as follows: The Automation Engine system will insert the job card defined in this Job object, whether the JCL contains a job card or not.

New Job Status Capturing and Tracking Function for OS/400 Jobs

In order to be able to take immediate action, the possibility to query job statuses of OS/400 jobs has been added. Using SQL statements you may not only display a list of jobs that are in the MSGW (=waiting for messages) status, which might require additional actions. You also may get detailed information about the execution and status of the jobs in question.

SAP BW: Data for Chain Steps Published as Script Variables

In SAP jobs with BW chains, the agent creates several script variables for each child process. These variables and their values are available automatically in the (child) post process tab, and appear in the Detail Window of the tasks. For the list of variables and their values at the Chain, Step, and Step Job levels, see SAP BW: Data for Chain Steps Published as Script Variables.

Previous release included the E_TYPE_TEXT and E_VARIANT_TEXT script variables, which are now renamed to &@sap_bw_type_text and &@sap_bw_variant_text.

Notification Object - Notification Tab: Character Limit in Text Field Removed

Previously the number of characters in the text field of the Notification tab of the Notification object was limited to 8000.
This limit has been removed, the number of characters you may use there is now unlimited.