AutoConfig is a tool that simplifies and standardizes configuration management t asks in an Oracle Applications environment.

Context File <CONTEXT_NAME>=<SID>_<HOSTNAME> is an XML based repository of Applications Environment information. Application Context File - $APPL_TOP/admin/<SID>_<HOSTNAME>.xml is an X ML based repository for environment specific details used by AutoConfig to confi gure the application tier. Information from this file is used to generate Applications configuratio n files and update relevant database profiles. Information stored includes: Name and location of the database Port numbers for Forms and Web servers Product-specific port numbers Information about application tier services controlled by AutoCo nfig The values of the context variables that make up the context file are in part determined by the choices you make when you run Rapid Install. Database Context File-$RDBMS_ORACLE_HOME/appsutil/<SID>_<HOSTNAME>.xml i s an XML based environment repository which is used to generate configuration fi les used on the database tier when AutoConfig is next run. AutoConfig Scripts Key AutoConfig configuration scripts include: adautocfg.sh - Wrapper script that passes the name of the specif ic environment context file to adconfig.sh. adconfig.sh - Invoked by adautocfg.sh, this script is a wrapper for adconfig.pl. adconfig.pl - Invoked by adconfig.sh, this Perl script calls the Java API to carry out the actual configuration tasks. The relevant Java code is located in the <JAVA_TOP> directory. Application Tier :-<COMMON_TOP>/admin/scripts/<SID>_<HOSTNAME> Database Tier:- <RDBMS_ORACLE_HOME>/appsutil/scripts/< SID>_<HOSTNAME> AutoConfig Directories Several Autoconfig directories are created as follows Directory Name Directory Conten ts <COMMON_TOP>/admin/install/<CONTEXT_NAME> Install scripts <COMMON_TOP>/admin/scripts/<CONTEXT_NAME> Control scripts <COMMON_TOP>/admin/log/<CONTEXT_NAME> Log files Context Value Management is an AutoConfig component that is used to manage the values of variable s in the context file, and automate required updates to it. CVM supports updates to both the application tier and database tier context files. CVM actions include: Adding new variables to a context file. Updating values of variables in an existing context file. Applying new versions of context file templates. Executing scripts or configuration tools that must complete befo re the AutoConfig engine starts, for example when generating the tnsnames.ora fi le. File Location <APPL_TOP>/bin/adcvm.sh script <APPL_TOP>/admin/template/adcvmat.xml ed data for the application tier Stores CVM-relat Description Main CVM

<RDBMS_ORACLE_HOME>/appsutil/bin/adcvm.sh Main CVM script <RDBMS_ORACLE_HOME>appsutil/template/adcvmdb.xml Stores C VM-related data for the database tier AutoConfig Files Template Files AutoConfig template files are used as the starting point for creating si te-specific configuration files. AutoConfig evaluates the context variables in a template file, determine s the actual values required, and creates a configuration file with these values substituted.& this process is called INSTANTIATION. There is one template file for each configuration file. Template files are located in the various <PROD>_TOP/admin/template dire ctories on the application tier. <RDBMS_ORACLE_HOME>/appsutil/template directory on the database tier. Templates for APPL_TOPConfiguration files. These are either files requiring configuration-specific information in t he APPL_TOP, or files used to load configuration profiles into the Applications database. Templates for Management Scripts To run all the standard processes required by Applications, Rapid Instal l creates scripts to start and stop each of these required processes. These scri pts need configuration information in order to: Create the correct environments for each process. Start the processes with the correct parameters. Point the processes at the correct database instance (if applica ble). Driver Files AutoConfig driver files are used to list the corresponding template files and lo cations, and specify the commands to be executed. For example, the commands migh t update profile options. Driver files are located in each <PROD>_TOP/admin/driver directory on the applic ation tier, and in the <RDBMS_ORACLE_HOME>/appsutil/template directory on the da tabase tier. Configuration Files AutoConfig configuration files, such as httpd.conf, are created as a result of A utoConfig instantiating the corresponding template files. Configuration files contain values corresponding to the settings specified for a particular site. After AutoConfig has been run, numerous configuration files wi ll have been created in various directories Applications Context File + || || || V AUTOCONFIG ENGINE || || || V CONFIGURATION FILE The adautocfg.sh script updates configuration files and profile options in the following way: 1. Instantiates template files with instance-specific values der Driver File (1 Per Product) + Template File (n Per Product)

ived from the relevant context file. 2. Copies in any customizations. 3. Overwrites existing configuration files with newly instantiat ed ones. 4. Runs SQL scripts to update database profile options. Role of Template & Driver Files AutoConfig uses the various template files to determine the basic settin gs needed. There is one template file for each configuration file. The driver files list the names and locations of the files that need to have context variables replaced. They also define the phases into which instanti ation is divided, and specify the commands that are to be executed for specific products. When AutoConfig runs, it cycles through the various <PROD>_TOP/admin/dri ver directories looking for driver files such as adtmpl.drv, fndtmpl.drv, and ic xtmpl.drv. Phases of Operation (during Autoconfig run) As AutoConfig parses the driver files, it carries out a series of action s, grouped into several distinct phases: INSTE8 - Instantiates AutoConfig template files to the AutoConfig config uration files specified in the relevant template driver files. INSTE8_SETUP - Executes setup scripts that carry out activities not invo lving connection to the database. INSTE8_PRF - Executes setup scripts that update profile options. INSTE8_APPLY - Executes setup scripts that carry out activities involvin g updates to the database. BINCPY - Copies the file mentioned from the source file to the configura tion file, creating parent directories for the latter if necessary. AutoConfig w ill report an error if the source file cannot be found. BINCPY_IGERR - Copies the file mentioned from the source file to the con figuration file, creating parent directories for the latter if necessary. AutoCo nfig will not report an error if the source file cannot be found. AutoConfig carries out these actions in the following order: 1. All INSTE8 and BINCPY actions - Carries out all file instantiations called fo r during INSTE8, INSTE8_SETUP, INSTE8_PRF and INSTE8_APPLY, and all copying from source files to target configuration files. 2. INSTE8_SETUP actions - For the files that were instantiated in Step 1, AutoCo nfig runs all SETUP scripts. 3. INSTE8_PRF actions - For the files that were instantiated in Step 1, AutoConf ig runs all PRF scripts. 4. INSTE8_APPLY actions - For the files that were instantiated in Step 1, AutoCo nfig runs all APPLY scripts. Managing the Context OAM enables you to edit the Context file as required. Adminstration>Autoconfig>Edit Parameters You can run adchkcfg.sh to see the proposed changes in the applications. To undo the configuration changes run restore.sh utility.which enables you to ro ll back the changes made by an AutoConfig run Location <APPL_TOP>/admin/<CONTEXT_NAME>/out/MMDDhhmm on the application tier, an d <RDBMS_ORACLE_HOME>/appsutil/out/MMDDhhmm on the database tier. Examining the changes adchkcfg.sh <AD_TOP>/bin --Application Tier. <RDBMS_ORACLE_HOME>/appsutil/bin --Database Tier.

This utility generates a report that highlights differences between existing con figuration files and the new ones that AutoConfig will generate. The report is c alled cfgcheck.html.