Broker 10.5 | webMethods Broker Documentation | Running webMethods Broker in a High-Availability Windows Enterprise Server Cluster | Installation and Configuration | Configure the webMethods Broker High-Availability Cluster Scripts
 
Configure the webMethods Broker High-Availability Cluster Scripts
 
Configure the High-Availability Cluster Scripts
Edit the wment-defs.sh File
Verify the webMethods Scripts Work Correctly
By default,webMethods Broker HA cluster scripts are installed on the webMethods Broker_directory /scripts/generic_cluster directory. This file contains the following scripts:
*wment-defs.sh This file contains configuration parameters representing the webMethods Broker setup; the startBroker.sh, stopBroker.sh, and brokerStatus.sh scripts refer to this file. The parameters of this file are described in Edit the wment-defs.sh File.
*startBroker.sh This script starts a Broker Server. Broker Server details are specified in the wment-defs.sh parameter file.
*stopBroker.sh This script stops a Broker Server. Broker Server details are specified in the wment-defs.sh parameter file.
*brokerStatus.sh This script checks the health of a Broker Server. Broker Server details are specified in the wment-defs.sh parameter file.
You can configure this script to run in two different modes, based on the requirements of the clustering software. You can either run the script once until Broker is pinged successfully, or run the script indefinitely until Broker is not available.
You may rename these scripts. For example, in a Veritas cluster you should rename them to online, offline, and monitor, respectively.
Important:
Always use the startBroker.sh and stopBroker.sh scripts to start and stop the Broker Server. If you use the S45broker65 script you may receive unexpected results.