Home, Instance, Directories & Domain In Oracle Weblogic (10.3.6) 11g

Home, Instance, Directories & Domain In Oracle Weblogic (10.3.6) 11g

a) MW_HOME – Fusion Middleware Home : This is top level directory for Fusion Middleware products and is created at the time of webLogic Server installation.

b) WLS_HOME – Oracle WebLogic Server Home : This is directory under Fusion Middleware Home and is created at the time of webLogic Server installation. This directory contains binaries (software) for Oracle WebLogic Server.

c) ORACLE_HOME – Oracle Home : contains binaries (software) related to specific oracle middleware product (soa, webcenter,OID, HTTP).
– ORACLE_HOME does NOT contain any logs or configuration files (logs or configuration file will either be in domain orInstance Directory).
– Each Oracle Middleware Product (SOA, WebCenter, OID, HTTP Server) should be installed in its own ORACLE_HOME inside Fusion Middleware Home.
– Oracle HOME resides within directory structure of Fusion Middleware Home
– Each Oracle ORACLE_HOME can be associated with multiple Oracle Instances or WebLogic Domain.

d) ORACLE_INSTANCE – Oracle Instance : contains runtime (configuration, log..) files for one or more System Components (HTTP Server, WebCache, OID)
– System Components (HTTP Server, WebCache, OID) are configured in Oracle Instance
– Oracle Instance can reside anywhere (inside or outside fusion middleware home) on server.

e) WebLogic Domain – Domain is logical grouping of one (and only one) Administration Server and zero or more Managed Server in WebLogic Server.
– Java Components (SOA , WebCenter..) are configured in WebLogic Domain
– You can configure multiple domain for multiple Oracle Fusion Middleware component (one domain for SOA , another for Webcenter third for OID) or can cnfigure all Fusion middleware components in to single domain (webcenter, SOA, OID in same domain)

Homes in Weblogic:
There are 4 homes in weblogic.
1)JAVA_HOME
2)WL_HOME
3)MW_HOME
4)DOMAIN_HOME

Directories in Weblogic:

1.Java_Home
Bin---------important binaries related to java, like jps and jstack.     
Lib --------.jar files
Db
a)bin-------.bat files
b)lib-------some .jar files
Man-----------UTF-8 and man related directory     
Include-------linux dir and .h files
Jre
a)bin------some important binaries of java, like jcontrol, servertool etc.
b)lib------some libraries.
c)plugin and .txt files-----desktop dir.


2.Wl_home
cd $WL_HOME
common  inventory  L10N  server  sip  uninstall

$WL_HOME/common
bin  deployable-libraries  derby  eval  lib  nodemanager  quickstart  templates  wlst

$WL_HOME/common/bin
commEnv.sh  config.sh  setPatchEnv.sh  startManagedWebLogic.sh  unpack.sh   wlscontrol.sh   wlst.sh
config_builder.sh  pack.sh  startDerby.sh  stopDerby.sh  upgrade.sh  wlsifconfig.sh

$WL_HOME/common/nodemanager
nm_data.properties  nodemanager.domains  nodemanager.log  nodemanager.log.lck  nodemanager.properties

$WL_HOME/common/quickstart
images  quickstart.sh  resources  wls_qsConfig.xml

$WL_HOME/common/templates
applications  domains  scripts  silent_scripts
Inventory
L10N
Server
Sip
Uninstall   

$WL_HOME/server/bin
international  nohup.out  setWLSEnv.sh  startNodeManager.sh

3.MW_HOME

cd $MW_HOME
domain-registry.xml  modules  patch_wls1036  registry.xml   utils
logs  ocm.rsp  registry.dat   user_projects  wlserver_10.3

cd $MW_HOME/utils
bsu  ccr  clone  config  quickstart  uninstall  utils.jar

cd $MW_HOME/utils/bsu
bsu.jar  bsu.sh  cache_dir  patch-client.jar  smartupdate.ico

cd $MW_HOME/utils/quickstart
images  libjni.so  qs.html  quickstart.jar  quickstart.sh

cd $MW_HOME/utils/uninstall
extftr  libjni.so  uninstall.jar  uninstall.sh  WebLogic_Platform_10.3.6.0

cd $MW_HOME/logs
wlsconfig_20151211131015.log  wlst_20151214124918.log  wlst_20151217155251.log  wlst_20151218121910.log
wlsconfig_20151219172057.log  wlst_20151214124918.out  wlst_20151217155251.out  wlst_20151218121910.out
wlst_20151211134604.log       wlst_20151217091248.log  wlst_20151217161205.log  wlst_20151218122907.log

