Monitoring CCM server health
![](http://jazz.net/_images/myphoto/a6550612453705f0fd7f4f35e1a7cc9e.jpg)
2 answers
![](http://jazz.net/_images/myphoto/a6550612453705f0fd7f4f35e1a7cc9e.jpg)
If you are trying to find a good URL that would test the most major components.
A good choice would be the one to capture the list of users.
e.g: https://<server>:<port>/<contextroot>/admin#action=com.ibm.team.repository.manageUsers
This is a great 'double' test that will exercise both your webserver, RTC instance, and your DB instance.
Because this list of users is dependent a connection point between RTC and your database.
If you wanted to capture diagnostic details results, this is another good URL to check.
https://<server>:<port>/<contextroot>/admin#action=com.ibm.team.repository.admin.serverDiagnostics
A good choice would be the one to capture the list of users.
e.g: https://<server>:<port>/<contextroot>/admin#action=com.ibm.team.repository.manageUsers
This is a great 'double' test that will exercise both your webserver, RTC instance, and your DB instance.
Because this list of users is dependent a connection point between RTC and your database.
If you wanted to capture diagnostic details results, this is another good URL to check.
https://<server>:<port>/<contextroot>/admin#action=com.ibm.team.repository.admin.serverDiagnostics