JOC Cockpit Startup

Start Script

The JOC Cockpit includes a Start Script to manage the application:

On Linux systems

...

• The JOC Cockpit Start Script is available for Unix only.
  • The default location of the jetty.sh Start Script is:

• • • /opt/sos-berlin.com/js7/joc/jetty/bin

...

• ./jetty.sh stop|start

On Windows systems

• • •  for Unix.

• For Windows systems JOC Cockpit is started from its Windows Service.

Usage

Running the JOC Cockpit Start Script allows use of the following commands:

Usage: jetty.sh command
  command:
    start
    stop
    restart

Environment Variables

The following environment variables are considered by the JOC Cockpit Start Script;

• JAVA_HOME
  • Points to the location of the Java Runtime Environment (JRE).
  • Without setting this environment variable Java will be used from the location specified by the system path.
  • Please consider that JAVA_HOME does not point to the location of a JDK but to a JRE directory where the bin/java executable resides, for example if the location of the Java executable is /opt/java/jdk8u202-b08/jre/bin/java then JAVA_HOME=/opt/java/jdk8u202-b08/jre.
• JAVA_OPTIONS
  • Specifies Java options, e.g. the Java memory settings for the JOC Cockpit.
  • Without setting this environment variable the Java options default to the value specified during installation of JOC Cockpit.

Running the JOC Cockpit

• SOS does not recommend to run the JS7 JOC Cockpit as root (for Unix) or as Administrator (for Windows) for a simple reason: there is no need to do so.
• The JOC Cockpit does not execute any jobs as this task is performed by Agents. Therefore any user account can be used to operate the JOC Cockpit.

Starting the JOC Cockpit

jetty.sh start

Stopping the JOC Cockpit

jetty.sh stop

This command will safely terminate the Controller (recommended).

Restarting the JOC Cockpit

jetty.sh restart

Windows Service Interface

...

• C:\Program Files\sos-berlin.com\js7\joc\service

...