AD FILE IDENTIFICATION

TO FIND THE VERSION OF A PARTICULAR FILE

Up to 12.1 VERY RARELY used the above service. From 12.2 onwards, for registering the Custom
developed also needs to register and it should do through the AD SPLICE. For custom product
schema (custom registered schema) will there for registering this AD Splice need s to run.

LICENSE MANAGER
REPORTS
It is run through OAM. Base language is always American English.
Applin DBA online patching(ADOPMON) utility. Will monitor the current patching .eg while patching,
if monitoring ADOPMON will gives you what is running in the current session

ADOP patching detailed information will be there in AD_ZE_LOGS TABLE, more information in
ADOPMON utility. The above table don’t have the full information that means 5 mins earlier data,
only current information.

This utility will give you only the required event information. This utility logs located in $AD_TOP/bin
MODULE 5 LESSION 3

S_EBS_BASE – base directory of EBS

Anything which is product is using or patch update that under FS1 and FS2. Anything is not impacted
by patch is under Non Editioned FS.

PATCH_TOP – the location where the patches are copying.

APPL_TOP_NE – appl top specific to NE version.

APPLCSF – it will look into the concurrent Manager Layer.

Inst_top is local FS.

FUSION MIDDLEWARE
Webtier is the WEBTIER ORACLE_HOME(OHS) (above mentioned)

Webtier configuration files are stored in instances folder and it is the Webtier INSTANCE_HOME as
above mentioned.

WL_HOME = wlsserver_10.3

DOMAIN_HOME is represented by user_projects

, ORACLE_HOME and INSTANCE_HOME comes under the WL_HOME

Webtier is the webserver and is built on the top of Apache Server. HTTP requests are served by this
server.

Oracle_common (ORACLE_HOME common above markded) is the folder where the multiple
common files which is common across the FMW. PATCHING and CLONING the FWM env. Files are in
this common oracle home.
Lesson 4 – Common Top, Appl Top,
Log Home

Once Java classes are compiled from the java folder, then the compiled java files moved to the
_pages.
JAR files means JAVA put it into JAVA Archive files.

JRE- java Runtime Environment.

Each products core files are in the APPL_TOP. It is parallel to COMMON_TOP in the directory
structure. It is under FS1/EBsApps and FS2/ EBsApps.

$CONTEXT_HOME = <SID>_<HOSTNAME>

$LOG_HOME under the INST_TOP only.

INST_TOP will not have the configuration files.

$INST_TOP/logs does not have the logs for

a. Oracle Http Server (OHS)

b. Weblogic Server (WLS)
c. Concurrent Manager (CM)
d. Patch
AutoConfig logs are under the $INST_TOP/admin/logs

Lesson 5 – Console – WebLogic &

FMW Control in R12.2

WLS is a logical collection of JVM, JDBC and so on.

Only one Admin Server is possible in EBS WebLogic Doman.

In WLS, we have both the admin server and Managed Servers.

In EBS, we can have either Single Appln Tier or Multiple Appln. Tier if High Availability (HA) is
there.

If HA is there, Admin Server cannot run from multiple nodes. It is always be active/passive. If one
admin server goes down, either manually or automatically we need to migrate the admin server
and start the node.

If Admin Server down, the pathing cannot be triggered.

The Admin Server serve two console a. WebLogic Console(/console) & FMW/em console(/em).
Default port number for Weblogic Admin default port is 7001.
Performance Tuning related console for JDBC in WLS

The Data Source connected in WLS and this is the way EBS appln tier is talking to the Database

using OACORE and FORMS clusters. The connections are using by the JDBC.

One Admin Server and 4 Cluster Managed Servers.

Module-6 Lesson 1 – R12.2 Services
Start/Stop Overview