What's New in 21.0.10

This section provides information about the new features and enhancements that have been implemented in Automic Automation 21.0.10.

This page includes the following:

Agents

This section outlines the new Agent features and functions implemented in this Automic Automation version:

Java-Based Windows and Linux (x64) Agents

Automic Automation v24 kicked-off an OS agent refresh initiative to have all OS agents use a common Java-based framework. This means that we are able to provide a consistent user experience where common functionality is implemented in the same way across all of our most used agents, such as TLS/SSL support or Secure outbound email support (SMTPS).

The first release included new agents for x64 Linux and Windows, which are now also available in v21.0.10. Other OS agents will be released with future updates.

These Java-based x64 Linux and Windows Agents are included additionally to the existing OS Unix and Windows Agents x32, x64, and x86, respectively.

Note: These Agents require a JRE on every machine in which an Agent is running; therefore you have to make sure JRE is available. They require Java version 11 or higher and will not work with Java 1.8.

Fore more information, see:

CAU Packages for x64 Linux and Windows Agents

This version of Automic Automation includes two different CAU packs for the x64 Linux and Windows Agents: one OS native and one Java-based. The respective pack name distinguishes them clearly.

If you want to keep using an OS native x64 Linux or Windows Agent after an upgrade, do not download and install the CAU pack for the corresponding x64 Java-based version; otherwise you would convert your OS native Agent to a Java-based one.

The same applies when downloading Agents from the Process Assembly or the Administration perspective in AWI.

For more information, see:

Sending Secure Emails via Agents

As of this version, you can use the new Java-based x64 Linux and Windows Agents to send secure emails using SMTPS.

Please note that using TLS to secure the STMP connection requires a certificate that must be available in the UC_TRUSTEDCERTS Storage object in Client 0.

For more information, see Setting up Secure Emails.

Job Execution Limits for Linux (x64) Agents

This new version of the x64 Linux agent also allows you to set job execution limits for users using the pam_limit.so library.

Note: You only require the pam_limit.so library, you do not need to install and configure PAM.

For more information, see Setting Job Execution Limits for Users.

Agent Connection Status in Service Manager

You can start the new x64 Windows and Linux Java-based Agents using the Service Manager and use the -svc%port% parameter to have the ServiceManager display the connection status of the Agent along with its name.

For more information, see:

Security Enhancement

Security was enhanced by limiting the access permissions for the files needed during the execution of a Job object, such as a shell script, report, or resource, to the user specified in the Login object. Ensure that this user has read/write permission for the Agent's temp folder. For details, see Granting Automation Engine Authorizations

INI Files: New trustedCertFolderOnly Parameter

The [AUTHORIZATION] section of the INI files for all Java Agents (including the Cloud Integrations), the Proxy, the TLS Gateway and the AE Application Interface have a new trustedCertFolderOnly parameter, which enables you to pin JCP certificates.

When set, the system expects the JCP certificates to be in the trustedCertFolder. The certificate validation uses only the content of that folder and ignores other trust stores.

When it is not set (default), the certificate validation uses other OS and Java trust stores as well as the trustedCertFolder.

For more information, see Configuration (INI) Files.

Automic Web Interface

This version includes the following new features and enhancements in AWI:

New Optional Connection Parameter in uc4config.xml

In some setups the AWI cannot reach the REST JCP(s). This is the case when the REST JCP(s) are behind a Load Balancer that the AWI cannot reach, or if the AWI and the AE are on different nets, and so on.

As of this version, a new parameter in the uc4config.xml configuration file lets you specify the REST endpoint. For more information, see uc4config.xml - Configuring the Connection Between AWI and AE.

Agent Integrations

The cloud Agents listed in this section have been extended or implemented recently and can be integrated with this Automic Automation version.

Avaloq
Azure Logic Apps
AWS Step Functions
S3

For more information, see Cloud Integrations.