Automation Engine Interface

AE offers efficient component interfaces for integrating PeopleTools processes into AE job processing. The component interfaces work independently of the PeopleTools Database in use. It also offers an extended range of functions, such as script elements (see JCL for PeopleSoft ). The collection of all UC4_* Component Interfaces is called AE interface.

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.

Requirements

The following requirements must be met in order to use the AE interface:

• PeopleTools Application Designer
• Authorization to import projects into the PeopleTools Database
• Authorization to set access authorizations in PeopleSoft.

1. On the host computer, import the project to the PeopleTools database.

   1. Import the project files that correspond to your version of PeopleTools.

   2. Start the Application Designer from PeopleTools in the "2 Tier Mode" (with direct connection to database).

   3. Copy the project from the AE CD using the command File->Copy Project from File (8.2x) or Tools->Copy Project->From File... (8.4x)  in Application Designer. Select the appropriate IMAGE:AGENTS\PEOPLESOFT\_TRANS\PTx directory. Click OK.

   4. Load all project data into the PeopleTools database. Select all object types and click Copy.

2. Test the component interfaces.

   The component interfaces are displayed by double-clicking the folder Component Interface. Select a component interface and use Tools->Test Component Interface. If you follow this process, you should avoid errors.

3. Set access authorization.

   When the project is imported (such as PT8.4/UC4_V1_02), a permission list called UC4_ALL is loaded. Assign the permission list to those Operator IDs by whom jobs should be started and to the Operator ID for the startup of the AE agent (see ERP LOGIN).

4. Activate the component interface.

   The component interface is activated through an entry in the INI file of the PeopleSoft agent. For more information, see Agent PeopleSoft.

See also:

• Installing the Agents Manually
• Installing the Agent for PeopleSoft (Windows)
• PeopleSoft Agent - Installation Process (Windows)
• Automation Engine INI file
• Agent PeopleSoft INI file