Page History

...

Controller Cluster Checks

Anchor
check_controller_id check_controller_id

Check Controller ID

Both Controller instances for a Cluster have to be installed with the same Controller ID, which is a unique identifier for the Controller Cluster.

...

• Stop the Controller service, see JS7 - Controller - Command Line Operation.
• Remove Controller journal files
  • The journal files have to be removed from the configuration directory with the state sub-folder. This means that any orders, which have been submitted for workflows will be removed and that workflows will have to be redeployed:
    • Unix: rm -f /var/sos-berlin.com/js7/controller/state/*
    • Windows: del C:\ProgramData\sos-berlin.com\js7\controller\state\*
  • Note that a different location for the configuration directory can be specified during installation.
• Modify the Controller ID
  • Unix: For headless installation as an exception to the rule the Controller ID is specified in the installation directory in the bin/environment_variables.sh file, see JS7 - Controller - Headless Installation on Linux/Windows.
    • Modify the following environment variable:
    • JS7_CONTROLLER_ID=<controller-id>
  • Windows: If the installer has been used (in headless mode or in graphical mode), then reinstall the Controller, see JS7 - Controller - Installation Using the Windows Graphical Installer.
• Restart the Controller instance.

Anchor
check_cluster_settings check_cluster_settings

Check Cluster Settings

The secondary Controller has to use the following configuration from its config/controller.conf file, see JS7 - Controller Configuration Items:

...

The steps required are summarized below, for details see JS7 - How to apply a JS7 License Key

Anchor
license_key_on_premises license_key_on_premises

Handling for Installation on premises

The following chapters can be skipped if a license key was added when using the Windows installer for the Controller. However, the steps described are required when a license key for an existing installation is to be added or replaced without updating the Controller.

...

• Binary code for clustering is available from the js7-license.jar file, which can be obtained from JS7 - Download.
• By downloading the binary code for clustering you consent with the license terms for a commercial license of JS7.
• The js7-license.jar file has to be stored to the following locations:
  • Unix: Controller Installation Directory with lib/user_lib sub-folders
    • Default Location: /opt/sos-berlin.com/js7/controller/lib/user_lib
    • A different location for the installation directory can be specified during installation.
  • Windows: Controller Installation Directory with lib\user_lib sub-folders
    • Default Location:C:\Program Files\sos-berlin.com\js7\controller\lib\user_lib
    • A different location for the installation directory can be specified during installation.

Anchor
license_key_docker license_key_docker

Handling for Docker® Installation

Basically the same locations for license key and licensed binary code apply as already explained for Unix operating systems in previous chapters.

...

You have a choice register of registering a Standalone Controller (within scope of the JS7 Open Source License) or a Controller Cluster for high availability (requires a JS7 Commercial License, see JS7 - Licensing).

Anchor
register_controller_cluster register_controller_cluster

Register Controller Cluster

A Controller Cluster implements high availability for automated fail-over should a Controller instance be aborted or killed or become unavailable.

...

• This dialog allows the Primary Controller instance, the Secondary Controller instance and an Agent Cluster Watcher to be specified.
• The title added for each Controller instance will be shown in the JS7 - Dashboard view.
• Primary and Secondary Controller instances require a URL as seen from JOC Cockpit. This URL is used by JOC Cockpit to connect to the relevant Controller instances.
• The URL of the Controller typically includes the hostname and port that the Controller instance is operated for.
• The Agent Cluster Watcher is required for operation of a Controller Cluster. The Agent is contacted by both Controller Cluster members to verify the cluster status should a direct connection between Controller Cluster members not be available.
  • The Agent is assigned an Agent ID which is a unique identifier for this Agent and cannot be modified during lifetime of an Agent. Change of the Agent ID requires the removal and re-addition of the Agent with JOC Cockpit. It is not necessary to uninstall/reinstall the Agent.
  • The Agent Name is a unique identifier that is used for example in the JOC Cockpit Configuration view to assign Agents to jobs. The Agent Name can be modified later on.
  • The Agent URL is the hostname and port for which the Agent is operated.
• Note that the following connections should be accessible and that this might require the addition of firewall rules to allow access to the ports:
  • JOC Cockpit connection to the Primary Controller host and port.
  • JOC Cockpit connection to the Secondary Controller host and port.
  • Primary Controller connection to the Secondary Controller host and port.
  • Secondary Controller connection to the Primary Controller host and port.
  • Primary Controller connection to the Cluster Watcher Agent host and port.
  • Secondary Controller connection to the Cluster Watcher Agent host and port.

Anchor
register_agents register_agents

Register Agents

After the connection between JOC Cockpit and the Controller is established you can add Agents. To register an Agent, switch to the Manage Controller/Agents view from the user menu. Click on the Action Menu of the Controller for which an Agent should be registered and select Add Agent.

Explanation: 

• The Agent is assigned an Agent ID which is a unique identifier for this Agent that cannot be modified during the lifetime of an Agent. Change of the Agent ID requires the removal of and re-addition of the Agent with the JOC Cockpit. It is not necessary to uninstall/reinstall the Agent.
• The Agent Name is a unique identifier that is used for example in the Configuration view to assign Agents to jobs. The Agent Name can be modified later on.
• In addition, you can add Agent Alias Names to make the same Agent available by different names.
• The Agent URL includes the protocol, the hostname and port for which the Agent is operated.

...