PeopleSoft Jobs

PeopleSoft Job objects start and monitor processes in the PeopleSoft target system. Jobs in a PeopleSoft system usually contain statements that start multiple processes (sub jobs). This job structure is replicated in the Automic Web Interface. The PeopleSoft Job you create in the Automation Engine is the parent of those sub Jobs (child processes) and serves as their container.

When you execute the PeopleSoft Job in the AWI, its children are started and displayed in the Tasks list (Process Monitoring perspective). Their object type is JOBD (dynamic job) and each child has its own unique RunID. In the Process Monitoring perspective you can check their status in the target system. You can also add comments, restart, cancel, edit them, and open the list of objects in which they are being used.

For details on the integration between the Automation Engine and PeopleSoft, see AE and PeopleSoft.

Prerequisites

The Automation Engine system is connected to PeopleSoft via the Agent. The Agent interprets and transforms the commands sent by the Client so that PeopleSoft understands them. To create Jobs in the Automic Web Interface and execute them in the PeopleSoft Client you need a Login (LOGIN) object. The Login object contains the necessary connection data and PeopleSoft credentials (user name and password). You assign the Login object to the Job on its Attributes Page.

PeopleSoft Commands

PeopleSoft Jobs in the Automation Engine are supplied with sets of predefined commands. A command is a group of PeopleSoft-specific strings or functions. You build the logic of a PeopleSoft Job on its Process page by adding commands to it. For more information, see Process Pages.

User-Friendly Scripting Using Forms

The script editor of the Process page in a PeopleSoft Job has two views. The usual one that is available for all Jobs, and the Form view. The Form view is an intuitive, user-friendly way of depicting the values you must enter for a particular command. The Form view of a command can contain dropdown lists, input fields, radio buttons, and so on. For more information, see Forms View on the Process Page.

Replicating Child Processes

Many PeopleSoft Jobs start multiple processes (sub jobs). These jobs have a parent/child structure in the PeopleSoft system that you can replicate in the Automic Web Interface. The commands of these Jobs contain two options that you must activate for this purpose:

• Replicate Children
• Process Ends with Error: Suspend

As a result, when the PeopleSoft Job is executed, it creates JOBD child tasks per started sub job. These tasks are displayed in the Tasks list in the Process Monitoring perspective.

Transferring Output Files to the Automation Engine

The PS_RUN_PROCESS and PS_RUN_JOB PeopleSoft commands create output files that you may want to store in the Automation Engine. To do so, activate the Register Outputfile(s) checkbox in the corresponding Form. As a result, the files generated by the execution of the job are transferred to the Automation Engine's database and are stored there as external reports.

To Download the Output Files

1. Open the Reports window.
2. From the Reports dropdown list, select Directory to display the list of available external reports.

3. Do one of the following:

   • Click the download icon
   • Right-click the report and select Partial Download

Downloaded reports can be displayed through Automation Engine external viewers

Tracking External Jobs via the Remote Task Manager

Use the Remote Task Manager (JOBQ) to monitor processes that have not been started by the Automation Engine through a PeopleSoft Job.

Prerequisites:

• The connection between the Automation Engine and the target PeopleSoft system is up and running.

• A Login object is available that provides the necessary PeopleSoft credentials (username and password). This Login object is specified in the APPLICATION_LOGIN key available in the UC_HOSTCHAR_DEFAULT static variable . Its default value is ERP_LOGIN. The UC_HOSTCHAR_DEFAULT static variable is supplied with client 0. For more information, see UC_HOSTCHAR_DEFAULT - Host Characteristics.

  Whenever the Remote Task Manager requests data, this Login object is used in the background.

 

Restarting PS Jobs from the Automation Engine

If a job fails (its status is ENDED_NOT_OK), instead of initiating a new process request, you can simply restart it from the Task list in the Process Monitoring perspective. For more information, see Monitoring and Restarting External Tasks.

Defining PeopleSoft Jobs

A PeopleSoft Job definition consists of the following pages:

• Standard pages that are always available, no matter what type of object you are defining:
  • General Page
  • Version Management Page
  • Documentation Page
• Additional pages that are always available for executable objects:

  • Process Pages

    Note: PeopleSoft Jobs have an extra Child Post Process page. You build the logic of the child processes on this page.

  • Attributes Page
  • Output Pages
  • Variables Page
  • Prompt Sets Page
  • Rollback Page

• The PeopleSoft page

  • In the Runtime Options section activate the Process Request: Delete after execution checkbox if you want the process request to be deleted in PeopleSoft after it has been executed
  • For information on the Job Report section, see Job Reports

See also:

• Jobs (JOBS)
• Functional Logic with Scripts
• Script Processing
• Monitoring and Restarting External Tasks