The heartbeat functionality performs heartbeat checks towards HTTP based network nodes on behalf of a plug-in. When a heartbeat fails, the plug-in is set to state INACTIVE. The heartbeat functionality will continue trying to connect to the node and when a positive answer is received the plug-in re-enters state ACTIVE.
The following network protocol plug-ins use this functionality:
Parlay X 2.1 Short Messaging/MLP
Extended Web Services WAP Push/PAP
Parlay X 2.1 Multimedia Messaging/MM7
Configuration and Management
The heartbeat OAM functionality is shared among the plug-ins. They all use the same MBean, com.bea.wlcp.wlng.heartbeat.management.HeartbeatMBean. But the result is rendered per plug-in (one instance is displayed per plug-in). It appears slightly differently depending how to the MBean is accessed:
Using the Management Console, one instance of the OAM is displayed in connection with the plug-in it is used by, so the management attributes for the heartbeat module are reached from the service:
In an MBean browser, such as JConsole, one instance of the MBean is displayed using the the same ObjectName (at the same hierarchical level) as the plug-in it is used by.
You need to configure heartbeat attributes for all of the above mentioned plug-ins that are going to use this functionary. Only the heartbeat attributes for the related plug-in are displayed in the OAM.
Specify if heartbeats should be enabled for the associated plug-in or not in Attribute: Enabled.