Server Status

Each server collects performance data and status information for several subsystems. Since the system may consist of hundreds of geographically diverse servers, you need the ability to monitor this data and quickly isolate problems.

There are several aspects to monitoring server status. You can monitor the administrative state of each server in the system, as well as the status of the alarms, replication, collection, high availability, database, and process systems on each server.

The Application State field for each server displays the current administrative state of the application running on that server. Stopping application software places it in the Disabled Application State. Restarting application software places it in the Enabled Application State. Servers that are restarted by clicking Restart restart all application processes, regardless of their current state.

Note:

Enabled and Disabled are administrative states. They do not reflect the current status or running state of the application software.

The Collection subsystem gathers status and alarm information from all other subsystems. Each of these subsystems reports varying degrees and severities of status. The status reported is not the same between subsystems. For this reason, the Server Status page provides a common status reporting framework to help identify problems at a server level.