You use the job object (JOBS) when you want to execute processing steps in a target system. Jobs can run independently or be added to a group (JOBG) or to a workflow. They can execute commands on computers or in enterprise business solutions (SAP, PeopleSoft, Siebel, Oracle Applications, etc.). As these solutions differ from each other, templates for each are available.
Object class: Executable object
Object type/Short form: JOBS
Default Object Templates/Subtypes: Templates for specific platforms. You can customize them or create your own ones.
General Information on Job Processing
The JCL of a job object is stored in its Process definition page. Its logic can be very complex if you make use of the Automation Engine script language.
Depending on the JCL and on the script elements, an agent-specific executable job is generated and transmitted to the target system via a file transfer.
The list below tries to depict a possible road-map to define and work with Job objects and provides short descriptions of the actions you can take, additional information that can help you understand how they work and links to topics that further describe them:
Define the job general settings, which include the following:
- The basics, on the General Page.
- If required, apply a Sync object to the job; You do so on the Sync Page.
- On the Runtime Page specify the job runtime settings.
- Fine-tune access rights at object level on the Authorization Page.
- Specify the object Attributes on the Attributes Pages of Executable Objects.
- Register the output files that will be produced when processing them on the Output Page.
- To be able to carry out searches in those output files and, if required, perform follow-up actions, specify these settings on the Output-Scan Page.
- You may want to use variables or prompts. You do so on the Variables & Prompts Pages.
- You may want to define the settings to backup and restore a job task when included in a workflow. This is useful to recover the last successful status in case of failed processes. You do this on the Rollback Page.
- The Version Management Page lists all the versions of an object and allows you to restore it to an older version in case of a misconfiguration.
- Enter information on the job you are defining on the Documentation Page.
Job objects (JOBS) have three pages on which you enter the scripts to be processed. They provide a number of convenience functions to help you with your work. If you enter scripts on all of them, they are processed in the following order:
- You can easily reuse code using Include Object (JOBI), which saves time and helps you keep your scripts consistent.
Execute the job.
There are multiple ways to do this that can be grouped as follows:
By a parent task.
This is the case of jobs that are included in a parent object (for example a Workflow or a Group). When defining them, take into account that their activation time can be different from their start time; the latter usually depends on the parent object.
This is the case when the job is not part of a parent object or, even if it is, you execute it independently of its parent. You have three possibilities:
When executable objects are processed, they go through the following four stages: 1. Activation, 2. Generation, 3. Processing and 4. Completion. Take a look at these topics to understand what happens with every processing stage.
When processing jobs, the Automation Engine generates output files and reports that guarantee traceability and auditability. Have a look at the following topics to learn more about this:
- In the Process Monitoring perspective a number of functions are available, depending on the status of the job. See Working with Tasks.