IBM BPM, V8.0.1, All platforms > Reference > User interface help reference > Widgets for Process Portal spaces > Administration widgets
System Health
Use System Health to view a snapshot of the overall system health of your business solution. This widget provides a single place from which you can quickly assess the status of application servers, nodes, clusters, deployment environments, messaging engines and their queues, databases, system applications, and failed events.
Tabs
The System Health widget displays the status of and information about the following items on your system, organized into tabs for easy browsing.
- Topology tab
- Deployment environments
- Lists the status of all deployment environments on the system that match any filter criteria you specified. If you specify no criteria, all objects are displayed.
- Clusters
- Lists the status of all clusters on the system that match any filter criteria you specified. If you specify no criteria, all objects are displayed.
- Standalone servers
- Lists the status of all standalone servers on the system that match any filter criteria you specified. If you specify no criteria, all objects are displayed.
- Node agents
- Lists the status of all node agents on the system.
- System Applications tab
- System applications
- Lists the status of Business Process Choreographer, Common Event Infrastructure (CEI) and Service Component Architecture applications and services configured on your system (for example, the failed event manager, Business Process Choreographer containers, and the Event Service), as well as Business Space widgets and the Business Space Manager.
- System data sources
- Lists the data sources that match any filter
criteria you specified. If you specify no criteria, System Health
displays all data sources on the system, including the Common database, the Business Process Execution database, the Common Event Infrastructure
database, and the Service Integration Bus database.
The widget does not provide accurate status information for the following types of data sources:
- Custom data sources or support cluster data sources that were not configured as part of the deployment environment. These data sources are not listed in the widget.
- A data source whose authentication alias is not set. In this case, the data source is listed in the widget but its status is Unavailable.
Use the administrative console to determine the actual status, as described in
Test connection problems for messaging engine data sources.
- System messaging engines
- Lists the messaging engines configured on the system and application buses (SCA.SYSTEM. busID.Bus, SCA.APPLICATION. busID.Bus, CEI. cellName.BUS, and BPC. cellName.Bus).
- Applications tab
- Applications
- Lists enterprise applications installed on the system that match any filter criteria you specified. If you specify no criteria, all objects are displayed.
- Failed event count tab
- If the Recovery subsystem is enabled, lists the number of failed events.
- Queues tab
- Queue depth
- Displays current queue depth for the messaging point. If not all messaging engines are running, only partial queue depth is available. Use the radio buttons to select the subset of queues you want to display in the System Health widget.
Status icons
Status for application servers, nodes, clusters, deployment environments, messaging engines, databases, and system applications are indicated by the following icons.
| Status | Icon |
|---|---|
| Running |
|
| Stopped |
|
| Unavailable |
This status can occur when the node manager is not running in a deployment environment, or when you have not set an authentication alias for a data source. |
- Configure System Health
Use the optional configuration parameters in the System Health widget if you want to customize the content displayed in the widget and the rate at which that content is refreshed. - Determining system health
Use the System Health widget to quickly assess the status of application servers, nodes, clusters, deployment environments, messaging engines and their queues, databases, and system applications on your system, and to determine if there are any outstanding failed events that need further attention.