Step-By-Step Application Server Clustering

Follow these steps to cluster an application server:

[spacer]

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 altered than in the mentioned properties files.

1. Install the application with the Custom method. If you are working with a previous installation, modify the database host name in owareapps\installprops\lib\installed.properties (overriding properties originally in owdatabase.properties).

You can validate these for a new installation. For an existing installation using MySQL, you must override two database properties for each of these initial steps. For example (if huey is the database host:)

com.dorado.meta_database.name=//huey:3306/owmetadb

com.dorado.jdbc.database_name.mysql=//huey:3306/owbusdb

MySQL is the default, embedded database. Comment the MYSQL line for the com.dorado.bom_dbms.name property, and override with uncommented Oracle line for that database.

The following properties are configured by the installer when you select an Oracle installation. You can validate that installation has correctly configured the overriding installed.properties file with the following properties for your Oracle database:

#z‘#com.dorado.jdbc.database_name.oracle=@host:port:SID

#com.dorado.jdbc.database_name.oracle=@mydbserver1:1521:mydb1sid

2. 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.

3. Optionally, you can confirm that the following SonicMQ jms properties in /oware/lib/owjms.properties or in \owareapps\installprops\lib\installed.properties (you must eventually do this in both servers and clients).

jms.provider=SONICMQ

jms.qf=QueueConnectionFactory

jms.tf=TopicConnectionFactory

com.dorado.eventchannel.VendorInitFactoryClass.sonicmq=com.dorado.core.jms.OWSonicMQInitFactory

com.dorado.jms_vendor.port.sonicmq=2506

com.dorado.eventchannel.protocol.sonicmq=tcp://

[spacer]

After making the change to the above properties, you must re-source the Oware Environment. Do not override these uncommented properties. Uncomment them in the owjms.properties file itself. You must do this in Application and Mediation Servers, and in Clients connected to your installation.

4. If the server does not have to receive traps (typical for a distributed application where the mediation server receives the traps), comment the following properties in oware/lib/owappserver­startup.properties file,

oware.server.startup.class=\

 

#com.dorado.core.mediation.snmp.OWSnmpSRTrapListenerMBean,\

#com.dorado.core.mediation.snmp.OWSnmpSRInformListenerMBean,\

[spacer]

Insert a blank line between property name and the properties as shown above.

5. The start command is now 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.

You must do these steps on all application servers.