| Include Page | ||||
|---|---|---|---|---|
|
Here are guidelines on for maintaining your Grouper implementation, including suggestions ot help keep your database manageable.
Pruning Logs and Registry
Pruning the Change Log
When updates are made in Grouper (group add, membership add, etc), updates are also made to the temp change log (grouper_change_log_entry_temp) as part of the same transaction. The Grouper Daemon later (by default every minute), moves these changes to grouper_change_log_entry with sequence numbers and also adds flattened notifications and permission notifications.
...
Grouper has several tables that have names starting with "grouper_pit_" that are used to store point in time data. These tables are populated by the Grouper Daemon. If an object has been deleted from Grouper, the object remains in the point in time tables with an end date. Using GSH, you can delete objects in the point in time tables that have end dates. See Point in Time Auditing.
Pruning the Registry
*****Chris please add content here, for example on deleting old course groups Additional information to added:****
Monitoring Various Grouper Functions
- Using rules to send notifications by email (Emily/Shilen)
- Setting up XMPP notification (Shilen)
- Pruning the registry, for example to delete old course groups (Chris)
- Set up Nachos to check the web service status page to be sure the daemons are running (Chris)
- Be sure your logs email you so you can see when people have errors (Chris)
- Set up a recurring meeting in Outlook that says "Go change a Confluence group and be sure the XMPPs are still going across" (Chris)
- Check the daily Grouper Loader report (Chris)
Setting up Notifications
asdf