Professional Documents
Culture Documents
Oracle Apps Architecture
Oracle Apps Architecture
Slide No. 1
e- Business Suite
Financial,
Human Resources,
Manufacturing,
Supply Chain,
Front Office Applications
Slide No. 3
Oracle Applications
Product Families
Oracle Business Productivity
Slide No. 4
Slide No. 5
Slide No. 7
Servlet Engine
Java Server Pages (JSP)
WebDB
Discoverer
Slide No. 8
Slide No. 9
Slide No. 10
Application Tier
The application servers form the middle tier between the
desktop clients and Release 11 database servers.
They provide load balancing, business logic, and other
functionality.
In installations that use multiple application servers, only one
needs to run the Oracle Web Application Server software.
The application tier has Forms server, Reports Server, HTTP
Server (WebDB/Apache HTTP), Concurrent Processing
server, Discoverer Server, Administration Server
Slide No. 11
Slide No. 12
Form Server
The Forms client can display any Oracle Applications screen,
and provides field-level validation, multiple coordinated
windows, and data entry aids such as list of values.
A Java-enabled Web browser manages the downloading,
start-up, and execution of the Forms client on the desktop.
Another software component, the HTTP server, helps start a
client session over the internal or external Web. The HTTP
server in Release 11i is WebDB
Slide No. 13
Slide No. 14
Database Tier
Release 11 Database Tier
The database tier holds all data and data-intensive programs, and
processes all SQL requests for data
The database tier includes the
Oracle8 Server
administration server
concurrent processing server.
Slide No. 15
Database Tier
Database Server
The Release 11 database server contains the data associated
with Oracle Applications.
This machine does not contain any Oracle Applications files,
only the Oracle8 Server files, and an Applications database
instance that physically stores the tables, indexes, and other
database objects for your installation.
The installation process for Oracle Applications
begins at database tier, by installing and creating a database and
configuring Net8 to accept connections from other servers.
Once you have created your database, you administer the
Applications data from the administration server.
Slide No. 16
Database Tier
Administration Server
The administration server is the machine from which you maintain
the data in your Applications database.
There are three types of operations you will carry out here, each
using a different program:
Installing and upgrading the database. You use the AutoInstall program
to do this.
Applying Applications database updates. You use the AutoPatch
program to apply the updates ( bugs fixes) to the database objects
from the administration server
Maintaining the Applications data. The AD Administration program
(adadmin) allows you to do this.
Report Reviewing
Report Reviewer
Oracle Applications uses a tool called the Report Review
Agent to view concurrent processing files online.
This utility is on the concurrent processing server and uses
Net8 to transfer files from the concurrent processing server
to the forms server.
It then transmits the file contentsone page at a time or in
its entiretyto the desktop client.
The forms server sends reports to the client web browser for
online viewing in either unformatted text, native HTML or
Adobe Acrobat format.
Slide No. 19
Slide No. 20
HTML-Based Products
In addition to Forms-based products, Release 11i includes
other products that are not Forms-based, such as the Oracle
Self-Service Web Applications products, Oracle Workflow,
and the Oracle Business Intelligence System (BIS) products.
Do not use the Forms server as the application tier software
or the Forms client on the desktop
Rely on HTTP-based servers on the application tier and a
Java-enabled Web browser on the desktop.
The Self-Service Applications are designed in pure HTML and
JavaScript, and operate by direct connection to an HTTP
listener running Oracle Web Application Server
Slide No. 21
Discoverer
Reports
Forms
Concurrent Manager
Slide No. 22
Slide No. 23
HTML-based Products
Logic is controlled through stored procedures that execute
through the Web Application Servers PL/SQL Cartridge, and
Java servletsJava programs executed by the Web
Application Serverthat communicate with the database
using JDBC.
They operate by direct connection to an HTTP server, such as
WebDB or the Apache HTTP server.
The Apache and WebDB servers can be the same machines
used by Oracle Forms.
Slide No. 24
Servlet Engine
Java Server Pages (JSP)
WebDB
Forms
Concurrent Manager
Slide No. 25
BIS
To support BIS ERP products, Release 11i includes a file that
will generate an Oracle Discoverer End User Layer (EUL).
When the EUL is generated, workbooks and queries can be
saved to the database.
Slide No. 27
BIS
Desktop Tier
Browser
running Java
applet and
HTML
Application Tier
Database Tier
HTTP Server
(WebDB)
Data Server
Reports Server
Discoverer Server
Slide No. 28
Discover End
User
Layer
(EUL)
Slide No. 29
Oracle Applications
File system Level ( Directory structure & standards)
Database Level
Logical setup in Oracle Applications for above two
Slide No. 30
Fnd
Admin
AU
AR
GL
11.5.0
bin
Admin
forms
Help
reports
sql
11.5.0
bin
Admin
forms
Help
reports
US
sql
US
sql
*.sql files
*.rdf files
*.fmx files
Pl/sql procedure,
package definition
files *.pls
Slide No. 32
Directory Structure
Product TOP Variables
AutoInstall sets <prod>_TOP environment variables that point to
each products directory tree.
In the installation depicted in earlier slide the variable GL_TOP
points to $APPL_TOP/gl/11.5.0
To display data entry forms for Oracle General Ledger, for
example, the Oracle Applications system accesses files in
$GL_TOP/forms.
Slide No. 33
Directory Structure
Forms directory contains executable fmx files.
bin : Contain executables code of your concurrent
programs written in a programming language such as C,
Pro*C, Fortran, or an operating system script.
lib: Contains compiled object code of your concurrent
programs.
Sql : Contains concurrent programs written in SQL*Plus and
PL/SQL scripts.
RESOURCE: Contains PL/SQL libraries used with Oracle
Forms, which must be copied to $AU_TOP for forms
generation.
Reports: contains *.rdf files for reports to be executed thru
concurrent programs.
Slide No. 34
Directory Structure
Admin Directory and Environment File
The admin directory (which replaces the install directory from
previous releases) holds files used to install or upgrade any
Oracle Applications products.
This admin directory is used by AutoInstall.
Subdirectories in this directory hold the log and restart files that
record the actions AutoInstall performs.
Java and HTML Files
Java file naming conventions indicate that a machine should have
a single directory under which all Java class files are stored.
Slide No. 35
Directory Structure
Localization Directories
For product files, each localization region is treated like a
separate product. Module files are stored in the region
directory trees.
for example European localizations (je).
For this directory tree, AutoInstall sets the variable
JE_TOP to $APPL_TOP/je/11.5.0
Slide No. 36
Directory Structure
Log and Output Files
When the concurrent managers run Oracle Applications reports,
they write the output files, as well as diagnostic log files and
temporary files, to directories that you define during the
installation process.
Slide No. 37
Directory Structure
Using Common Directory for all log and out files
You designate the common directory and the subdirectories when
you run AutoInstall or by re-creating the environment file using
adadmin.
Slide No. 38
fnd
FND_TOP
au
AU_TOP
ak
AK_TOP
Oracle Inventory
inv
INV_TOP
icx
ICX_TOP
wip
WIP_TOP
Slide No. 40
Slide No. 41
Slide No. 43
Slide No. 44
Product Groups
In Release 11, you can have only one product group in each
database.
The products installed in each database do not have access
to the data of products installed in another database .
The default schema names GL, PO, AP, and APPLSYS by
Auto installation.
Oracle user Ids
Each Oracle Applications product has a default ORACLE user ID
that uses the product abbreviation as both the schema name and
password. Example General Ledger GL/GL
Slide No. 45
Schema
APPS schema
Since a products data objects are created in their own schema
(such as the GL schema) and the user accesses all data objects
through the APPS schema
AutoInstall creates the necessary grants and synonyms between the
schemas.
The APPS schema is an ORACLE schema that has access to the
complete Oracle Applications data model. It is analogous to the
SYSTEM schema, which has access to the entire database.
Oracle Applications responsibilities connect to an APPS schema.
AutoInstall automatically sets the environment variable FNDNAM to
the name of the APPS schema.
There is one APPS schema for every product installation group.
Slide No. 46
Example
GL ( General Ledger )
GL tables GL indexes GL sequences
INV ( Inventory)
INV tables INV indexes INV sequences
AP ( Accounyts Payables)
AP tables AP indexes AP sequences
APPLSYS ( Application Object Library)
AOL tables AOL indexes AOL sequences
ALR ( Alerts)
ALR tables ALR indexes ALR sequences
Slide No. 48
APPS details
APPS schema will contain following:
GL packages GL views GL procedures GL functions GL triggers
INV packages INV views INV procedures INV functions INV triggers
AP packages AP views AP procedures AP functions AP triggers
AOL code objects ALR code objects AD code objects Various grants and
synonyms
Slide No. 49
APPS
APPLSYS
AOL tables
AOL indexes
AOL sequences
GL
GL tables
GL indexes
GL sequences
ALR tables
ALR indexes
ALR sequences
AD tables
AD indexes
AD sequences
-
Slide No. 50
INV
INV tables
INV indexes
INV sequences
AP
AP tables
AP indexes
AP sequences
APPS
AOL code objects
ALR code objects
AD code objects
GL packages
GL views
GL procedures
GL functions
GL triggers
INV packages
INV views
INV procedures
INV functions
INV triggers
AP packages
AP views
AP procedures
AP functions
AP triggers
Accessing Data
Data Access
Some views access packages or functions, but the value
returned by the package or function may depend on the
environment.
The environment is initialized automatically when accessing
Oracle Applications through the Sign-On screen or when
using concurrent processing with Oracle Reports or SQL
scripts.
When accessed from SQL*Plus directly, the site value of the
profile option is used, not the setting for a particular
applications user.
Slide No. 51