Shibboleth Developers

[Scott Cantor <>]

> So, since this will come up, and I've had trouble with it, 
> what's the sequence for upgrading an origin build?  I've 
> tried just moving webapps/shibboleth to 
> webapps/shibboleth.bak and moving in the new shibboleth.war; 
> but this causes tomcat not to start up.  Suggestion?  The 
> sequence that Scott went thru a little too quickly for me to follow?

Well, what I was doing was:

I unpack the origin tarball in /opt
I create /opt/shibboleth-origin-1.0/conf
I copy all the default config files into conf
Then I change origin.properties in the webapp to point out to there with 
file:// URLs

This is pretty workable for updates as far as just reducing it to maintaining 
origin.properties across updates. You still have to
trash the old tree to get the new one to unpack.

Walter pointed out that the better way is to turn off Tomcat's expansion of 
warfiles, and basically maintain the config inside a
build tree of the source. Then you just change or update it, run ant, copy 
the dist/war over, bounce, and done.

I like that a lot.

-- Scott

------------------------------------------------------mace-shib-design-+
For list utilities, archives, subscribe, unsubscribe, etc. please visit the
ListProc web interface at 

    http://archives.internet2.edu/

------------------------------------------------------mace-shib-design--