Administration Guide > Installation > Service Pack and Hotfix Installation > Installing the Agent for PeopleSoft (UNIX)

Installing the Agent for People Soft (UNIX)

This document describes the hotfix installation procedure for the 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 is executed in PeopleSoft by 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.

Requirements

Supplied Files

Agent files are packed in UCXJPSX.tar tar files, and can be found in the IMAGE:AGENTS\PEOPLESOFT\UNIX subdirectories. The names of the subdirectories indicate the respective UNIX platforms, as described in 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

 


Procedure

Transferring the tar file and setting up the system environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications.

 


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

Copyright © 2016 Automic Software GmbH