In Oracle : Oracle Applications 11i Context/ Environment Files

Oracle Applications EBS 11i, R12      Oracle Database      Data Warehouse & BI      Oracle Middleware      PL/SQL      Linux ...

Oracle Applications EBS

Oracle Apps 11i DBA (I) Oracle Apps 11i DBA (II) Oracle Apps 11i DBA (III) Oracle Apps 11i Sys Admin UPGRADE 11i Apps to R12 Oracle Apps R12 DBA

The last articles in the site (HOT)

The most visited articles in the site

In-Oracle.com  -> Oracle Applications (apps)  -> 11i 

-> Oracle Applications 11i Context/ Environment Files

 

Oracle Applications 11i Context/ Environment Files  

The topic of this article contains:

 

    Oracle Applications Context Files

    

    During the Oracle Applications eBusiness Suite installation Rapid Install save the configuration parameters in 2 files (context files) named  <CONTEXT_NAME>.xml.  The <CONTEXT_NAME> by default is <SID>_<hostname>. For instance if $ORACLE_SID is VIS and $HOSTNAME is apps_svr.localdomain the context file will be VIS_apps_svr.xml. These context files are not used directly to configure the Oracle Applications; the context files are only repositories which store the the configuration parameters. 

 

    The 2 context files are: 

       <RDBMS ORACLE_HOME>/appsutil/VIS_apps_svr.xml  (for the database tier) 

and 

       <APPL_TOP>/admin/VIS_apps_svr. xml  (for each node of the the application tier)

 

    The context files could be modified in 3 situations:

  1. Apply a patch from Oracle that adds or changes the variables in VIS_apps_svr.xml, AutoConfig template files or AutoConfig driver files;

  2. Using Context Editor (editcontext ) ( which is provided by the patch number 2873456);

  3. Using Oracle Applications Manager (OAM) H or higher. OAM automatically stores the new values in the database and update the context files. 

    Oracle recommends using OAM; however if the OAM is not accessible the Context Editor must be used.  

    

    The Context Editor is located at:

  • Application tier: <COMMON_TOP>/util/editcontext/

  • Database tier:    <RDBMS ORACLE_HOME>/appsutil/editcontext/

    The Context Editor executable file is editcontext (for UNIX) and EditContext.cmd (for Windows). The Context Editor contains 3 screens: 1st locate the context file and load it in the editor, the 2nd screen allows to edit the values in the context file and the 3rd screen allows you to save the changes to the context file. 

 

    If the Context File is lost, the Context File can be generated by using the adbldxml.pl (for 11.5.9 or higher).

 

    On UNIX, to create the Context File for the database:

    

    cd <RDBMS ORACLE_HOME>

    . <CONTEXT_NAME>.env       

    cd <RDBMS ORACLE_HOME>/appsutil/bin     

    perl adbldxml.pl tier=db appsuser=<APPSuser> appspasswd=<APPSpasswd>

 

   Note: If <CONTEXT_NAME>.env file is not present $ORACLE_HOME, $ORACLE_SID, $TNS_ADMIN must be set for the database.

 

    On UNIX, to create the Context File for the application tier (for 11.5.8 or higher):

    

     . <APPL_TOP>/<CONTEXT_NAME>.env       

     cd <AD_TOP>/bin

     perl adbldxml.pl tier=apps appsuser=<APPSuser> appspasswd=<APPSpasswd>

 

     When the Context File is created using adbldxml.pl Oracle will use the current environment settings. For this reason is very important to ensure that the system is correctly sourced. If the application environment file (<CONTEXT_NAME>.env files) is lost is possible to generate it from the database (run adadmin and chose option 2.Maintain Applications Files menu and after that 2.Create Applications environment file ). If the Context File is created for a RAC environment,  all the RAC instances must be running. 

    Some Benefits of the Context Files:

  • APPL_TOP/ database environment settings are situated in only 2 places and is easy to manage;

  • The cloning process is easier;

  • XML format is easy to read and platform independent;

  • Fewer files to maintain and support. 

 

   Oracle Applications Environment Files

 

    If the context file is the repository of these parameters and cannot be used to source the environment directly, the Oracle Applications Environment Files are the files which are used to configure (source) the system directly. The environment files mustn't be modified directly because these files are generated automatically by AutoConfig. 

 

    Here are the environment files in Oracle Application 11i :

 

