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, see Starting and Stopping Servers.
In the following table, WL_HOME
refers to the top-level installation directory for WebLogic Server, such as c:\bea\wlserver_10.3\
.
where
DOMAIN_NAME is the name of the directory in which you located the domain, typically BEA_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.
|
|||
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 Node Manager Administrator’s Guide. On Windows, you can use a shortcut on the Start menu to start the Node Manager (WebLogic ServerToolsNode Manager). See “Starting the Administration Console” in Introduction to Oracle WebLogic Server. See “Create and configure machines” and “Assign servers instances to machines” in the Administration Console Online Help.
For information on additional ways to start Managed Servers, see Starting and Stopping Servers.
|
|||
To start clustered Managed Servers with Node Manager, see
“Start Managed Servers in a cluster” in the Administration Console Online Help.
|
It is recommended that you shutdown 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.
On Windows, you can stop the Medical Records Server, Examples Server, and Administration Servers that you have created using the Configuration Wizard, from the Start menu.