|
Problem |
When the Advanced Single Server Edition
runs as an application, logging a user off
of the machine ends the Advanced Single Server Edition process. With Fix
Pack 2 of WebSphere Application Server (4.0.2), you can run the Advanced
Single Server Edition Version 4.0 as a Windows NT or 2000 service instead
of as an application, which allows the Advanced Single Server Edition to
run without a user being logged onto the machine. |
|
|
|
Solution |
To run the Advanced Single Server
Edition as a service, use the WASService utility. For information on using
WASService, at a command prompt enter the command
WASService -help
To add the Advanced Single Server Edition to the
Windows NT or 2000 services using the default configuration file
(product_installation_root/config/server-cfg.xml), enter the
command
WASService -add service_name
For example: WASService -add myAEsApplServer
To add the Advanced Single Server Edition to the
Windows NT or 2000 services using your own configuration file
(product_installation_root/config/server-cfg.xml), enter the
command
WASService -add service_name -configFile
server_configuration_file
For example:
WASService -add myAEsApplServer -configFile
C:\WebSphere\AppServer\config\myAEsAppserver-cfg.xml
To start the Advanced Single Server Edition service on
Windows NT or 2000, go to the Services dialog, select the Advanced Single
Server Edition service, and click Start. Or, enter the command WASService
-start service_name. For example:
WASService -start myAEsApplServer
To stop the Advanced Single Server Edition service on
Windows NT or 2000, go to the Services dialog, select the Advanced Single
Server Edition service, and click Stop. Or, enter the command WASService
-stop service_name. For example:
WASService -stop myAEsApplServer
To remove the Advanced Single Server Edition service
from Windows NT or 2000 Services, use the command
WASService -remove service_name
For example: WASService -remove myAEsApplServer
To list the status of the Advanced Single Server
Edition service, enter the command
WASService -status service_name
For example: WASService -status
myAEsApplServer |
|
|
|
|
Historical Number |
115633 |
|
|
|
|