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.

Tip! This page refers only to the manual installation process. If you want instructions on how to install a containerized Java agent, see Installing Containerized Java Agents.

This page includes the following:

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.

Supplied Files

The files are stored in the directory IMAGE:AGENTS\PEOPLESOFT\_TRANS. It is not required to change or adjust the enclosed project files before they are imported.

Folder: PT8.53

Description: Directory that contains the project files of the AE interface for PeopleTools 8.53 and higher.

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:

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 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.

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.

Integrating PeopleTools processes into AE job Processing

  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: