Users Guide

Verifying Clustered Installations | Clustering
130 OMNM 6.5.3 Installation Guide
Follow these steps to configure Mediation server clusters:
1 (For MySQL installations only) If the installation has not already done so, override the
database host name originally specified in
oware/lib/owdatabase.properties .
2 Set oware.config.server in owareapps/installprops/medserver/lib/
installed.properties
, setting it to the primary mediation host’s name (for example:
aaron ).
3 This property needs to be enabled only if the MBeans (Trap / Data Collection) is in
Forwarding/Standby Mode so that mediation servers work as peers and have listener failover
capability.
com.dorado.mediation.listener.use.high.availability=true
An HA “cluster” consists of only two mediation servers. You can have more than two, but that
just enables more than one standby server (something we do not test). If you set the
HAproperty to false, all clustered mediation servers are active at the same time, and any
number of mediation servers can be in the same cluster.
4 Mediation server peers use a multicast address for communication. If the server requires
another mediation server peer setup, change this multicast address for that peer.
com.dorado.mediation.listener.multicast.intercomm.address=228.0.0.200
For an alternative to multicasting, see Disabling Multicast on page 111.
5 An example of the mediation cluster’s start command:
startmedagent -c PrimarymedServer (aaron) -a primaryappserver (laika) -p
ClusterName (qacluster) -m address (228.0.0.200)
For an alternative startup, see Starting Clusters Durably on page 132. Remember, start the
primary first. Wait until it has completely started before starting the secondary.
NOTE:
When setting up a failover mediation cluster in owareapps/installprops/medserver/
lib/installed.properties
, do not set up an application server cluster for the mediation
servers. The config server for these mediation clusters is the same machine the individual mediation
server runs on.
Independent and Clustered Mediation Agents
Mediation clusters can failover for traps. When you have independent or clustered mediation
agents that communicate with a cluster of application servers, you must still follow these steps:
1 By default oware.config.server in owareapps/installprops/medserver/lib/
installed.properties
, is localhost IP address. (This is different for each mediation
server, rather than the same for a mediation server cluster.)
2 (For MySQL installations only) Modify the database hostname, using owareapps/
installprops/medserver/lib/installed.properties
to override oware/lib/
owdatabase.properties
.