Skip navigation.
Downloads | Product Documentation | Support

Configuring and Managing WebLogic Server

# Starting and Stopping Servers: Quick Reference

The following sections describe simple, frequently used ways to start and shut down instances of WebLogic Server:

- Starting Instances of WebLogic Server
- Shutting Down Instances of WebLogic Server

For a comprehensive discussion of starting and shutting down WebLogic Server instances, refer to "Starting and Stopping Servers" in the Administration Console Online Help.

# Starting Instances of WebLogic Server

In the following table, `WL_HOME` refers to the top-level installation directory for WebLogic Platform.

Table 11-1 Starting Server Instances

To Start | Do The Following
--- | ---
The MedRecServer sample server | Invoke: `WL_HOME``\samples\domains\medrec\startMedRecServer.cmd` (Windows) `WL_HOME``/samples/domains/medrec/startMedRecServer.sh` (UNIX) The server starts as an Administration Server in the MedRec domain. On Windows, you can also start MedRecServer from the Start menu.
The Examples server | Invoke: `WL_HOME``\samples\domains\examples\startExamplesServer.cmd` (Windows) `WL_HOME``/samples/domains/examples/startExamplesServer.sh` (UNIX) The server starts as an Administration Server in the Examples domain. On Windows, you can also start ExamplesServer from the Start menu.
An Administration Server that you have created | Invoke: `domain_directory``\startWebLogic.cmd` (Windows) `domain_directory``/startWebLogic.sh` (UNIX) where `domain_directory` is the directory in which you created the domain. If the server prompts you to enter a username and password, enter the name of a WebLogic Server user who has permission to start servers. For more information, refer to "Providing Usernames and Passwords to Start a Server" in the Administration Console Online Help. Note: In a development environment, it is usually sufficient to start an Administration Server and deploy your applications directly onto the Administration Server. In a production environment, you typically create Managed Servers to run applications. On Windows, you can instruct the Domain Configuration Wizard to create a shortcut on the Start menu to start the server that you create. You can also instruct the wizard to install the server as a Windows service. If you do so, the server starts automatically when you boot the host machine.
A Managed Server that you have created | Start the domain's Administration Server. (If you have configured the server as a Windows service, it starts automatically when you boot the Windows host computer.) Start the Node Manager on the computer that will host the Managed Server you want to start. (If you have configured the Node Manager as a Windows service, it starts automatically when you boot the Windows host computer.) For more information, refer to Starting and Stopping Node Manager. Start the domain's Administration Console. For more information, refer to "Starting the Administration Console." In left pane of the Administration Console, expand the Servers folder. Click on the name of the server. (See Figure 11-1.) Figure 11-1 Click on the Name of the Server In the right pane, select the Control —> Start/Stop tab. Select Start this server and click Yes to confirm. For information additional ways to start Managed Servers, refer to "Starting and Stopping Servers."

# Shutting Down Instances of WebLogic Server

The recommended procedure for shutting down a server is as follows:

1. Start the domain's Administration Console. See "Starting the Administration Console" in the Administration Console Online Help.
2. In left pane of the Administration Console, expand the Servers folder.
3. Click on the name of a server. (See Figure 11-1.)
4. In the right pane, select the Control —> Start/Stop tab.
5. Select Shutdown this server and click Yes to confirm.

This initiates a graceful shutdown, in which the server notifies subsystems to complete all in-work requests. After the subsystems complete their work, the server stops.