WebSphere Start-up Order
By Siva
Praturi
You can
create the WebSphere Application Server and the WebSphere Node Agent to run as
Windows services. These services must be created so that they will start in the
correct order.
The
WASService command line tool enables you create a service for WebSphere
Application Server Java processes. The
WASService.exe command file is located in the app_server_root\bin directory.
Potential services include the following server processes:
- The default server1 process on an application
server node
- The nodeagent process on an application server node that is part
of a deployment manager cell
- The deployment manager process, dmgr
Note: As an alternative to the WASService
command, you can use the WASServicecmd utility, which compliments the
WASService command and reduces possible configuration errors.
After you
create WebSphere Server and Node Agent to run as Windows services, you need to
perform additional step to setup correct start-up order. This can be
done in two ways.
Option 1: Using Registry Editor
- Use a registry editor, such as Regedit, and open registry key of WebSphere Application Server i.e. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IBMWAS70Service-server01
- Create a Multi-String Value named DependOnService.
- Enter the value as WebSphere
Node Agent service name i.e. "IBMWAS70Service-node01" in this
new key.
Option 2: Using SC Command in Windows
SC command
to add the dependency is:
sc config
“IBMWAS70Service-server01” depend= “IBMWAS70Service-node01”
This can be
verified by looking at dependencies tab in properties of “IBMWAS70Service-server01”
service in service console.
References:
- http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rins_wasservice.html
- http://www-01.ibm.com/support/docview.wss?uid=swg21397335
- http://serverfault.com/questions/24821/how-to-add-dependency-on-a-windows-service-after-the-service-is-installed
No comments:
Post a Comment