Administration Guide > Installation > New Installation > Installing the Agent for PeopleSoft (Windows) - Details

Installing the Agent for People Soft (Windows) - Details

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.


1.

Installing the Microsoft Visual C++ 2010 Redistributable Package

This installation step can be ignored if the packageA Package is an instance (a version, a revision, a tag, …) of your application and defines the content which you want to deploy. Here you decide, if you want to deploy the entire application or just a few specified components. is already available in the required version. Refer to the Control Panel -> Add or Remove Programs to see if and which version of the package is available.

2. Installing the Java Runtime Environment (JRE)

Note that PeopleTools Version 8.53 requires at least Java Version 1.7!

If JRE is already available in the required version, this step of the installation process can be ignored.

java -version

If several JRE or Java SDK Versions are installed on the computer, the order of the directories indicated in the settings of %PATH% or $PATH is relevant. The particular Java Runtime Environment that is first found in the listing of directories is applied.

3. Installing the AE Interface  

The AE interface installation process is described in a separate document.

AE's interface is required or use bind variables.

4.

Adjusting values in the field OUTDESTTYPE (PeopleSoft)  

Value Active Eff Dt Long Name Short Name
0 01.01.1899 Any Any
1 01.01.1899 (None) NONE
2 01.01.1899 File FILE
3 01.01.1899 Printer PRINTER
4 01.01.1899 Window WINDOW
5 01.01.1899 Email EMAIL
6 01.01.1899 Web WEB
7 01.01.1899 Default DEFAULT
5.

Installing the Agent and setting up the System Environment

The file psjoa.jar is stored in the folder "web" in the installation directory of PeopleSoft. If PeopleSoft is not installed on the same computer as the agent, releaseReleases combine a set of activities and a set of packages as well as other release artifacts under a timeline (a plan including milestones and phases), which can be planned, baselined and tracked. the folder "web" as share. The user under which the agent starts must have computer access rights.

The psjoa.jar file's content was changed as of People Soft version 8.54. Some Java classes are missing from it. They may be found in the People Soft 8.54 Internet Architecture installation in the following directory:

<PS_HOME>\webserv\peoplesoft\applications\peoplesoft\PORTAL.war\WEB-INF\classes

You have to add the psjoa.jar and the missing classes to the CLASSPATH of the following components:

  1. People Soft Agent (to enable jobAn Automation Engine object type for a process that runs on a target system. execution)
  2. UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."] (to order to be able to use FORMS, when defining People Soft Jobs).

Please use the ServiceManager to start the agent as a service.

6. Using ERP Forms(optional)

Example:

[ENVIRONMENT]
classpath=.;.\ucdj.jar.;.\psjoa.jar.;.\ucxjps84.jar

7.

Shortening the Interval for Task checking in PeopleSoft

We recommend shortening the interval for job checking. This required that a separate variable is created for the hostComputer, target system. characteristic and assigned to the installed agent.

8.

 

Editing ERP Login

The agent's start-up phase requires loginAn Automation Engine object type that stores account credentials used by agents on target systems. data for the PeopleSoft applicationAn application is a software which helps a user to fulfill specific tasks. In the context of ARA see also: Application entity. (operator ID, passwordA secret combination of characters for a Automation Engine user.). This information is stored in client 0000, Login objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task "ERP_LOGIN"

9.

Defining Operator IDs in AE

Operator IDs are required for the execution of tasks in PeopleSoft. AE must know the passwords for these user IDs. The operator ID and password is assigned in the Login object of the client used to execute tasks.

10.

Testing the PeopleSoft Connection

11.

Functional 

12.

Configuration for using Bind Variables (optional)

The following SQL script is required if you use PeopleSoft version 8.50 or 8.51:

INSERT INTO PS_PRCSTYPEDEFN
SELECT 'UC4_'||PRCSTYPE,
OPSYS,
DBTYPE,
VERSION,
PARMLIST,
CMDLINE,
WORKINGDIR,
OUTPUTDEST,
GENPRCSTYPE,
WINPARM,
MVSSHELLID,
AS4JOBDESCNAME,
AS4JOBDESCLIB,
'UC4_'||PRCSTYPEDESCR,
RESTARTENABLED,
SYSDATE,
'UC4'
FROM PS_PRCSTYPEDEFN;
0
COMMIT;

