Starting Clusters Durably

This application’s 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, you must modify the owareapps/lib/installprops/lib/installed.properties file with a text editor.

If you install without autostart selected, the required boot configuration in files on Solaris do not get updated rendering the pmstartall, pmgetstatus or pmstopall commands inoperable.

Starting, stopping and managing such installations uses the following scripts:

pmstartall (or startpm1)

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.process­monitor.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.

If you start a server in a remote shell, killing the shell can kill the server process.




  1. Tip: It’s often helpful to add nohup to this command line