Page History

...

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 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 directory for the joc application by default in the following locations:

...

• 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 considered 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 with the names joc.properties-example and shiro.ini-example will be stored in the resources/joc folder, alongside the original files.

...