I've searched around in this forum and have not found anything on this topic
, which I find strange (perhaps I'm simply searching for the wrong thing).

I've inherited a WAS/WPS infrastructure of 2 WPS nodes configured in a clust
er and the people who originally installed and configured the system tell me
 that the WPS server must be started manually by the workstation administrat
or from the admin client.

Now the problem with this is that when the Administrator logs off the WPS se
rver shuts down (even though the Windows Server is still up and running).

I was told that this is the way it must work you can't configure WAS/WPS Clu
stering to be started as a Windows service (but they never gave me reasons w
hy).

So, my question to the group is is this indeed true? If so why? If not how c
an I configure the system to run as a Windows Service so that when the windo
ws box is booted WPS will be brought up and remain up w/o manual interventio
n?

Thanks
Mike Barlow
mwb@infionline.net

[ Post a follow-up to this message ]

You can run WebSphere as Windows Service and have it automatically upon
reboot.

Which version of WAS / WPS are you running ?

[ Post a follow-up to this message ]

Thanks for the quick reply Ben, I'm running WAS/WPS 5.1 in a clustered envir
onment on Windows 2K.
So to set WAS/WPS to launch as a windows service would I use the:
"WASService -add nodeagent..."
process to set this up?

Thanks
Mike B

[ Post a follow-up to this message ]

Yes, I believe so.

I used that command with WAS Express and WAS Base to make an Application
Server a service. But the fact is that making the nodeagent a service is an
option at installation time, so I didn't have to use with WAS ND. But if I
had to do it I'd try that...

[ Post a follow-up to this message ]

Great Ben, thanks for your help, I'll give that a try.

Mike B

[ Post a follow-up to this message ]