Page History

...

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.

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

Usage

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

...

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

• JAVA_HOME
  • Points to Indicates the location of the JVM, either a JRE (Java Runtime Environment) or JDK (Java Development Kit).
  • Without setting 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.

...

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 Graphical Installer.

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

...

Configuring the Windows Service

After installation of the Windows Service, users find the 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.

...

• The JOC Cockpit instance log level can be increased using the JOC Cockpit's Apache ProcRun Daemon Service Manager daemon/service.
• For 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 to revert reverting the log level to its original value once they are finished with debugging.

...