Wednesday, June 06, 2007

Creating a Windows service for WebSphere AppServer

For those who need to set up a WAS profile to run as a Windows service in case it was originally selected as not to run as a Windows Service in the profile creation wizard or for those using Curam's automatic install scripts which deletes the profile, there is a command in C:\Program Files\WebSphere\AppServer\bin called WASService.exe. To create the new service invoke the following command: WASService.exe -add CuramWAS -serverName CuramServer -profilePath "c:\Program Files\IBM\WebSphere\AppServer\profiles\default" This will create a service called "IBM Websphere Application Server V6 - CuramWAS" so don't look for something that starts with "CuramWAS" One other note. It sets up the "Startup Type" for the service as "Manual" by default, so if you want it to start up when the system reboots you need to set it up as "Automatic"

2 comments:

brewdude said...

Be careful in 6.1. IBM doesn't recommend creating services for anything other than the "nodeagent".
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg1PK58459
This APAR was created as a result of a PMR I opened with Websphere Support.

Archimedes Trajano said...

Is that still applicable for the standard edition not the Network Deployment version?