Page History
...
Users might choose to convert a Standalone Controller to a Controller Cluster:
- the The Controller Cluster provides high availability,
- Use of the Controller Cluster is subject to the JS7 - License. Both JOC Cockpit and Controller instance instances require a license key being present:
...
For details see JS7 - Controller - Command Line Operation.
Operating the Cluster Watch
A Controller Cluster requires the role of a Cluster Watch to be present, see JS7 - Controller Cluster.
This role can be taken either by JOC Cockpit or from an Agent.
Starting the Cluster Watch Agent
Users choose an existing Standalone Agent or Primary Director Agent in a JS7 - Agent Cluster to act as a cluster watch for the Controller Cluster.
...
- Users should modify the Controller Type to Cluster.
- For the Primary Controller instance users should enter the URL of the current Standalone Controller that is intended to act as the active Controller instance in a cluster.
- For the Secondary Controller instance users should enter the URL of the standby Controller instance.For the Cluster Watch Agent the respective URL has to be added.
...
- The Test Connection buttons can be used to verify if JOC Cockpit can establish a connection to both Controller instances.
- For the Cluster Watch Role either JOC Cockpit or an Agent is specified, see next chapters.
Configuring JOC Cockpit a Cluster Watch
The Cluster Watch role for JOC Cockpit can be configured from a radio button like this:
Configuring an Agent as Cluster Watch
The Cluster Watch role can be assigned an Agent from a radio button like this:
Operating the Controller Cluster
...
Overview
Content Tools