Grouper Multiple Deployments and Upgrading Shilen Patel Duke University This work licensed under a Creative Commons Attribution-NonCommercial 3.0 Unported License.

Handling Multiple Deployments Upgrading Grouper 2 Contents

Problem You may have multiple environments – development, test, production You may use multiple components – Daemon, UI, WS, Client Difficult to manage all configuration files. 3 Multiple Deployments

Solution Automate build procedure for each component of each environment. Non-environment specific configuration can be saved in default configuration files. Environment specific configuration can be saved in a build script. Store modified configuration in a version control system. Follow best practices, such as encrypting passwords. Example from University of Pennsylvania: veral+environments veral+environments 4 Multiple Deployments (continued)

Release notes explain upgrade procedure in detail. Typical upgrade steps: Download new versions of each component. Merge configuration files and JARs. Stop Grouper Daemon and prevent updates. Run the change log job using the old API via GSH. Backup database. Run ‘-registry -check’ using new API and verify SQL file. Run ‘-registry -runsqlfile’. Initialize new data (sometimes) Start Grouper Daemon and deploy new components. 5 Upgrading Grouper

Click on the quiz link in the video description to reinforce your knowledge of this topic.quiz link 6 Quiz

Thanks! Further information: Infosheets, mailing lists, wiki, downloads, etc.: Grouper demo server: grouperdemo.internet2.edu/ grouperdemo.internet2.edu/ Grouper Online Training Home: spaces.internet2.edu/x/IIGfAQ This work licensed under a Creative Commons Attribution-NonCommercial 3.0 Unported License. 7

Next Video in Grouper Online Training is: Grouper Loader This work licensed under a Creative Commons Attribution-NonCommercial 3.0 Unported License.