User Guide > Objects > Alphabetical Listing > Creating Jobs - Basics

 Creating Jobs - Basics

Job-type objects are probably the most used object types. They can be used for executing commands on computers or in Enterprise Business Solutions (SAP, PeopleSoft, Oracle Applications, and Siebel). Individual Job objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task templatesPre-defined 'workflows' for specific components/tasks, e.g. Tomcat, SubVersion. are available for each of these platforms because they all differ from each other. Therefore, the first step when you create a jobAn Automation Engine object type for a process that runs on a target system. is to decide upon the operating system or business solution on which it will actually run.

Procedure

  1. Click the  button in the toolbar. A window opens and lists all the available object types including the objects for the individual platforms. Select one of them.
  2. Assign an appropriate name for the Job object and open it. Click the Notification tab
  3. Agents are actually executing the job. Select the particular agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host in the Host tab which runs on your computer or is connected to the business solution on which the commands should be processed.
  4. The agent requires loginAn Automation Engine object type that stores account credentials used by agents on target systems. information for the execution of the job. This information is stored in Login objects. Select the required one in "Login".
  5. The various Job objects have their individual Host tabs, each depending on the platform. The settings that are available for job reports are what they have in common. Select where the job reportA report provides more detailed information about a task's execution or a component. should be stored. The particulars applying to the individual operating systems or Enterprise Business Solutions are described in the document Creating Jobs - Details.
  6. The settings in the Runtime tab can be used for monitoring the job while it is being executed.
  7. The following tabs are available in Job objects and can be used for storing the processing statements:
  8. The order of the Process tabs listed above represents the order in which they are processed. A detailed overview is found in the document Stages of Workflow execution. You can also control the generation time of the Pre-Process and Process tabs with the option Generate at runtimeThe duration of a task's execution. It refers to the period between a task's start and end. It does not include its activation period (see also: activation and start). which is available in the Notification tab. Activating of this option causes the two tabs not to be generated at object activation but rather when it is started. job activation and generation can take place at different points in time - when the object is executed in a workflowAn object of the Automation Engine that can include several executable objects and which runs them in a specified order. [Formerly called "ProcessFlow" and "JobPlan."], for example.

More settings can be specified in Job objects. Detailed descriptions are available in the documents of the particular tabs.

 

See also:

Creating Jobs - Details

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH