Best practices for configuring Peoplesoft Agent
search cancel

Best practices for configuring Peoplesoft Agent


Article ID: 268441


Updated On:


CA Automic Applications Manager (AM)


This article was written to cover some best practices when configuring Applications Manager Peoplesoft Agent with Peoplesoft and Peoplesoft server.


Release : 9.4.x


Peoplesoft User and Connect ID/User ID/Access ID relationship

The Applications Manager documentation covers the Peoplesoft Agent configuration process, and references the creation or use of a PeopleSoft User that exists or is created on the Peoplesoft end.

This may cause some confusion as Peoplesoft has a number of User access types such as Connect ID, User ID, and Access ID. 

However, the Peoplesoft User that is referenced by the documentation simply refers to a normal User that is created like any other User and have no relationship to Connect ID/User ID/Access ID

App Domain and password

A common error seen when testing the Peoplesoft Agent connection to Peoplesoft is "DOWNbea.jolt.ServiceException: Invalid Session". When this occurs, the Peoplesoft User may become blocked or locked on the Peoplesoft end.

If this occurs, this is likely related to the App Domain and password.

The Peoplesoft App domain that Applications Manager connects to CAN NOT have a domain password. If the app domain contains a password, then the Peoplesoft Agent will not be able to connect to Peoplesoft. 

If the current App Server that the Peoplesoft Agent is trying to connect to requires a domain passwordk, it is required to CREATE A SEPERATE APP DOMAIN specifically for Applications Manager to use. The below directory listing should look familiar to your Peoplesoft team:

hrdv -- ps-hrdv-app01 > ls
apwx01  debug  hrdv01  hrdvmsg  prcs

In the above example, "apwx01" is an app domain specifically created for the Peoplesoft Agent.

The psappsrv.cfg for apwx01 should have a blank password as seen in the example below:

; Security settings
Validate Signon with Database=0
; Enable/Disable Login Audit
; Y - Enable Login Audit (Default)
; N - Disable Login Audit
Enable Login Audit=Y

Jolt Port

The Jolt port(s) need to be opened in the firewall for both incoming and outgoing communication.

Even though only one Jolt port is defined in Applications Manager in the Peoplesoft psappsrv.cfg file, the integration uses a port range which is defined by the number of "handlers" parameter in the psappsrv.cfg file.

Below is a psappsrv.cfg example of the Jolt port 9300 being used with 7 max handlers resulting in a port range of 9300 to 9306, which has to be opened incoming/outgoing communication.

[JOLT Listener]
; Settings for JOLT Listener
SSL Port=9010
JSL Min Encryption=0
JSL Max Encryption=256
Min Handlers=5
Max Handlers=7
Max Clients per Handler=40
Client Cleanup Timeout=10
Init Timeout=5
Client Connection Mode=ANY
Jolt Compression Threshold=1000000