Components involved in workload service assurance
- Planner
- The planner component is triggered
by the JnextPlan command. It includes a series of actions that
result in the creation of the Symphony file on
the master domain manager.
When workload service assurance is enabled, the planner calculates job streams and job networks, taking into consideration all "follows" dependencies in the new plan.
The planner then identifies all the jobs and job streams that are part of a critical network. These are jobs that are direct or indirect predecessors of a critical job. For each job, a critical start time is created and added to the Symphony file. It represents the latest time at which the job can start without putting the critical job deadline at risk. The plan information is then replicated in the database.
The Symphony file is subsequently distributed to all agents.
- Plan monitor
- The plan monitor component is introduced with the workload service assurance feature. It runs in the WebSphere Application Server Liberty
Base on the master domain manager and is
responsible for keeping track of the job streams and job network and for updating it when changes to
the plan occur either because of the normal running of jobs or because of manual operations.
The plan monitor holds the information that is required to monitor the progress of the jobs involved in a critical network, for example critical start, planned start, estimated start, and risk level. It changes these values in response to changes in the plan, identified by the batchman process running on the master domain manager and communicated to the plan monitor using the server.msg file.
The information maintained by the plan monitor can be viewed on the Dynamic Workload Console in specialized views for critical jobs, allowing you easily to identify real and potential problems.
- Agent processes (batchman and jobman)
- Jobs in the critical network that
are approaching the critical start time and have not started are promoted.
The time at which the job is considered to be approaching its critical
start time is determined by the global options setting promotionOffset.
The batchman process monitors the critical start time to determine if promotion is required and if so to schedule it at the highest job priority available in IBM Workload Scheduler. The batchman process also communicates with the jobman process, which is responsible for promoting the job at operating system level so that it receives more system resources when it starts. The operating system promotion is controlled by the local options settings jm promoted nice (UNIX™) and jm promoted priority (Windows™).