I would like to add an /etc/init.d script to strart Wbsphere
I would like to execute the command to start WPS automatically on start up rather than have to do it manually. IBM support says I can do this as an init.d script......problem is I don't know how to create an /etc/init.d script.
This is the start command (below): How do I make sure this runs on start up? This is a Redhat5 Linux OS.
/opt/IBM/WebSphere/AppServ
This is the start command (below): How do I make sure this runs on start up? This is a Redhat5 Linux OS.
/opt/IBM/WebSphere/AppServ
ASKER
run-level 5 2010-08-17 16:09 last=S
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
2 solutions there - omarfarid's is for a script that accepts start, stop & restart as arguments which your script apparently doesn't do. In that case, WS will get stopped at shut-down when init kills everything, but it won't get stopped otherwise.
Actually I think omarfarid expects you to write a script containing a reference to startServer.sh - that should work fine. Setting environment variables may be necessary also. But because IBM supplied the script, I rather imagine they might be doing that for you already, in which case it will work to invoke it directly as I posted
ASKER
Hi...I am setting up a VM to test this in....stand by
ASKER
I used this command to configure and I grabbed a script from another websphere server....it starts up OK, but does not stop when I am rebooting
./wasservice.sh -add "WebSphere_Portal" -serverName "WebSphere_Portal" -profilePath "/opt/IBM/WebSphere/wp_pro
./wasservice.sh -add "WebSphere_Portal" -serverName "WebSphere_Portal" -profilePath "/opt/IBM/WebSphere/wp_pro
how the script is created under /etc/rc5.d directory? what are the permissions of the file? does the file name starts with S ? does it include all required env. variables?
If you put this directly into inittab, init will stop it if it is still running (and you invoked it with "&" at the end). You need to modify the script(s) involved so they don't start another job and return in that case.
If you went the rc.5 route, you have an S script there to start it and you need a K script in all the other rc directories to stop it. Usually they are all symbolic links to the same script, but S & K could be different
If you went the rc.5 route, you have an S script there to start it and you need a K script in all the other rc directories to stop it. Usually they are all symbolic links to the same script, but S & K could be different
ASKER
I did this, but in /etc/init.d rather than /etc/rc5.d and I noticed that there are links in /etc/rc5.d to the elements in /etc/init.d.
you should have a dir /etc/rc5.d
under this dir create the startup script e.g.
S99myscript
which contains all commands necessary to startup WPS
the script should have all necessary env variables set in it, plus it should be executable.
Note that the script name should start S
etc-rc5.d.png
you should have a dir /etc/rc5.d
under this dir create the startup script e.g.
S99myscript
which contains all commands necessary to startup WPS
the script should have all necessary env variables set in it, plus it should be executable.
Note that the script name should start S
etc-rc5.d.png
/etc/rc5.d looks perfectly normal. The S files are invoked with the argument start and the K files are invoked with the argument stop, when run level 5 is entered. It is indeed more common to use this system than to invoke commands from init.d directly. If your scripting is up to it, you could write a little script of your own which accepts start, stop & restart:-
start invokes the command you already use
stop invokes some command that will stop Websphere (you will have to find that command)
restart invokes stop followed by start
place that script in init.d and make S & K symbolic links to it. Make he S number large, so it will be started close to last (unless you have a reason to start it early) and make the K number small to stop early (unless ... ). Place S link in rc5.d and a K link in all the other rc<n>.d directories.
Or leave it as it is and live with it
start invokes the command you already use
stop invokes some command that will stop Websphere (you will have to find that command)
restart invokes stop followed by start
place that script in init.d and make S & K symbolic links to it. Make he S number large, so it will be started close to last (unless you have a reason to start it early) and make the K number small to stop early (unless ... ). Place S link in rc5.d and a K link in all the other rc<n>.d directories.
Or leave it as it is and live with it
who -r
then I will provide you with how to do it