Page History
The appropriate software must be restarted whenever the configuration is modified.
Tomcat
Restart when server.xml, shrine.conf or override.conf are modified, or a new WAR file is put in place
Starting Tomcat:
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
sudo -u shrine bash cd /opt/shrine/tomcat ./bin/startup.sh |
To deploy a new WAR file:
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
sudo -u shrine bash ./bin/shutdown.sh rm -fr ./webapps/shrine api* cp <Shrine war file> ./webapps ./bin/startup.sh |
Shibboleth
(Re)start when shibboleth2.xml or other Shibboleth configuration files are modified.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
sudo -u root bash service shibd restart service httpd restart |
Apache
Restart after restarting Shibboleth; or when there is a change in Apache configuration.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
sudo -u root bash service httpd restart |
NextStep:
SHRINE 4.1.0 Appendix A.9 10 - Using SSO-Enabled Shrine
Overview
Content Tools