Page History

...

• A Secondary Controller instance specifies this setting to indicate that this instance starts as a standby node (Backup). Without this setting being in place both instances of a Controller Cluster will start as standalone instances.
• This setting is relevant for initial operation only. It is independent of which Controller instance later on will be the active one and which instance will be the standby instance.
• This setting has to be added by the user before start of a Secondary Controller.

• This setting is used for Controller instances in cluster mode only, it is not used for standalone Controller instances.
• The registration of Primary and Secondary Controller instances is performed by JOC Cockpit during initial operation.
  • Therefore the only setting required for cluster operation is 
    • js7.journal.cluster.nodesnode.is-backup=yes: For a Secondary Controller instance this setting specifies that during initial operation the given instance will be the inactive standby node.
  • Additional settings can be applied, however, we recommend to use JOC Cockpit instead.
    • nodes
      • Primary, Backup: For a Primary Controller instance this setting specifies the URLs of the Primary and Backup (Secondary) instance. The URL includes specification of the protocol http/https, the hostname and port.
    • watches
      • Watches are Agents in a JS7 environment that are involved in the decision about a fail-over situation. If Controller instances in a cluster are not connected to each other any longer, e.g. due to network errors, then the majority of Agents decides if a fail-over should take place.
      • At least one Agent has to be specified by its URL.

...