This script outputs the google search URL required for search on edocs documentation.
This script outputs the banner required for edocs documentation.
This script outputs the google search parameters required for search on edocs documentation.
Managing Server Startup
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, see Starting and Stopping Servers.
Starting Instances of WebLogic Server
In the following table,
WL_HOME refers to the top-level installation directory for WebLogic Server, such as
Table A-1 Starting Server Instances
The server starts as an Administration Server in the medrec domain.
On Windows, you can start the Medical Records Server from the Start menu (Examples
Start Medical Records Server). By default, the username and password for the medrec domain are set to
The server starts as an Administration Server in the wl_server domain.
On Windows, you can start the Examples Server from the Start menu (Examples
Start Examples Server). By default, the username and password for the wl_server domain are set to
An Administration Server that you have created
is the name of the directory in which you located the domain, typically
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
Start Admin Server for WebLogic Domain).
Start the domain’s Administration Server.
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 and Servers.
On Windows, you can use a shortcut on the Start menu to start the Node Manager (Tools Node Manager).
Start the domain’s Administration Console.
" in Starting the Administration Console Introduction to WebLogic Server and WebLogic Express.
Associate Managed Servers with Node Manager by assigning them to a Machine upon which Node Manager runs.
” and “ Configure Machines
” in the Assign Servers Instances to Machines Administration Console Online Help.
In the left pane of the Administration Console, expand Environment and select Servers.
In the Servers table, click the name of the Managed Server you want to start.
Select Control Start/Stop.
In the Server Status table, select the check box next to the name of the server you want to start and click Start.
Click Yes to confirm.
For information on additional ways to start Managed Servers, 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
Administration Console Online Help
Shutting Down Instances of WebLogic Server
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.