A Starting and Stopping Servers: Quick Reference

Learn simple and frequently used ways to start and shut down instances of Oracle WebLogic Server.

Also, see Starting and Stopping Servers.

This appendix includes the following sections:

• Starting Instances of WebLogic Server
  Learn how to start WebLogic Server instances in various domains such as medrec, medrec-spring, wls_examples, and more.
• Shutting Down Instances of WebLogic Server
  Use the Remote Console or a WebLogic Server stop script to shut down WebLogic Server instances.

Starting Instances of WebLogic Server

Learn how to start WebLogic Server instances in various domains such as medrec, medrec-spring, wls_examples, and more.

In the following table, ORACLE_HOME represents the directory you specified as the Oracle Home when you installed WebLogic Server; for example, C:\Oracle\Middleware\Oracle_Home.

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 samples domain. For more informaion, 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 samples domain. 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 Code Examples domain. 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. 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 Remote Console and connect to an Administration Server. See Connect to an Administration Server in the Oracle WebLogic Remote Console Online Help. Associate Managed Servers with Node Manager by assigning them to a Machine upon which Node Manager runs. See Configure Machines and Assign a Server Instance to a Machine in the Oracle WebLogic Remote Console Online Help. In the WebLogic Remote Console, in the Monitoring Tree, go to Environment, then Servers. Select the server you want to start, then click Start. See Starting and Stopping Servers.

Shutting Down Instances of WebLogic Server

Use the Remote Console or a WebLogic Server stop script to shut down WebLogic Server instances.

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

• See Shutdown a Server in the Oracle WebLogic Remote Console Online Help.

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