Applications File System

An Oracle Applications Release 11i system utilizes components from many Oracle
products. It stores these product files within several different top level directories:
 <db name>APPL or APPL_TOP: Contains the product directories and files for
Oracle Applications.
 <db name>COMM or COMMON_TOP: Contains directories and files used
across products.
 <db name>ORA or ORA_TOP: Contains ORACLE Home’s for the Application
technology stack components
The Oracle Application database related file systems are:
 <db name>DB: Contains the database ORACLE_HOME
 <db name>DATA: Contains the Oracle Applications database files.

Note: No Applications files are installed on desktop client machines, although JAR files
and their supporting utilities are downloaded as required.

Depending on how you chose to install Applications, these product directories may be
located on a single machine (the simplest case) or on multiple machines (the most
common type of deployment). Operating system environment settings indicate the
location of the various files in the file systems of the database and application server
machines. This chapter discusses the association between these environment settings and
the corresponding files and directories.

Note: <dbname> is the name of your system determined through Rapid Install at the time
of installation. For example, PROD.
 Figure 2-1 Top-Level Applications Directory Structure

 The <dbname>DATA or DATA_TOP directory is located on the database

server machine, and contains the system tablespaces, redo log files, data
tablespaces, index tablespaces, and database files.
 The <dbname>DB directory is located on the database server machine,
and contains the ORACLE_HOME for the Oracle9i database.
 The <dbname>APPL or APPL_TOP directory contains the product
directories and files for Oracle Applications.
 The <dbname>ORA directory contains the ORACLE_HOMEs for the
Applications technology stack components.
 The <dbname>COMN or COMN_TOP (or COMMON_TOP) directory
contains directories and files used across products.

The DATA Directory

The <dbname>DATA file system contains the data (.dbf) files of the Oracle database.
Rapid
Install installs the system, data, and index files in directories below several mount points
on the database server. You can specify the directory names of the mount points on the
database server during installation.
APPL_TOP

The Oracle Application top level directory path is defined in the environment variable
APPL_TOP.for both an installation and upgrade of Oracle Application ,Rapid Install
creates the new APPL_TOP,or Applications top level directory and defaults the
APPL_TOP directory value to <db name>APPL.

The APPS <context name> .env files calls <context name>.env in the APPL_TOP and
<context name>.env in the 8.0.6 Oracle Home. The <context name>.env file in the
APPL_TOP is very important file containing parameters definition the Oracle Application
environment. Directory Contains Product Directories and Files for Oracle Application. The
main Application Environment file called <CONTEXT_NAME>.env.The consolidate
environment file called APPS<CONTEXT_NAME>.env

The APPL_TOP directory contains:

• The core technology files and directories.

• The product files and directories (for all products).

• The main applications environment file, called <CONTEXT_NAME>.env on UNIX,

• The consolidated environment file, called APPS<CONTEXT_NAME>.env on UNIX,

Product Directories

Each product has its own subdirectory under <PROD>_TOP, where <PROD> is the
product schema name.. The subdirectories are named in accordance with the product’s
standard abbreviation, such as gl for Oracle General Ledger. Within each product directory
is a subdirectory that is named using the base Oracle Applications release number, such as
11.5.0. This directory contains the various subdirectories for the product files

The Oracle Applications product directories contain many subdirectories that group the
different files for a given product. A typical product directory has the subdirectories
shown, however, there may be differences based upon configuration.

