Skip navigation.
Downloads | Product Documentation | Support

WebLogic Server Command Reference

## STARTCLUSTER

Starts all of the servers that are in a cluster have been configured to use a Node Manager.

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 Startup Mode field in the Administration Console determines whether a Managed Server starts in the `RUNNING` state or `STANDBY` state. See "Server Life Cycle" in Configuring and Managing WebLogic Server.

### Syntax

>     java [ SSL Arguments ] weblogic.Admin
>          [-url URL]
>          [ User Credentials Arguments ]
>        STARTCLUSTER -clusterName clusterName

Argument | Definition
--- | ---
{-url [`protocol``://`]`listen-address:listen-port``}` | Specify the listen address and listen port of the Administration Server. If you specify a secure listen port, you must also specify a secure protocol. If you do not specify a value, the command assumes `t3://localhost:7001`. For more information, refer to the -url entry in Table 1-3 on page 11 and Protocol Support.
`-clusterName` `clusterName` | The name of the cluster as specified in the domain's configuration file (`config.xml`).

### Example

The following example starts a cluster:

>     java weblogic.Admin -url AdminHost:7001
>       -username weblogic -password weblogic
>       STARTCLUSTER -clustername MedRecCluster

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

If the command succeeds, it returns output similar to the following:

>     Starting servers in cluster MedRecCluster: MedRecMS2,MedRecMS1
>     All servers in the cluster "MedRecCluster" started successfully.