Product_TOP . I have taken the example of FND_TOP
ADMIN directory explained
driver : AutoInstall driver files (.drv) tell AutoInstall what to do.
import : Import files (.dat and .dmp), DataMerge files (.ctl, .dat, and .exp), and Applications loader files (.slt, .plt, .vlt, .clt, .msg, .wft,.jlt) are used to install seed data.
odf : Object description files (.odf) are used to create the tables and other database objects like seq,index etc
sql : SQL scripts (.sql) and PL/SQL scripts (.sql, .pls and .plb) are used to create objects and install and upgrade data.
template: Autoconfig template for various Product configuration file are stored there
it contains Phase driver files that tell AutoInstall what to do during each step of the installation/upgrade process.The installation process is broken up into several phases. AutoInstall completes one phase for every product before moving on to the next phase.
Example filenames are
Explained using “ Module” as Example ( The files xxseq.drv, xxplb.drv, xxfile.drv and xxdep.drv can be found under $XX_TOP/admin/driver )
“xxpls.drv”, which creates package specification
“xxplb.drv” , which creates package bodies during the package bodies phase.
“xxfile.drv” ( driver file ) which lists all the files you need to run the application which is categorized by the type of file like
– form files
– report files
– concurrent programs
– message files
This is more relavant in R11i
• DataMerge files (.ctl, .dat, and .exp), and
• Applications loader files (.slt, .plt, .vlt, .clt, .msg, .wft,.jlt)
afmkinit.sh registersessionwithlog.sh txkWfClone.cmd
afTk2Motif_UTF8.txt robots.txt txkWfClone.sh
afwdbsvr.cmd runcol.sh txkWfClone.sh.Old
afwdbsvr.sh runpref.sh txkWfClone.sql
afwebprf_nt.sql runses.sh txkWfClone.sql.Orig
afwebprf_ux.sql runssodatan.cmd txkxmlctx.tmp
afwebprf.cmd security_nt_ias1022.conf unregistercollector.cmd
afwebprf.sh security_ux_ias1022.conf unregistercollector.sh
afwebprf.sql soap_ias1022.properties unregisterpreference.cmd
antisamy soapConfig.xml unregisterpreference.sh
The concurrent programs, other C language programs and shell scripts for each product are stored in its respective bin directory. Core Executable to Oracle Applications are the FND_TOP/bin and AD_TOP/bin directories.
FNDIMON: Internal Monitor (in FND_TOP/bin)
FNDLIBR: the concurrent manager (in FND_TOP/bin)
FNDSM: Service Manager start the concurrent manager (in FND_TOP/bin)
FNDCPASS: The utility to change password (in FND_TOP/bin)
FNDMDGEN: a message file generator (in FND_TOP/bin)
adadmin: the AD Administration utility (in AD_TOP/bin)
adpatch: the AutoPatch utility (in AD_TOP/bin)
GLPOS : General ledger Posting ($GL_TOP/bin)
If these files get deleted , we can always get it by adrelink utility
adrelink.sh force=y ranlib=y “FND FNDSM”
The include directory contains header (.h) files.
These files may be required by the files contained in the lib directory for the re-linking process.
Note :- Not All Products have an include directory.
The lib sub-directory contains files pertinent to the process of re-linking Applications programs:
object files : (.o files), one for each C program to re-link.
library file : (.a file) the compiled C code common to that product’s programs.
The adpatch gets the new version of these files and it used adlibin and adlibout utility to rebuild the .a file
-There are many SQL*Plus scripts used by Oracle Applications for concurrent processing.
-These scripts are stored as .sql files in this sub-directory.
-These scripts typically produce reports or perform concurrent processing.$PRODUCT_TOP/media
-The Applications Forms client applets display text and graphics in the form of .gif files.
-The media directory contains all product specific .gif files.
–To make the translation process easier, the messages that the forms and concurrent programs use are stored in message files, separate from the forms and programs
-The mesg directory holds those message files per product
-Applications forms display messages at the bottom of the screen and in pop-up boxes.
-Applications concurrent programs print messages in their log and output files.
.-Each product’s mesg directory contains one or more message files for the language-specific messages that the product uses:
-US.msb is the binary message file used at runtime.
-If you install a non-English language version of Oracle Applications, then you have an additional message file that contains the translated messages for that language.
-The file name is .msb
– We use adadmin to generate the messages files
$PRODUCT_TOP/log & $PRODUCT_TOP/out
There are two methods for storing log and output files:
1) in each product’s log and out directories, which is the default or. The default directory and the default file names can be changed by changing the APPLLOG and APPLOUT environment variables in the Application environment file.By default, $APPLLOG is set to ‘log’ and $APPLOUT is set to ‘out’.
2) a common log and output sub-directory. You can consolidate all product log and out files into one directory by defining the APPLCSF environment variable in the application environment
The log directory holds
1) concurrent log files from each concurrent request and
2) the concurrent manager log files.
3) Log File Name of a Concurrent Request will be :- l.req ( small “L” )
The out directory holds
1. The concurrent report output files.
2 The default locations for these two files are _TOP/log and _TOP/out