Configure the Start, Stop, and Status Scripts
Incorporate the scripts of each cluster node into the cluster control software with the help of the cluster vendor’s installation consultant.
![*](icon_task_xpe.png)
To configure the start, stop, and status scripts of a server
1. Provide the location of the start and stop scripts to the cluster vendor consultant.
The scripts to start and stop a Universal Messaging server are located here:
Universal Messaging_directory /server/server_name/bin/nserver to start the server.
Universal Messaging_directory /server/server_name/bin/nstopserver to stop the server.
2. Implement a status script using the Universal Messaging API and provide the script to the cluster vendor consultant. For example, to return the server time stamp, you can use: Universal Messaging_directory /java/server_name/bin/ngetservertime.
a. Modify env.sh and change last command from “$SHELL” to “$SHELL $*”.
b. Run this command to monitor the server status:
./env.sh -c "ngetservertime" | grep "Server Time"