Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This utility, when run via command line, is read-only; it does not make any membership changes in your database.  However, the daemon (see below) will actually fix any problems that are found.  Note that in 2.3, the daemon can be configured to run on a schedule.  In 2.4, the daemon is automatically configured to run at 1am.

Usage

As of Grouper v 2.1, this utility runs with GSH.

...

If bad memberships or groupSets are found, the utility will print a message to standard output.

Resolving bad memberships

If bad memberships are found in your Grouper database, a GSH script called findbadmemberships.gsh will be created to help you resolve the issues. 

...

  1. Review the GSH script before applying any changes to your database.
  2. Run the GSH script.
  3. Re-run the bad membership finder utility to verify that bad memberships have been fixed

Daemon

For Grouper 2.3+ (with API patch 56), there's a daemon that can find and fix bad/missing memberships.  Just enable the job and set a schedule in grouper-loader.properties.

Code Block
otherJob.findBadMemberships.class = edu.internet2.middleware.grouper.misc.FindBadMembershipsDaemon
otherJob.findBadMemberships.quartzCron = 0 0 1 * * ?


Query for bad composites

(assumes Grouper 2.0 grouper_memberships_lw_v):

...