This document guides you through the new installation of a PeopleSoft agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host.
Process scheduling in PeopleSoft is executed via PeopleTools components. The PeopleSoft agent can be implemented for all versionsAn application version holds zero or more deployment packages and may have dependencies to zero or more application versions of the same (or to different) applications of PeopleTools supported by AE. See:Requirements for Operating AE.
The following guide describes how to install an agent in an AE system in which authentication is not used. Additional installation steps are required before the agent can be started and used if you intend to use one of the available authentication methods. More detailed information is provided in the document Advanced Security.
Automic strongly recommends installing the agent in a separate directory (such as C:\AUTOMIC\AGENTS\PEOPLESOFT).
The additional requirements listed below must be fulfilled so that PeopleTools Process Scheduler Batch server processThe core of the component Automation Engine. Different types are available: communication, work and dialog processes, as well as nonstop processes. logs can be added to the AE databaseA database is an organized collection of data including relevant data structures.:
These are the requirements for using AE's Interface:
The directory IMAGE:AGENTS\PEOPLESOFT\WINDOWS. contains the files listed below:
File name |
Description |
---|---|
UCXJPSX.EXE |
AE agent for PeopleSoft |
UCXJPSX2.DLL | Runtime library for PeopleTools Version 8.1x (AE interface) |
UCXJPSX3.DLL | Runtime library for PeopleTools Version 8.1x (AE interface, Java API) |
UCXJPSX4.DLL |
Runtime library for PeopleTools Version 8.1x (Standard Interface, Java API) |
UCXJPSX5.DLL |
Runtime library for PeopleTools Version 8.4x (Standard Interface, Java API) |
UCXJPSX6.DLL |
Runtime library for PeopleTools Version 8.4x (AE interface, Java API) |
UCXJPSX.INI |
INI file for the PeopleSoft agent |
UC.MSL | Message library |
ZUSYNCHK.DLL | Runtime library for syntax checks |
ZU00132.DLL |
Runtime libraries for shared functions |
UCXJPS82.jar |
Java classes |
SETUP.EXE |
Installation program |
The other files from this subdirectory are part of the installation program. The files of the AE Interface and how they are implemented is described in a separate document.
Component Interfaces (Java classes) can be used for connecting the agent to PeopleSoft/PeopleTools.
Accesses for jobAn Automation Engine object type for a process that runs on a target system. processing are made via the Java Classes of the supplied UC4_* componentA component is a single deployable application artifact. As an example, this can be yourfile.war to be deployed into a Tomcat container. Each component has different properties which determine where to get it from, how to configure it, etc. You will need one component per application artifact: e.g., one for the application tier and one for the database backend. interfaces.
Accesses for job processing are made via the Java Classes of the PROCESSREQUEST component interface.
Check |
Step |
Optional |
---|---|---|
|
Installing the Microsoft Visual C++ 2010 Redistributable Package |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |