...
The JOC Cockpit installation procedure contains the option of installing and using the Jetty Web Server that is included in with the JOC Cockpit installation archive. This option was shown in the above series of screen shots (Step 4). An alternative web server, which is capable of handling Java web applications, such as Tomcat or an own Jetty server, can also be used.
Status
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 still be written to the file system. The locations of these files will depend on whether or not a Jetty web server was previously 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....