Administration Guide > Installation > New Installation > Installing the Agent for PeopleSoft (UNIX) - Basics

Installing the Agent for People Soft (UNIX) - Basics

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 uses components of PeopleTools. The PeopleSoft agent can be implemented for all PeopleTools 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 that are 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 UC4/Agent/peoplesoft).

Requirements

Supplied Files

The agent files are supplied in compressed form (UCXJPSX.tar.gz) and are found in the IMAGE:AGENTS\PEOPLESOFT\UNIX subdirectories. The names of the subdirectories indicate the supported UNIX platforms in accordance with the Terminology:

File Name Description
UCXJPSX AE agent for PeopleSoft

UCXJPSX.INI

INI file for the PeopleSoft agent
UCX.msl Message library

psexj.bin

Syntax file

UCXJPS82.jar
UCXJPS84.jar

Java Classes

libsysapi, libzu00132, libzusynchk, libgcc_s, libstdc++, libucxjpsx3, libucxjpsx4, libucxjpsx5, libucxjpsx6

AE runtimeThe duration of a task's execution. It refers to the period between a task's start and end. It does not include its activation period (see also: activation and start). system for the PeopleSoft agent

File ending with "a" indicates AIX
File ending with "sl" indicates HP-UX
File ending with "so" indicates Solaris

 


Technical Implementation

Component Interfaces (Java classes) can be used to connect the agent to PeopleSoft/PeopleTools.

1) People Tools with AE Interface (Java Classes)

Job processing is accessed via Java Classes of the 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.

2) People Tools with Standard Interface (Java Classes)

Job processing is accessed via Java Classes of the PROCESSREQUEST component interface.

 


Startup

If a UNIX agent is already installed on the system, its userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. ID can be used for startup.

Steps for Starting Up

Check

Step

Optional

Installing the AE Interface

 

Transferring the Agent's tar file to the Host and unpacking it

 

Adjusting the Agent's configuration file

 

Creating start script

 

Using ERP Forms

Shortening the interval for task checking in PeopleSoft

 

Editing ERP Login

 

Defining operator IDs in AE

 

Testing the PeopleSoft connection

 

Functional test

 

Entering the Agent's start script for system start

 

Configuration for using Bind Variables

Configuration for using the RemoteTaskManager

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH