Cisco Cisco Workload Automation 6.3 User Guide
9
Cisco Systems, Inc.
www.cisco.com
2
Configuring the PeopleSoft Adapter
Overview
To run and monitor a PeopleSoft job from CWA, you must create a CWA job definition for it. The job or processes may
already exist within PeopleSoft.
already exist within PeopleSoft.
CWA then controls the PeopleSoft job in the CWA environment, first making sure that all of the job’s dependencies have
been met. Once the job clears CWA’s queues, it queues a request in the PeopleSoft process request tables.
been met. Once the job clears CWA’s queues, it queues a request in the PeopleSoft process request tables.
The PeopleSoft Process Scheduler runs the requested process and CWA monitors its progress. Operators can control
the job and, when the job is complete, view the job output from the CWA
the job and, when the job is complete, view the job output from the CWA
Job Activity
pane.
The PeopleSoft Adapter software is installed as part of a standard installation of CWA.
However, before the PeopleSoft Adapter can be used, the following configuration procedures must be completed:
—
—
—
All of these procedures are described in this chapter.
See
for information about general and adapter-specific properties that can be set to
control things like logging and connection properties.
Configuring the Adapter
Note:
For the Windows master, ensure that the CWA master service logs on as a specific user account. The master
should not log on as a local system.
To configure the PeopleSoft adapter:
1.
Create a security policy to assign to the users that will schedule PeopleSoft jobs. You may want to create different
security policies to differentiate between users who just run PeopleSoft jobs versus users who can run and edit
PeopleSoft jobs. You could also just add the security functions to the existing policies for each user as needed. Refer
security policies to differentiate between users who just run PeopleSoft jobs versus users who can run and edit
PeopleSoft jobs. You could also just add the security functions to the existing policies for each user as needed. Refer