...

• 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 Note that JAVA_HOME does should 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.

...

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

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

Installing the JOC Cockpit Jetty Service

...

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

Debugging

• The JOC Cockpit instance log level can be increased using the JOC Cockpit's Apache ProcRun Demon Service Manager demon/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 the ProcRun Manager, select the Logging tab in the Manager interface and set the level to Debug. 
• The location of log files is explained above. 
• Consider reverting a debug the log level to its orignal value once you are finished with debugging.