Oracle EBS R12 Architecture
Oracle EBS R12 Architecture
Oracle EBS R12 Architecture
(EBS)
What is Oracle Applications/Oracle E-Business Suite ?
Oracle Cost Management helps to maintain the costs of items in your inventory
and the immediate modules that it interacts with are Oracle Inventory, Oracle
Bills of Material, Order Management.
10.7 : Oldest Release of Oracle ERP which is character, thin client based. Oracle has
stopped support for this release from year 1998.
11 :
11i :
R12 : Latest Release Of EBS by Oracle .
1
Oracle EBS R12 Architecture
Oracle EBS R12 Applications is a three-tiered architecture.
1. Desktop Tier
2. Application Tier
3. Database Tier
Desktop Tier :
The Forms client applet must be run within a Java Virtual Machine (JVM) on the
desktop client. The Sun J2SE Plug-in component allows use of the Oracle JVM on web
clients, instead of the browser’s own JVM. This is implemented as a browser plug-in.
Please Note : In 11i , we use Jinitiator for the for the JVM.
In Release 12, the application tier contains Oracle Application Server 10g
(OAS10g). Three servers or service groups comprise the basic application tier
for Oracle Applications:
• Web services
2
• Forms services
Database Tier :
The database tier contains the Oracle database server, which stores all the
data maintained by Oracle Applications.
Techstack Components :
DB_TIER
APPL-TIER
3
There are two versions of Oracle Application server 10g (OAS10g) used,
4
(ORACLE EBS R12 ORACLE_HOMES )
Oracle EBS R12 file system has come up with new model - Code, Data,
Configurations are segregated for easy maintenance, to avert NFS mount issues on
shared appl tier configuration systems. Auto-config will not write anything in
APPL_TOP, COMMON_TOP area in R12. All instance specific configurations, log files
are written in INST_TOP area. Instance Home provides the ability to share
Applications and technology stack code among multiple instances.
The image shown below describes the complete directory structure for complete e-bs
installation i.e. DB_TOP, APPL_TOP and new INST_TOP. If you look into the
INST_TOP we will find that it only contains all the configuration files, start-stop
scripts, log files, certificate files, pid files etc, so as to make DB_TOP and APPL_TOP
untouched for any instance specific changes.
5
INSTANCE TOP :
Instance home is the top-level directory for an Applications Instance which is known
as Instance Home and is denoted the environment variable $INST_TOP. This contains
all the config files, log files, SSL certificates etc.
• The additional Instance Home makes the middle tier easier to manage
and organized since the data is kept separate from the config files.
• The Instance Home also has the ability to share the Applications and
Technology stack code across multiple instances.
• Another advantage of the Instance Home is that the Autoconfig writes only
in INST_TOP so APPL_TOP and ORACLE_HOME can also be made read only
file system if required.
• To create a new instance that shares an existing middle-tier, just create a
new instance_top with proper config files and NFS Mount the middle tier
in the
6
INSTANCE TOP – STRUCTURE:
$INST_TOP: $APPS_BASE/inst/apps/$CONTEXT_NAME/
/admin
/scripts : ADMIN_SCRIPTS_HOME: Find all AD scripts here
/appl : APPL_CONFIG_HOME. For standalone envs, this is set to
$APPL_TOP
/fnd/12.0.0/secure : FND_SECURE: dbc files here
/admin : All Env Config files here
/certs : SSL Certificates go here
/logs : LOG_HOME: Central log file location. All log files are
placed here (except adconfig)
/ora : ORA_CONFIG_HOME
/10.1.2 : 'C' Oracle home config, Contains tnsnames and forms
listener servlet config files
/10.1.3 : Apache & OC4J config home, Apache, OC4J and opmn
This is the 'Java' oracle home configuration for OPMN, Apache
and OC4J
/pids : Apache/Forms server PID files here
/portal : Apache's DocumentRoot folder