The following SQL script is required if you use PeopleSoft version 8.2x or 8.4x:

INSERT INTO PS_PRCSTYPEDEFN
SELECT 'UC4_'||PRCSTYPE,
OPSYS,
DBTYPE,
VERSION,
PARMLIST,
CMDLINE,
WORKINGDIR,
OUTPUTDEST,
GENPRCSTYPE,
WINPARM,
MVSSHELLID,
AS4JOBDESCNAME,
AS4JOBDESCLIB,
'UC4_'||PRCSTYPEDESCR,
RESTARTENABLED,
SYSDATE,
'UC4'
FROM PS_PRCSTYPEDEFN;

COMMIT;

Assign execution rights to the new process types:

INSERT INTO PS_SERVERCLASS
SELECT ORIG.SERVERNAME,
ORIG.OPSYS,
'UC4_'||ORIG.PRCSTYPE,
ORIG.PRCSPRIORITY,
ORIG.MAXCONCURRENT
FROM PS_SERVERCLASS ORIG
WHERE 0 =
(SELECT COUNT(*) FROM PS_SERVERCLASS SC
WHERE SC.SERVERNAME=ORIG.SERVERNAME
AND SC.OPSYS=ORIG.OPSYS
AND SC.PRCSTYPE='UC4_'||ORIG.PRCSTYPE )  
AND 0 <
(SELECT COUNT(*) FROM PS_PRCSTYPEDEFN PT
WHERE PT.PRCSTYPE='UC4_'||ORIG.PRCSTYPE
AND PT.OPSYS=ORIG.OPSYS );

COMMIT;

MS SQL Server:

The following SQL script is required if you use PeopleSoft version 8.50 or 8.51: 

INSERT INTO PS_PRCSTYPEDEFN
SELECT 'UC4_' + PRCSTYPE,
OPSYS,
DBTYPE,
VERSION,
PARMLIST,
CMDLINE,
WORKINGDIR,
OUTPUTDEST,
GENPRCSTYPE,
WINPARM,
MVSSHELLID,
AS4JOBDESCNAME,
AS4JOBDESCLIB,
LEFT('UC4_' + PRCSTYPEDESCR,30),
RESTARTENABLED,
GETDATE(),
'UC4',
0
FROM PS_PRCSTYPEDEFN; 

The following SQL script is required if you use PeopleSoft version 8.2x or 8.4x:

INSERT INTO PS_PRCSTYPEDEFN
SELECT 'UC4_' + PRCSTYPE,
OPSYS,
DBTYPE,
VERSION,
PARMLIST,
CMDLINE,
WORKINGDIR,
OUTPUTDEST,
GENPRCSTYPE,
WINPARM,
MVSSHELLID,
AS4JOBDESCNAME,
AS4JOBDESCLIB,
LEFT('UC4_' + PRCSTYPEDESCR,30),
RESTARTENABLED,
GETDATE(),
'UC4'
FROM PS_PRCSTYPEDEFN;

Assign execution rights to the new process types:

INSERT INTO PS_SERVERCLASS
SELECT ORIG.SERVERNAME,
ORIG.OPSYS,'UC4_' + ORIG.PRCSTYPE, ORIG.PRCSPRIORITY, ORIG.MAXCONCURRENT
FROM PS_SERVERCLASS ORIG WHERE 0 =
(SELECT COUNT(*) FROM PS_SERVERCLASS SC
WHERE SC.SERVERNAME=ORIG.SERVERNAME
AND SC.OPSYS=ORIG.OPSYS
AND SC.PRCSTYPE='UC4_' + ORIG.PRCSTYPE )  
AND 0 <
(SELECT COUNT(*) FROM PS_PRCSTYPEDEFN PT
WHERE PT.PRCSTYPE='UC4_' + ORIG.PRCSTYPE
AND PT.OPSYS=ORIG.OPSYS );

13.

Configuration for using the RemoteTaskManagerIt monitors and controls external Jobs that were not started by the Automation Engine (AE). An AE object type. [Formerly called "QueueManager."] (optional)

 


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

Copyright © 2016 Automic Software GmbH