Installing Containerized Agents

This section guides you through the installation of containerized agents. This means that you can run a Windows, UNIX, or Java Agent in a container by building and running a Docker image hosting one of these Agents. These agents can be used either for an on-premises Automic Automation system or an Automic Automation Kubernetes Edition environment.

Tip! This section contains information relevant for agents installed in a container. If you are searching for information relevant to the manual installation of on-premises agents, see Installing the Agents Manually.

The Broadcom Software Academy provides examples on how to deploy an Automic Automation Java, Windows or UNIX agent in a container. To access this additional information please select the relevant link:

• Build and run a container hosting a Java based agent

• Build and run a container hosting a UNIX agent

• Build and run a container hosting a Windows based agent

Connecting to the Automation Engine

The Automation Engine and the Windows, UNIX, and Java Agents communicate using TLS/SSL. These agents establish a connection with the Java communication process (JCP), which uses trusted certificates to prove their identity to other communication partners.

Important! Make sure you are familiar with the TLS/SSL and certificate implementation before installing and/or upgrading the respective component. For more information, see:

• TLS/SSL Considerations for Automic Automation

• Securing Connections to the AE (TLS/SSL)

When you used certificates signed by a CA, the certificates are stored in the respective Java or OS store by default; that is the Java trust store for Java components and Java Agents, the Windows OS store for Windows Agents, or the TLS/SSL store for UNIX Agents. In this case, you only have to check that the root certificates already are in the respective store.

If the relevant certificates are not there and you want to import them, you can use OS or Java specific tools for that purpose, such as Keytool, cert-manager, OpenSSL and such. For more information on how to use those tools, please refer to the respective product documentation.

If you do not want to use the default locations for the components and Agents listed above, make sure you use the trustedCertFolder=, agentSecurityFolder=, and keyPassword= parameters (if applicable) in the respective configuration (INI) file to define the path to the folder where the trusted certificates are stored.

Note: The TLS/SSL implementation does not apply to the HP-UX Agent, as it is no longer supported as of version 21.0.

Important! TLS/SSL Agents (in containers and on-premises) as well as the TLS Gateway, when used for the Automic Automation Kubernetes Edition, establish a connection to an ingress / HTTPS load balancer, which requires a certificate for authentication.

Make sure that address of the load balancer is defined on both sides: the Automation Engine and the Agent / TLS Gateway and that your HTTPS load balancer has the required certificates in place. For more information, see Connecting to AWI, the JCP and REST Processes Using an Ingress.

Check the compatibility matrix to see which version is compatible with your system. For more information, see Compatibility Information.

This section includes the following pages: