Page History

...

After login a dialog window pops up that ask asks to register a Controller. 

Image Removed

Explanations:

...

. You will find the same dialog later on from the User -> Manage Controllers/Agents menu.

You have a choice to register a Standalone Controller or to register a Controller Cluster for high availability (requires JS7 - Licensing).

Register Standalone Controller

This registration dialog offers to specify a Standalone Controller or a Controller Cluster.

...

Use of the Standalone Controller is in scope of the JS7 open source license.

Image Added

Explanations:

• You can add a title to the Controller instance that will become visible with the JS7 - Dashboard View.
• The URL of the Controller instance has to match the hostname and port that the Controller instance is operated for.
  • Should you use a Docker network then all containers will "see" each other and all inside container ports are accessible within the network.
    • In the above example a Docker network js7 was used and the Controller container was started with the hostname js7-controller-primary.
    • The port 4444 is the inside HTTP port of the Controller that is visible in the Docker network.
  • Should you not use a Docker network then it is up to you how to map hostnames:
    • The Controller container could be accessible from the Docker host, i.e. you would specify the hostname of the Docker host. 
    • The outside HTTP port of the Controller container has to be used that is specified with the --publish option when starting the Controller container.

Register Controller Cluster

A Controller cluster implements high availability for automated fail-over should a Controller instance be terminated or become unavailable.

Consider that the high availability feature of clustering is subject to JS7 - Licensing. Without a license no fail-over/switch-over will take place between Controller cluster members.

Image Added

Explanations:

• This dialog offers to specify the Primary Controller instance, Secondary Controller instance and .Agent Cluster Watcher.
  • You can add a title to each Controller instance that will become visible with the JS7 - Dashboard View.
  • Primary and Secondary Controller require a URL as seen from JOC Cockpit.
  • In addition, each Controller instance can be added a URL from which it is accessible by its partner cluster member.
    • Typically the URL is the same as the URL for JOC Cockpit.
    • Should you operate e.g. a proxy server between Primary and Secondary Controller instances then the URL for a given Controller instance to access its partner cluster member might be different from the URL used by JOC Cockpit
    Use of the Standalone Controller is in scope of the JS7 open source license
    • .
• The URL of the Controller instance has to match the hostname and port that the Controller instance is operated for.
  • Should you use a Docker network then all containers will "see" each other and all inside container ports are accessible within the network.
    • In the above example a Docker network js7 was used and the Primary Controller container was started with the hostname js7-controller-primary. The Secondary Controller was started with the hostname js7-controller-secondary.
    • The port 4444 is the inside HTTP port of the Controller instance that is visible in the Docker network.
  • Should you not use a Docker network then it is up to you how to map hostnames:
    • The Controller Container container could be accessible from the Docker host, i.e. you would specify the hostname of the Docker host. 
    • The outside HTTP port of the Controller instane has to be used that was specified with the --publish option when starting the Controller container.
• The Agent Cluster Watcher is required for operation of a Controller cluster. The Agent is contacted by Controller cluster members to verify the cluster status should no direct connection between Controller cluster members be available.
  • Consider that the above example makes use of an Agent that by default is configured for use with HTTP connections. 
  • For use of the Agent's hostname and port the same applies as for Controller instances.

Register Agents

After the connection between JOC Cockpit and the Controller is established you can add Agents like this:

...