Grouper changes v2.2

This document lists instructions for people with existing groups installations on how to upgrade to newer versions of grouper (or grouper related products).  If you notice something missing please let us know.  The instructions are in descending order based on date/release.  You will find instructions below for Grouper, Grouper-ws, Grouper-ui, etc.  It is assumed if you are running grouper-ui that you will perform both the grouper upgrade notes, and the grouper-ui upgrade notes.  It is understood that you will get the new source/javadoc/etc files, this document addresses configurations, jars, etc.  

Grouper

• v2.1.2: Update the grouperClient.jar
•  

Grouper UI

•  The status servlet is available in the UI.  If you want to take advantage of this, you might need to map a new URL if your diagnostics app (e.g. nagios) cannot authenticate.  on the demo server this is what was changed in the apache config, then bounce apache, and you can see status here: https://grouperdemo.internet2.edu/grouperstatus_v2_2/status?diagnosticType=sources

FROM:

ProxyPass /grouper_v2_2/ ajp://localhost:8111/grouper_v2_2/



TO: (note, new config is above old config since more specific, to avoid apache warning)

# unauthenticated status
ProxyPass /grouperstatus_v2_2/status ajp://localhost:8111/grouper_v2_2/status

ProxyPass /grouper_v2_2/ ajp://localhost:8111/grouper_v2_2/

Grouper WS

• The status servlet moved to the API, if you use this, migrate any configs from the WS config to the API config.  Note, the config keys did not change.

Subject API

• v2.2: If you implement a custom source which does not extend the BaseSourceAdapter, you will need to recompile your source with change for realms
  

Grouper Client