Page History

...

• Jobs and Job Chains can be executed by Agents. 
• Agents can be operated in a an Agent Cluster:
  
  • Fixed Priority Scheduling
    • JobScheduler Master selects the first available Agent from a cluster for job execution.
    • Should an Agent not be available then the next available Agent is used.

    • Jira
      server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1554

  • Round-Robin Scheduling
    • JobScheduler Master switches the Agent used for each job execution.
    • Should an Agent not be available then the next available Agent is used.

    • Jira
      server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1188

• Example configuration files are provided for downloading.

...

• The process class is assigned a Primary Agent and a Fallback Agent

  • Code Block
    language xml title Process Class configuration for Fixed Priority Scheduling collapse true
    <process_class> <remote_schedulers select="first"> <remote_scheduler remote_scheduler="http://agent1:4445"/> <remote_scheduler remote_scheduler="http://agent2:4445"/> </remote_schedulers> </process_class>

• All jobs are executed by the Primary Agent.
• Only If the Primary Agent becomes inavailable unavailable then the Fallback Agent will become active.
• If later on the Primary Agent becomes available then subsequent jobs will be executed on that Agent.

Note that:

• Fixed Priority Scheduling requires that the select parameter is set to first as shown in the code block above.
• If the select parameter is not set then fixed priority scheduling will be carried out by default.

Example

• Download fixed_priority_scheduling_agent.zip
  • Extract the archive to your live folder, a directory fixed_priority_scheduling_agent will be created.
• The process class - 01_ProcessClass_Fixed_Priority_Scheduling_Agent - has been configured for two Agents: adjust these values to point to your Agent installations.

...

• The process class is assigned a two Agents that are use interchangeably.

  • Code Block
    language xml title Process Class configuration for Round-Robin Scheduling collapse true
    <process_class> <remote_schedulers select="next"> <remote_scheduler remote_scheduler="http://agent1:4445"/> <remote_scheduler remote_scheduler="http://agent2:4445"/> </remote_schedulers> </process_class>

• Jobs are executed interchangeably on each Agent.
• If one Agent becomes inavailable unavailable then the jobs will be executed on the remaining Agent.

Note that:

• Round-Robin Scheduling requires that the select parameter is set to next as shown in the code block above.
• If the select parameter is not set then fixed priority scheduling will be carried out by default.

Example

• Download round_robin_scheduling_agent.zip
  • Extract the archive to your live folder, a directory fixed_priority_scheduling_agent will be created.
• The process class - 01_ProcessClass_Round_Robin_Scheduling_Agent - has been configured for two Agents: adjust these values to point to your Agent installations.

...