How to start and stop Weblogic Server

An Administration Server is a Weblogic Server instance that maintains configuration data for a domain. 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.

Before starting services in Oracle Weblogic, ensure that you are familiar with Domain , Administration & Managed Server

There are multiple ways to start Weblogic server. This post covers Weblogic Startup/Shutdown using scripts.  

There are two type of Weblogic Server instance in a domain, Administration Server and Managed Server

–You can start Managed Server without Administration Server with exception for first time. If you are starting Managed Server for first time then Administration Server should be Up. Managed Server can cache config files locally(in its local config directory) and later Managed Server can start on its own.
– To start Managed Server using script, supply Admin Server protocol, Server Name and Listen Port(check startup command for more information).
–If startup mode of domain is “production” then startup will prompt you for username & password to start services 

–If you create domain and startup mode is “development” then startup will not prompt for username/password as username password are stored in boot identity file in security directory of Domain at BEA_HOME / user_projects / domains / <domainName> / servers/ <serverName>/ security / boot.properties
 

Step to start the Admin Server

Ways to start Administration Server in Oracle Weblogic

1.Using startup script
2. From Windows Start Menu (windows only)
3. Using “java weblogic.Server” command
4. Using WLST (WebLogic Scripting Tool) and Node Manager
5. Using WLST without Node Manager

Step to start the Managed Server

Ways to start Managed Server in Oracle WebLogic 

1.Using startup script
2. Using Administration Console
3. Using WLST and Node Manager
4. Using “java weblogic.Server” command

Below is the another way to start the Servers 

1. Starting Administration Server (startWeblogic.cmd or .sh)

2. Starting Managed Server (startManagedWeblogic.sh or .cmd)

To Start WebLogic Administration Server Instance

Go to domain for which you wish to start Administration Server

cd $BEA_HOME/user_projects/domains/<domain_name>/bin

startWeblogic.cmd (for Windows)
startWeblogic.sh (for Unix)

confirm that Weblogic Administration Server started properly by looking at message “Service started RUNNING mode“. Log file in below picture shows that Admin Sever is listening on Port 7001 and all IP addresses on specific machine.

Startup/Shutdown Log file can be found at $BEA_HOME/ user_projects/ domains/ <domain_name> /servers/<ServerName> /logs / <ServerName>.log

To Start Managed Server Instance
If you created Managed Server while creating domain then you can start Managed Server using startManagedWebLogic command

$BEA_HOME/user_projects/domains/<domain_name>/bin

startManagedWeblogic.cmd <managed_server_name> <admin_url> (for Windows)
startManagedWeblogic.sh  <managed_server_name> <admin_url> (for Unix)

I created Managed Server MS1 with Admin Port as 7003
startManagedWeblogic.cmd ms1 http://localhost:7003 (Windows)

For further reference, please check the below mention link.

http://docs.oracle.com/cd/E11035_01/wls100/server_start/server_startTOC.html