Page History
...
Explanation:
- This dialog allows the to specify of the Primary Controller instance, Secondary Controller instance and .Agent Cluster Watcher.
- You can add a title for each Controller instance that will become visible with the JS7 - Dashboard View.
- Primary and Secondary Controller instances 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 used between Controller instances is the same as the URL for used by 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.
- 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 hostnamejs7-controller-primary
. The Secondary Controller was started with the hostnamejs7-controller-secondary
. - The port
4444
is the inside HTTP port of the Controller instance that is visible in the Docker network.
- In the above example a Docker network
- Should you not use a Docker network then it is up to you how decide 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 instane has to be used that was specified with the
--publish
option when starting the Controller container.
- Should you use a Docker network then all containers will "see" each other and all inside container ports are accessible within the network.
- 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.
- Note that the example above 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.
...
Overview
Content Tools