PeopleSoft plugin fails to start (WA Agent)

Products

• Workload Automation Agent
• CA Workload Automation AE - Business Agents (AutoSys)
• CA Workload Automation AE - System Agent (AutoSys)
• CA Workload Automation DE - Business Agents (dSeries)
• CA Workload Automation DE - System Agent (dSeries)

Issue/Introduction

The WA Agent will not start.  PeopleSoft plugin has been added.

Environment

CA Workload Automation Agent 12.x
CA Workload Automation Agent for PeopleSoft 12.x
OS - Any

Cause

The CA WA Agent log directory will have "peoplesoft.log".  It captures information about the PS plugin.
The following error from the peoplesoft.log indicates that PS plugin is unable to login to the database.
 

07/19/20xx 14:08:01.054-xxxx 4 main.MainThread.PsConfigProcessor.<init>[:161] - Created PsConfigProcessor
07/19/20xx 14:08:01.055-xxxx 4 main.MainThread.PsDbHandler.<init>[:xxx] - Initializing PsDbHandler
07/19/20xx 14:08:01.473-xxxx 0 main.MainThread.PsDbHandler.<init>[:xxx] - 
java.sql.SQLException: ORA-28000: the account is locked
                    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450)
                    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:392)
                    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:385)
                    at oracle.jdbc.driver.T4CTTIfun.processError(T4CTTIfun.java:1018)
                    at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthenticate.java:501)
                    ...................
07/19/20xx 14:08:01.479-xxxx 1 main.MainThread.CybPsPluginDriver.runApplication[:135] - cybermation.plugins.ps.PsConfigException: 
Failed to connect to PS DB using: jdbc:oracle:thin:@db.example.com:12345:ORADB

 

Resolution

Check the password that was used at the install.  Consult PeopleSoft Admin / DBA to get the account unlocked.
 

Additional Information

Note:  The CA WA Agent checks all the plugins at startup.  If PeopleSoft plugin has issues and cannot connect to the database, the Agent will not startup.  This is to prevent the jobs from failing and causing additional issues on the manager or scheduler side.