Filename Location of the file Environment sourced Call other environment files
<CONTEXT_NAME>.env (Unix/ Linux)

<CONTEXT_NAME>.cmd (Windows)

9.2.0/ 10.2.0.3

ORACLE_HOME

Database Tier No
<CONTEXT_NAME>.env (Unix/ Linux)

<CONTEXT_NAME>.cmd (Windows)

iAS ORACLE_HOME HTTP Server  No
<CONTEXT_NAME>.env (Unix/ Linux)

<CONTEXT_NAME>.cmd (Windows)

8.0.6 ORACLE_HOME Technology stack No
<CONTEXT_NAME>.env (Unix/ Linux)

<CONTEXT_NAME>.cmd (Windows)

APPL_TOP Applications Yes

APPS<CONTEXT_NAME>.env 

(Unix/ Linux)

<CONTEXT_NAME>.cmd (Windows)

APPL_TOP

Technology stack

+

Applications

Yes

        

 

APPS<CONTEXT_NAME>.env  is named consolidated setup file because is used to source both Technology stack and Applications. APPS<CONTEXT_NAME>.env call the file which contains the customizations (if exists) and also <CONTEXT_NAME>.env for Technology stack and Applications.

 

Here is the content of a consolidated setup file (named APPSVIS_apps_svr.env):

 

$ more APPSVIS_apps_svr.env
(...)

# Source the custom file if it exists
customfile=/APPS/visappl/customVIS_apps_svr.env
if [ -f $customfile ]; then
. /APPS/visappl/customVIS_apps_svr.env
fi
. /APPS/visora/8.0.6/VIS_apps_svr.env
. /APPS/visappl/VIS_apps_svr.env

 

 

Key Parameters in Environment Files

 

 

Key Parameter Description Example
APPLFENV Applications File Environment name. If the environment file is renamed this parameter must be changed.   $ echo $APPLFENV
VIS_apps_svr.env
PLATFORM   The OS on which the Oracle Applications are installed. This value must match the value in adpltfrm.txt file:

    $ more $APPL_TOP/admin/adpltfrm.txt
    LINUX

$ echo $PLATFORM
LINUX
APPL_TOP The top-level directory for the Oracle Applications directory. $ echo $APPL_TOP
/APPS/visappl
FNDNAM   The Oracle schema used by System Administration Responsibility to connect to the database. The default value is APPS and should not be changed.  $ echo $FNDNAM
APPS
FND_TOP The directory where the Oracle Applications Object Library is installed. $ echo $FND_TOP
/APPS/visappl/fnd/11.5.0
AU_TOP The directory where the Oracle Applications Utilities are installed. $ echo $AU_TOP
/APPS/visappl/au/11.5.0
<PROD>_TOP The directory where each Oracle Applications Product is installed. $ echo $GL_TOP
/APPS/visappl/gl/11.5.0
PATH   The directories where the executables or the libraries are installed. 

$ echo $PATH

/APPS/visappl/fnd/11.5.0/bin:

/APPS/visappl/ad/11.5.0/bin:

/APPS/viscomn/util/java/1.4/j2sdk1.4.2_04/bin:

/APPS/viscomn/util/unzip/unzip/unzip-5.50:

/home/oracle/bin:

/APPS/visora/8.0.6/bin:/usr/bin:/usr/ccs/bin:

/usr/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:

/usr/bin:/usr/X11R6/bin

