WAS 6.1 setup Windows NT Service
There is a handy WASService command available in WAS_ROOT\bin allowing Websphere Application Server 6.1 integration with Windows Services.
Samples and documentation on IBM InforCenter – WASService Command
For WAS with security enabled first thing we encountered was a failure to stop WAS service from service console.
RoleBasedAuth E SECJ0306E: No received or invocation credential exist on the thread. … The stack trace is java.lang.Exception: Invocation and received credentials are both null
To mitigate the problem add “stopArgs” parameters specifying username and password. In addition to make storing of passord more secure specify “-encodeParams” and password will be stored in registry in non readable format.
WASService.exe -add “DEV01N01” -serverName server1 -profilePath C:\IBM\pf\ESB\DEV01N01 -stopArgs “-username userA -password passwordXXX” -encodeParams