TriniDBA

Problem:

If the user that starts the IBM WebSphere web server logs off the system, the web server is shut down. A Windows service must be created to ensure that the web service(s) remain running.

Solution:

At Command Prompt, issue the following commands:

E:
 cd E:IBMWebSphereAppServerbin
 WASService.exe -add fsdev -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservfsdev -logFile E:IBMWebSphereAppServerlogsstartNodefsdev.log -restart true -startType automatic
WASService.exe -add fsdmo -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservPIA_fsdmo -logFile E:IBMWebSphereAppServerlogsstartNodefsdmo.log -restart true -startType automatic
E:IBMWebSphereAppServerbin>cd E:IBMWebSphereAppServerbin
E:IBMWebSphereAppServerbin>WASService.exe -add fsdev -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservfsdev -logFile E:IBMWebSphereAppServerlogsstartNodefsdev.log -restart true –startType automatic
 Adding Service: fsdev
 Config Root: E:PSOFTFS900webservfsdevconfig
 Server Name: server1
 Profile Path: E:PSOFTFS900webservfsdev
 Was Home: E:IBMWebSphereAppServer
 Start Args:
 Restart: 1
 IBM WebSphere Application Server V6.1 - fsdev service successfully added.
 E:IBMWebSphereAppServerbin>
The “IBM WebSphere Application Server V6.1 – fsdev” service is created.
Note that the log file is E:IBMWebSphereAppServerlogsstartNodefsdev.log
E:>E:
 E:>cd E:IBMWebSphereAppServerbin
E:IBMWebSphereAppServerbin>WASService.exe -add tramdmo -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservPIA_tramdmo -logFile E:IBMWebSphereAppServerlogsstartNodetramdmo.log -restart true -startType automatic
 Adding Service: tramdmo
 Config Root: E:PSOFTFS900webservPIA_tramdmoconfig
 Server Name: server1
 Profile Path: E:PSOFTFS900webservPIA_tramdmo
 Was Home: E:IBMWebSphereAppServer
 Start Args:
 Restart: 1
 IBM WebSphere Application Server V6.1 - tramdmo service successfully added.
To remove the service:
 cd E:IBMWebSphereAppServerbin
 WASService.exe -remove tramdmo
E:>E:
 E:>cd E:IBMWebSphereAppServerbin
E:IBMWebSphereAppServerbin>WASService.exe -add peoplebooks -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservPSOL_fsdmo -logFile E:IBMWebSphereAppServerlogsstartNodepeoplebooks.log -restart true -startType automatic
Adding Service: peoplebooks
 Config Root: E:PSOFTFS900webservPSOL_fsdmoconfig
 Server Name: server1
 Profile Path: E:PSOFTFS900webservPSOL_fsdmo
 Was Home: E:IBMWebSphereAppServer
 Start Args:
 Restart: 1
 IBM WebSphere Application Server V6.1 - peoplebooks service successfully added.
 E:IBMWebSphereAppServerbin>
To remove the service:
 cd E:IBMWebSphereAppServerbin
 WASService.exe -remove peoplebooks

Reference:
http://handly.blogspot.com/2008/05/setting-up-websphere-61-cluster-to.html

Setting up the WebSphere Node Manager as a Windows service

First, you need to set up the Node Manager on each physical server to run as a service and restart after a reboot:

Open a Command Window and go to the ..IBMWebSphereAppServerbin directory
Type in the following command (adjusted for your install paths):

WASService -add “IBM WebSphere Node Agent” -servername nodeagent -profilePath D:IBMWebSphereAppServerprofilesAppSrv01 -wasHome D:IBMWebsphereAppserver -logFile D:IBMWebSphereAppServerprofilesAppSrv01logsnodeagentstartNode.log -logRoot D:IBMWebSphereAppServerprofilesAppSrv01logsnodeagent -restart true -startType automatic