Application Architecture

1. Overview
2. Desktop Tier
3. Application Tier
4. DataBase Tier

The Desktop Tier

The client interface is provided through HTML for the newer HTML-based applications,
and via a Java applet in a Web browser for the traditional Forms-based interface.

Forms Client Applet:

The Forms client applet is a general-purpose presentation applet that supports all Oracle
Applications Forms-based products, including those with customizations and extensions.
The Forms client applet is packaged as a collection of Java Archive (JAR) files. The JAR
files contain all Java classes required to run Oracle Applications forms.
Oracle JInitiator:
The Forms client applet must run within a Java Virtual Machine (JVM) on the desktop
client. For Oracle Applications the JVM is supplied by Oracle JInitiator. The Oracle
JInitiator component allows use of the Oracle JVM on web clients, instead of the
browser’s own JVM.
JInitiator is implemented as a plug-in (Netscape) or ActiveX component (Microsoft
Internet Explorer).In the traditional, Forms-based Oracle Applications environment,
JInitiator was run as part of the standard Applications sign-on process. Now, with the
move to a mainly HTML-based environment, JInitiator is only invoked when a user
chooses to access functions that require it, such as running a form. If JInitiator has not
been installed, the Web browser prompts the user to download the required installation
executable.
The Forms client applet and commonly used JAR files are downloaded from the Web
server at the beginning of the client’s first session. Less commonly used JAR
files are downloaded as needed.
Application Tier:
The application tier has a dual role: hosting the various servers that process the business
logic, and managing communication between the desktop tier and the database tier. This
tier is sometimes referred to as the middle tier. Oracle9 i Application Server (9 iAS)
provides the technology used on the application tier. Six servers comprise the
application tier for Oracle Applications:
• Web server
• Forms server
• Concurrent Processing server
• Admin server
• Reports server
• Discoverer server (optional)
The Application tier provides the communication between Desktop Tier and DataBase
Tier.

Web Server
The Oracle HTTP server (powered by Apache) acts as the Web server. It
processes the requests received over the network from the desktop clients, and includes
additional components such as:
• Web Listener
• Java Servlet Engine
• Java Server Pages (JSP)
The Web listener component of the Oracle HTTP server accepts incoming HTTP
requests (for particular URLs) from desktop client (browsers).If possible; the Web server
services the requests itself, for example by returning HTML to construct a simple Web
page. If the page referenced by the URL needs advanced processing, the listener passes
the request on to the servlet engine, which contacts the database server as needed.
The HTML Applications are also Called Self-Service Applications. The Oracle
HTML Application:
  Do not use Oracle Forms for the interface.
 Are designed in pure HTML and JavaScripts
 Dynamically generates HTML pages by executing Java Code.

The Default Port is 8000, Name of the Server is httpd and Control File for this is
adapcctl.sh--- (Start, Stop, and Status).

Forms Server Architecture

The Forms server architecture is essentially three-tier architecture. The Form Client
applet is exists on desktop tire. The user uses the interface to type in a field, click button,
or pass information to the application tier
The Java client exists on the desktop. The user uses the interface to type in a field, click a
button, or pass information to the application tier.When a user initiates an action, the
middle tier user interface logic decides what to do based on this action. The action may
open a new window; runs a query, or any number of other actions. The database tier hosts
the database and contains data intensive logic. In this configuration with all logic on the
servers, all software updates can be performed in one data center and have it automatically
accessible to users in a LAN, WAN, and even through a dial-up connection.

The Default Port is 9000, Name of the Server is f60webmx or f60srvm and Control File
for this is adfrmctl.sh--- (Start, Stop, and Status).

Concurrent Processing Server:

As described previously, user interactions with Oracle Applications data can be

conducted via HTML-based Applications or the more traditional Forms-based
Applications. How ever, there are also reporting programs and data updating programs
that need to run either periodically, or on an ad hoc basis. These programs, which run in
the background while users continue to work on other tasks, may require a large number
of computations, and are run using the Concurrent Processing architecture.
Processes that run on the Concurrent Processing server are called Concurrent Program.
You submit a request to run concurrent program through Oracle Application Forms or
HTML-based request. The request inserts a row into a database table specifying the
program to be run. A concurrent manager then reads the applicable requests in the table,
and starts the concurrent program. Log and out files are generated on the Concurrent
Processing Server.

The Default Port is 7000, Name of the Server is FNDLIBR and Control File for this is
adcmctl.sh--- (Start, Stop, and Status).
Report Review Agent
Oracle Applications uses a tool called Report Review Agent to view Concurrent
Program Log and Output files online.Tese files are stored on the node containing
the Concurrent Processing server.
Using Report Review Agent, you can copy entire report or log file to your PC
Accessing Concurrent Processing Output
The Concurrent Processing Server Communicates with the data server using Net
Services. The resultant Concurrent Program log and output file from a request is
passed back as a report to the Report review Agent. The Report Review Agent
passes a file containing the entire report to the form server. The form server
passes the report back to the user’s browser one page at a time .You can use
profile options to control the size of the files and pages passed through the
system.

Report Server
The reports server resides on the application tier with the concurrent processing server.
The reports server is used primarily to produce reports for Business Intelligence System
products (BIS).There are other Oracle Applications products that utilize the reports server
as well, such as Inventory and Purchasing.
The Reports server is automatically installed on the same node as the Concurrent
Processing server and its reports are contained in the same directory with the regular
concurrent processing reports. However, reports generated by the Reports server are
monitored and administered separately from concurrent processing reports.

The Default Port is 7000, Name of the Server is rwmts60 and Control File for this is
adrepctl.sh--- (Start, Stop, and Status).

Admin Server
The Admin server is located on the node where you maintain the data model and data in
your Oracle Applications database. You perform the following operations from this
server:
• Upgrading Oracle Applications
This process is conducted only when you are upgrading to a new release. You use
the Auto Upgrade utility (adaimgr) to upgrade Oracle Applications and the
AutoPatch utility (adpatch) to upgrade Oracle Application
• Applying database patches to Oracle Applications
Most patches consist of files and scripts that update the file system and/or
database objects. You use the AutoPatch utility (adpatch) to perform these
updates. AutoPatch may also be used to apply cumulative patches such as mini-
packs (11i.GL.C) and maintenance packs (11.5.4).
• Maintaining the Oracle Applications data
Some features such as Multiple Reporting Currencies require regular maintenance
to ensure updates are propagated to the additional tables and schemas used by this
feature. The AD Administration utility (adadmin) allows you to do this as well as
other file system and database maintenance tasks.
Discoverer Server
This Discoverer Server Compliments the reports server as a tool to perform ad hoc
queries and analysis of the resultant query output .It also allows users to perform
projections as various business and strategic factors are changed.
End User Layer
The End user Layer is the Key to providing ease of use0020.The End User Layer is a
layer of metadata that sits in the Oracle Applications database but on top of the Oracle
Application data. Oracle Discoverer hides the complexity of the database and converts it
to an easy to understand interface for users. It maps the unfamiliar terms in the database
such as tables and columns to familiar terms that a user may understand .Therefore, an
analyst or manager with no database syntax familiarity can easily access key information
through easy to understand, familiar terms such as customer, name and revenue.
The End User Layer is one of the key components of the Discoverer process. It is in the
database but is separate from the Oracle Application data.
Database Tier
The Database tier contains the database server and holds all the data stored and
maintained by the Oracle Application System .It contains some processing code that is
stored in the database to optimize performance .In Release11i the database also includes
the Oracle Applications help information.
More specifically, the database tier contains Oracle database server files and an Oracle
Application database, which physically stores the tables, indexes, and other database
objects for your system
By definition the database server does not communicate directly with the desktop clients,
but rather with the server on the application tier, which immediate these communications.

ORACLE HOMES
Oracle Applications utilizes three Oracle homes:
Oracle 8 ORACLE_HOME:
 Contains Oracle Developer tools built with Oracle8 database libraries.
 Is Shared by the Oracle Developer Products.
Oracle iAS ORACLE_HOME:
 Is used by iAS, which includes the Oracle HTTP server powered by
Apache.
Oracle RDBMS ORACLE_HOME:
 Is used by the Oracle database server for Optimal scalability and
functionality.
The Oracle Applications Technology Layer:

