...

The JOC Cockpit installation procedure includes installing the Jetty servlet container provided in the JOC Cockpit installer archive. An alternative servlet container capable of handling Java web applications, such as Tomcat, might work, however, support by SOS is limited to the JOC Cockpit application and the Jetty servlet container included. Users of the Open Source License are free to operate JOC Cockpit for individually installed servlet containers.

Installation using alternative Servlet Containers

If the Jetty servlet container included with JOC Cockpit is not to be installed, then the installer will check if a jetty_base symlink from a previous installation is to be found in the JETTY_HOME directory. Particularly relevant for system administrators is the shiro.ini.active file (containing authentication and authorization settings) and the is the joc.properties file (containing JOC Cockpit installation settings).

...

With a fresh installation, the installer will not find an existing Jetty servlet container and will store the resources sub-directory for the joc application by default in the following locationslocation:

• for Unix systems:
  
  • /opt/sos-berlin.com/js7/joc/resources/joc
• for Windows systems:
  
  • C:\Program Files\sos-berlin.com\js7\joc\resources\joc

Location of the resources/joc directory after update

If JOC Cockpit is updated without the Jetty servlet container but on top of an existing installation that includes the Jetty servlet container then the resources/joc directory will not be moved from its location. Practically this means that the "new" resources directory after the update will be found with the following directories (assuming that default directories were have been specified during the original installation):

• for Unix systems:
  
  • /opt/sos-berlin.com/js7/joc/resources/joc
• for Windows systems:
  
  • C:\Program Files\sos-berlin.com\js7\joc\resources\joc

In this situation:

• the shiro.ini and joc.properties files from an earlier installation will not be overwritten.
• an existing hibernate.cfg.xml database configuration file will be read during update and the settings will be suggested as default values. This file will be deleted and a new version of the file will be stored in the joc_home directory.
• an update of JOC Cockpit will not overwrite any existing configuration files. However new versions of the joc.properties and shiro.ini files file with the names joc.properties-example and shirolog4j2.inixml-example will be stored in the resources/joc folder, alongside the original files.

...