bea.com | products | dev2dev | support | askBEA
 Download Docs   Site Map   Glossary 
Search

Configuring and Managing WebLogic Server

 Previous Next Contents Index View as PDF  

Starting and Stopping Servers: Quick Reference

The following sections describe simple, frequently used ways to start and shut down instances of WebLogic Server:

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

 


Starting Instances of WebLogic Server

In the following table, WL_HOME refers to the directory in which you installed the WebLogic Server software.

Table 11-1 Starting Server Instances

To Start

Do The Following

The MedRecServer sample server

Invoke the following command:

WL_HOME\samples\server\config\startMedRecServer.cmd (Windows)
WL_HOME\samples\server\config\startMedRecServer.sh (UNIX)

The server starts as an Administration Server in the MedRec domain.

On Windows, you can also start MedRecServer from the Start menu by selecting Start—>Programs—>BEA WebLogic Platform 8.1—>BEA WebLogic Server 8.1—>Server Tour and Examples—>Launch Medical Records

The Examples server

Invoke the following command:

WL_HOME\samples\server\config\startExamplesServer.cmd (Windows)
WL_HOME\samples\server\config\startExamplesServer.sh (UNIX)

The server starts as an Administration Server in the Examples domain.

On Windows, you can also start ExamplesServer from the Start menu by selecting Start—>Programs—>BEA WebLogic Platform 8.1—>BEA WebLogic Server 8.1—>Server Tour and Examples—>Launch Examples Server

An Administration Server that you create

Invoke the following command:

domain_directory\startWebLogic.cmd (Windows)
domain_directory\startWebLogic.sh (UNIX)

where domain_directory is the directory that you specified as the domain directory.

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 create Managed Servers to run applications.

On Windows, you can instruct the Domain Configuration Wizard to create a shortcut on the Start menu for the server that you create. If you do so, you can start your Administration Server from the Start menu by selecting Start—>Programs—>BEA WebLogic Platform 8.1—>User Projects—>domain_name—>Start Server

A Managed Server that you create

Do the following:

  1. Start the domain's Administration Server.
  2. Configure the Managed Server to communicate with a Node Manager. For more information, refer to "Configuring a Machine."
  3. Start the Node Manager on the computer that you want to host the Managed Server.
    For more information, refer to "Starting Node Manager."
  4. Start the domain's Administration Console.
    For more information, refer to "Starting the Administration Console."
  5. In left pane of the Administration Console, expand the Servers folder.
  6. Click on the name of the server. (See Figure 11-1.)

    Figure 11-1 Click on the Name of the Server


     

  7. In the right pane, select the Control tab. Then select the Start/Stop tab.
  8. Select Start this server. Then click Yes to confirm and start the server.

For information additional ways to start Managed Servers, refer to "Starting and Stopping Servers."

For information on the username and password that you use when starting a server, refer to "Providing Usernames and Passwords to Start a Server."

 


Shutting Down Instances of WebLogic Server

The recommended procedure for shutting down a server is as follows:

  1. Start the domain's Administration Console. For more information, refer to "Starting the Administration Console"
  2. In left pane of the Administration Console, expand the Servers folder.
  3. Click on the name of a server. (See Figure 11-1.)
  4. In the right pane, select the Control tab. Then select the Start/Stop tab.
  5. Select Shutdown this server. Then click Yes to confirm and shut down the server.

This initiates a graceful shutdown, in which the server notifies subsystems to complete all in-work requests. After the subsystems complete their work, the server stops.

 

Back to Top Previous Next