...
These files contain the configuration information from the last JOC Cockpit and Jetty web server installations.
Files that are not removed during a normal uninstall (i.e. when the checkbox is not ticked) are noted in the File Structure section of this article below.
Manual Jetty Configuration
Text ... < TO BE COMPLETEDaddeD
Anchor | ||||
---|---|---|---|---|
|
...
If the Jetty provided with the JOC Cockpit is not to be installed, a resources
folder, containing files that will likely be the installation program will look and see if configuration files from a previous installation are to be found in a subdirectory of the jetty_base
directory. Particularly relevant for system administrators - i.e. would be the shiro.ini
file (containing default authentication and authorization information) and the joc.properties
file (containing default database configuration information) - will still .
- If configuration files are found then these will not be overwritten or removed.
- Default configuration files will be written to the file system
...
- in in the
joc_home
directory. - System administrators can then move the
shiro.ini
file and other resources to the appropriate application directory as required.
Location of the resources/joc
folder with a fresh installation
With a fresh installation, the installer will not find an any existing Jetty and will save the resources
directory by default as follows:
- on Linux systems:
< PATH TO BE CONFIRMED/home/[user]/sos-berlin.com/joc
/resources/joc
- on Windows systems:
C:\Program Files\sos-berlin.com\joc\resources\joc
Location of the resources
/joc
folder with an installation on top of a JOC Cockpit installation with
...
Jetty
...
If the JOC Cockpit is being installed without the included Jetty but on top of an installation that has included the JOC Cockpit Jetty then the resources\joc
folder will not be moved from its location. This means that the resources
folder will be found after the new installation as follows (if the original installation was carried out in the default directory):
- on Linux systems:
< PATH TO BE CONFIRMED/home/[user]/sos-berlin.com/joc
/resources/joc
- on Windows systems:
C:\ProgramData\sos-berlin.com\joc\resources\joc
In this situation the shiro.ini
and joc.properties
file from the earlier installation will not be overwritten.
An update of the JOC Cockpit will neither overwrite the new or old configuration files. However new versions of the hibernate.cfg.xml
, the joc.properties
and shiro.ini
files named joc.properties-example
and shiro.ini-example
files will be written to the resources\joc
folder, overwriting any existing versionsalongside the originals.
File Structure
Windows Systems
...