Unable to kickoff jobs using PeopleSoft plugins

[Sandeep Veetil]

We have Autosys 11.3.6 SP0 in our environment. We are using Autosys agent 11.4 on the PeopleSoft server and in the process of moving the jobs from PS adapters to PS plugins.

While trying to kickoff jobs from PS Adapters, we are able to successfully launch the job and completes. However, while trying to kickoff jobs using PS plugins, we are receiving an error in PeopleSoft. I am attaching the PS adapter jobs, PS plugin job and other relevant files for your reference.

=========================================

bash-3.2$ autoflags -a

1643 LINUX ANY 11.3.6 SP8 110a4c42 el06psply01 el06psply01

=========================================

bash-3.2$ ./cybAgent -v

CA Workload Automation Agent for:

   Linux x86_64 64-bit

   11.4, Service Pack 01, Maintenance Level 0, Build 1933

Enabled plug-in(s):

   - runner

   - router

   - filemon

   - objmon

   - filebrowser

   - ftp

   - ps

Enabled Advanced Integration(s):

Built at: Jul 13 2018, 11:47:19

=========================================

------------------------------
Sandeep Veetil
Application Administrator
------------------------------

Attachment(s)

agentparm.txt   5 KB 1 version

Autosys_Code.txt   1 KB 1 version

PS_Message_Log_Adapter.txt   2 KB 1 version

PS_Message_Log_Plugins.txt   2 KB 1 version

[Chandrasekaran Venkataraman]

Sandeep, 
database names are different between the PS adaptor and the plugin; FSPLYIC Vs FSPLY. Maybe you are testing against different databases?

Plugin log shows the following error:

Error in sign on
Database Type: 7 (ORACLE)
Database Name: FSPLY
Server Name: -CD
OperID: PSPROC
ConnectID: people
Process Instance: 0
Reason: Could not sign on to database FSPLY with user PSPROC.

Check the agentparm.txt for the following parameters and ensure they are the correct:

• ps.default.oprId

  Sets the default operator ID under whose authority the PeopleSoft reports run. The agent plug-in validates this operator ID against the corresponding value in the PeopleSoft database. The ps.default.oprPassword parameter specifies the password that is related to this ID. You can specify an operator ID in a job definition to override the default value.

  Example: VP1
• ps.default.oprPassword
  Sets the encrypted password for the default operator ID specified in the ps.default.oprId parameter.
  Example: 6343B940CFCBC53E

Thanks,
Chandru Venkataraman