Skip navigation.
Downloads | Product Documentation | Support

Managing Server Startup and Shutdown

# 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, see Starting and Stopping Servers.

# Starting Instances of WebLogic Server

In the following table, `WL_HOME` refers to the top-level installation directory for WebLogic Server, such as `c:\bea\weblogic90\`.

Table A-1 Starting Server Instances

To Start | Do The Following
--- | ---
The MedRec server | Invoke: `WL_HOME``\samples\domains\medrec\bin\startWebLogic.cmd` (Windows) `WL_HOME``/samples/domains/medrec/bin/startWebLogic.sh` (UNIX) The server starts as an Administration Server in the medrec domain. On Windows, you can start the Medical Records Server from the Start menu (Examples—>WebLogic Server—>Start Medical Records Server). By default, the username and password for the medrec domain are set to `weblogic`.
The Examples server | Invoke: `WL_HOME``\samples\domains\wl_server\bin\startWebLogic.cmd` (Windows) `WL_HOME``/samples/domains/wl_server/bin/startWebLogic.sh` (UNIX) The server starts as an Administration Server in the wl_server domain. On Windows, you can start the Examples Server from the Start menu (Examples—>WebLogic Server—>Start Examples Server). By default, the username and password for the wl_server domain are set to `weblogic`.
An Administration Server that you have created | Invoke: `DOMAIN_NAME``\bin\startWebLogic.cmd` (Windows) `DOMAIN_NAME``/bin/startWebLogic.sh` (UNIX) where `DOMAIN_NAME` is the name of the directory in which you located the domain, typically `BEA_HOME``\user_projects\domains\``DOMAIN_NAME`. 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, see Provide User Credentials to Start and Stop Servers. 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, the Configuration Wizard creates a shortcut on the Start menu to start the Administration Server that you created (User Projects—>`DOMAIN_NAME`—>Start Admin Server for WebLogic Domain).
Managed Servers | 1. Start the domain's Administration Server. 2. Start the Node Manager on the computer that will host the Managed Server you want to start. The WebLogic Server custom installation process optionally installs and starts Node Manager as a Windows service on Windows systems. If it's not already running, you can start Node Manager manually at a command prompt or with a script. See Starting and Running Node Manager. On Windows, you can use a shortcut on the Start menu to start the Node Manager (Tools—>Node Manager). 3. Start the domain's Administration Console. See "Starting the Administration Console" in Introduction to WebLogic Server and WebLogic Express. 4. Associate Managed Servers with Node Manager by assigning them to a Machine upon which Node Manager runs. See "Configure Machines" and "Assign Servers Instances to Machines" in the Administration Console Online Help. 5. In the left pane of the Administration Console, expand Environment and select Servers. 6. In the Servers table, click the name of the Managed Server you want to start. 7. Select Control—>Start/Stop. 8. In the Server Status table, select the check box next to the name of the server you want to start and click Start. 9. Click Yes to confirm. For information on additional ways to start Managed Servers, see Starting and Stopping Servers.
A cluster of Managed Servers | To start clustered Managed Servers with Node Manager, see "Start Managed Servers in a Cluster" in the Administration Console Online Help.

# Shutting Down Instances of WebLogic Server

It is recommended that you shutdown WebLogic Server instances through the Administration Console:

- See "Shut Down a Server Instance" and "Control Graceful Shutdowns" in the Administration Console Online Help.
- For information on gracefully shutting down the Managed Servers in a cluster, see "Shut Down Servers in a Cluster" in the Administration Console Online Help.

Alternatively, invoke a Weblogic Server stop script to shutdown the server. See Shutting Down Servers with a Stop Script.

On Windows, you can stop the Medical Records Server, Examples Server, and Administration Servers that you have created using the Configuration Wizard, from the Start menu.