Page History

...

• From the Unix command line or from the Controller instance start script controller_<instance>.sh:

  Code Block
  language bash title Unix example to run the Controller start script with debug options
  # Set debug options before running the Controller start script export JAVA_OPTIONS="-Djavax.net.debug=ssl" ./controller.sh start # Alternatively set debug options when running the Controller start script ./controller.sh start --java-options="-Djavax.net.debug=ssl" # For use with a Controller daemon add this line to the Controller instance start script controller_<instance>.sh export JAVA_OPTIONS="-Djavax.net.debug=ssl"

• From the Unix command line or from the Agent instance start script agent_4445.sh (assuming that port 4445 is used for the Agent):
  
  

  Code Block
  language bash title Unix example to run the Agent start script with debug options
  # Set debug options before running the Agent start script export JAVA_OPTIONS="-Djavax.net.debug=ssl" ./agent.sh start # Alternatively set debug options when running the Agent start script ./agent.sh start --java-options="-Djavax.net.debug=ssl" # For use with an Agent daemon add this line to the Agent instance start script agent_<port>.sh export JAVA_OPTIONS="-Djavax.net.debug=ssl"

• Alternatively the JAVA_OPTIONS environment variable can be set with
  • the profile (~/.bashrc, ~/.bash_profile etc.) of the run-time account used for Controller or Agent,
  • the JS7 - systemd Service Files for automated Startup / Shutdown with Unix Systems.

Windows Operating Systems

...

• The Jetty start script is available from the installation directory  /opt/sos-berlin.com/js7/joc/jetty/bin/jetty.sh or a location specified during installation:

  Code Block
  language bash title Unix example to run the Jetty start script with debug options
  # Set debug options before running the Jetty start script export JAVA_OPTIONS="-Djavax.net.debug=ssl" ./jetty.sh start

• When running JOC Cockpit as a daemon then the following line can be added to the $HOME/.jocrc file of the JOC Cockpit run-time account. This file is created by the installer is used if it exists and is executable. The $HOME directory is identified from the /etc/passwd file during installation.

  Code Block
  language bash title Unix example to use $HOME/.jocrc with debug options
  export JAVA_OPTIONS="-Djavax.net.debug=ssl"

• When running JOC Cockpit as a daemon then the  /etc/default/joc file can be created (requires root permission) by the user. This file is not created by the installer, it will be used if it exists and is executable. This file will not be used if the $HOME/.jocrc file is present, see above.

  Code Block
  language bash title Unix example to use /etc/default/joc with debug options
  export JAVA_OPTIONS="-Djavax.net.debug=ssl"

• Alternatively the JAVA_OPTIONS environment variable can be set with
  • the profile (~/.bashrc, ~/.bash_profile etc.) of the run-time account used for JOC Cockpit,
  • the JS7 - systemd Service Files for automated Startup / Shutdown with Unix Systems.

Windows Operating Systems

...

• Only when JOC Cockpit is not installed as Windows Service then the start script C:\Program Files\sos-berlin.com\js7\joc\jetty\bin\jetty.cmd is available.

  Code Block
  language bash title Windows example to run the JOC Cockpit start script with debug options
  @rem Set debug options before running the JOC Cockpit start script set JAVA_OPTIONS="-Djavax.net.debug=ssl" .\jetty.cmd start

• When operating the JOC Cockpit as a Windows Service then from the .\service directory of the installation run
  
  • for JOC Cockpit: js7_jocw.exe
    
    • Example: C:\Program Files\sos-berlin.com\js7\joc\service\js7_jocw.exe
  • This brings up a utility that allows Java options to be specified:
    
    
    • 
      
      
  • Note that the : The JOC Cockpit Windows Service has to be restarted to apply changes to Java options.

...