Users Guide

Step-By-Step Application Server Clustering | Clustering
122 OMNM 6.5.3 Installation Guide
This installation program does not automatically create the database
structure required by the application. This is a manual task that may
require some initial MySQL database administration.
15 Create OpenManage Network Manager and Portal Tablespaces: loaddb -u system -w
d0rad0 -s
16 Modify Portal-ext.properties
Go to
/opt/dorado/oware/synergy/tomcat-7.0.30/webapps/ROOT/WEB-INF/
classes
, and edit the file portal-ext.properties .
oware.appserver.ip=127.0.0.1
medserver.support=true
This tells the web server to use local application server. By default, mediation control is off.
Adding
medserver.support=true enables mediation control in the control panel.
17 Start the application server with command #/etc/init.d/oware start
This command is equivalent to startpm , which starts both application server and its process
monitor. The command
pmstartall only starts application server. See Starting Clusters
Durably
on page 132 for more about these.
18 Use the tray icons in Windows, or in Linux ./oware status, to check whether the server
is already running.
19 When the application server is ready, start the web server (in Windows, right-click the Apache
icon, in a Linux shell, type
#etc/init.d/synergy start.)
20 If you are upgrading, reindex all search indexes. Login to the current web server, Go to
Control Panel > Server > Server Administration and click Execute next to Reindex all search
indexes
.
NOTE:
Because of an issue with the open source Portal classes, you must reindex every time you upgrade.
21
In Control Panel’s Portal Settings panel, change the Virtual Host field to the IP of the load
balancer or to the local server IP if not using load balancer.
1
Do these steps on all application servers.
Starting the Cluster
To start the cluster, first start the config server, then after it has started completely start another
server. Continue to wait until servers are completely started to add others to the cluster. You can
start a distributed database server at any time (before or after) this process, but you must start
distributed mediation servers and clients after the application server cluster starts. In mediation
server clusters, you must also start the primary server first.
If you do not elect to autostart (not recommended), the start command looks something like the
following:
startappserver -c [Config Server] -p [ClusterName] -m [multicast address]
for example:
startappserver -c 192.168.6.11 -p appcluster -m 225.0.0.1
For an alternative startup, see Starting Clusters Durably on page 132.
1. Even when using the load balancer, the installer defaults the virtual host IP to the applica-
tion server IP that we set up in portal-ext.properties. However, we want the virtual host IP to
be the public facing IP (IP address that end users connect to), which is the load balancer IP.