Page History
...
Both Controller instances in a cluster have to be installed with the same Controller ID, which is a unique identifier for the Controller Cluster. Users can adjust the Controller Instance Start Script that holds the environment variable: JS7_CONTROLLER_ID=<controller-id>
- Unix: The Controller ID is specified with the
JS7_CONTROLLER_HOME/bin/controller_instance.sh
Instance Start Script, see JS7 - Controller - Headless Installation on Linux/Windows. - Windows: The Controller ID is specified with the
JS7_CONTROLLER_HOME\bin\controller_instance.cmd
Instance Start Script, see JS7 - Controller - Installation Using the Windows Graphical Installer.
Changing the Controller ID requires reinstallation of the Controller instances by carrying out the following steps for each instance:
- Stop the Controller service:
- Unix, Windows: Stop the Controller instance from the command line, see JS7 - Controller - Command Line Operation.
- Windows: Stop the Controller instance from the Windows service panel.
- Remove Controller journal files:
- The journal files have to be removed from the configuration directory with the
state
sub-directory. 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\*
- Unix:
- Note that a different location for the configuration directory can be specified during installation.
- The journal files have to be removed from the configuration directory with the
- Modify the Controller ID:
- Users can modify the Controller Instance Start Script that holds the environment variable:
JS7_CONTROLLER_ID=<controller-id>
- Unix: The Controller ID is specified with the
bin/controller_instance.sh
Instance Start Script, see JS7 - Controller - Headless Installation on Linux/Windows. Windows: The Controller ID is specified with the
bin\controller_instance.cmd
Instance Start Script. - Users can modify the Controller Instance Start Script that holds the environment variable:
- For Windows users can run the graphical installer to reinstall the Controller, see JS7 - Controller - Installation Using the Windows Graphical Installer.
Anchor | ||||
---|---|---|---|---|
|
The secondary Secondary Controller has to use the following configuration from its JS7_CONTROLLER_DATA/config/controller.conf
file, see JS7 - Controller Configuration Items:
...
If changes to the above configuration are required then users can carry out the following steps for the secondary Secondary Controller instance:
- Stop the Controller service:
- Unix, Windows: Stop the Controller instance from the command line, see JS7 - Controller - Command Line Operation.
- Windows: Stop the Controller instance from the Windows service panel.
- Remove Controller journal files:
- The journal files have to be removed from the configuration directory with the
state
sub-directory. This means that any Any orders that 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\*
- Unix:
- Consider that a A different location for the configuration directory can be specified during installation.
- The journal files have to be removed from the configuration directory with the
- Modify the the
config/controller.conf
file to reflect the js7.journal.cluster.node.is-backup=yes
setting. - Restart the Controller instance.
...
- The license key can be added during installation of each a Controller instance and each a JOC Cockpit instance.
- The license key can be added later on by storing the license certificate file in to the following locations:
- Unix: Controller configuration directory with
license
sub-directory.- Default location:
/var/sos-berlin.com/js7/controller/config/license
- A different location for the configuration directory can be specified during installation.
- Default location:
- Windows: Controller Configuration Directory with
license
sub-directory.- Default location:
C:\ProgramData\sos-berlin.com\js7\controller\<controller-id>\config\license
- where
<controller-id>
is the unique identifier for the Controller that is specified during installation.
- where
- A different location for the configuration directory can be specified during installation.
- Default location:
- Unix: Controller configuration directory with
...
Note: No access to the container's file system is available before the container is running, which makes it impossible to add or replace licensed binary code before the Controller is started.
Adding a License Key
- The license key can be is added by storing the license certificate file in to the following location:
/var/sos-berlin.com/js7/controller/config/license
- The directory
/var/sos-berlin.com/js7/controller
is typically mounted from a Docker var volume when running the container, for details see JS7 - Controller Installation for Docker Containers
...