A Starting and Stopping Servers: Quick Reference

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

This appendix includes the following sections:

See Starting and Stopping Servers.

Starting Instances of WebLogic Server

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

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.

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.

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.

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

  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.

    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.

  3. Start the domain's Administration Console.

    See Starting the WebLogic Server Administration Console in Understanding Oracle WebLogic Server.

  4. 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.

  5. In the left pane of the WebLogic Server Administration Console, expand Environment and select Servers.

  6. In the right pane, select the Control tab.

  7. In the Server Status table, select the check box next to the name of the server you want to start and click Start.

  8. Click Yes to confirm.

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 Administration Console or stopWeblogic script to shut down WebLogic Server instances.

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

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