Dynamic job scheduling scenarios
This section describes the dynamic job scheduling scenarios.
- Setting up your environment for dynamic scheduling
- Applying an order of preference to possible targets
In this scenario, you create a job that uses logical resources to apply an order of preference to a group of eligible target computers on which a job can run. - Performing load balancing based on available free memory
In this scenario, an optimization policy is defined to balance the distribution of a set of jobs between resources based on total physical memory available on each resource. - Specifying software license requirements by using resources
In this scenario, a job requires two software licenses to run. Using logical resources to represent license availability, a company ensures compliance to license requirements. - Dynamic job scheduling - A procedure to optimize writing job definitions that simulate the use of templates
This scenario shows how you can set up JSDL job definition templates that you can reuse for several job definitions. In this way you can optimize the number of steps required to submit jobs to dynamic workload broker. Taking this concept a little further, you can set up a different JSDL template for every class of job that you want to submit. For background information, see Using JSDL job definition templates in Scheduling workload dynamically. - Scheduling jobs dynamically on SAP R/3 systems - A high availability scenario
This scenario shows how to achieve high availability when scheduling critical jobs dynamically on SAP R/3 systems. Tivoli® Workload Scheduler for Applications users can take advantage of the dynamic scheduling capabilities of HCL Workload Automation version 8.5.1 by defining a group of two or more HCL Workload Automation agents, configured to schedule on a given SAP R/3 system, as completely interchangeable. If an agent is unavailable to schedule on the SAP R/3 system, another agent in the group is dynamically selected. - Defining and scheduling new and classic jobs with dynamic capabilities
This scenario describes how you can use the new workstations with dynamic capabilities to run the jobs you created for the previous HCL Workload Automation workstations. To run these jobs on the new workstations, you must change only the workstation where you want the job to run. You can also define new job types. While the classic HCL Workload Automation job is a generic script or command, you can now define specific job types, such as database or Java™ jobs. To create this type of jobs, you do not need specific skills on the applications where the job runs.