...

• Initial Operation is performed after installation of the JS7 components.
• Operation of a Controller Cluster and of a JOC Cockpit Cluster requires a commercial license, see JS7 - Licensing.
• Tasks include to apply the license key and licensed binary code.
• Tasks include to register the Controller Cluster and Agents.
• This optionally includes to adjust global settings to your needs.

Prerequisites

Initial Operation

...

This step requires that a Controller, Agent and JOC Cockpit are successfully installed and are up and running.

• Consider that a Controller Cluster requires two Controller instances to be installed.
  • For details see JS7 - Installation
• The steps for initial operation are the same for any supported platforms:
  • JS7 - On Premises
  • JS7 - Docker Containers
  • JS7 - Cloud

Controller Cluster

xxxx

Check Controller ID

• Both Controller instances for a Cluster are installed with the same Controller ID that is a unique identifier for a Controller Cluster.
  • Changing the Controller ID requires to reinstall the Controller instances by applying the following steps to each instance:
    • 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 folder which implies that any submitted orders for workflows will be removed and that workflows have to be redeployed:
        • Unix: rm -f /var/sos-berlin.com/js7/controller/state/*
        • Windows: del C:\ProgramData\sos-berlin.com\js7\controller\state\*
      • Consider that a different configuration directory can be specified during installation.
    • Modify Controller ID
      • Unix: For headless installation as an exception to the rule the Controller ID is specified in the installation directory with the bin/environment_variables.sh file, see JS7 - Controller - Use of Linux/Windows Headless Installation.
        • 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 - Use of Windows Graphical Installer.
    • Restart the Controller instance.

x

• The secondary Controller is using the following configuration from its config/controller.conf file, see JS7 - Controller Configuration Items:
  • Apply the following line to this file:
    • js7.journal.cluster.nodes.is-backup=yes
  • If changes to the above configuration are required then the
    • its config/controller.conf file
    • The journal files have to be removed from the configuration directory with the state folder which implies that any submitted orders for workflows will be removed and that workflows have to be redeployed:
      • Unix: rm -f /var/sos-berlin.com/js7/controller/state/*
      • Windows: del C:\ProgramData\sos-berlin.com\js7\controller\state\*
    • Consider that a different configuration directory can be specified during installation.
    • x

JOC Cockpit Cluster

License Key and Licensed Binary Code

Customers equipped with a commercial license receive both a license key from SOS and the binary code that allows clustering of JS7 components.

Find below the summary information, for details see JS7 - FAQ - How to apply a JS7 License Key

Adding a License Key

• The license key can be added during installation of each Controller instance and of each JOC Cockpit instance.
• The license key can be added later on by storing the license certificate file to the following locations:
  • Unix
    • Controller Configuration Directory with license sub-folder
      • Default: /var/sos-berlin.com/js7/controller/config/license
      • A different configuration directory can be specified during installation.
    • JOC Cockpit Configuration Directory with license sub-folder
      
      • Default: /var/sos-berlin.com/js7/joc/resources/joc/license
      • A different configuration directory can be specified during installation.
  • Windows
    • Controller Configuration Directory with license sub-folder
      • Default: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.
      • A different configuration directory can be specified during installation.
    • JOC Cockpit Configuration Directory with license sub-folder
      • Default:C:\ProgramData\sos-berlin.com\js7\joc\resources\joc\license
      • A different configuration directory can be specified during installation.

Applying Licensed Binary Code

• Binary code for clustering is available from the js7-license.jar file that is offered 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: /opt/sos-berlin.com/js7/controller/lib/user_lib
      • A different installation directory can be specified during installation.
    • JOC Cockpit Installation Directory with lib/ext/joc sub-folders
      
      • Default: /opt/sos-berlin.com/js7/joc/lib/ext/joc
      • A different installation directory can be specified during installation.
  • Windows
    • Controller Installation Directory with lib\user_lib sub-folders
      • Default:C:\Program Files\sos-berlin.com\js7\controller\lib\user_lib
      • A different installation directory can be specified during installation.
    • JOC Cockpit Installation Directory with lib\ext\joc sub-folders
      • Default:C:\Program Files\sos-berlin.com\js7\joc\lib\ext\joc
      • A different installation directory can be specified during installation.

Login to JOC Cockpit User Interface

...