The Cluster Explorer figure above shows the hierarchy of cluster members. Inactive agents (which could be standby agents or failed agents) are dimmed.
Engines that are not defined in the site topology file are known as unpredefined engines. There are some differences between predefined and unpredefined engines.
Note that if you start a predefined TIBCO BusinessEvents engine at the command line (outside of MM) and you use a different JMX port from the one specified in the topology file, the engine starts as an
unpredefined engine.
Part of cluster health is checking to see that all members are running. When a member becomes inactive, Cluster Explorer and other parts of the MM Console displays a visual indicator. Standby agents in a fault tolerant group display as inactive, as well as cluster members that have stopped operating.
If a machine is inactive, processes and agents on that machine are also marked as inactive. Similarly, if a process is inactive, agents running in that process are also marked as inactive.
When a cluster member is inactive, you can still view the last available data in the panel for that member, but overlaid with a gray panel with the label: "Entity Inactive".
When a cluster member is inactive, and a pane relating to that member has been promoted to the Cluster Overview panel, the pane displays in gray with a message:
Inactivity is determined by the unsuccessful return of a health ping. Health pings are set up for machines and processes only. Process pings use JMX. Machine pings use TIBCO Hawk. If TIBCO Hawk is not available, cluster health status is determined using the health status of the processes (TIBCO BusinessEvents engines) running on each machine.