TGS TGS

Module Overview

Oracle Applications File System

This module consists of the following topics:
• Oracle Applications file system
• APPL_TOP directory
Chapter 8 • Globalizations
• Distributing files
• Structure of product directories
• Contents of product directories
• Important APPL_TOP subdirectories

TGS TGS

Module Overview

This module consists of the following topics:

• Common components directory (COMMON_TOP)

• COMMON_TOP and Java files

• Applications technology stack directories (<db name>ORA)

• Oracle Applications database files directory (<db name>DATA)

• The Oracle database server Oracle home (<db name>DB)

1
TGS TGS

Note: For Release 11i, all Oracle Applications products, regardless of license
status, are installed in the database and the file system. Do not remove files for
unlicensed products.

TGS TGS

2
TGS TGS

Note: Some products do not have all of the subdirectories you see on this slide.

TGS TGS

3
TGS TGS
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.

TGS TGS
Bin Directory
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 you to run FND and AD executables from any
location.

4
TGS TGS

Forms Directory

Oracle Forms files include portable source files (.fmb files) or generated
runtime files (.fmx files). Forms files are generated by converting the .fmb
source file to .fmx runtime files. The forms directory for most products
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.
The help directory contains online help source files. These files are imported
into the database to optimize the performance of online help.

Fresh installations of Oracle Applications have help preinstalled.

Upgrade customers must install the help files during post-upgrade tasks.

Under the help directory, there is a language directory to store the help files
for each language.

TGS TGS

The html subdirectory contains HTML, Javascript, and Java Server Page files
The include directory contains header (.h) files for custom development.
used by a product.

The Javascript (.js) and Java Server Page (.jsp) files are kept in the main
Note: Most products do not have an include directory.
html directory.

HTML and related files are stored in language-specific directories under the
html directory.

5
 TGS TGS

This directory is used to store Java files. During the installation or the upgrade, the files are
copied to the directories identified in the JAVA_TOP environment variable to optimize
processing.

The JAVA_TOP directory is defined in the environment file created during the installation
process. For each product that uses Java, there are one or more Java Archive (JAR) files under
the jar directory. There is also a product specific Java dependency (.dep) file under the make
directory that lists the components of the JAR files.

TGS TGS
Lib Directory

The lib subdirectory contains files used to the relink Oracle Applications
programs:
• object files (.o files in UNIX and .obj files in Windows): There is one
for each C
program to relink.
• library file (.a file in UNIX and .lib file in Windows): Is the compiled C
code common to that product’s programs.
• makefile (.mk file): Specifies how to create each C executable program
in the product’s bin directory.
For example, the GL_TOP/lib directory contains:
• glpmai.o (object module for the GLPPOS program)
• glcmai.o (object module for the GLCCON program)
• other .o files
• libgl.a (the GL library file)
• gl.mk (the makefile for all GL programs)

Note: Oracle Applications programs are relinked using the AD Administration

utility. AD programs are relinked using AD Relink. Do not relink Oracle
Applications programs manually.

6
TGS TGS
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 (shown in this slide).

• In common log and out directories.

During the installation, Rapid Install sets the log and out directories to a
common location and assigns this location to the APPLCSF parameter in the
<context name>.env environment file.

The default location for log and out files are COMMON_TOP/admin/log and
COMMON_TOP/admin/out.The log directory holds concurrent log files from
each concurrent request and the out directory holds the concurrent report
output files. Oracle Applications displays text and graphics in the form of .gif files. The
media directory contains all product specific .gif files.
Note: The log and out directories should be monitored for disk space usage
and purged periodically.

TGS TGS

Oracle Applications stores message files in the mesg directory. Message files The patch directory contains files AutoPatch uses to update the database.
are used to display messages in forms and reports. Message files are
translated and are named according to the language they represent. For Patch files are grouped in the following subdirectories:
example: • driver: contains driver files (.drv). These are only used by older patches.
• sql: contains sql (.sql) and PL/SQL (.pls) scripts.
• US.msb is the American English message file. • odf: contains object description files (.odf).
• JA.msb is the Japanese message file. • import: contains files used to update seed data.

You should have a message file for each language installed in your Oracle Note: The patch directory should not be used as a staging area to unzip patches.
Applicationssystem.

7
TGS TGS

These directories contain PL/SQL libraries used by Oracle Applications reports

and forms. All PL/SQL libraries are stored in AU_TOP.

• The files in the plsql subdirectory (.pll files) are used by Oracle Reports.

• The files in the resource subdirectory (.pll and .plx files) are used by Oracle The sql directory contains SQL scripts used by Oracle Applications products
Forms.

TGS TGS
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:

• The Applications Context file (<context name>.xml)

• An environment file defining certain file and directory locations
• Text files.
• SQL scripts.
• A preupg directory containing product-specific pre-upgrade scripts.
• Log, out and restart directories used by AD utilities.
• 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.

Some programs cannot access the <SID> value and therefore use the log, out
and restart directories directly under the APPL_TOP/admin directory.

8
TGS TGS

Applications Context File

The Application Context file:

• Is an XML file
• Is located in APPL_TOP/admin
• Contains information specific to that APPL_TOP
• Is used to configure your system
• Is Node-specific
• Ties multiple environments and configurations to make one
Applications instance description

TGS TGS

• adconfig.txt: contains system configuration variable values.

• adlinkbk.txt: lists files the AD Relink utility should back up 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.

AD stands for Applications DBA. Applications DBA is a set of tools used for
• appl<LANG>.txt (e.g., applUS.txt): contains language translations of installing, upgrading, and administering the Oracle Applications system. The AD
product names. directory contains utilities such as AutoUpgrade (adaimgr), AutoPatch (adpatch),
and AD Administration (adadmin).

9
TGS TGS

AU stands for Application Utilities. The <db name>COMN directory contains directories and files that are used across products or
are used in conjunction with other third-party products.
The AU_TOP directory contains other product files that are consolidated in a single
location for optimal processing. These files include: This directory also contains the default consolidated log and output directories used by
concurrent processing. The directories are COMMON_TOP/admin/log and
• PL/SQL libraries used by Oracle Reports, in the plsql subdirectory. COMMON_TOP/admin/out.
• PL/SQL libraries used by Oracle Forms, in the resource subdirectory.
• Oracle Forms source files, in the forms subdirectory. The default location for the Java directory (JAVA_TOP) and the HTML directory
• Certain reports needed by Discoverer or BIS, in the reports subdirectory. (OAH_TOP) is under COMMON_TOP.

TGS TGS

10
TGS TGS

11