> If I could do this without having to do a root logon to start the > middleware services that would be ideal.
Since init is effectivly uid 0 while starting the system up, the scripts in /etc/init.d *are* run as root. Scripts in /etc/init.d are how every other system resource gets started -- user applications that need to run as daemons are no different. Nothing special about Linux here; this is classic Sys V Unix practice, just like on Solaris and AIX. If this was a Berzerkely-derived system like FreeBSD, you'd put the startup commands in /etc/rc.local. > The problem I need to resolve is how to enable the middleware > on each Linux > instance in a specific order. There are dependancies between WebSeal > Server, HTTP server, Tivoli Access Manager Server and Policy > Authorization > server, LDAP Server, DB2 UDB Server, WebSphere Application Server. If the applications are in separate Linux instances, that part should be done in the PROFILE EXEC. Parsing the output of Q NAMES is trivial, as is retrieving a list of prerequisite machines from a NAMES file using NAMEFIND. Retrieve the prereqs, do a Q USERID for each prereq, and determine whether the entire list is logged on. If not, sleep for a few seconds and try again. When all your prereqs are logged in, start yourself. > In the case of LDAP and WebSeal there was no option to > autostart that I am > aware of. You need to logon as root to start each middleware > service as > well as stop each service. If you can type it, you can script it. The /etc/init.d scripts are structured to handle this automagically, both start and stop. > TAM does autostart successfully if it was shutdown properly > to begin with. See above. TAM *is* fairly fragile, isn't it? 8-( > WebSphere Application Server v5.0 does not autostart. As installed it > requires root to start the WAS server so that it is open for > ebusiness. > WebSphere can be changed so that a non-root userid can start WAS. No need. See above. > I thought that using REXX I could have more control on the > IPL order and > the middleware services startup order. You need to use both techniques. If you need to sequence the Linux AUTOLOGs, use the SYNC parm on XAUTOLOG and check in the individual machine's PROFILE EXECs whether the necessary prereqs are logged on before starting yourself. Once Linux is initializing, you use init to run the scripts needed to start the middleware applications as part of the startup processing. > Dave, will your presentations be on linuxvm.org ? After the Hillgang meeting in December, they'll be publically available, probably on www.sinenomine.net with a pointer from linuxvm.org. It's only fair that attendees get them first. Of course if this is for a project IBM is getting paid for, I'd be happy to write them for you for a reasonable small gratuity...8-) -- db
