Environment Settings

Rapid Install creates several environment files that set up the Oracle database, the Oracle technology stack, the Oracle HTTP server, and the Oracle E-Business Suite environments.
The location of these environment files is shown in the following table:

Table 2-2 Locations of Applications Environment Files

Filename	Location	Path	Environment
<CONTEXT_NAME>.env or CONTEXT_NAME>.cmd	10.2.0.2 ORACLE_HOME	db/tech_st/10.2.0	Oracle Server Enterprise Edition
<CONTEXT_NAME>.env or <CONTEXT_NAME>.cmd	OracleAS 10.1.2 ORACLE_HOME	inst/apps/<context>/ora/10.1.2	Oracle tools technology stack
<CONTEXT_NAME>.env or <CONTEXT_NAME>.cmd	OracleAS 10.1.3 ORACLE_HOME	inst/apps/<context>/ora/10.1.3	Java technology stack
<CONTEXT_NAME>.env or <CONTEXT_NAME>.cmd	APPL_TOP	apps/apps_st/appl	Applications
APPS<CONTEXT_NAME>.env or APPS<CONTEXT_NAME>.cmd	APPL_TOP	apps/apps_st/appl	Consolidated setup file

On UNIX, Oracle E-Business Suite includes a consolidated environment file called APPS<CONTEXT_NAME>.env, which sets up both the Oracle E-Business Suite and Oracle technology stack environments. When you install Oracle E-Business Suite , Rapid Install creates this script in the APPL_TOP directory. Many of the parameters are specified during the install process.
On Windows, the equivalent consolidated environment file is called %APPL_TOP%\envshell<CONTEXT_NAME>.cmd. Running it creates a command window with the required environment settings for Oracle E-Business Suite. All subsequent operations on the APPL_TOP (for example, running adadmin or adpatch) must be carried out from this window.
The following table lists the key environment settings in APPS<CONTEXT_NAME>.env.

Table 2-3 Key Environment Settings

Parameter	Description
APPLFENV	The name of the environment file, <CONTEXT_NAME>.env. If you rename the environment file, this parameter setting must be updated.
PLATFORM	The operating system in use. The value (for example, LINUX) should match the value in the APPL_TOP/admin/adpltfrm.txt file.
APPL_TOP	The top-level directory for this Oracle E-Business Suite installation.
ADMIN_SCRIPTS_HOME	Directory under $INST_TOP that Identifies the location of scripts such as adautocfg.sh, adpreclone.sh, adstrtal.sh, and adstpall.sh.
FNDNAM	The name of the ORACLE schema to which the System Administration responsibility connects. The default is APPS.
GWYUID	The public ORACLE username and password that grants access to the Oracle E-Business Suite initial sign-on form. The default is APPLSYSPUB/PUB.
FND_TOP	The path to the Application Object Library directory. For example, apps/apps_st/appl/fnd/12.0.0.
AU_TOP	The path to the Applications Utilities directory. For example, apps/apps_st/appl/au/12.0.0.
<PROD>_TOP	The path to a product's top directory. There is one entry for each Oracle E-Business Suite product.
PATH	Sets the directory search path, for example for FND_TOP and AD_TOP.
APPLDCP	Specifies whether distributed concurrent processing is being used. Distributed concurrent processing distributes processing load across multiple concurrent processing nodes.
APPCPNAM	Indicates whether the format of the concurrent manager log and output files follow 8.3 file name conventions (maximum of 8 characters to the left of the dot and 3 to the right; for example, alogfile.log). If this parameter is set to "REQID" (required), the concurrent manager uses file names that meet 8.3 naming requirements.
APPLCSF	Identifies the top level directory for concurrent manager log and output files if they are consolidated into a single directory across all products. For example, /inst/apps/<context>/logs/appl/conc.
APPLLOG	The subdirectory for concurrent manager log files. The default is log.
APPLOUT	The subdirectory for concurrent manager output files. The default is out.
APPLTMP	Identifies the directory for Oracle E-Business Suite temporary files. The default is $INST_TOP/tmp on UNIX.
APPLPTMP	Identifies the directory for temporary PL/SQL output files. The possible directory options must be listed in the init.ora parameter utl_file_dir.
INST_TOP	Identifies the top-level directory for this instance. For example, inst/apps/<context>. Introduced with Release 12.
NLS_LANG	The language, territory, and character set installed in the database. The default for a fresh install is "AMERICAN_AMERICA.US7ASCII".
NLS_DATE_FORMAT	The National Language Support date format. The default is "DD-MON-RR", for example 14-JUL-08.
NLS_NUMERIC_CHARACTERS	The National Language Support numeric separators. The default is ".," (period and comma).