APPLTMP  The directory for the Oracle Applications temporary files. $ echo $APPLTMP
/APPS/viscomn/temp
APPLPTMP The directory for the Oracle Applications temporary PL/SQL output files. The options must be listed in utl_file_dir parameter. The default value must/ could be changed because the files  from this directory are  deleted when the server is restarted. $ echo $APPLPTMP
/usr/tmp
APPLCSF  Top-level directory for the concurrent manager log & output files if they are consolidated into one directory for all products. $ echo $APPLCSF
/APPS/viscomn/admin
APPLOG  The subdirectory for concurrent manager log files. In this case the log files for the concurrent manager are in $APPLCSF/log/VIS_apps_svr directory. $ echo $APPLLOG
log/VIS_apps_svr
APPLOUT The subdirectory for concurrent manager output files. In this case the log files for the concurrent manager are in $APPLCSF/out/VIS_apps_svr directory. $ echo $APPLOUT
out/VIS_apps_svr
NLS_LANG The national language, territory and character set installed in the database. In this case, the language is "American", the territory is "America" and the character set is "UTF8". $ echo $NLS_LANG
American_America.UTF8
NLS_DATE_FORMAT The format of the National Language. $ echo $NLS_DATE_FORMAT
DD-MON-RR
NLS_NUMERIC_CHARACTERS The National Language Support numeric separators.  $ echo $NLS_NUMERIC_CHARACTERS
.,
FORMS60_MAPPING The Oracle Applications forms Web server host name and port. $ echo $FORMS60_MAPPING
http://apps_svr.localdomain:8000/OA_TEMP
REPORTS60_TMP The directory for temporary Oracle Reports files. $ echo $REPORTS60_TMP
/APPS/viscomn/temp
GRAPHICS60_PATH The directory where the Oracle Graphics Files are located.  $ echo $GRAPHICS60_PATH
/APPS/visappl/au/11.5.0/graphs

 


The <CONTEXT_NAME>.env (located in $APPL_TOP) call other environment configuration files as well. These environment files are:

  1. $APPL_TOP/admin/adovars.env

  2. $APPL_TOP/fnd/11.5.0/fndenv.env ($APPL_TOP/fnd/11.5.0 is $FND_TOP). This script call devenv.env ( located under  ${FND_TOP}/${APPLUSR}, ${APPLUSR}= usrxit ) which sets variables that let us link custom Oracle Forms, Reports and concurrent programs.

 

Here are some of the variables defined in adovars.env:

 

Key Parameter Description Example
JAVA_TOP Indicates the top-level directory where all Java class files will be copied.  $ echo $JAVA_TOP
/APPS/viscomn/java
OA_JRE_TOP Indicates the location where you have installed the Java Runtime Environment (JRE) on your machine. You do not have to set this variable, however Oracle recommend you using this to update CLASSPATH, LD_LIBRARY_PATH and PATH variables rather than hardcode the location of the JRE. $ echo $OA_JRE_TOP
/APPS/viscomn/util/java/1.4/j2sdk1.4.2_04
CLASSPATH Java requires CLASSPATH to be defined on most platforms. The CLASSPATH variable lists the directories and zip files to be scanned for Java class files needed at runtime.  n/a
LD_LIBRARY_PATH LD_LIBRARY_PATH is used on some platforms to list the directories to be scanned for dynamic library files needed at runtime. This is usually set in your Oracle environment. This variable should include your Java libraries (from your JRE) and Oracle libraries.  n/a
OAH_TOP Define the locations to which Oracle Applications copies HTML  files. $ echo $OAH_TOP
/APPS/viscomn
OAD_TOP Define the locations to which Oracle Applications copies context-sensitive documentation files.  $ echo $OAD_TOP
/APPS/viscomn
OA_HTML, OA_SECURE, OA_MEDIA, OA_DOC, OA_JAVA The OA_HTML, OA_SECURE, OA_MEDIA, OA_DOC, and OA_JAVA variables correspond to the virtual directory settings of the same names you define in your web server. $ echo $OA_HTML
/APPS/viscomn/html

 

 

In-Oracle.com  -> Oracle Applications (apps)  -> 11i 

-> Oracle Applications 11i Context/ Environment Files

Oracle Applications EBS 11i, R12      Oracle Database      Data Warehouse & BI      Oracle Middleware      PL/SQL      Linux ...

 

     Copyright (c) 2011-2015  www.in-oracle.com  |  Disclaimer: The views expressed on this web site are my own and do not reflect the views of Oracle Corporation. You may use the information from this site only at your risk.