The Oracle Applications technology layer lies between the Oracle Application
technology stack and the Oracle Applications product-specific modules. It provides
features common to all Oracle Applications products.
Products in the Oracle Applications technology layer include:
• Oracle Applications DBA (AD)
• Oracle Applications Object Library (FND/AOL)
• Oracle Applications Utilities (AU)
• Oracle Common Modules (AK)
• Oracle Workflow (WF)
• Oracle Alert (ALR)
• Oracle Applications Framework (FWK)
• Oracle XML Publisher (XDO)

Oracle Applications DBA (AD):

The Applications DBA product provides a set of tools that helps in the administration of
the Oracle Applications file system and database. AD tools are used for installing,
upgrading, maintaining, and patching the Oracle Applications system.
The AD utilities include:
• AD Administration - Performs general maintenance tasks for Oracle Applications.
• AD Merge Patch - Merges multiple patches into a single, integrated patch.
• AutoConfig - Manages configuration changes in an Oracle Applications system.
• AutoPatch - Applies patches and adds new languages and products to an Oracle
Applications system.
• AutoUpgrade - Upgrades a system to the latest version of Oracle Applications.
• Rapid Clone - Used to copy (clone) an Oracle Applications system.
• Rapid Install - Sets up a fully configured Oracle Applications system, including the
latest certified technology stack and all patches, mini-packs, and other updates.

Oracle Applications Utilities (AU)

The Applications Utilities (AU) component is used to maintain the Oracle Applications
system.AU hosts a collection of files copied from other products. This allows generating
on-site classes of files such as Forms and reports, or running reports invoked by the
Reports server from a standard, shared location. Generating forms or reports may require
access to shared PL/SQL libraries, so these files are copied to AU_TOP as well. The
Oracle Applications Java a files are stored in AU_TOP, as w ell as in JA V A_TOP and
<PROD>_TOP.

Oracle Application Object Library (FND/AOL)

The Oracle Application Object Library is a large component of the Applications

technology layer. It consists of a collection of reusable code, programs, and database
objects that provides common functionality across all products.
AOL provides many features to make system administration easier, such as security setup
and maintenance, and management of concurrent Processing.
Using Application Object Library ensures that the processing of flexfields or the
procedure for report submission, for instance, does not vary from one product to another.
Oracle Application Object Library also provides capabilities for developers to extend the
operation of Oracle Applications by allowing the creation of custom programs that
interact with the base modules.
AOL Features and System Administrators:
The AOL provides many features to make administration of Oracle Application easier.
The Oracle Applications System Administration can:
 Set up new users- register new oracle Applications users and give them access to
only those forms, functions and reports they need to do their jobs.

 Manage and Control Security- Decide which user have access to each
product ,and within a product ,which forms ,functions ,and reports a user can
access.

 Set users and System Profiles- A profile is asset of changeable options that affects
the way Oracle Applications look and behaves .A System Administrator can set
profile values at the site, application, responsibility, and user levels.
 Manage Concurrent Processing-Concurrent Processing is an Oracle Applications
facility that lets long-running ,data-intensive tasks run simultaneously with online
operations ,taking full advantage of multi-tasking and parallel processing. system
administrator can monitor and control concurrent processing using a few simple
interfaces, including forms and Oracle Application manager(OAM)

Oracle Common Modules (AK)

The Common Modules is an active data dictionary that enables you to define Oracle
Applications components for the HTML Applications and generate many of the oracle
Applications characteristics at runtime.
AK is heavily used to develop inquiry applications for the HTML Applications without
programming .AK allows storing languages translated labels for all attributes ,or reusable
components ,such as the customer name attribute ,which can be reused anytime a
customer name fields is displayed on an HTML pages.
Oracle Workflow (WF)
Oracle Workflow allows for communication of data between products and accomplishes
these important business requirements.
 Route Information
 Define Rules
 Deliver Electronic notifications
For Example, Self-Service Web Expenses utility Workflow in its approval process and
this process can be tailored for each site. By use of Workflow, electronic notification can
be delivered via email to any oracle Applications or internet user.

Oracle Alert
Oracle Alert allows you to electronically mail system notifications to users when an
exception or event has occurred .Some products are delivered with predefined alerts,
which allow you to notify users about specified database exceptions as they occur and
perform routine tasks automatically according to a schedule you define.