A Starting and Stopping Servers: Quick Reference

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 (WebLogic Server > Examples > Start Medical Records Server). By default, the username for the medrec domain is set to weblogic and the password is welcome1.

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 (WebLogic Server > Examples > Start Examples Server). By default, the username for the wl_server domain is set to weblogic and the password is welcome1.

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 MW_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 Node Manager" in the Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server.

• On Windows, you can use a shortcut on the Start menu to start the Node Manager (WebLogic Server > Tools > Node Manager).

• See "Starting the Administration Console" in Oracle Fusion Middleware Introduction to Oracle WebLogic Server.

• Start the domain's Administration Console.

3. 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 Fusion Middleware Oracle WebLogic Server Administration Console Help.

4. In the left pane of the Administration Console, expand Environment and select Servers.

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

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

7. Click Yes to confirm.

For information on additional ways to start Managed Servers, see Chapter 2, "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 Fusion Middleware Oracle WebLogic Server Administration Console Help.