Technical data

2 Starting and Stopping WebLogic Servers
2-26 Administration Guide
of SERVER_START_PENDING for 2 minutes. Then it changes the status to
STARTED.
The modified
beasvc invocation for the Administration Server will resemble
the following:
"D:\bea\wlserver6.1\bin\beasvc" -install
-svcname:mydomain_myAdminServer
-javahome:"D:\bea\jdk131"
-delay:120000
-execdir:"D:\bea\wlserver6.1"
-extrapath:"D:\bea\wlserver6.1\bin" -cmdline:%CMDLINE%
For more information about beasvc, enter the following command at a
command prompt:
weblogic\server\bin\beasvc -help, where
weblogic is the directory in which you installed WebLogic Server.
4. Install the Administration Server Windows service.
5. Before you install the Managed Server as a Windows service, do the following:
a. In a text editor, open the
weblogic\config\mydomain\installNTService.cmd script.
b. Add the following argument to the command that invokes the beasvc utility:
-depend:Administration-Server-service-name
where
Administration-Server-service-name is the name of the
Administration Server Windows service. To verify the service name, look on
the Windows Services Control Panel.
With this option, the Windows SCM will wait for the Administration Server
Windows service to report a status of
STARTED before it starts the Managed
Server Windows service.
For example, the modified
beasvc invocation for the Managed Server will
resemble the following:
"D:\bea\wlserver6.1\bin\beasvc" -install
-svcname:mydomain_myManagedServer
-javahome:"D:\bea\jdk131"
-depend:"mydomain_myAdminServer"
-execdir:"D:\bea\wlserver6.1"
-extrapath:"D:\bea\wlserver6.1\bin" -cmdline:%CMDLINE%