Page History

...

• To run a job on a remote JobScheduler Workload instance or Agent for remote execution
  • Process classes can reference remote JobScheduler instances for execution of a job:
    • At the time of job execution the initiating JobScheduler hands over the job configuration to the remote JobScheduler instance.
    • After completion of the job the initiating JobScheduler regains full control and will continue execution e.g. with the next job in a job chain.
    • The connection to the remote JobScheduler instance makes use of TCP, i.e. the remote instance is configured by host:port.
• Example

  • Code Block
    language xml title Process class for Resource Contention ManagementRemote Execution with a Master collapse true
    <?xml version="1.0" encoding="ISO-8859-1"?> <process_class max_processes="10" remote_scheduler="somehost:4444"/>

...

• Process classes can be used as a means to implement high availability:

  • Display feature availability
    StartingFromRelease 1.8

  • A sequence of JobScheduler Agents can be specified that would be checked for availability by the initiating JobScheduler instance at run-time.
  • If a JobScheduler Agent were not avaiable then the next Agent would be selected for execution of a job.
  • The connection to an Agent makes use of the HTTP or HTTPS protocol; i.e. the remote instance is configured by http://host:port or https://host:port .
• Example

  • Code Block
    language xml title Process class for Resource Contention ManagementUse with Agents collapse true
    <?xml version="1.0" encoding="ISO-8859-1"?> <process_class max_processes="10"/> <remote_schedulers> <remote_scheduler remote_scheduler="http://Andreas-MacBook-Pro.local:4445" http_heartbeat_timeout="15" http_heartbeat_period="10"/> <remote_scheduler remote_scheduler="http://localhost:4445" http_heartbeat_timeout="15" http_heartbeat_period="10"/> </remote_schedulers> </process_class>

...