Skip navigation.
Downloads | Product Documentation | Support

WebLogic Server Command Reference

## STARTINSTANDBY

(Deprecated) Starts a Managed Server using Node Manager.

In previous releases, this command started a Managed Server using the Node Manager and placed it in a `STANDBY` state. In this state, a server is not accessible to requests from external clients.

In the current release, the Startup Mode field in the Administration Console determines the state in which a Managed Server starts, regardless of which command you use to start the server instance. See "Starting a Managed Server in the STANDBY State" in the Administration Console Help.

This command requires the following environment:

- The domain's Administration Server must be running.
- The Node Manager must be running on the Managed Server's host machine.
- The Managed Server must be configured to communicate with a Node Manager. For more information, refer to "Configuring a Machine" in the Administration Console Online Help.
- The domain must be configured to use a domain-wide administration port as described in "Enabling the Domain-Wide Administration Port" in the Administration Console Online Help.

For more information about server states, refer to "Server Life Cycle" in the Configuring and Managing WebLogic Server guide.

### Syntax

>     java [ SSL Arguments ] weblogic.Admin
>        [-url URL]
>        [ User Credentials Arguments ]
>        STARTINSTANDBY targetServer

Argument | Definition
--- | ---
-url `secure-protocol``://``listen-address:listen-port` | You must specify the Administration Server and domain-wide administration port as follows: `t3s://``Admin-Server-listen-address:domain-wide-admin-port` or `https://``Admin-Server-listen-address:domain-wide-admin-port` For more information, refer to the -url entry in Table 1-3 on page 11 and Protocol Support.
`targetServer` | The name of the WebLogic Server to start in the `STANDBY` state.

### Example

The following example instructs the Administration Server and Node Manager to start a Managed Server:

>     java weblogic.Admin -url t3s://AdminHost:9002 -username weblogic
>     -password weblogic STARTINSTANDBY MedRecManagedServer

When you issue the command, the following occurs:

1. The Administration Server determines which machine `MedRecManagedServer` is configured to run on. It instructs the Node Manager that is running on that machine to start `MedRecManagedServer` in the state that the Start Mode field specifies.
2. The Node Manager indicates its progress by writing messages to its standard out. You can view these messages from the Administration Console on the Server—>Control—>Remote Start Output tab.
3. If the command succeeds, the `weblogic.Admin` utility returns to the following message:

>     Server "MedRecManagedServer" was started ...
>     Please refer to server log files for completion status ...

When you use the Node Manager to start a Managed Server, the Node Manager writes standard out and standard error messages to its log file. You can view these messages from the Administration Console on the Machine—>Monitoring tab.

For more information about the environment in which this example runs, refer to Example Environment.