***NOTE: As with all Tips and Tricks we provide on the IDMWorks blog, use the following AT YOUR OWN RISK. We do not guarantee this will work in your environment and make no warranties***
Configuring Startup and Shutdown Procedures On Reboot for the ITIM and Associated Applications
Step 1
Create a script that will perform the Startup and Shutdown processes. Below is a script that was we used where ITIM, Directory Manager, Node Agent and jmsservers needed to be shutdown and started during reboot of the system.
The directory is /etc/init.d and the member that we are working with is IBMitim (within this member is where the startup and shutdown commands reside.
From there we have Status, Startup and Shutdown commands. The status command will determine whether to start or stop the various servers. On this system there were 4 different servers that needed to be stopped or started during a reboot of the system (Deployment Manager, Node, jms servers and ITIM).
The script as follows:
state=”$1″
. /export/home/db2admin/sqllib/db2profile
case “$state” in
‘status’)
/opt/WebSphere/AppServer/bin/serverStatus.sh –all
/opt/WebSphere/DeploymentManager/bin/serverStatus.sh -all
;;
‘start’)
echo “Starting deployment manager “
/opt/WebSphere/DeploymentManager/bin/startManager.sh
echo “Start WebSphere Node”
/opt/WebSphere/AppServer/bin/startNode.sh
echo “Starting jms server”
/opt/WebSphere/AppServer/bin/startServer.sh jmsserver
echo “Starting ITIM”
/opt/WebSphere/AppServer/bin/startServer.sh ITIM
;;
‘stop’)
echo “Stopping ITIM”
/opt/WebSphere/AppServer/bin/stopServer.sh ITIM
echo “Stopping jms server”
/opt/WebSphere/AppServer/bin/stopServer.sh jmsserver
echo “Stopping WebSphere Node”
/opt/WebSphere/AppServer/bin/stopNode.sh
echo “Stopping Deployment Manager “
/opt/WebSphere/DeploymentManager/bin/stopManager.sh
echo “Stop WebSphere Server1″
/opt/WebSphere/AppServer/bin/stopServer.sh server1
;;
*)
echo “Usage: $0 { start | stop | status }”
exit 1
;;
esac
exit 0
Step 2
Determine where your procedure will reside. Now you need to create a link within a specific rc#.d directory. There are several rc#.d directories including rc0.d, rc1.d, rc2.d, rc3.d and rcS.d. During a system reboot these rc files are processed in order, rc0.d first and so on. You will need to determine when the process needs to occur. For this configuration of ITIM the startup and shutdown process will be placed in rc3.d.
Create a link for Startup/Shutdown by entering a link command as follows:
- ln command format “ln A B”
A = where your new script resides, this is what was performed in step 1when IBMitim was created.
B = file that is linked to IBMitim, there are certain rules that apply when creating these. First character must be a “K” for stop and a “S” for start. The next 2 must be numeric, which will determine when they are processed. And the last 4 can be whatever you want.
As stated above we are going to place are Startup/Shutdown process in rc3.d, first cd /etc/rc3.d, now enter pwd at the command prompt to verify that you are pointing to /etc/rc3.d (displayed below). The ls (List command) will display what members reside in this directory.
Now we need to perform the link command.
- ln /etc/init.d/IBMitim K01itim – this will link /etc/init.d/IBMitim to /etc/rc3.d/K01itim
- ln /etc/init.d/IBMitim S99itim – this will link /etc/init.d/IBMitim to /etc/rc3.d/S99itim
After a ls(list command) you can see the link that was created(K01itim), perform the same process for S99itim.
Questions? We have answers. Feel free to reach out to us at IDMWorks.
