bea.com | products | dev2dev | support | askBEA |
|
e-docs > WebLogic Server > Configuring and Managing WebLogic Server > Starting and Stopping Servers: Quick Reference |
Configuring and Managing WebLogic Server |
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.
WL_HOME\samples\server\config\startMedRecServer.cmd (Windows) 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 |
|
WL_HOME\samples\server\config\startExamplesServer.cmd (Windows) 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 |
|
domain_directory\startWebLogic.cmd (Windows) 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 |
|
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:
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.