A Starting and Stopping Servers: Quick Reference

Prefer simple and frequently used methods to start and stop the server instances. It maintains the server life cycle for longer period by avoiding the critical issues associated with the server.

This appendix includes the following sections:

For a comprehensive discussion of starting and shutting down WebLogic Server instances, see Starting and Stopping Servers.

Starting Instances of WebLogic Server

You can use simple methods to start WebLogic Server instances that include the administration server, managed servers, cluster of managed servers, and other example servers.

In the following table, WL_HOME refers to the top-level installation directory for WebLogic Server, such as c:\Oracle\Middleware\Oracle_Home\wlserver\.

Table A-1 Starting Server Instances

To Start	Do The Following
The MedRec server	Invoke: `ORACLE_HOME\user_projects\domains\medrec\bin\startWebLogic.cmd` (Windows) `ORACLE_HOME/user_projects/domains/medrec/bin/startWebLogic.sh` (UNIX) The server starts as an Administration Server in the medrec domain. For more information, see Sample Applications and Code Examples in Understanding Oracle WebLogic Server.
The MedRec server (Spring version)	Invoke: `ORACLE_HOME\user_projects\domains\medrec-spring\bin\startWebLogic.cmd` (Windows) `ORACLE_HOME/user_projects/domains/medrec-spring/bin/startWebLogic.sh` (UNIX) The server starts as an Administration Server in the medrec-spring domain. For more information, see Sample Applications and Code Examples in Understanding Oracle WebLogic Server.
The Examples server	Invoke: `ORACLE_HOME\user_projects\domains\wl_server\bin\startWebLogic.cmd` (Windows) `ORACLE_HOME/user_projects/domains/wl_server/bin/startWebLogic.sh` (UNIX) The server starts as an Administration Server in the wl_server domain. For more information, see Sample Applications and Code Examples in Understanding Oracle WebLogic Server.
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 `ORACLE_HOME\user_projects\domains\DOMAIN_NAME`. If the server prompts you to enter a user name 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 on the Administration Server. In a production environment, you typically create Managed Servers to run applications.
Managed Servers	Start the domain's Administration Server. Start the Node Manager on the computer that will host the Managed Server you want to start. If it's not already running, you can start Node Manager manually at a command prompt or with a script. See Starting and Stopping Node Manager in the Administering Node Manager for Oracle WebLogic Server. Start the domain's Administration Console. See Starting the Administration Console in Understanding Oracle WebLogic Server. Associate Managed Servers with Node Manager by assigning them to a Machine upon which Node Manager runs. See Create and configure machines and Assign servers instances to machines in the Oracle WebLogic Server Administration Console Online Help. In the left pane of the WebLogic Server Administration Console, expand Environment and select Servers. In the right pane, select the Control tab. In the Server Status table, select the check box next to the name of the server you want to start and click Start. 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 Oracle WebLogic Server Administration Console Online Help.

Shutting Down Instances of WebLogic Server

Use the recommended methods to shut down the server instances. These methods help to stop the server instance smoothly without any session data loss.

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

See Shut down a server instance and Control graceful shutdowns in the Oracle WebLogic Server Administration Console Online Help.
For information on gracefully shutting down the Managed Servers in a cluster, see Shutdown servers in a cluster in the Oracle WebLogic Server Administration Console Online Help.

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