...

• The jetty.log file reports about initial start up of the servlet container.
• The joc.log file includes e.g. information about database access.

...

Initial Operation

...

For initial operation, the JOC Cockpit is used to make Controller instance(s) and Agent instances known to the job scheduling environment

...

General information about initial operation can be found in the following article:

• JS7 - Initial Operation for JOC Cockpit Cluster

Additional information about initial operation with containers can be found below.

Accessing JOC Cockpit from the Browser

Image Removed

Explanations:

For

...

use

...

of

...

JOC Cockpit

...

with the Open Source license the following

...

• User Account: root
• Password: root

Register Controller and Agents

After logging in a dialog window pops up that asks for the registration of a Controller. Users will find the same dialog later on in the Manage Controllers/Agents menu.

Users have a choice of registering a Standalone Controller or a JS7 - Controller Cluster for high availability (requires JS7 - License).

Register Standalone Controller

This registration dialog allows a Standalone Controller or a Controller Cluster to be specified.

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

Image Removed

Explanation:

• Users can add a title to the Controller instance which will be shown in the JS7 - Dashboard View.
• The URL of the Controller instance has to match the hostname and port used to operate the Controller instance.
  • Should a Docker network be used then all containers will "see" each other and all internal container ports will be accessible within the network.
    • In the above example a Docker network js7 is used and the Controller container will be 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.
  • If no Docker network is used then users are free to decide how to map hostnames:
    • The Controller container is accessible from the Docker host, i.e. the hostname of the Docker host is specified. 
    • The outside HTTP port of the Controller container is used, which is specified with the --publish option when starting the Controller container.

Register Controller Cluster

A Controller cluster implements high availability for automated fail-over if a Controller instance becomes unavailable.

Note that the high availability clustering feature is subject to the JS7 - License.

Image Removed

Explanation:

• The Primary Controller instance, Secondary Controller instance and Agent Cluster Watcher are specified in this dialog.
  • Users can add a title for each Controller instance which will be shown in the JS7 - Dashboard view.
  • Primary and Secondary Controller instances require a URL as seen from the JOC Cockpit.
  • In addition, a URL can be specified for each Controller instance to allow it to be accessed by its partner cluster member.
    • Typically the URL used between Controller instances is the same as the URL used by the JOC Cockpit and therefore this setting is not used.
    • Should users operate for example 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 the JOC Cockpit.
• The URL of the Controller instance has to match the hostname and port that the Controller instance is operated on.
  • Should a Docker network be used 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 is used and the Primary Controller container will be started with the hostname js7-controller-primary. The Secondary Controller container will be 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 no Docker network be used then users are free to decide how to map hostnames:
    • The Controller container is accessible from the Docker host and the hostname of the Docker host is specified.
    • The outside HTTP port of the Controller instance is used which 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 in addition to direct connections between Controller Cluster members.
  • 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.

Register Agents

...

information applies:

• JS7 - Initial Operation for Standalone Controller
• JS7 - Management of Standalone Controllers
• JS7 - Management of Standalone Agents

If the JS7 is used for high availability in a JS7 - JOC Cockpit Cluster, JS7 - Controller Cluster or JS7 - Agent Cluster using the commercial JS7 - License the following information applies:

• JS7 - Initial Operation for JOC Cockpit Cluster
• JS7 - Initial Operation for Controller Cluster
• JS7 - Management of Controller Clusters
• JS7 - Management of Agent Clusters

Image Removed

Explanation:

• For each Agent a unique identifier is specified, the Agent ID. The identifier remains in place for the lifetime of an Agent and cannot be modified.
• Users can add a name for the Agent that will be used when assigning jobs to be executed with this Agent. The Agent name can be modified later on.
• In addition users can add alias names to make the same Agent available under different names.

Further Resources

Configuring the JOC Cockpit

...