In this blog, I will cover important steps that are required after successfully installing and configuring your weblogic domain.
1) Environment File.
If you have not created environment file yet, create one now.
export ORACLE_BASE=/u01/app/oracle export ORACLE_HOME=$ORACLE_BASE/middleware/Oracle_Home export ORACLE_COMMON=$ORACLE_HOME/oracle_common export MW_HOME=$ORACLE_HOME export WLS_HOME=$MW_HOME/wlserver export WL_HOME=$WLS_HOME export DOMAIN_BASE=$ORACLE_BASE/config/domains export DOMAIN_HOME=$DOMAIN_BASE/fmw_domain export JAVA_HOME=$MW_HOME/java/jdk1.7.0_79 export PATH=$JAVA_HOME/bin:$PATH
2) boot.properties file.
If you have configured domain in Development mode, it will automatically be created for you else if you have configured it in Production mode, you have to create it manually.
The password will be encrypted first time you start the server.
3) Starting the Weblogic Server Instance.
Oracle recommends following sequence to start the server instances.
a) Start Node Manager
b) Start Admin Server
If you tail the startup logs, you will see server instance using boot.properties file that we created eariler.
Wait for the server to be in RUNNING state.
Now you can access weblogic admin console which is deployed on Admin Server.
c) start Managed Server
Do not forget to create boot.properties as we did it for AdminServer.
$DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_server_url
Once you execute above command, you will see the status of Managed server getting changed to STARTING and then RUNNING.
We started first managed server using script. Lets start the other one using Admin Console. Make sure NodeManager is running because Admin Server coordinates with NodeManager to start Managed Server.
You can check, what’s happening in background in logs at below highlighted location.
4) Stopping the Weblogic Server Instance.
You can use below command to stop admin and managed server.
$ # Stop WebLogic Admin Server $ $DOMAIN_HOME/bin/stopWebLogic.sh $ # Stop Managed Server $ $DOMAIN_HOME/bin/stopManagedWebLogic.sh OW_MS1
To STOP NodeManager just kill -9 the process id.