Orchestration Monitor overview

The Orchestration Monitor gives you granular control over your plan, enabling you to take direct action over every item in your plan.

The Orchestration Monitor is a Dynamic Workload Console section that functions like a control hub that oversees all of your workload associated with a specific engine. From there, you can monitor:
  • Workstation
  • Job stream
  • Job
  • Resource
  • Prompt
  • File
Queries
You can use queries to search for specific items, and from there you can take direct control by performing manually a range of actions, depending on which item you have queried. Queries can also be saved and shared with other users or groups, to speed up your monitoring operations.
Tree view
A tree view is available to let you monitor your workload through the folders that contain the items in your plan. The tree view is updated in real time, so that you can always be aware of the folder system that contains the items you are monitoring.
You can configure the tree view to display items from both the current folder and all nested subfdirectories:
  1. From the Monitor & Reporting menu, select Orchestration Monitor.
  2. Click the Tree view configuration icon located at the bottom-left of the panel.
  3. Switch the Include subfolders toggle to On.
  4. Click Save.
Dependencies
Using the Dependencies action, you can monitor all the dependencies of job or a job stream displayed in a graphical way through a tile system. You can manually take action on the dependencies, releasing them or editing them for the job and job streams in your plan.
Operator instructions

When monitoring jobs and job streams, operators can access the Operator instructions panel from the More actions menu to retrieve definition information from the Description and Documentation fields. The availability of this information within the Orchestration Monitor facilitates rapid comprehension of job or job stream parameters during monitoring activities.

The Operator instructions panel displays definition information based on the selected item. For a job stream, the panel presents the content of the Description and Documentation fields from the job stream definition. For a job, the panel displays three sections:
Job stream
Displays the Description and Documentation fields of the job stream to which the selected job instance belongs.
Job instance
Displays the Description and Documentation fields of the selected job instance.
Job definition
Displays the Description field of the job definition referenced by the selected job instance.
Job stream description column
From the Table configuration menu, you can add the Description column to your results table. The Description column provides immediate operational context for job streams. By surfacing this information directly in the monitoring view, you can access relevant details without opening the job stream definition or the Operator Instructions panel.

The description field can store any meaningful identifier, such as:

  • Alternative names: Intuitive or descriptive titles that complement formal naming conventions.
  • Project metadata: References to specific business units or project affiliations.
  • System mapping: Identifiers from legacy environments or external systems.
While the results table displays information in plain text, you can view the full Markdown formatting from the dedicated panel by clicking over the Description field of the selected job stream.
Note: The column displays the description as it existed when the job stream entered the plan. If the description in the job stream definition is updated after plan entry, the new values are visible only in the Operator Instructions panel.
Querying and filtering
The Description column is fully searchable via Orchestration Query Language. Using OQL to filter by description simplifies and accelerates the search process, especially in environments with a high volume of objects.
For example, consider a job stream with the following troubleshooting details in the Description field:
First step: Check error code. For "503" and "500" errors, contact: serversupport@ittech.com
For any other error, contact: softwaresupport@ittech.com

To quickly identify the correct support contact during monitoring, use the following OQL syntax to filter for specific error codes:

description LIKE '@503@'
Workflow details
Using the Workflow details panel, you can monitor information about plug-in jobs and list the operations that you have performed on the whole job or on one or more files in the job.

For z/OS users: To monitor your plug-in jobs from a Dynamic Workload Console different from the console where the job was defined, ensure that you stored the plug-in job' s jar file into the <DWC_home>/usr/servers/dwcServer/resources/lib/zconn/applicationJobPlugIn folder.

Monitor certificate expiration
The certificate expiration date for workstations is visible in the results table when querying for workstations. You can make the certificate expiration column visible from the Table configuration menu.
Update agent certificates
You can remotely update the certificates on dynamic agent workstations running version 10.2.6 or later by selecting Update agent certificates from the Actions menu. The selected dynamic agent contacts the primary domain manager to directly download new certificates from the master domain manager <data_dir>/ssl/depot folder, replacing its existing ones.

You can verify the success of the agent certificate update process by checking the Certificate expiration column.

For more information on how to use the Orchestration Monitor, see this Orchestration Monitor scenario

For details about how to add a z/OS engine to the list of discovered engines that are available from the Orchestration Monitor, see Mirroring the z/OS current plan to enable the Orchestration Monitor.