Skip to Content.
Sympa Menu

shibboleth-dev - Re: Upgrade steps for origin

Subject: Shibboleth Developers

List archive

Re: Upgrade steps for origin


Chronological Thread 
  • From: Walter Hoehn <>
  • To: "'Shib Design Team'" <>
  • Cc: "'Nate Klingenstein'" <>
  • Subject: Re: Upgrade steps for origin
  • Date: Mon, 28 Jul 2003 17:51:35 -0400

Here is a first cut at steps for the origin upgrade. It would be nice if folks that are testing the upgrade used this list before we publish it.

1. Shutdown tomcat.

2. Copy to a scratch directory:

origin properties file (default of $CATALINA_HOME/webapps/shibboleth/WEB-INF/classes/conf/origin.properties),

the resolver configuration file ( default of $CATALINA_HOME/webapps/shibboleth/WEB-INF/classes/conf/resolver.xml),

the logging configuration file ( default of $CATALINA_HOME/webapps/shibboleth/WEB-INF/classes/conf/log4j.properties),

the HS keystore ( default of $CATALINA_HOME/webapps/shibboleth/WEB-INF/classes/conf/keystore.jks),

your web application deployment descriptor ( default of $CATALINA_HOME/webapps/shibboleth/WEB-INF/web.xml),

any ARPS you created ( default of $CATALINA_HOME/webapps/shibboleth/WEB-INF/classes/conf/arps/*),

the crypto handle repository keystore (if you are using it) ( default of $CATALINA_HOME/webapps/shibboleth/WEB-INF/classes/conf/handle.jks),

the targetedId attribute keystore (if you are using it) ( default of $CATALINA_HOME/webapps/shibboleth/WEB-INF/classes/conf/persistent.jks),


3. Delete the old origin.

4. Deploy the new origin.

5. Copy over the files from the scratch directory.

6. Startup tomcat.

That should just about do it. All configuration options from 1.0 are still valid.

-Walter

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature




Archive powered by MHonArc 2.6.16.

Top of Page