Introduction
- Initial operation for JOC Cockpit includes that
- a database is available and is accessible,
- the JOC Cockpit container will be started
- the database objects will be created.
Pulling the JOC Cockpit Image
Pull the version of the JOC Cockpit image that corresponds to the JS7 release in use:
Pulling the JOC Cockpit Image
docker image pull sosberlin/js7:joc-2-0-0-SNAPSHOT
Running the JOC Cockpit Container
After pulling the JOC Cockpit image you can run the container with a number of options like this:
Running the JOC Cockpit Container for HTTP Connections
#!/bin/sh docker run -dit --rm \ --user="$(id -u $USER):$(id -g $USER)" \ --hostname=js7-joc-primary \ --network=js7 \ --publish=17446:4446 \ --env="RUN_JS_JAVA_OPTIONS=-Xmx256m" \ --mount="type=volume,src=js7-joc-primary-config,dst=/var/sos-berlin.com/js7/joc/resources/joc" \ --mount="type=volume,src=js7-joc-primary-logs,dst=/var/log/sos-berlin.com/js7/joc" \ --name js7-joc-primary \ sosberlin/js7:joc-2-0-0-SNAPSHOT
Explanations:
--user
Inside the container the JOC Cockpit instance is operated for the user accountjobscheduler
. In order to access e.g. log files created by the JOC Cockpit instance that are mounted to the Docker host it is recommended that you map the account that is starting the container to thejobscheduler
account inside the container. The--user
option accepts the user ID and group ID of the account that will be mapped. The above example makes use of the current user.--network
The above example makes use of a Docker network - created e.g. with the commanddocker network create js7
- to allow network sharing between containers. Consider that any inside ports used by Docker containers are visible within a Docker network. Therefore a JOC Cockpit instance running for the inside port4446
is accessible with the container's hostname and the same port within the Docker network.--publish
The JOC Cockpit is prepared to listen to the HTTP port4446
. An outside port of the Docker host can be mapped to the JOC Cockpit inside HTTP port. This is not required for use with a Docker network, see--network
, however, it will allow direct access to the JOC Cockpit from the Docker host by its outside port .--env=JAVA_OPTIONS
This allows to inject any Java options to the JOC Cockpit container. Preferably this is used to specify memory requirements of JOC Cockpit, e.g. with-Xmx256m
.--mount
The following volume mounts are suggested:config
: The optional configuration folder allows to specify individual settings for JOC Cockpit operation, see below chapters and the JS7 - JOC Cockpit Configuration article. Without this folder the default settings are used.logs
: In order to have JOC Cockpit log files persisted they have to be written to a volume that is mounted for the container. Feel free to adjust the volume name from thesrc
attribute, however, the value of thedst
attribute should not be changed as it reflects the directory hierarchy inside the container.
Configuring the JOC Cockpit
Database Connection
Install Database Objects
# create database objects docker exec -ti js7-joc-primary /bin/bash -c /opt/sos-berlin.com/js7/joc/install/joc_install_tables.sh
Explanations:
- The
docker exec
command connects to the JOC Cockpit containerjs7-joc-primary
and executes a script to install the database object required for operation of JOC Cockpit..
Overview
Content Tools