...
If the Jetty provided with the JOC Cockpit is not to be installed, files in the resources folder, containing files that will likely be relevant for system administrators - i.e. the shiro.ini file (containing default authentication and authorization information) and the joc.properties file (containing default database configuration information) - will not be written to locations described in Step 4 of the installation procedure above. The exact locations will depend on whether the installation program finds an older Jetty installation within the JOC Cockpit installation path specified in Step 3 of the installation procedure. System administrators can then move the shiro.ini file and other resources to the appropriate application directory as required.
Location of the resources folder with a fresh installation
With a fresh installation, the installer will not find an existing Jetty and saves will save the resources directory by default as follows:
- on Linux systems:
...< PATH TO BE COMPLETED
- on Windows systems:
C:\Program Files\sos-berlin.com\joc\resources
...< PATH TO BE COMPLETED
Location of the resources folder with an installation on top of an installation with Jetty
| Status | ||||
|---|---|---|---|---|
|
If the JOC Cockpit is being installed without the included Jetty but on top of an installation that had included the JOC Cockpit Jetty then the resources folder will not be moved from its current location. This means that the resources folder will be found after the new installation as follows:
- on Linux systems:
...< PATH TO BE COMPLETED
- on Windows systems:
C:\ProgramData\sos-berlin.com\joc\resources
...< PATH TO BE COMPLETED
In this situation the shiro.ini and joc.properties file from the earlier installation will not be overwritten. However new versions of the hibernate.cfg.xml , joc.properties-example and shiro.ini-example files will be written to the resources folder, overwriting any existing versions.
File Structure
| Status | ||||
|---|---|---|---|---|
|
...