Page History
...
Converting the Standalone Controller
Starting the
...
Primary Controller Instance
The Standalone Controller automatically becomes the active Primary Controller instance in a cluster. This change of role does not require the Standalone Controller being restarted.
For successful execution of the subsequent steps the Controller instance has to be started.
Preparing the
...
Secondary Controller Instance
Users have to prepare the standby Secondary Controller instance to its role:
Users should specify the standby role from the Controller instance's
controller.conf
file:Code Block title controller.conf file for Standby Secondary Controller Instance # Cluster configuration js7.journal.cluster { node { is-backup = yes } }
For details see JS7 - Controller Configuration Items
- Users should remove an existing journal of the standby Secondary Controller instance. More precisely users should remove the contents of the standby Secondary Controller instance's
state
folder.
Starting the
...
Secondary Controller Instance
In a next step the standby Secondary Controller instance is started like this:
Code Block | ||
---|---|---|
| ||
# starting the Standby Controller instance for Unix from the command line ./controller_instance.sh start # starting the Standby Controller instance for Unix from systemd sudo systemctl start controller.service |
Code Block | ||
---|---|---|
| ||
@rem starting the Standby Controller instance for Windows from the command line .\controller_instance.cmd start @rem starting the Standby Controller instance Windows Service from the command line .\controller_instance.cmd start-service @rem alternatively the Standby Controller instance can be started from the Windows Service Panel |
...
The radio buttons Standalone and Cluster determine the Controller type.
- Users should modify the Controller type 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.
...