Note: Some products do not have all of the subdirectories you see on this slide.
Admin Directory
The admin subdirectory contains files used by AutoUpgrade to upgrade products to the
current release.
The admin subdirectory has several subdirectories of its own:
driver: Contains the upgrade driver files (.drv). The upgrade process is divided into
phases. Phase driver files specify processing by phase.
Example files are:
• glseq.drv creates sequences for the General Ledger (GL) product during the
sequence phase.
• glfile.drv lists the GL files needed to run the product.
• gldep.drv specifies dependencies between GL and other products so that upgrade
jobs between products are processed in the correct order.
import: Contains the import files used to upgrade seed data.
odf: Contains the object description files used to create and maintain tables, indexes,
sequences, and views.
sql: Contains SQL scripts and PL/SQL scripts used to upgrade data and PL/SQL package
creation scripts.
Bin Directory
The concurrent programs, other C language programs and operating system shell scripts
for each product are stored in its respective bin directory. Of particular importance to
Oracle Applications are the FND_TOP/bin and AD_TOP/bin directories. Some of the
important programs in these directories include:
f60webmx: the Applications Forms processor (in FND_TOP/bin)
FNDLIBR: the concurrent manager (in FND_TOP/bin)
startmgr: a UNIX shell script to start the concurrent manager (in FND_TOP/bin)
fdfcmp: the flexfield compiler (in FND_TOP/bin)
FNDMDGEN: a message file generator (in FND_TOP/bin)
adadmin: the AD Administration utility (in AD_TOP/bin)
adaimgr: the AutoUpgrade utility (in AD_TOP/bin)
adpatch: the AutoPatch utility (in AD_TOP/bin)
Note: The FND_TOP/bin and AD_TOP/bin directories are included in the PATH
variable. This allows FND and AD executables to be accessed from any location.
Forms Directory
Oracle Forms files include portable source files (.fmb files) and generated runtime files
(.fmx files). Forms files are generated by converting the .fmb source file to .fmx runtime
files. The forms directory contains Oracle Forms runtime files. The source files are stored
in AU_TOP/forms so that runtime files can be generated more easily.
A subdirectory exists for the language(s) installed. This subdirectory is named according
to the language, for example, US for American English forms, D for German forms, F for
French forms.
Help Directory
The Help directory contains online help source files .these files are imported into the
database to optimize the performance of online help. Fresh installation of Oracle
Applications have help preinstalled. Upgrade customers must install the help files during
post-upgrade tasks.
Include Directory
The include Directory contains header (.h) files for customer development .most Product
don’t have this include directory.
Log and Out Directories
When the concurrent managers run Oracle Applications reports or data update programs,
they write output files as well as diagnostic log files and temporary files to directories
defined during the installation process. There are two methods for storing log and output
files:
• In each product’s log and out directories.
• In common log and output directories.
The log directory holds concurrent log files from each concurrent request. The concurrent
manager log files are stored in FND_TOP/log.
The out directory holds the concurrent report output files.
You can consolidate all product log and out files into one directory by defining the
APPLCSF environment variable in the <db name>.env environment file.
The APPLCSF parameter identifies common directories to hold all log and output files.
Note: The log and out directories should be monitored for disk space usage and purged
periodically.
Message directory
Oracle Application stores message files in the mesg directory .Message files are used to
display messages in form and reports.Messaage files are translated and are named
according to the language they represent. They are:
 US.msb is the American English message files
 JA.msb is the Japanese’s message files
Patch Directory
The Patch directory contains files AutoPatch uses to update the database.Patch files are
grouped in the following subdirectories:
Driver: contains driver files (.drv).these are used only used by older patches.
Sql: Contains sql (.sql) and PL/SQL (.pls) scripts
Odf: Contains Object description files (.odf)
Import: Contains files used to update seed data.
Note: the patch directory should not be used as a staging area to unzip patches.

APPL_TOP/admin Directory

APPL_TOP/admin Directory
The APPL_TOP/admin directory contains files and scripts used by the AD utilities during
the upgrade and maintenance processes. These include:
• A custom environment file defining certain file and directory locations (adovars.env).
• Text files read by AutoUpgrade.
• Scripts run during the upgrade.
• A preupg directory containing product-specific pre-upgrade scripts.
• Log and out directories for upgrade log and output files.
• A restart directory where AD programs create restart files.
Most AD utilities put their log, out and restart files in a separate <SID> subdirectory. The
value for <SID> comes from the TWO_TASK or ORACLE_SID parameter. The
upgrade, patch and administration utilities obtain this value and store their log, out and
restart files in the <SID> subdirectory.
Some programs, when run from the command line, cannot access the <SID>
value and therefore store their log, out, and restart files in the log, out and restart
directories directly under the APPL_TOP/admin directory.
The Application context file is located in the admin directory in your APPL_TOP.It is
called <context name>.xml

Admin Directory Text Files

There are many text files stored under the admin directory. These files are used by many
different utilities. Some of the files include:
• adconfig.txt: contains system configuration variable values.
• adlinkbk.txt: lists files the adrelink utility should backup rather than delete.
• applcust.txt: lists registered customizations.
• applora.txt: contains minimum or required settings for database initialization
parameters.
• applprod.txt: lists products available in this release.
• applterr.txt: contains territory descriptions for globalizations.
• appl<LANG>.txt (e.g., applUS.txt): contains language translations of product names.
COMMON_TOP
This is the base directory for the COMMON_TOP .It contains the other directory
for files that are used across product or in conjunction with the third-party
products

