Scope

Master / Agent Redundancy

Master Cluster

Feature

• JobScheduler Master supports Cluster Operation with redundancy of the involved cluster members.
  • see Passive Cluster
  • see Active Cluster
  • see Master / Agent Cluster
• Clustering is frequently used for high-availability and in some cases for improved performance.

Agent Bundles

Feature

• The JobScheduler allows multiple Agents to be specified for a single Process Class.
  • The JobScheduler Master contacts Agents in round-robin mode (JS-1188): 
    • the first Agent that is configured to execute jobs for the process class will be contacted.
    • if the first Agent is not available then the next Agent listed in the process class configuration will be contacted
    • this procedure will be repeated until an Agent is found that can execute the job.
  • Use cases for this scenario include
    • all Agents running on different server nodes: the switch to the next available Agent implements a fail-over to the next server node.
    • a number of Agents running on the same server node: the switch to the next available Agent implements redundancy  of Agents within a single server node.
• Feature Availability
  • FEATURE AVAILABILITY STARTING FROM RELEASE 1.9

Delimitation

• This feature is not intended for load sharing as the JobScheduler will always use the first available Agent.
• This feature is not intended for scalability as it does not allow the execution of jobs in parallel on a number of Agents (clustering).

Change Management References