Service Category |
If Not Healthy |
---|---|
Reverse Proxy - <Proxy Service Name>: Indicates the general health of all configured proxy services. A separate row is created for each proxy service. |
Check the health of the web server. |
AGM - Configuration: Indicates whether all configuration changes have been applied. |
Do the following:
If the issue persists, view the Apache error.log file to discover the cause. The file is located in /var/log/novell-apache2/. |
TCP Listener - <IP Address:Port>: Indicates whether Access Gateway Service is listening on the specified port. A separate row is created for each port the Gateway Service is configured to listen on. |
Restart the Apache service. |
ApacheGateway.log: Appears when Access Gateway Service is not healthy. It displays the latest error from the Apache error.log file. |
View the error.log file in /var/log/novell-apache2/. |
Embedded Service Provider Configuration: Indicates whether Access Gateway has been configured to trust an Identity Server and whether that configuration has been applied. At least one Identity Server must be configured and set up as a trusted authentication source for Access Gateway. A green status indicates that a configuration has been applied; it does not indicate that it is a functioning configuration. |
See Managing Reverse Proxies and Authentication for information about assigning an Identity Server configuration to Access Gateway. |
Configuration Datastore: Indicates whether the configuration datastore is functioning correctly. |
Restore the configuration datastore. See Repairing the Configuration Datastore. |
Clustering: Indicates whether all the cluster members are active and processing requests. |
Restart the cluster members that are not active or remove them from the cluster. |
Signing, Encryption and SSL Connector Keys: Indicates whether these keystores contain a valid key. |
Click Access Gateways > Edit > Service Provider Certificates 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 goes down, the problem is resolved as other members of the cluster are informed that a member is down. If a member is slow because of insufficient physical resources (speed or memory) to handle the load, upgrade the hardware. |
TCP Listener(s): Indicates whether the listening port for ESP is healthy. |
Restart Access Gateway. |
Embedded Service Provider’s Trusted Identity Provider: Indicates whether the configuration that Access Gateway trusts has been configured to contain at least one Identity Server. |
Modify Identity Server configuration and add an Identity Server. Configure Access Gateway to trust an Identity Server configuration. See Creating a Proxy Service. |
Audit Logging Server: Indicates 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 auditing server. |