JS7 JobScheduler

Space shortcuts

Page tree

Versions Compared

Old Version 32

changes.mady.by.user Andreas Püschel

Saved on

compared with

New Version 33

changes.mady.by.user Andreas Püschel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Initial Operation is performed after installation of the JS7 Controller, Agent and the JOC Cockpit.

Operation Use of a Controller Cluster is subject to the agreements of the JS7 - License.

...

A Controller Cluster implements high-availability for automated fail-over should a server node operating the Controller instance become unavailable.

A Controller Cluster requires an arbitrator to act as Cluster Watch. This role can be assigned JOC Cockpit or an Agent.

Controller Registration using JOC Cockpit as Cluster Watch

Image Added


Controller Registration using a Cluster Watch Agent


This dialog allows the Primary Controller instance, the Secondary Controller instance and an Agent Cluster Watcher Watch to be specified.

Explanation

  • Title: The title added for each Controller instance is displayed in the JS7 - Dashboard view.
  • URL for JOC Cockpit: Primary and Secondary Controller instances are accessed from the JOC Cockpit using this URL.
    • The URL includes the protocol, hostname and port that the relevant Controller instance is operated with.
    • By default the HTTP protocol is used. The HTTPS protocol can be used if TLS/SSL certificates are in place, see the JS7 - Controller HTTPS Connections article.
  • URL for Secondary / URL for Primary: The Primary Controller establishes a connection to the Secondary Controller and vice versa.
    • Input to this field is not required if the URL for a Controller instance is the same across the network.
    • Input to this field is required should Proxy Services be involved that make use of specific URLs.
  • Cluster Watcher: An Watch: Either JOC Cockpit or an Agent is required for operation of a Controller Cluster. The Agent is
    • If JOC Cockpit is assigned the Cluster Watch role then JOC Cockpit will contact both Controller Cluster members.
    • If an Agent is used then it will be contacted by both Controller Cluster members to verify the cluster status
    should a direct connection between Controller Cluster members not be available
    • .
      • Agent ID: The Agent is assigned a unique identifier. Uniqueness is applied for all Agents registered with the same Controller. The Agent ID cannot be modified during the lifetime of an Agent. Changes to the Agent ID require the Agent to be removed and re-added with JOC Cockpit.
      • Agent Name: The name of an Agent is used for example when assigning the Agent to jobs. Similarly to the Agent ID the Agent Name has to be unique but can be changed later on.
      • Agent URL: The protocol HTTP or HTTPS, host name or IP address and port by which the Agent is accessible to the Controller.

Note: The following connections should be accessible and might require additional firewall rules to allow access to the relevant ports:

  • JOC Cockpit connection
    • to the Primary Controller's host and port.
    • to the Secondary Controller's host and port.
  • Primary Controller connection
    • to the Secondary Controller's host and port.
    • to the Cluster Watcher and any additional Agent's host and port.
  • Secondary Controller connection
    • to the Primary Controller's host and port.
    • to the Cluster Watcher and any additional Agent's host and port.

For more information about network connections see JS7 - System Architecture.

...