HEARTBEAT_ACTIVATION_PERIOD

Parameter: HEARTBEAT_ACTIVATION_PERIOD_COUNT

Definition

The number of polling periods of inactivity after which the heartbeat mechanism is activated

Description and Use

The heartbeat mechanism is in charge of checking whether the instances are still alive by pinging them at regular intervals. To avoid network congestion, this mechanism is activated if a connection has not been used for a while. The HEARTBEAT_ACTIVATION_PERIOD_COUNT parameter specifies the number of polling periods of inactivity after which the heartbeat mechanism is activated.

Example

If HEARTBEAT_POLLING_PERIOD=2s and HEARTBEAT_ACTIVATION_PERIOD_COUNT=2 then the heartbeat mechanism tests a connection only if it was unused for 4 seconds.

Notes

The activation timeout equals (number of periods * HEARTBEAT_POLLING_PERIOD).
A similar parameter exists on client side through the com.highdeal.cnd.message.ServiceClientTuning class. Please consult this class documentation and the SAP CC Java API Reference (Javadoc) for more information and user assistance.

Syntax and Constraints

This parameter must be greater than or equal to 0.

Defined Constraints

The SAP CC Core Server system verifies the following constraints:

Instance Type	Constraint
Rater instances	The parameter must be greater than or equal to 0 .
Updater instances	The parameter must be greater than or equal to 0 .
Guider instances	The parameter must be greater than or equal to 0 .
Bulkloader instances	The parameter must be greater than or equal to 0 .
Taxer instances	The parameter must be greater than or equal to 0 .
Dispatcher instances	The parameter must be greater than or equal to 0 .

Technical Details

For more information, consult this section.

Name

HEARTBEAT_ACTIVATION_PERIOD_COUNT

The number of polling periods of inactivity after which the heartbeat mechanism is activated

Category Parameter

Type Integer

Access (RO/RW)

RW(-): Dynamic Read / Static Write

An immediate change is not possible. For a deferred and permanent change, use the set command of the Admin+ user interface to change the parameter value for a specific type of instance in the SAP CC Core Server system. A restart is needed for permanent changes.

Groups

System: Network and Communication

Instance Types

This system parameter is available in the following types of instances in a running SAP CC Core Server system:

rater, updater, guider, bulkloader, taxer, dispatcher

Default Values (Factory Settings)

The predefined default values are:

Instance Type	Value
Rater	`1`
Updater	`1`
Guider	`1`
Bulkloader	`1`
Taxer	`1`
Dispatcher	`1`

You can use a default value to reset the runtime value or the restart value (persistent) in the Admin+ user interface.

Note

A default value is part of the factory settings of the SAP CC Core Server systems. It differs from the original value set during the installation or after the Customizing activities.

In Admin+, you can reset a parameter value to this default value, but it is not recommended:

This value may differ from the original value set during the installation of your SAP CC system.
Note that it may also differ from the value defined by the implementation project team and set during the Implementation Phase of the integration project.

Verify the values in your running SAP CC systems before to use the reset command.

Constraints

The SAP CC system checks the following constraints:

Rater instances	The parameter must be greater than or equal to 0 .
Updater instances	The parameter must be greater than or equal to 0 .
Guider instances	The parameter must be greater than or equal to 0 .
Bulkloader instances	The parameter must be greater than or equal to 0 .
Taxer instances	The parameter must be greater than or equal to 0 .
Dispatcher instances	The parameter must be greater than or equal to 0 .