Skip to end of metadata
Go to start of metadata

JOC Cockpit Start-up

Start Script

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

  • 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 for Unix.
  • On Windows systems the JOC Cockpit is started by its Windows Service.

Usage

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

Usage for Unix
Usage: jetty.sh command
  command:
    start
    stop
    restart

Environment Variables

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

  • JAVA_HOME
    • Indicates the location of the JVM, either a JRE (Java Runtime Environment) or JDK (Java Development Kit).
    • When this environment variable is not set, Java will be used from the location specified by the system path.
    • The JAVA_HOME environment variable does not necessarily 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, for example 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 the root account (for Unix) or as the Administrator account (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

The following information applies to headless installation for Windows systems. For installation with a GUI and user dialog see JS7 - JOC Cockpit - Installation Using the Graphical Installer for Linux and Windows.

The JOC Cockpit can be operated as a Windows Service. In addition, a number of management scripts are available:

  • The default location of management scripts is the directory:
    • C:\Program Files\sos-berlin.com\js7\joc\service

Installing the JOC Cockpit Jetty Service

install_jetty_windows_service.cmd

Starting the JOC Cockpit Jetty Service

start_jetty_windows_service.cmd

Uninstalling the JOC Cockpit Jetty Service

uninstall_jetty_windows_service.cmd

Configuring the Windows Service

The .\service\js7_<joc_service_name>w.exe file is installed along with the Windows Service. This program can be executed to configure the Windows Service.

For example, go to the "Startup" tab
to modify start parameters

Debugging

  • The JOC Cockpit instance log level can be increased using the JOC Cockpit's Apache ProcRun Daemon Service Manager daemon/service.
  • On  Windows systems, this is installed in the JOC Cockpit instance's service folder with a name such as js7_<joc_service_name>w.exe where <joc-service-name> is the unique JOC Cockpit service name.
  • Users can start the ProcRun Manager, select the Logging tab in the user interface and set the log level to Debug
  • The location of log files is explained above. 
  • Users should consider reverting the log level to its original value once they are finished with debugging.