Configure the Start, Stop, and Status Scripts

About this task

Incorporate the scripts of each cluster node into the cluster control software with the help of the cluster vendor’s installation consultant.

To configure the start, stop, and status scripts of a server

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

Important: When you have basic authentication enabled on the server, you must configure the UM_PASSWORD or UM_PASS_PASSWORD_IN_CONSOLE property before running the ngetservertime command. For more information about UM_PASSWORD and UM_PASS_PASSWORD_IN_CONSOLE, see Running the Java Sample Applications when Basic Authentication is Enabled.
1. Modify env.sh and change last command from “$SHELL” to “$SHELL $*”.
2. Run this command to monitor the server status:
```
./env.sh -c "ngetservertime" | grep "Server Time"
```