JOC Cockpit

...

Start-up

Start Script

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

...

• JAVA_HOME
  • Points to the location of the JVM, either a JRE (Java Runtime Environment (JRE) or JDK (Java Development Kit).
  • Without setting this environment variable Java will be used from the location specified by the system path.
  • Note that The JAVA_HOME should  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, e.g. 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.

...

• SOS does not recommend to run the JS7 JOC Cockpit as the root account (for Unix) or as 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.

...

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 Linux/Windows Graphical Installer.

The JOC Cockpit jetty can be operated as a Windows Service.

...

After installation of the Windows Service, you will find users find the .\service\js7_<joc_service_name>w.exe file. Run this This program can be executed to configure the Windows Service.

...

• The JOC Cockpit instance log level can be increased using the JOC Cockpit's Apache ProcRun Demon Daemon Service Manager demondaemon/service.
• For 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.
• Start Users can start the ProcRun Manager, select the Logging tab in the Manager user interface and set the log level to Debug. 
• The location of log files is explained above. 
• Consider reverting Users should consider to revert the log level to its original value once you they are finished with debugging.

...