Click Devices > Identity Servers > [Name of Server] > Health.
For more information about the icons, see Section 27.1, Health States.
To ensure that the information is current, select one of the following actions:
Click Refresh to get the latest health available from Administration Console.
Click Update from Server to send a request to Identity Server to update its status information. This can take a few minutes.
Examine Services Detail that displays the status of each service.
|
Status Category |
If not healthy |
|---|---|
|
Status: Whether Identity Server is online and operational. |
Verify whether Identity Server has been stopped or is not configured. Verify that network problems do not interfere with communications between Identity Server and Administration Console. |
|
Services: The general health of all configured services. |
If one service is unhealthy, this category reflects that status. See the particular service that also displays an unhealthy status. |
|
Identity Server Configuration: The status of the configuration. |
Configure Identity Server or assign the server to a configuration. See Configuring Identity Servers Clusters |
|
Configuration Datastore: The status of the installed configuration datastore. |
You might need to restart Tomcat or reinstall Administration Console. If you have a backup Administration Console, you can restore it. See Back Up and Restore. If you don’t have a backup, try repairing the configuration datastore. See Repairing the Configuration Datastore. To convert a secondary console to primary console, see Converting a Secondary Administration Console into a Primary Console. |
|
User Datastores: Whether Identity Server can communicate with the user stores, authenticate as the admin user, and find the search context. |
Ensure that the user store is operating and configured correctly. You might need to import the SSL certificate for communication with Identity Server. See Section 2.2, Configuring Identity User Stores. |
|
Signing, Encryption and SSL Connector Keys: Whether these keystores contain valid a key. |
Click Identity Servers > Edit > Security and replace any missing or expired keys. |
|
System Incoming and Outgoing HTTP Requests: Appears when throughput is slow. This health check monitors incoming HTTP requests, outgoing HTTP requests on the SOAP back channel, and HTTP proxy requests to cluster members. If one or more requests remain in the queue for over 2 minutes, this health check appears. |
Verify that all members of the cluster have sufficient bandwidth to handle requests. If a cluster member is going down, the problem resolves itself as other members of the cluster are informed that the member is down. If a cluster member is slow because it does not’ have enough physical resources (speed or memory) to handle the load, upgrade the hardware. |
|
SSL Communication: Indicates whether SSL communication is operating correctly. This health check appears only when the SSL communication check fails. |
Check SSL connectivity. Check for expired SSL certificates. |
|
Audit Logging Server: Whether the audit agent is functioning and able to log events to the auditing server. Auditing must be enabled on Identity Server to activate this health check (click Devices > Identity Servers > Edit > Auditing and Logging). |
Check the network connection between Identity Server and the auditing server. |
Click Close.