Terminology
The following terms are used to describe components related to the Batch Scheduling Facility:
|
Name |
Page |
Description |
|
Batch Definition |
Batch Definitions |
How a Batch is written. The Batch Definition is edited from the Batch Definitions editor which contains components that define the Batch. Once created, you can manage the Batch from the Batch Definitions page. |
|
Batch Component |
Batch Registry editor |
When a Batch Definition is created, it consists of a Batch component, which can contain other components, such as ServiceCommand components, Conditional components, and other Batch Components. The Batch Definitions editor lets you add, remove, and edit Batch components and other components it contains. |
|
Batch Entry |
Batch Schedule |
When a Batch Definition has been instantiated by being scheduled on the Batch Schedule page, a Batch Entry is created. The Batch Entry either runs immediately, or waits to run, depending on what scheduling components are added to the Batch Definition. |
|
Batch Execution |
Batch Admin |
When a Batch Entry runs, it creates a Batch Execution, which does whatever was defined in the Batch Definition. For example, if a Batch Definition uses the ServiceCommand to start ten Service Sessions, the Batch Execution does that. The Batch Execution is managed on the Batch Admin page. Any actual Service Sessions created can be managed on the Grid Components > Services > Service Session Admin page. |
|
Service Runner |
Service Runners |
Service Runners enable you to define a registered Service Type with options and init data that can be used in a Batch Definition. |