Date Created: Fri 18-Jan-2008

Related Document Categories:

Get my WebSphere Application Server course here >> http://www.themiddlewareshop.com/products/


Basic tips using WASService.exe to help with configuring windows services for IBM WebSphere Application Server.

When a WAS server is installed on Windows 2003 servers the start-up arguments are defaulted, and this means the default services that are registered will no longer work if Administration security is enabled. It must also be noted that you will have to set dependancies using registry to ensure that the node agent always starts before the servers. The server tasks depend on the node agents to start.

Note: You can also use soap.client.props to configure passwords.

By default WAS does not have Administrative security enabled and thus once set the service will no longer work properly.

Steps how to correctly register your WAS Windows Service.

1. Using Regedit.exe export a copy of the current WAS service key. This is currently found in

Then navigate to the appropriate key.

Export the key to a file, so you can re-implement it is there is a problem.

Note: The best way to find what key your looking for is to look in the service applet and see what it might look like using the properties of the service entry e.g.

2. Using the WASService tool in the <WASRoot>\AppServer\Bin directory to register your New Service.

Here is a batch file you can use to make this task easier.

c:\61websphere\AppServer\bin\WASService.exe -add "Node01" -serverName "server1" -profilePath "c:\61WebSphere\profiles\AppSrv01" -logRoot "c:\61WebSphere\profiles\AppSrv01\logs\server1" -startArgs "-username n114291 -password SAUCe123!!%" -stopArgs "-username <username>-password <password>" -restart false

3. Once you have confirmed the new service has been added correctly you can use regedit to delete the old service entry.

4. You can now set the service to "Automatic" to auto start the WAS Service on startup.

Note: you can look at the WASService help to get more information on commands.

e.g.

C:\61WebSphere\AppServer\bin>wasservice

Usage: WASService.exe (with no arguments displays this help)
|| -add <service name>
-serverName <Server>
-profilePath <Server's Profile Directory>
[-wasHome <Websphere Install Directory>]
[-configRoot <Config Repository Directory>]
[-startArgs <additional start arguments>]
[-stopArgs <additional stop arguments>]
[-userid <execution id> -password <password>]
[-logFile <service log file>]
[-logRoot <server's log directory>]
[-encodeParams]
[-restart <true | false>]
[-startType <automatic | manual | disabled>]
|| -remove <service name>
|| -start <service name> [optional startServer.bat parameters]
|| -stop <service name> [optional stopServer.bat parameters]
|| -status <service name>
|| -encodeParams <service name>

5. To manually start and stop use the startserver.bat and stopserver.bat batch files located in the root bin or default profile bin directories.

C:\61WebSphere\AppServer\bin>

or

C:\61WebSphere\AppServer\profiles\AppSrv01\bin>

When using stopserver.bat You will be asked a username and password if your added stopArgs to your service.

Sample batch files templates to automatically add NT services for WebSphere. Please change as required.


remove_server1.batadd_nodeagent.batadd_server1.batremove_nodeagent.bat

|| means optional

Usage: WASService.exe (with no arguments displays this help)
|| -add <service name>
-serverName <Server>
-profilePath <Server's Profile Directory>
[-wasHome <Websphere Install Directory>]
[-configRoot <Config Repository Directory>]
[-startArgs <additional start arguments>]
[-stopArgs <additional stop arguments>]
[-userid <execution id> -password <password>]
[-logFile <service log file>]
[-logRoot <server's log directory>]
[-encodeParams]
[-restart <true | false>]
[-startType <automatic | manual | disabled>]
|| -remove <service name>
|| -start <service name> [optional startServer.bat parameters]
|| -stop <service name> [optional stopServer.bat parameters]
|| -status <service name>
|| -encodeParams <service name>

Get my WebSphere Application Server course here >> http://www.themiddlewareshop.com/products/

Steve Robinson - IBM Champion 2013

About Me

Steve Robinson has been working in IT for over 20 years and has provided solutions for many large-enterprise corporate companies across the world. Steve specialises in Java and Middleware.

In January 2013, I was awarded the prestigous 'IBM Champion' accolade.


  • Linked In
  • Twitter
  • About Me
  • My Blog
  • Contact Me

Read my books?

IBM WebSphere Application Server 8.0 Administration Guide

IBM WebSphere Application Server 8.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Categories

Other Categories