4.Domain_home

cd $DOMAIN_HOME
autodeploy  config    edit.lok  init-info  pending   servers   startWebLogic.sh
bin  console-ext  fileRealm.properties  lib  security  shutdown.py  tmp

cd $DOMAIN_HOME/config
configCache  config.lok  config.xml  deployments  diagnostics  jdbc  jms  nodemanager  security  startup

cd $DOMAIN_HOME/init-info
domain-info.xml  security.xml  startscript-unsub.xml  startscript.xml  tokenValue.properties

cd $DOMAIN_HOME/servers
AdminServer  domain_bak  ms-01  ms-02  ms-03  ms-04

cd $DOMAIN_HOME/bin
nodemanager  server_migration   setDomainEnv.sh          startWebLogic.sh        stopWebLogic.sh
nohup.out    service_migration  startManagedWebLogic.sh  stopManagedWebLogic.sh

Note:
1)Pending directory in DOMAIN_HOME
2)domain_bak under DOMAIN_HOME/servers
3)cache_dir under MW_HOME/utils/bsu

4)Autodeploy under DOMAIN_HOME
Pending directory: This directory contains the domain configuration files that represent the configuration changes that have

been requested, but not yet been activated. After the configuration changes are activated, the configuration files are deleted

from this directory. Configurations can be changed at runtime in the console of the Administration Server. Before they are

implemented within the domain, they are temporarily stored in this directory.

1.start/stop of Admin and Managed servers and contains configuration files.
setDomainEnv.sh
startWebLogic.sh
stopWeblogic.sh
$DomainHome/$serverName/bin

2. All important components e.g.  Domain configurtaion,  JMS, JDBC etc
config.xml
jdbc config files
jms config files
fmwconfig files etc
$DomainHome/$serverName/config

4. Encrypted wls username and password, used while starting the server.
boot.properties
$DomainHome/$serverName/servers/AdminServer/security

5. nodemanager script and other environment scripts are located:
startNodeManager.sh
setWLSEnv.sh
$WL_HOME\server\bin

6. All troubleshooting logfiles are stored:
access.log,
AdminServer.log
ManagedServer.log
gc.log
domain.log
AdminServer.out
ManagedServer.out files
$DomainHome/$serverName/servers/$serverName/logs

6.Contains Management Service logs and trace file for troubleshooting purpose.
emoms.log
emoms.trc
$DomainHome/$serverName/sysman/log

7. weblogic related important files are located:
commEnv.sh       
config.sh
setPatchEnv.sh
startManagedWebLogic.sh
unpack.sh 
wlscontrol.sh 
wlst.sh
config_builder.sh
pack.sh 
startDerby.sh 
stopDerby.sh           
upgrade.sh
wlsifconfig.sh
$WL_HOME/common/bin

8. Node manager related important files are located:
nm_data.properties
nodemanager.domains
nodemanager.log
nodemanager.log.lck
nodemanager.properties
$WL_HOME/common/nodemanager

9. weblogic upgrading related scripts loacted:
quickstart.sh
$WL_HOME/common/quickstart

1) where is the location of config.sh in wl (for domain creation) ?
ans) cd $WL_HOME/common/bin

2) where is the location of Nodemanager startup script ?
ans) cd $WL_HOME/server/bin

3) Where is Nodemanager configuration files ?
ans) cd $WL_HOME/common/nodemanager

4) Weblogic uninstall utility ?
ans) cd $WL_HOME/uninstall

5) Weblogic quickstart location ?
ans) cd $WL_HOME/common/quickstart

6) Logfiles location in Middleware ?
ans) cd $MW_HOME/logs

7) Where is the location of bsu.sh script ?
ans) cd $MW_HOME/utils/bsu

8) Domain directories location ?
ans) cd $MW_HOME/user_projects

9) Where is the location of Autodeploy directory ?
ans) cd $DOMAIN_HOME

10) Where is the location of startup & shutdown scripts for weblogic and managed server ?
ans) cd $DOMAIN_HOME/bin

11) Where is the location of nm_password.properties ?
ans) cd $DOMAIN_HOME/config/nodemanager

12) Where is the location of Admin server and Managed server logfiles (tmp/cache/logs)?
ans) cd $DOMAIN_HOME/servers