# System Administrator’s Guide

# Configuring Heartbeats

The following section describes how to configure heartbeats for HTTP-based stateless network protocol plug-ins.

- Configuration and Management
- Reference: Attributes and Operations for HeartbeatConfiguration

## Introduction

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:

- Plugin_px21_multimedia_messaging-HeartbeatConfiguration
- Plugin_ews_push_message_papHeartbeatConfiguration
- Plugin_px21_terminal_location_mlp-HeartbeatConfiguration

- 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.

Note: | 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.

1. Specify if heartbeats should be enabled for the associated plug-in or not in Attribute: Enabled.
2. If heartbeats are enabled, define:

Attribute: ContentMatch

Attribute: Interval

Attribute: NetworkServiceUrl

## Reference: Attributes and Operations for HeartbeatConfiguration

Managed object: HeartbeatConfiguration

MBean: om.bea.wlcp.wlng.heartbeat.management.HeartbeatMBean

Below is a list of attributes for configuration:

- Attribute: ContentMatch
- Attribute: Enabled
- Attribute: Interval
- Attribute: NetworkServiceUrl
- Attribute: Status (r)

### Attribute: ContentMatch

Scope: Cluster

Unit: n/a

Format: String

The content for matching the returned heartbeats. If the returned string differs from this, the heartbeat is assumed to have failed. Leave this empty to match any content.

### Attribute: Enabled

Scope: Cluster

Unit: n/a

Format: Boolean

Specifies if the heartbeat functionality is applied for the plug-in.

### Attribute: Interval

Scope: Cluster

Unit: seconds

Format: integer

Specifies the time interval between heartbeats.

### Attribute: NetworkServiceUrl

Scope: Cluster

Unit: n/a

Format: String

Specifies the URL to which heartbeats are sent.

### Attribute: Status (r)

Scope: Cluster

Unit: n/a

Format: boolean

Read-only.
If true, there was a successful response to the last heartbeat. If the previous Status was false, the plug-in state is altered from INACTIVE to ACTIVE.
If false, there was no or an incorrect response to the last heartbeat. In this case the associated plug-in is set state INACTIVE and an alarm is generated.