Common Components Directory - COMMON_TOP

The <system name>COMN directory contains directories and files that are used across
products or are used in conjunction with other third-party products.
This directory also contains the default consolidated log and output directories used by
concurrent processing. The directories are COMMON_TOP/admin/log and
COMMON_TOP/admin/out.
Unlike previous releases, Release 11i supports the placement of the Java directory
(JAVA_TOP) and the HTML directory (OAH_TOP) anywhere in your file system. The
default location for these directories is under COMMON_TOP.
Note: COMMON_TOP is not a defined environment variable.
Copying Java Files: Product Files
Oracle Applications Release 11i makes extensive use of Java. Many Oracle Applications
products use Java on the front end for forms and on the back end for data processing.
Java files are installed into Oracle Applications product directories and then copied to
directories under the common components directory to facilitate optimal processing.

Copying Java Files: apps.zip

apps.zip is a patchable archive of all Java class files required by Oracle Applications.
Individual Java class files are usually not present on the file system.
apps.zip is located in AU_TOP/java and a public copy is stored under JAVA_TOP.
The public copy is the one utilized in a Web server environment, as the Web server can
see the JAVA_TOP stored apps.zip but, for security reasons, does not access the
AU_TOP/java apps.zip directly.

The <dbname>COMN or COMMON_TOP directory contains files used by many

different Oracle Applications products, and which may also be used with third-party
products.

The admin directory under COMMON_TOP is the default location For concurrent
Manager Log and Output directories. When concurrent managers run oracle application
reports, they write log files and temporary files to the log sub directory of the admin
directory and output files to the subdirectory of admin directory.
The Install subdirectory of the admin directory contains scripts and log files used by
Rapid Install. The scripts subdirectory of admin contains scripts used to start and stop
services such as listeners and concurrent managers.
The html directory
The OA_HTML environment setting points to the html directory. The Oracle applications
HTML-based sign-on screen and Oracle HTML-based Applications HTML files are
installed here. The html directory also contains other files used by the HTML-based
products, such as JavaServer Page (JSP) files, Java scripts, XML files, and style sheets.
Rapid Install and the AD utilities copy the HTML-based product files from each
<PROD>_TOP directory to subdirectories in the html directory.
The java directory
The JAVA_TOP environment setting points to the java directory. Rapid Install installs all
Oracle Applications JAR files in the Oracle namespace of this JAVA_TOP directory. The
java directory also holds third-party Java files used by Oracle Applications, as well as
other zip files.
The portal directory
The portal directory contains the Rapid Install Portal files. The Rapid Install Portal is a
web page that provides access to post-install tasks that may be necessary for your
installation, plus server administration scripts, installation documentation, and online
help. Using a browser, you can view the Rapid Install Portal after you run Rapid Install.
The temp directory
The temp directory is used for caching by some products such as Oracle Reports.
The util directory
The util directory contains the third-party utilities licensed to ship with Oracle
Applications. These include, for example, the Java Runtime Environment (JRE), Java
Development Kit (JDK) and the Zip utility.
The scripts directory
The scripts directory contains application tier control scripts such as adstrtal.sh and
adstpall.sh, which are located in the <CONTEXT_NAME> subdirectory.
ORA_TOP

The Base directory for the RDBMS installation.

There are two Oracle Home‘s Application 8.0.6 and iAS directory. It is also Know as
Technology Stack.

Technology Stack Directory - ORA_TOP

To take advantage of the technology stack components’ latest features, there are multiple
ORACLE_HOME directories under the technology stack directory. This slide shows
which technology stack components are located in each directory:
• 8.0.6: Contains the ORACLE_HOME for the Developer 6i products(Forms, Reports
and Graphics).The Product libraries in the 8.0.6ORACLE_HOME are used to relink
Oracle Application executables..
• iAS (8.1.6): Contains the ORACLE_HOME for the Oracle HTTP server.

For Practice
1. Login to applmgr user
2. Run the Environment File
$ cd $ <Path to APPL_TOP>
$ .APPS<context name>.env
3. To list all the files in the directory (APPL_TOP).Use “ls” command.There is a
 <PROD>_TOP for each product available with Oracle Applications.
4. Review the directory structure for Product.Go to GL_Top directory to review the
directory structure for the GL.
$ cd $ GL_TOP
5. Navigate the COMMON_TOP
$ cd $ COMON_TOP