Configuring the Message Server
Communication
Use
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 officially advised to do so by SAP support.
Procedure
...
1.
Start the
J2EE Engine Visual
Administrator.
2. Choose Dispatcher/Server → Kernel → Cluster Manager → Properties tab.
3. Modify the values of the following properties:
a. Use ms.hostto specify the host (IP address,) where the message server is running.
b. Use ms.portto specify the port, on which the message server listens for connections.
c. Use ms.message.pool.size to define the size of the message library pool.
The size of this pool can be changed for optimization purposes.
d. Use 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 non-responding cluster elements and the node will be rebooted.
e. If necessary, you can 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. To do so, modify the value of the ms.keepalive property.
f. Use ms.reconnect.timeoutto 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.
4.
Choose 
Save Properties to save your changes
and restart the cluster node.
See also: