New PeopleSoft Extension agent is failing.
search cancel

New PeopleSoft Extension agent is failing.

book

Article ID: 89873

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

New PeopleSoft Extension agent is failing.

Environment

Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent
Component:

Resolution

Detailed Description and Symptoms

The test environment is PeopleTools version 8.53. 
I followed the process I typically do (according to the PSE manual from Automic) and all the steps were successful, but the agent will not start, and I receive this error: 

bea.jolt.SessionException: TPEPERM - bad permissions 
at bea.jolt.JoltSession.decodeLOGON(JoltSession.java:785) 
at bea.jolt.JoltSession.logon(JoltSession.java:268) 
at bea.jolt.JoltSession.(JoltSession.java:125) 



Solution

We are using Java 7u1 and PeopleTools 8.5.3. 
PeopleSoft admin made the following change:As we suspected earlier the issue was with the "DomainConnectionPwd" parameter, it looks like Applications Manager doesn't provide a way of passing this password through its connection parameters to the app servers.The old tools had this set to a default two character password which Applications Manager seemed happy with but the new tools release doesn't let us have a password which is less than 8 characters in length which Applications Manager doesn't like.
The new PeopleTools version is ok with getting rid of the password or if that domain password is required for some other services in PeopleSoft, like app messaging, you may also create a new PeopleSoft app server domain specifically for Applications Manager. 

If you create a new PeopleSoft app server domain, change the agent definition to use the Jolt port for the new domain with no password.