Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
| Table of Contents | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Here are key places in the Grouper documentation and training with information on operational considerations:
- Tools & Topics for Ongoing Administration
- Ongoing Administration Tasks
- Grouper Training - Admin - Maintenance - Take 1
- Grouper high availability
- Grouper diagnostics
- Grouper report
You can monitor the health of the Grouper using the Grouper diagnostics URLs at http://{hostname}/grouper/status?diagnosticType=[trivial|db|all] for the Grouper UI, and http://{hostname}/grouperWS/status?diagnosticType=[trivial|db|all] for Grouper WS. If everything is ok, a 200 HTTP code will be returned, otherwise a 500 is returned with a description of the issue. The diagnostic URL has many options and is suitable for monitoring by systems like Nagios, Big Brother, etc. If you do not see the word SUCCESS on the “all” page, then something is wrong. Have monitoring tools like Nagios look for SUCCESS.
Use the Unresolvable Subject Deletion Utility (USDU) to clean up membership assignments for subjects that are no longer resolved by the Subject API.
Grouper Deployment Guide
- Executive Summary
- Introduction to the GDG
- Understanding Grouper
- Operational Considerations
- Access Control Models
- Provisioning Models
- Operational Considerations
- Conclusion
- Example Access Policies
Related content
| Content by Label | ||||||
|---|---|---|---|---|---|---|
|
Get help
Can't find what you are looking for?
| Button Hyperlink | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Previous: Provisioning Models
Next: Conclusion