Users Guide

Starting Clusters Durably | Clustering
132 OMNM 6.5.3 Installation Guide
Starting Clusters Durably
Clusters provide failover protection for the processes they maintain, or “high availability.” To
automate restarting this and other applications’ processes, install the application with process
monitor. To configure process monitor to start and stop clusters if you have not installed electing
autostart, you must modify the
owareapps/lib/installprops/lib/
installed.properties
file with a text editor.
Starting, stopping and managing such installations uses the following scripts:
•
pmstartall (or startpm
1
)
•
pmstopall
• pmgetstatus (displays the system’s status as proccess monitor knows it.)
The command line includes the host IP address and port:
pmstartall -h <server IP> -p <port>
Defaults are for server IP and port are localhost and 54321. (Though you can use the host name,
best practice is to use the server IP address.) To see all available command line options, run the
above commands with
-? as a parameter.
You can override the administrative port of Process Monitor (originally in the property file
owmisc.properties) by setting the property
com.dorado.core.processmonitor.remoteCmdPort to the desired numeric value. If this
port number is changed, all process monitor clients must send requests to the changed port
number value.
CAUTION:
If you start a server in a remote shell, killing the shell can kill the server process.
pmstartup.dat
The text file /oware/lib/pmstartup.dat manages restart frequency if your application server
starts automatically. For more information about using this file, consult the comments within the
file itself.
Recovery Procedure
The procedure for recovery from server failure is automated. If something other than server failure
is at the root of a cluster’s failure, you must stop any running server the process manager, as follows:
pmstopall <hostname> <port>
The process manager automatically restarts the failed server.
Temp Directory Deletion
Starting your application server may be inhibited by corrupted files in \oware\temp\ . This is
identified when the application / mediation server does not start successfully and reports a probable
JMS startup failure. Delete the contents of the
oware\temp\ and restart. Unfortunately, when
this directory’s contents are deleted and you are using a cluster, you must restart the entire cluster.
1. Tip: It’s often helpful to add nohup to this command line