JOC Cockpit Startup
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
/opt/sos-berlin.com/js7/joc/jetty/bin
for Unix.
- The default location of the
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.
- Note that
JAVA_HOME
should not point to the location of a JDK but to a JRE directory where thebin/java
executable resides, for example if the location of the Java executable is/opt/java/jdk8u202-b08/jre/bin/java
thenJAVA_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 asAdministrator
(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 Linux/Windows Graphical Installer.
The JOC Cockpit jetty can be operated as a Windows 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
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.
For example, go to the "Startup" tab |
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 asjs7_<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 the log level to its orignal value once you are finished with debugging.