Configuring Message Server
Communication
Message server communication is established through the message server that is used as a dispatcher when sending messages. The advantage of this way of communication is that it provides a failover function that avoids the loss of information.
Use this procedure to configure the default settings of the message server communication.

We recommend that you do not modify the default message server communication settings unless you are advised to do so by SAP Support.
...
1. Start the Config Tool.
2. Set the View in Expert Mode.
3. Choose cluster-data→ template → instance - <n> → managers → ClusterManager.
4. From the list of properties, select the property you want to modify:
○ ms.host to specify the host (IP address,) where the message server is running.
○ ms.port to specify the port on which the message server listens for connections.
○ ms.message.pool.size to define the size of the message library pool.
○ The size of this pool can be changed for optimization purposes.
○ ms.confirmation.timeout to specify the timeout period that a joining cluster node waits for the confirmation replies from the cluster participants.

Modify the value of this property if you receive an error message during cluster startup indicating that there are errors when getting a confirmation message due to nonresponding cluster elements and the node is rebooted.
○ ms.keepalive to increase the time the system waits before triggering a liveliness check (ping/pong protocol) event if there has been no communication between a cluster node and the message server.
○ ms.reconnect.timeout to increase the time period during which you can reconnect to the message server. After this time elapses, you are no longer able to reconnect to the message server.
5. In the Custom value field, set the required value.
6. To apply the new value, choose Set.
7.
To save the
changes, choose
Apply
changes.
8. For the changes to take effect, restart the cluster.