Installing the Agent for Rapid Automation
Rapid Automation (RA) refers to a generic technology that includes and processes various agent solutions in conjunction with the Automation Engine. RA Agents make the functions of a RA solution accessible.
As of version 21.0, 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.
Note: The TLS/SSL implementation does not apply to the HP-UX Agent, as it is no longer supported in this version.
You can use the trustedCertFolder=, agentSecurityFolder=, and keyPassword= parameters in the respective INI file to point to the relevant certificates. If the trustedCertFolder= parameter is not set, the certificates should be installed in the respective store; that is the Java trust store for Java Agents, the Windows OS store for Windows Agents, or the TLS/SSL store for UNIX Agents. For more information, see Securing Connections to the AE (TLS/SSL).
For more information about the different certificate types and for detailed instructions on how to create and use them, see What Kind of Certificates Should I Use for Automic Automation v21.
TLS/SSL Agents and the TLS Gateway, when used for the Automic Automation Kubernetes Edition, establish a connection to an ingress / HTTPS load balancer and not the JCP directly. The ingress / HTTPS load balancer must be reachable and requires a certificate for authentication. The address of the load balancer must be defined on both sides: the Automation Engine and the Agent / TLS Gateway.
Important! When you install or upgrade Agents manually for an Automic Automation Kubernetes Edition system, you have to make sure that you configure your Agents and/or TLS Gateway to reach the TCP or HTTPS load balancer and not the CP or JCP directly. Also, make sure that your HTTPS load balancer has the required certificates in place. For more information, see Connecting to the AAKE Cluster.
All RA Agent solutions use common technology, so the install procedure for each of them is similar. However, there are specific requirements and installation steps for each Agent solution. Furthermore, there are often different requirements and installation steps for different versions of the same Agent solution, which are supported for various Automation Engine releases.
The installation instructions for each Agent are included in a stand-alone RA Agent documentation.
There are several Rapid Automation solutions available, including the following:
- RA Banner Agent
- RA Business Objects Agent
- RA FTP Agent
- RA Hadoop Agent
- RA Hyperion EPMA Agent
- RA Hyperion ESSBASE Agent
- RA Hyperion FDMEE Agent
- RA Hyperion FM Agent
- RA Hyperion Planning Agent
- RA Informatica Agent
- RA JD Edwards Agent
- RA JMS Agent
- RA Oracle E-Business Suite Agent
- RA Oracle Retail Agent
- RA Web Service REST Agent
- RA Web Service SOAP Agent
You can also access the RA Agent documentation from https://docs.automic.com/documentation.
See also: