Understanding PeopleSoft Master Scheduler
Managing PeopleSoft Master Scheduler
Servers
This chapter provides an overview of PeopleSoft Master Scheduler functions and discusses:
• Circumstances in which a Master Scheduler is required.
• How to use multiple Master Schedulers.
• Master Scheduler request prioritization.
• How to manage workload across servers.
Understanding PeopleSoft Master Scheduler Functions
A Master Scheduler enables load balancing of workload by automatically routing requests to available
Process Scheduler servers, which ensures that you maintain optimal processing at all times. This feature also offers fault tolerance in your batch environment. In the event of a server failure, a Master Scheduler can redistribute queued requests among the remaining active Process Scheduler servers. In addition, an active
Master Scheduler manages and controls all Process Scheduler server domains that are on the same PeopleSoft database. It enforces all of the rules that are specified in either the process or job definitions, and monitors the running of all processes. It becomes the centralized control as it checks the Process Request table looking for any queued requests to run, and then dispatches them to an appropriate available Process Scheduler server.
A Master Scheduler can be activated in any of the Process Scheduler servers in Microsoft Windows and
UNIX. This option is enabled by default when you are configuring a new Process Scheduler server in
Windows and UNIX. However, this option is not available in the IBM UNIX System Services (USS). For
DB2/OS390 customers who intend to start a Process Scheduler in USS and want to take advantage of this feature, a Process Scheduler server domain must be set up in either a Microsoft Windows or supported UNIX operating system other than USS.
Disadvantages of Using Multiple Process Schedulers with No Master Scheduler
When a Master Scheduler is not used, each Process Scheduler server that is brought up is responsible for managing its own
Servers
This chapter provides an overview of PeopleSoft Master Scheduler functions and discusses:
• Circumstances in which a Master Scheduler is required.
• How to use multiple Master Schedulers.
• Master Scheduler request prioritization.
• How to manage workload across servers.
Understanding PeopleSoft Master Scheduler Functions
A Master Scheduler enables load balancing of workload by automatically routing requests to available
Process Scheduler servers, which ensures that you maintain optimal processing at all times. This feature also offers fault tolerance in your batch environment. In the event of a server failure, a Master Scheduler can redistribute queued requests among the remaining active Process Scheduler servers. In addition, an active
Master Scheduler manages and controls all Process Scheduler server domains that are on the same PeopleSoft database. It enforces all of the rules that are specified in either the process or job definitions, and monitors the running of all processes. It becomes the centralized control as it checks the Process Request table looking for any queued requests to run, and then dispatches them to an appropriate available Process Scheduler server.
A Master Scheduler can be activated in any of the Process Scheduler servers in Microsoft Windows and
UNIX. This option is enabled by default when you are configuring a new Process Scheduler server in
Windows and UNIX. However, this option is not available in the IBM UNIX System Services (USS). For
DB2/OS390 customers who intend to start a Process Scheduler in USS and want to take advantage of this feature, a Process Scheduler server domain must be set up in either a Microsoft Windows or supported UNIX operating system other than USS.
Disadvantages of Using Multiple Process Schedulers with No Master Scheduler
When a Master Scheduler is not used, each Process Scheduler server that is brought up is responsible for managing its own