Troubleshooting
Problem
The wasservicehelper utility is a friendly interface for the WASService utility. Both utilities are provided with the WebSphere Application Server. The WASService utility is used for adding, updating, and removing WebSphere Services in Windows.
The wasservicehelper utility is provided in WebSphere Application Server v8 and higher and resides in the WAS_HOME\bin directory.
Symptom
Creating and removing a Windows WebSphere service is confusing and error prone.
Cause
The WASService utility requires several parameters that can be confusing to the user and often involve several long path strings leaving opportunities to set up incorrectly.
Environment
Windows
Resolving The Problem
Launch the utility: wasservicehelper
The wasservicehelper utility prompts you to select specific options and settings from a list and then calls the WASService.exe command passing all selected parameters. The time required to create a Windows service for WebSphere Application Server and the opportunity for user errors are reduced.
Flash demonstration - The wasservicehelper utility was previously named WASServiceCmd. The flash demonstration shows the earlier version of the utility. Only the utility name changed.The utility shows the WASService command syntax that is used. The information is also stored in the log file, WASServiceCmd.rep in the current directory.
Example of a log entry:
| [Fri Aug 14 12:22:01 -0500 2009] WASService.exe -add "Deployment Mgr01" -serverName "dmgr" -profilePath "C:\Program Files\IBM\WebSphere\AppServer\profiles\Dmgr01" -logRoot "C:\Program Files\IBM\WebSphere\AppServer\profiles\Dmgr01\logs\dmgr" -logFile "C:\Program Files\IBM\WebSphere\AppServer\profiles\Dmgr01\logs\dmgr\WS_startdmgr.log" -encodeParams -stopArgs "-username vanno -password ****** " -startType manual -restart false |
As-is download. Provided for use when the wasservicehelper utility is not available.
Place the WASServiceCmd.exe utility in the WAS_HOME\bin directory. This version of the utility creates a log file named WASServiceCmd.log instead of the WASServiceCmd.rep log.
Notice: If the browser downloads the file as docview.wss, rename the file with a ".zip" extension (for example, docview.zip or WASServiceCmd.zip).
Place the WASServiceCmd.exe utility in the WAS_HOME\bin directory. This version of the utility creates a log file named WASServiceCmd.log instead of the WASServiceCmd.rep log.
Notice: If the browser downloads the file as docview.wss, rename the file with a ".zip" extension (for example, docview.zip or WASServiceCmd.zip).
Related Information
[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"System Management\/Repository","Platform":[{"code":"PF033","label":"Windows"}],"Version":"9.0;8.5;8.0;7.0","Edition":"Base;Developer","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
24 February 2022
UID
swg21397335