bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Administration Console Online Help

Server --> Control --> Start-Stop

Tasks Additional Documentation

Overview

The Server—>Control—>Start/Stop tab changes the state of a server. Some of these commands require special setup and cannot be used for an Administration Server.

The following table describes the applicability and requirements of each command:

Command | Description | Requirements/Restrictions
--- | --- | ---
Start this server in standby mode | Starts a Managed Server but places it in the STANDBY state. In this state, the server can accept administration commands and it can participate in cluster communication, but it is not accessible to requests from external clients. | Requires the Node Manager. Requires the administration port to be enabled. Only available for Managed Servers.
Start this server | Starts a Managed Server. | Requires the Node Manager. Only available for Managed Servers.
Resume this server | Moves a server from the STANDBY state to RUNNING. | Requires the administration port to be enabled.
Shutdown this server | Gracefully stops a server. New requests are rejected but in-work requests are completed before the server stops. |
Force shutdown of this server | Immediately stops a server. In-work requests are dropped, no new requests are accepted, and the server immediately stops. |

Other settings affect how the commands on this tab behave:

- On the Servers—>General tab, in the Startup Mode field, you can specify the state in which a server starts. However, this setting only applies if you start a server from the local host using the weblogic.Server command. The Node Manager, and therefore the Start this server in standby mode... and Start this server... commands, do not use the value that you specify. For example, even if you specify RUNNING as the value for the Startup Mode, if you issue the Start this server in standby mode... command on this tab, the server will start in the STANDBY state.

- On the Servers—>General tab, in the Timeout for Server Lifecycle Operations box, you can enter the number of seconds that a lifecycle operation waits before timing out.

When you start a Managed Server using Node Manager, the messages that are usually printed to STDOUT or STDERROR when starting a WebLogic Server are displayed in the right pane of the Administration Console. These messages are also written to the Node Manager log file for that server.

Tasks

Starting a Server

Starting a Server in the STANDBY State

Resuming a Server

Shutting Down a Server

Forcing Shutdown of a Server

Configuring a Machine to Use Node Manager

Starting and Shutting Down Domains

Setting the Timeout Period for LifeCycle Operations

Additional Documentation

(Requires an Internet connection.)

Starting and Stopping WebLogic Servers

Managing Server Availability with Node Manager

Timeout Period for LifeCycle Operations

For information about administration ports, refer to Configuring a Domain-Wide Administration Port in the Managing and Monitoring WebLogic Server Domains guide.