Users Guide

General Information | Installing Distributed and HA Deployments
56 OMNM 6.5.3 Installation Guide
General Information
This section includes some general information about:
•
Distributed Installation
• Databases on Separate Servers
• Adding Mediation Servers
• High Availability and Clustering
Distributed Installation
A distributed installation requires the HA installer for your operating system. When you start the
installer, select the Custom installation option, and point to the same partition (by default named
for the Application server’s hostname concatenated with the word “partition”).
NOTE:
In distributed installations, by default, installing an Application server by itself means that the Mediation
server process (ordinarily included in stand-alone installations) is turned off. To turn on the Mediation
server, add the following property to the \owareapps\installprops\lib\installed.properties file:
oware.appserver.mediation.setup=true
Databases on Separate Servers
You can run loaddb after installing it and the run dbpostinstall to seed the components. Run
loaddb -s when the Web server is on a different host.
If your system’s Web server and Database server are on different machines, you must run
loaddb
-s
on the Web server host to create the Synergy/portal database.
Adding Mediation Servers
Often, such distributed installations use multicast to discover components. The command line
(startappserver or startmedserver) -m parameter specifies that mulitcast address, or you can specify
it in the owareapps\installprops\lib\installed.properties file with the following property for autostart
installations:
oware.application.servers=[Host IP address]
Multicast is optional. However, you can disabled it using the oware.application.servers property in
the owareapps\installprops\lib\installed.properties file if, for example, a firewall blocks multicast
between components. For example:
oware.application.servers= appserver_A_IPaddress , appserver_B_IPaddress
See Disabling Multicast on page 111 to disable multicast and for a way to configure the alternative
(a non-clustered Mediation server setup example also appears in
Installing Distributed and HA
Deployments
on page 55).
NOTE:
You can elect to ping Mediation servers before attempting to call a rule. This avoids the long timeout that
can occur when the Mediation server's network cable gets unplugged. To enable this, add a property
(
com.dorado.ping.medserver=true ) to installed.properties for each
Application server. Ping incurs some additional overhead incurred, so by default, the property is not set
and no ping occurs before rules.