WASService adds the WAS Services to Windows services list, but fails to stop/start them.
If I bounce the box, then services are getting started. If I stop them, it is setting the service status as blank. If I start it again, it throws "Windows could not start IBM WebSphere Application Server – servicename on local computer". When checked in the event logs "The IBM WebSphere Application Server V7.0 - CellManager01 service terminated with service-specific error %%134220456." is the message.
This is how I have added WAS Services to Windows Services
D:\IBM\WebSphere\AppServer\bin\WASService.exe -add CellManager01 -serverName dmgr -profilePath D:\IBM\WebSphere\AppServer\profiles\Dmgr01 -wasHome D:\IBM\WebSphere\AppServer -logFile D:\IBM\WebSphere\AppServer\profiles\Dmgr01\logs\dmgr\SystemOut.log -logRoot D:\IBM\WebSphere\AppServer\profiles\Dmgr01\logs\dmgr -restart true -startType automatic -stopArgs "-username xxxxxxxxx -password xxxxxxx" –encodeParams
To solve this, one can use WASServiceCmd Utility. This utility is easy to use, grabs all the info you need to pass, creates the service command, executes it.
Here is the technote about WASServiceCmd
Here is my WASServiceCmd log entry
wasservice.exe -add "CellManager01" -serverName "dmgr" -profilePath "D:\IBM\WebSphere\AppServer\profiles\Dmgr01" -encodeParams -stopArgs "-username xxxxxxxx -password ******** -startType automatic -restart true
wasservice.exe -add "Node01" -serverName "nodeagent" -profilePath "D:\IBM\WebSphere\AppServer\profiles\wlmprime01" -encodeParams -stopArgs "-username xxxxxxx -password ******** -startType automatic -restart true
These services are now, properly working.
--
Thanks and Regards
Bhaskar Ramaraju
http://www.linkedin.com/in/ramarajubhaskar
