Users Guide

Step-By-Step Application Server Clustering | Clustering
120 OMNM 6.5.3 Installation Guide
Step-By-Step Application Server Clustering
The following is an example cluster. It includes application and web server on the same machine,
and mediation server on a different machine. Follow these general steps to install the first
application server in a cluster (the see
Installing Remaining Application and Web Servers on page
124 for additional servers):
Step 1: Install Application + Web Server 01 - Primary appserver (See the steps follow-
ing this overview.)
Step 2: Install Mediation Server 01- Primary medserver (See Installing Mediation Serv-
ers on page 123)
Step 3: Validate system is operational with above nodes
Step 4: Proceed with upgrading remaining Application Servers + Web servers:
– Application + Web Server 02
– Application + Web Server 03
Step 5: Proceed with upgrading remaining Mediation Servers:
– Mediation Server 02
– Mediation Server 03
and so on...
The following are more detailed steps:
NOTE:
Best practice for changing properties in the following steps typically assumes that you override the
mentioned properties with properties pasted in
owareapps/installprops/lib/
installed.properties
, rather than altered in the mentioned properties files. Make sure these
installed.properties files match, except for variables local to each host.
1
When installing, make sure you have permissions to execute the installation script. For Linux,
add the execute permission:
chmod +x linux_install.sh , and then execute ./
linux_install.sh.
2 Install the application with the Custom method. Often, this means selecting Application
Server and Web Portal to install on a single host.
1
3 For Linux, select the Link Folder (where startup links reside). Typically this is the installing
user’s Home.
NOTE:
The primary server is the first one in the current server view list. This is the first one join the cluster.
4
Specify an application server partition (it defaults to the hostname where you are installing),
and check
Auto Start (a best practice, but not required) .
2
5 Specify your server’s and portal’s heap settings.
6 Specify the Config Server’s IP address (the lowest address among clustered servers).
7 Select Oracle as the database type.
1. For upgrades, in owareapps/installprops/lib/installed.properties over-
ride the
oware.config.server (“primary server”) setup (originally in oware/lib/
owappserver.properties
). The “primary server” is the server in a cluster which starts
first.