- The Individual Sub-Views
- Agent Clusters
- Agent Jobs Executed
- Process Classes
- Job Documentation
The Resources View provides access to JobScheduler objects that are not directly bound to specific Jobs, Job Chains or Orders. These are Agent Clusters, Events, Locks, Process Classes, Schedules, Calendars and Job Documentation.
Only users whose accounts have the necessary Permissions will be able to access and configure individual Resources sub-views.
See the JOC Cockpit - Authentication and Authorization articles for more information about Permissions.
The Individual Sub-Views
Agent Clusters are one or more JobScheduler Agents that are accessed by a common Process Class. The Process Class defines the address or addresses - i.e. the URIs - of the individual Agents as well as the maximum number of tasks that the Cluster may execute at any one time.
Process Classes are also JobScheduler resources and are shown in the JOC Cockpit Resources / Process Classes view (see below). Each Process Class specifying one or more Universal Agents is considered as a separate Agent Cluster. Conversely, Process Classes not including agent address information are not considered as Agent Clusters.
This means that:
- a group of Universal Agents specified in only one Process Class will be listed as one Agent Cluster, and
- a single Universal Agent operating "stand-alone" but listed in three Process Classes will be listed as three Agent Clusters.
The next screenshot shows the Resources / Agent Clusters view with three Agent Clusters on a common host and two of the Universal Agents offline. The information presented in this view is purely informational (i.e. non-interactive) and is updated in near real-time.
Permissions for viewing both Agent Clusters and for viewing Process Classes are required to view the Resources / Agent Clusters view in the JOC Cockpit.
See the JobScheduler Universal Agent - Agent Cluster article for more detailed information about Agent Clusters.
Agent Jobs Executed
Agent Jobs Executed view shows the sum of all the tasks executed on Agents controlled by the Masters reporting to the JOC Cockpit.
This information is automatically collected by the JOC Cockpit and is relevant to holders of commercial subscription licenses. A convenient Export in XLS format function is available with the button at the top right of the view.
This information also allow the number of tasks executed with different Agent URLs to be monitored, and could be used as part of a simple accounting system.
JobScheduler Event handling is a mechanism for implementing complex dependencies between jobs or between jobs and external events.
The Resources / Events view allows Events to be created and managed and shows the events. It shows all Event Objects that are listed in the Reporting Database - i.e. for all JobScheduler Masters - and which have not yet expired.
The information shown in this table is automatically updated by the
./sos/events/event_processor Order, which runs every 5 minutes and when a new Event is created or deleted.
A comprehensive Add Event function is available as shown in the next screenshot:
Note that changes to events - i.e. addition and deletion - carried out in the Events view take place asynchronously - there is a short delay before feedback is obtained that changes have been implemented.
Locks limit the number of jobs that access the same resources, e.g. databases, in parallel.
Locks allow mutual exclusive access, i.e. jobs wait without any consumption of CPU for a lock to be released.
Values shown in the Max. Non-Exclusive column are configured and static.
Values in the Number of Lock Holders and Number Opened columns are dynamic and reflect the current situation in near real-time.
See the Locks article for more detailed information about Locks.
Process classes limit the number of jobs that are running concurrently.
Process classes specify remote JobScheduler Workload instances and Agents on which jobs should be executed.
displays information about the Agent Cluster that a Job or Job Chain is to be executed on (if any) and the maximum number of processes that a task may use as well as the location - i.e. the Path - of the Process Class object in the JobScheduler Master's
Note that theincludes those Process Classes that do not include a Host parameter for specifying an Agent Cluster.
The screenshot above shows one Process Class - agent_cluster. This view is purely informational, i.e. non-interactive, and the Number of Processes column shows the current number of processes being executed for each Process Class in near real-time.
In addition, when a process class is being executed, detailed information is dynamically added to the table - the Agent, Job, Process and Task IDs and Running Since columns shown in the screenshot.
See the Process Classes article for more detailed information about Process Classes.
JS-1754 - Schedules are replaced by Calendars Deprecated for more information.
Schedules are run-time configurations that can be used to define the start times of jobs and orders.
- Schedules can include:
- a run-time configuration and
- a replacement configuration that allows one schedule to be replaced by a different schedule during a certain period.
- Schedules can therefore be used to:
- add reusable run-times to jobs and orders that can be centrally managed.
- implement Maintenance Window Management.
- edited, with edited changes being partially persistent;
- substituted with alternative Schedules, with the substitution also being partially persistent.
See the JOC Cockpit Run-time Editor article for more information about the persistence of changes to Schedules made with the JOC Cockpit.
Substituting and Run-times
Schedules and Run-times are mutually exclusive.
Substituting and modifying Schedules
Schedules can be substituted in the JOC Cockpit by:
- Selecting the Schedule or Schedules to be substituted from the Schedules tab list view and then opening the Substitute modal window by clicking the Substitute button at the top right of the view.
- This will open a list of all the schedules in the live folder of the JobScheduler Master as shown in the next screenshot.
- Note that Calendars and Frequencies can be specified for the substitution as can be seen in the screenshot, allowing complex repeating patterns if required.
Object Level Schedule Substitution
Schedules, like all JobScheduler objects, are saved as files within the JobScheduler Master's live folder. Scheduler substitutions can also be configured at this level, either using JOE - JobScheduler Object Editor or by editing the substitute schedule object file using a text editor. The JOC Cockpit can take account of substitution at this level. The following screenshot shows a folder in the Schedules view with three schedules:
- Schedule2_late has have been configured to substitute Schedule2 - for the day shown.
Each of these Schedules can be further substituted as described above.
See the Schedules article for more detailed information about Schedules.
FEATURE AVAILABILITY STARTING FROM RELEASE 1.12
Calendars specify the days on which Jobs and Orders are to be executed on and provide more sophisticated configuration than is possible with Schedules.
See the Calendar Management article for more detailed information about Calendars and their configuration and management.
The Job documentation feature allows job developers to write their own documentation in a number of formats and to import this information to the scheduling environment. Once imported, the documentation can be assigned - i.e. linked - to Jobs and other JobScheduler objects such as Job Chains, Process Classes and Locks. Developers can not only integrate documentation describing how jobs and other objects are to be configured but also documentation describing how objects are used in a scheduling environment.
FEATURE AVAILABILITY STARTING FROM RELEASE 1.12.8
See the Job Documentation article for more detailed information.