The Components screen

The Server Tools Components screen provides the following information.

Type	Type of component to show in the table, one of the following: All types Batch Process Message Destination Startable Service
Name	Name of component. This name is the work queue name, or, the message destination name, for example.
State	State of the component, for example, Assigned, meaning that there is a server that has the lease to run this component.
Start Requested	Date and time that the server received the component start request.
Started	Date and start time of the component.
Owner	Server ID of the PolicyCenter server on which the component runs.
Lease Expiration	Date and time at which the component lease expires. See Cluster member shutdown for more information on component leasing.
Stopped	Stop date and time of the server instance on which the component is running, due to one of the following reasons: Server instance stopped as intended Server instance failed due to lost power or network connection and automatic recovery failed or is still in progress
Actions	PolicyCenter shows a Complete Failover button if a component lease expires and a custom failover plugin implementation instructs PolicyCenter not to perform an automatic failover. See Cluster member shutdown for more information.
Terminate Requested	Date and time at which the server instance received a terminate request for this component.
Transfer Requested	Date and time at which the server instance received a request to transfer this component to another server instance.
Transfer Target	Server ID of the server to which the transfer request was made.
Retry Failover	Date and time of the deadline in which to complete the failover process. If a lease manager detects the expiration of a component lease owned by another cluster member, the first lease manager starts a failover process for this lease. This failover process is not instantaneous. It is possible that during the failover process the cluster member performing the failover itself might fail, or lose database connection, or encounter other potential problems. To be able to handle this situation gracefully, the cluster member starting the failover gives itself a deadline to complete the failover process. If the current failover process does not finish by the specified timestamp, some other cluster member needs to start the failover process for the same component lease. See Automatic failover of a component lease for a description of how PolicyCenter calculates this timestamp.

You can view similar information to that of the Components table on the Cluster Members screen, the Components tab.

Available actions on this screen

The following list describes the actions that you can take in Cluster Members screen.

Action	Description
Download cluster server report	Click Download to download an HTML report of the cluster components and component history. See Download a server component report for details.
Filter by component type	Select a component type from the Types drop-down list to filter the information by a specific component type.
Filter by component state	Select a component state from the State drop-down list to filter the information by a specific component state.
Filter by component	Click Filter by Component to open a Select Components screen. In this screen, you can select individual components of all available types to show in the component table.
Refresh the component information	Click Refresh to update the server component information in the table.
Review component history detail	Click the name of a component to open a component history detail screen.