Page History

...

• docker exec -ti is the command that connects to the JOC Cockpit container js7-joc-primary.
• js7-joc-primary is the name of the JOC Cockpit container as specified with the above docker run command.
• /bin/sh -c runs a shell inside the container and executes a script to install database objects required for operation of JOC Cockpit.

Log Files

Access to log files is essential to identify problems during installation and operation of JOC Cockpit.

When mounting a volume for log files as explained above you should have access to the files indicated with JS7 - Log Files and Locations article.

• 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 GUI is used to make Controller instances and Agent instances known to your job scheduling environment.

...

• This dialog allows to specify a Standalone Controller or a Controller Cluster.
  • Consider that use of a cluster is subject to JS7 - Licensing.
  • 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 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 has to be used that was specified with the --publish option when starting the Controller container.

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

Image Added

Explanations:

• 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.
• You 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 you can add alias names to make the same Agent available with different names.