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 for additional servers):

Step 1: Install Application + Web Server 01 - Primary appserver (See the steps following this overview.)

Step 2: Install Mediation Server 01- Primary medserver (See Installing Mediation Servers)

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:

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.bin, and then execute ./linux_install.bin.

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.

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.

8. Specify the database access information (User, Password, Host, Port, SID).

9. Click the Install button.

10. For Linux, when prompted, run the command /opt/dorado/install/root/setup.sh as root, and then click on Next.

11. If you have elected to autostart, select No when asked to start the server now.

12. In Linux, run the command /etc/init.d/synergy stop as root to shutdown the web server. The web server auto starts with the auto start installation option. The previous step only applied to the application server.

13. Test the database connection with pingbd.

pingdb -u system -p d0rad0

The d0rad0 password is an example in these steps.

14. For an installation that upgrades from a previous version, run oraclepostinstall

For a fresh installation, create Redcell Synergy tablespaces with this command:

loaddb -u system -w d0rad0

Seed the Redcell Synergy tables with this one:

ocpinstall -s

with the -s parameter, the installer will creates two new tablespaces for Redcell Synergy and portal called owsynergy01 and owportal01. Without -s it drops and recreates the Redcell tablespaces called owdata01 and owidx01. Dropping owdata01 results in the loss of all existing Redcell data.

15. Create Redcell Synergy 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 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.

Because of a portal issue, 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.3

You must do these steps on all application servers.




  1. For upgrades, in owareapps/installprops/lib/installed.properties override 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.
  2. If the server does not have to receive traps (typical for a dis­tributed application where the mediation server receives the traps), comment the following properties in oware/lib/owappserverstartup.properties file, oware.server.startup.class=\ #com.dorado.core.mediation.snmp.OWSnmpSRTrapListenerMBean,\ #com.dorado.core.mediation.snmp.OWSnmpSRInformListenerMBean,\ Insert a blank line between property name and the properties as shown above.
  3. Even when using the load balancer, the installer defaults the virtual host IP to the application 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.