Parameter: HEARTBEAT_ACTIVATION_PERIOD_COUNT
Definition
Description
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.
Range: This parameter must be greater than or equal to 0.
Detailed Information
| Name | HEARTBEAT_ACTIVATION_PERIOD_COUNT
|
|||||||||||||
| 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 |
|||||||||||||
| Group(s) | System: Network and Communication | |||||||||||||
| System Instances | This system parameter is available in the following types of instances in a running SAP CC system: rater, updater, guider, bulkloader, taxer, dispatcher | |||||||||||||
| Default Values (Factory Settings) |
|
|||||||||||||
| Constraint(s) |
The SAP CC system checks the following constraints:
|
|||||||||||||
