Technical data

Starting a WebLogic Managed Server
Administration Guide 2-17
4. Create an entry for the new server (Servers→Create a new server). Set the
machine for this Managed Server to the machine you just created an entry for.
Each server must have a unique name — even if the servers are in different
domains.
For more information on configuring servers, see Configuring WebLogic Servers and
Clusters.
Starting a WebLogic Managed Server
WebLogic Managed Servers can be started in either of the following ways:
n Remotely from the Administration Console, using a Node Manager on the target
machine where the Managed Server needs to be started.
n Locally, by invoking the server on the java command line in a command shell.
This section discusses how to start the WebLogic Managed Server locally. For
information on setting up and using the Node Manager to start Managed Servers
remotely, see Node Manager.
Note: If you right click on the name of a server in the left pane of the Administration
Console, one of the options is Start this server.... This option can only be used
to start a Managed Server if you have a Node Manager running on the machine
where the Managed Server is located. For more information, see Node
Manager.
Once you have added WebLogic Managed Servers to your configuration (see Adding
a WebLogic Managed Server to the Domain), you can start the Managed Servers from
the
java command line. The command to start the WebLogic Server can be either
typed in a command shell manually or it can be placed in a script to avoid retyping the
command each time the server is started. For information on the sample scripts
provided see Starting the WebLogic Managed Servers Using Scripts.
The main way in which the startup parameters for a Managed Server differ from an
Administration Server is that you need to provide an argument that identifies the
location of the Administration Server from which the Managed Server requests its
configuration. A WebLogic Server started without this parameter runs as an
Administration Server.