 |
| 11i file system |
Note: <dbname> is the name of your system determined through Rapid Install at the time of installation. For example, PROD.
• 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.
DB and ORA Directories
Oracle Applications supports employing an Applications database of one version, while linking Applications programs using the tools from a second or third version of the database. This multiple ORACLE_HOMEs configuration allows new features of the database to be supported, while maintaining compatibility with earlier releases.
Release 11i utilizes three ORACLE_HOMEs:
• The 9.2.0 ORACLE_HOME (Applications database home) is located in the <dbname>DB directory. It contains the files needed for running and maintaining the Oracle Applications database.
• The 8.0.6 directory contains the ORACLE_HOME for the Developer 6i products (Forms, Reports, and Graphics). The product libraries in the 8.0.6 ORACLE_HOME are used to relink Oracle Applications executables.
• The iAS directory, also under the <dbname>ORA, contains the ORACLE_HOME for Oracle9i Application Server.
The COMN Directory
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
The admin directory, under the COMMON_TOP directory, is the default location for the concurrent manager log and output directories. When the concurrent managers run Oracle Applications reports, they write the log files and temporary files to the log subdirectory of the admin directory, and the output files to the out subdirectory of the 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.
The APPL Directory
Oracle Applications files are stored in the <dbname>APPL directory, which is known as the APPL_TOP directory.
The APPL_TOP directory contains:
1. The core technology files and directories.
2. The product files and directories (for all products).
3. The main applications environment file, called .env on UNIX, and .cmd on Windows.
1. The core technology files and directories.
2. The product files and directories (for all products).
3. The main applications environment file, called .env on UNIX, and .cmd on Windows.
4. The consolidated environment file, called APPS.env on UNIX, and APPS.cmd on Windows.
Each product has its own subdirectory under APPL_TOP, and the Oracle Applications base release is typically reflected in the subdirectory name. For Release 11i, the base release is
11.5.0.
The directory path for a particular product is defined by the value of the environment variable PROD_TOP, where PROD is the product schema name. For example, If the directory path to APPL_TOP is /d01/prodappl, the paths to these product directories would be specified in the .env file as follows:
• APPL_TOP=/d01/prodappl
• AU_TOP= /d01/prodappl/au/11.5.0
• FND_TOP = /d01/prodappl/fnd/11.5.0
• INV_TOP= /d01/prodappl/inv/11.5.0
All Oracle Applications products, regardless of license status, are installed in the database and the file system. Files for unlicensed products should not be removed. Conversely, multiple releases and product versions must not be installed under a single APPL_TOP directory.
The same principle applies to all directories, apart for the admin directory.
• APPL_TOP=/d01/prodappl
• AU_TOP= /d01/prodappl/au/11.5.0
• FND_TOP = /d01/prodappl/fnd/11.5.0
• INV_TOP= /d01/prodappl/inv/11.5.0
All Oracle Applications products, regardless of license status, are installed in the database and the file system. Files for unlicensed products should not be removed. Conversely, multiple releases and product versions must not be installed under a single APPL_TOP directory.
The same principle applies to all directories, apart for the admin directory.
Product Directories
Each Oracle Applications product directory contains numerous subdirectories, which are used to group the various types of file used by the product. Not all products have all the sub-directories shown on the slide. There may also be differences depending on installation choices.
Additional Language Subdirectories
Translated forms files, reports files, and installation scripts are all stored in their own language specific directories. These directories are identified by a language directory code.
For example, all forms files located under the US directory are in American English, while all forms files located under the AR directory are in Arabic.
Message files are not stored in language-specific directories. Instead, message files are named according to the language of the messages they contain. For example, AR.msb is a file containing messages translated to Arabic.
For example, all forms files located under the US directory are in American English, while all forms files located under the AR directory are in Arabic.
Message files are not stored in language-specific directories. Instead, message files are named according to the language of the messages they contain. For example, AR.msb is a file containing messages translated to Arabic.
AU Directory
Applications Utilities (AU) are product files that are consolidated in a single location for optimal processing.
These files include:
• PL/SQL libraries used by Oracle Reports, in the PLSQL subdirectory.
• PL/SQL libraries used by Oracle Forms, in the resource subdirectory.
• Oracle Forms source files, in the forms subdirectory.
• A copy of all Java files used by JInitiator when regenerating the desktop client JAR files, in the java subdirectory.
• Certain reports needed by products such as Discoverer, in the reports subdirectory.
These files include:
• PL/SQL libraries used by Oracle Reports, in the PLSQL subdirectory.
• PL/SQL libraries used by Oracle Forms, in the resource subdirectory.
• Oracle Forms source files, in the forms subdirectory.
• A copy of all Java files used by JInitiator when regenerating the desktop client JAR files, in the java subdirectory.
• Certain reports needed by products such as Discoverer, in the reports subdirectory.
Common Components Directory - COMMON_TOP
The db_nameCOMN or COMMON_TOP directory contains files used by many different Oracle Applications products, and which may also be used with third-party products.
The COMMON_TOP/admin directory is the default location for the concurrent manager log and output directories. When the concurrent managers run Oracle Applications reports, they write the log files and temporary files to the log subdirectory of the admin directory (COMMON_TOP/admin/log) and the output files to the out subdirectory of the admin directory (COMMON_TOP/admin/out).
By default, the top-level directories for both Java (JAVA_TOP) and HTML (OAH_TOP) are both under COMMON_TOP.
The COMMON_TOP/admin directory is the default location for the concurrent manager log and output directories. When the concurrent managers run Oracle Applications reports, they write the log files and temporary files to the log subdirectory of the admin directory (COMMON_TOP/admin/log) and the output files to the out subdirectory of the admin directory (COMMON_TOP/admin/out).
By default, the top-level directories for both Java (JAVA_TOP) and HTML (OAH_TOP) are both under COMMON_TOP.
Applications Technology Stack Directory - (db_Name)ORA
Oracle Applications supports employing an Applications database of one version, while linking Applications programs using the tools from a second or third version of the database.
This multiple ORACLE_HOMEs configuration allows new features of the database to be supported, while maintaining compatibility with earlier releases.
Release 11i utilizes two ORACLE_HOMEs under the (db_Home)ORA directory:
This multiple ORACLE_HOMEs configuration allows new features of the database to be supported, while maintaining compatibility with earlier releases.
Release 11i utilizes two ORACLE_HOMEs under the (db_Home)
Database Technology Stack Directory - (DB_NAME)DB
The database server is located in its own directory structure, with its own ORACLE_HOME.The 9.2.0 ORACLE_HOME (Applications database home) is located in the DB directory. It contains the files needed to run and maintain the Oracle Applications database.
No comments:
Post a Comment