Page History

...

• The JobScheduler Master and Universal Agent do not require a TCP connection - as with the Classic Agent - see above - but use only a single connection (HTTP or HTTPS) to communicate.

• The Master does not need to send keep-alive packets to the Universal Agent as the Agent sends its own keep-alive packets in the form of HTTP Heartbeats.

• The HTTP Heartbeats are configured in <remote_scheduler> XML elements which are means that:

  •  The JobScheduler does not have to be restarted after a configuration change.

  • <remote_scheduler> XML elements are descendants of <process_class> elements which can be configured separately from jobs, job chains and orders and thereby reused.
  • Heartbeats can be configured within JOE.

• The following code block shows a typical configuration:

  Code Block
  language xml title The remote scheduler HTTP Heartbeat parameters
  <process_class max_processes="10"> <remote_schedulers> <remote_scheduler remote_scheduler="http://127.0.0.2:5000" http_heartbeat_period="10" http_heartbeat_timeout="15"/> </remote_schedulers> </process_class>

• The default HTTP heartbeat values are:
  • http_heartbeat_period: 10 seconds
  • http_heartbeat_timeout : 15 60 seconds
• See the <remote_scheduler> XML element reference article for more information.

...