Understanding AutoConfig in EBS/Oracle Apps R12.2

 

AutoConfig plays a pivotal role in Oracle E-Business Suite (EBS). When executed, it generates various configuration files from template files. In certain scenarios, you may need to identify and customize these template files to override the default settings used by AutoConfig.

**Key Considerations for Customizing AutoConfig Templates**

1. Non-Customizable Templates: If a template file contains the “LOCK” keyword, it is not eligible for customization. AutoConfig will ignore any alterations made to these locked templates.
2. Dual System Customization: Remember to customize the Template File on both the Patch and Run File systems for consistent application.

**Locating and Customizing AutoConfig Template Files**

To determine which AutoConfig template file you need to customize, follow these steps:

_{– **On the Apps Tier:** Execute `/bin/adtmplreport.sh contextfile=target=`
– **On the DB Tier:** Use `/appsutil/bin/adtmplreport.sh contextfile= target=`}

For Example:

$AD_TOP/bin/adtmplreport.sh contextfile=/u01/TEST/fs1/inst/apps/TEST_oraapps/appl/admin/TEST_oraapps.xml target=/u01/TEST/fs1/FMW_Home/webtier/instances/EBS_web_TEST_OHS1/config/OHS/EBS_web_TEST/security2.conf

This command will generate a log file detailing the associated configuration and template files, such as:

– **Template File:** `/u01/TEST/fs1/EBSapps/appl/fnd/12.0.0/admin/template/security2_conf_FMW.tmp`
– **Target File:** `/u01/TEST/fs1/FMW_Home/webtier/instances/EBS_web_TEST_OHS1/config/OHS/EBS_web_TEST/security2.conf`

Creating a Custom Template File

1. Setup:  Create a ‘custom’ folder in the directory where the template file is located.
2. Copy and Modify:** Copy the template file into this custom folder and implement the required changes.
3. Verification: Use the `adchkcfg` script to ensure that your custom template will modify files as anticipated.
4. AutoConfig Behavior: After these steps, AutoConfig will prioritize your custom template file during its next run.