Most temporary files are written to the location specified by the APPLTMP environment setting, which is set by Rapid Install.
Oracle E-Business Suite products also create temporary PL/SQL output files used in concurrent processing. These files are written to a location on the database server node specified by the APPLPTMP environment setting. The APPLPTMP directory must be the same directory as specified by the utl_file_dir parameter in your database initialization file.
Rapid Install sets both APPLPTMP and the utl_file_dir parameter to the same default directory.
Some Oracle E-Business Suite utilities use your operating system's default temporary directory even if you define the environment settings listed in the previous paragraph. You should therefore ensure there is adequate free disk space in this directory, as well as in those denoted by APPLTMP and APPLPTMP. On a multi-node system, the directory defined by APPLPTMP does not need to exist on the application tier servers.
Note: The temporary files placed in the utl_file_dir directory can be secured against unauthorized access by ensuring that this directory has read and write access for the Oracle database account only.

Other Environment Files

Several other key environment files are used in an Oracle E-Business Suite system.
The adovars.env file
The adovars.env file, located in $APPL_TOP/admin, specifies the location of various files such as Java files, HTML files, and JRE (Java Runtime Environment) files. It is called from the main applications environment file, <CONTEXT_NAME>.env. The adovars.env file includes comments on the purpose and recommended setting of each variable. In a Release 12 environment, adovars.env is maintained by AutoConfig, and should not be edited manually.
The adovars.env file includes the following parameters:

Table 2-4 Parameters Specified in the adovars.env File

Parameter	Description
AF_JLIB	Indicates the directory to which all Java archive files are copied. For example, apps/apps_st/comn/java/lib. Introduced with Release 12.
JAVA_BASE	Indicates the top-level Java directory . For example, apps/apps_st/comn/java. Introduced with Release 12.
JAVA_TOP	Indicates the directory to which all Java class files are copied. For example, apps/apps_st/comn/java/classes. Definition has changed with Release 12.
OA_JAVA	Indicates the directory to which all Java archive files are copied. For example, apps/apps_st/comn/java/classes.
OA_JRE_TOP	Indicates the location where the JRE is installed. For example, /local/java/jdk1.5.0_08.
OAH_TOP	Defines the location to which HTML files are copied. For example, apps/apps_st/comn/webapps/oacore.
OAD_TOP	Defines the locations to which context-sensitive documentation files are copied. For example, apps/apps_st/comn.
LD_LIBRARY_PATH	Path used on many UNIX platforms to list the directories that are to be scanned for dynamic library files needed at runtime.
CLASSPATH	Lists the directories and zip files scanned for Java class files needed at runtime.

The adconfig.txt file
AD utility programs perform a variety of database and file management tasks. These utilities need to know certain configuration information to run successfully. This configuration information is specified when Oracle E-Business Suite is installed, and subsequently stored in the adconfig.txt file in the <APPL_TOP>/admin directory. Once it has been created, this file is used by other Oracle E-Business Suite utilities.
Note: adconfig.txt is created with the APPL_TOP file system, and it shows the tiers that have been configured on a particular node. It is distinct from the config.txt file employed by Rapid Install.
The fndenv.env file
This file sets additional environment variables used by the Application Object Library. For example, it sets APPLBIN as the name of the subdirectory where product executable programs and shell scripts are stored (bin). This file should not be modified: the default values are applicable for all customers. The file is located in the FND_TOP directory.
The devenv.env file
This file sets variables that let you link third-party software and your own custom-developed applications with Oracle E-Business Suite. In Release 12, this script is located in FND_TOP/usrxit, and is automatically called by fndenv.env. This allows you to compile and link custom Oracle Forms user exits and concurrent programs with Oracle E-Business Suite.