...
Program Files
sos-berlin.com
joc
install
install_jetty_base.cmd
shortcut.vbs
sleep.exe
update_jetty_base.cmd
logs
- Install_ ... .log (files will remain after uninstall)
resources
joc
jobscheduler.hibernate.cfg.xml
(remains after uninstall if modified)joc.properties
(remains after uninstall)joc.properties-example
(only added ifjoc.properties
file is found at installation start)log4j.properties
(remains after uninstall if modified)jobscheduler.hibernate.cfg.xml
(remains after uninstall if modified)shiro.ini
(remains after uninstall)shiro.ini-example
(only added ifshiro.ini
file is found at installation start)
service
amd64
(directory)ia64
(directory)manager
(directory)x86
(directory)install_jetty_windows_service.cmd
LICENSE.txt
NOTICE.txt
RELEASE-NOTES.txt
set_java_home_for_jetty_windows_service.cmd
start_jetty_windows_service.cmd
uninstall_jetty_windows_service.cmd
Uninstaller
(the empty directory remains after uninstall)jobscheduler.ico
uninstall.cmd
uninstaller.jar
webapps
joc.war
.jocinstallinformation
(file, remains after uninstall)joc_install.xml
(file, remains after uninstall)
Clustering and Redundancy
Multiple instances of the JOC Cockpit, with each instance running on its own server, can either be installed as an active cluster or redundantly. In both cases, installation of the JOC Cockpit instances follows the standard procedure described above. The configuration of a the JOC Cockpit Cluster is described instances then follows the instructions provided in the Authentication and Authorization - Configuration article.
The JOC Cockpit - Authentication and AuthorizationClustering article provides more general information about the installation of a clusterinstalling and configuring multiple instances of the JOC Cockpit.
JOC Cockpit Configuration
...