Users Guide

Cluster Constraints | Clustering
112 OMNM 6.5.3 Installation Guide
5 And Uncomment
<!-- Alternative 2: non multicast-based replacement for MPING. Requires
a static configuration of *all* possible cluster members.>
<TCPPING timeout="3000"
initial_hosts="${jgroups.tcpping.initial_hosts:localhost[7600],local
host[7600]}"
port_range="1"
num_initial_members="3"/-->
CAUTION:
Make sure you modify stack "tcp" section, not "tcp-sync" section
Example:
<!--Alternative 1: multicast-based automatic discovery.
<MPING timeout="3000"
num_initial_members="3"
mcast_addr="${jboss.partition.udpGroup:230.11.11.11}"
mcast_port="${jgroups.tcp.mping_mcast_port:45700}"
ip_ttl="${jgroups.udp.ip_ttl:2}"/>
-->
Alternative 2: non multicast-based replacement for MPING. Requires
a static configuration of *all* possible cluster members.>
<TCPPING timeout="3000"
initial_hosts="${jgroups.tcpping.initial_hosts:localhost[7600],local
host[7600]}"
port_range="1"
num_initial_members="3"/
6 Start appserver
Disabling Multicast within a Cluster
Disabling multicast may be useful if a firewall exists between Java clients, application servers or
mediation servers that must discover each other. (See also Configuring the Cluster’s Multicast
Address on page 196.) Application-to-mediation server communication does not use multicast,
although mediation-to-application server does, unless disabled.
To disable multicast communication between application and mediation servers, define the
property oware.application.servers in the installedprops/medserver/lib/installed.properties file and
the property should point to the application server ip address and should be in the following
format:
oware.application.servers=<application server ip address>