1.2 Job components
A job represents a unit where a set of actions and action flow are executed depending on schedules or execution conditions. You can start operations by registering jobs. The following table describes job components.
|
No. |
Type |
Description |
|---|---|---|
|
1 |
Job |
A job consists of a group of configuration components which link business operations that you want to perform (What) to triggers by which such operations are performed (When). Depending on when executions take place, jobs are classified into the following two types: jobs executed on time, and jobs executed on event. You can schedule job executions by registering jobs each with a unique name (called a job name) in the job execution service. Specify the job name within 45 bytes. However, if multibyte characters are used, specify it within 15 characters. |
|
2 |
Item |
Job components are collectively referred to as items. There are seven types of items shown as Nos. 3 to 9 in this table. An item can be used by multiple jobs. Editing an item changes the execution settings of all the jobs executed on time that are registered and use the item. For a job executed on event, you need to register it again. Furthermore, users who design business operations (designers), such as individuals from the information systems division, can create custom items, which allow them to design highly sophisticated business operations. Users executing business operations (operators) can use the created custom items. |
|
3 |
Action |
An action defines a command executed in a job or a minimum execution unit on CPA, such as send mail. You can specify the file name of the command to be executed, a parameter to be specified for the command, or other settings. Different types of items are available depending on how actions are executed. |
|
4 |
Event monitor |
An event monitor defines the conditions for detecting event occurrence. Different types of items are available depending on what is being monitored (file monitor, mail reception, and so on). |
|
5 |
Action flow |
An action flow consolidates actions, event monitors, and action flows, and specifies the order in which items are executed. An action flow can be created and edited as an item, and it can be called from other action flows. |
|
6 |
Execution date |
An execution date determines the date when the job executed on time runs. You can specify a repeat pattern such as every day or every Monday. |
|
7 |
Execution time |
An execution time determines the time when the job executed on time runs. You can specify a repeat pattern such as every hour. |
|
8 |
Calendar |
A calendar refers to a date type used to determine job execution dates. There are two types of calendars: open day and closed day. You can define schedules with which jobs are executed only on weekdays by setting weekends and national holidays as closed days. You can also define operation time periods for calendars. No schedule is calculated for hours outside the operation time period. A calendar can be created and edited as an item. Different calendars can be registered for each job. |
|
9 |
Execution condition |
An execution condition defines conditions with which job execution is triggered by events. Execution conditions are used with event monitors. Once you register a job, CPA keeps monitoring event occurrence for the job. |
|
10 |
Unit |
A unit is a general term used to describe actions, event monitors, and action flows that are defined in an action flow. Ensure that every unit has a unit name that is unique in an action flow to enable the unit to be identified uniquely. |