PeopleSoft Jobs

For understandability purposes, we use the following two terms on this page:

• PeopleSoft Jobs are the Automic Automation Jobs that automate PeopleSoft processes on a target PeopleSoft system.

• Native PeopleSoft jobs are the jobs that run on that PeopleSoft target system.

PeopleSoft Jobs replicate native PeopleSoft jobs in Automic Automation and start and monitor processes in the PeopleSoft target system. The native PeopleSoft jobs usually contain statements that start multiple processes in the PeopleSoft target system (sub jobs). Automic Automation reproduces this job structure; the PeopleSoft Job is the parent of those sub jobs (they are child processes) and serves as their container. To reproduce the job structure of native PeopleSoft jobs, PeopleSoft Jobs have an additional Child Post Process page where you can enter your script. This script is processed for each individual child process immediately after it has finished.

When you execute the PeopleSoft Job in the AWI, its children start and are 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 more information about the integration between the Automation Engine and PeopleSoft, see AE and PeopleSoft.

This page includes the following:

1. In the Process Assembly perspective click Add Object. On the Add Object dialog, select one of the PeopleSoft templates. For information on how to add objects, see Adding Objects.

   A PeopleSoft object definition is made up 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

       PeopleSoft Process pages have an additional Forms view, see Forms View on the Process Page Also, PeopleSoft Jobs have an extra Child Post Process page. You build the logic of the child processes on this page.

     • Attributes Page
     • Registering External Output Files
     • Variables Page
     • Prompt Sets Page
     • Rollback Page
   • The PeopleSoft page described here.

   Note: You can also create PeopleSoft Jobs directly from the Using AWI Combo Boxes that serve to select objects.

2. On the Object Name dialog enter the name of the new object. Choose it carefully. For more information, see Best Practices: Naming Conventions.

3. Click OK to open the object definition pages.

4. 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.

5. For information on the Job Report section, see Job Reports

Building the PeopleSoft Job Logic Using PeopleSoft Commands

PeopleSoft Job templates contain sets of predefined commands. A command is a group of PeopleSoft -specific strings or functions. You build the logic of an PeopleSoft Job on its Process page by adding commands to it. The PeopleSoft Process pages contain an additional view called Forms, an intuitive and user-friendly way of depicting the values in a particular command. The Form view of a command can contain dropdown lists, input fields, radio buttons, and so on. For more information, see Process Pages and 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

Restarting PS Jobs from Automic Automation

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