AutoConfig - Simplifies configuration management in an Oracle E-Business Suite Release
.xml, located in $APPL_TOP/admin acts as a central repository for the instance-specific information that AutoConfig needs to configure an environment, including the name and location of the database, and port numbers for the application tier servers.

Autoconfig Centralizes and simplifies E-Business Suite configuration management.
AutoConfig can be used to instantiate files or scripts, and then execute them for installation and configuration.
Instantiation of a configuration file to be used at runtime
Instantiation of an SQL script that will set profile option values that can be either site or instance-specific
Instantiation of a shell script or Windows command file that will run an SQL script via SQL*Plus, and then execute the shell script
Instantiation of scripts to startup and shutdown services


Autoconfig Template and Driver Files 

AutoConfig uses template files to determine the basic settings that are needed. There is one template file for each configuration file.The template files are located in the relevant $PROD_TOP/admin/template directories. For example $AD_TOP/admin/template.

When AutoConfig runs, it cycles through the various /admin/driver directories looking for AutoConfig template driver files.

To Make a Modifiaction in the Context File :

- Running the Context Editor to make changes to the contents of the Applications context file, as described on the following pages
- Using Oracle Applications Manager 2.1.1 or higher, which includes a sophisticated, web-based context editor that can be used to edit the Applications (not database) context
- Can change the value in the Context file manually.

Running Autoconfig

Before Running Autoconfig on Production

1. Advisable to Take a backup of the listener.ora and tnsnames.ora
2. Run adchkcfg.sh and take a backup of files going to be affected by Autoconfig.
Running adchkcfg.sh (cont.)
This script generates a report that lists the differences that would arise on account of runing autoconfig. these differences should first be reviewed.

Usage
adchkcfg.sh contextfile={contextfilepath}

3. Running Autconfig requires downtime.

When Running autoconfig, Get the Applications Services Down , Database Services should be up and Running.
On 11i : $COMMON_TOP/admin/scripts/$CONTEXT_NAME/adstpall.sh
On R12 : $ADMIN_SCRIPTS_HOME/adstpall.sh or $INST_TOP/admin/scripts/adstpall.sh

To Run Autoconfig on the Applications Tier ,
On 11i , Use : $COMMON_TOP/admin/scripts/$CONTEXT_NAME/adautocfg.sh
On R12 , Use : $ADMIN_SCRIPTS_HOME/adautocfg.sh or $INST_TOP/admin/scripts/adautocfg.sh

and check the log file for Success / Errors.

To Run Autoconfig on the Database Tier ,
Use : $ORACLE_HOME/appsutil/scripts/$CONTEXT_NAME/adautocfg.sh
or Use : $ORACLE_HOME/appsutil/bin/adconfig.sh contextfile= appspass=


Reviewing Logs

AutoConfig log files are stored under:
$APPL_TOP/admin//log/MMDDhhmm/

Using Rollback Scripts

Each run of AutoConfig automatically creates a rollback script in case there is a need to revert to the previous configuration settings. This script and backups of all configuration files from each execution
of AutoConfig are stored in: $APPL_TOP/admin//out/