Page History

...

• Consider that the operational feature of clustering is subject to JS7 - Licensing. Without a license
  • no fail-over/switch-over will take place between JOC Cockpit cluster members.
  • you have to (re)start a secondary Secondary JOC Cockpit instance if you want this instance to become active after the primary Primary JOC Cockpit instance is shutdown or becomes unavailable.
• The installation of JOC Cockpit cluster members is the same as explained with the JS7 - JOC Cockpit Installation for Docker Containers
  • Both primary Primary and secondary Secondary JOC Cockpit containers can be started from the same image.
  • Both JOC Cockpit instances will become visible with each instance's Dashboard View.

...

To better visually distinguish primary Primary and secondary Secondary JOC Cockpit instances you can modify the instance title ("Primary JOC Cockpit", "Secondary JOC Cockpit")

• Navigate to the config volume that is mounted from the JOC Cockpit container as indicated with the JS7 - JOC Cockpit Installation for Docker Containers article.

• The volume is mounted to the /var/sos-berlin.com/js7/joc/resources/joc folder  directory and includes the file joc.properties:

  Code Block
  language bash title JOC Cockpit Dashboard configuration with joc.properties linenumbers true
  ################################################################################ ### If JOC Cockpit is used in a cluster then type a title to identify which node ### is currently used. Further type an ordering (Primary <= 0, Standby > 0) for ### the display order in JOC's dashboard title = PRIMARY JOC COCKPIT ordering = 0

  
  

  • Modify the instance title of the JOC Cockpit instance at your will.
  • Adjust the ordering, i.e. the sequence of JOC Cockpit instances displayed with the Dashboard View from left to right starting by 0.

...