Customizing AutoConfig Environment
Customizing an AutoConfig enabled environment used to be cumbersome. If youhave edited the final configuration files directly, they were overwritten each timeAutoConfig was run.
The way to do customization was to insert custom code between the BeginCustomization and End Customization blocks in the XML file. It was difficult todocument and keep track of the customizations that were made. Now Oracle hascome up with a better way to manage and maintain customizations.
As you have noted from the earlier discussion, AutoConfig uses template files togenerate final files. So the logical place would be to create a custom template file inthe same location and tell AutoConfig process to look at this custom template filerather than the normal template file that comes out of the box.
First find out the corresponding AutoConfig template file for the configuration file tobe customized
For example, if you want to customize $COMMON_TOP/html/bin/appsweb_$CONTEXT_NAME.cfg
Execute this step:
$AD_TOP/bin/adtmplreport.sh contextfile=$APPL_TOP/admin/$APPL_TOP/admin/(CONTEXT_NAME).xml \ target=$COMMON_TOP/html/bin/appsweb_$CONTEXT_NAME.cfg
The adtmplreport utility returns the name and location of the AutoConfig templatefile. For the above example it would return:$FND_TOP/admin/template/appsweb.cfg.
If you need to customize something on the Database side, you can use similarcommand structure $ORACLE_HOME/appsutil/bin/adtmplreport.sh contextfile= \ $ORACLE_HOME/appsutil/(CONTEXT_NAME).xml target= (Configuration File with FullPath)
Note: You cannot customize all AutoConfig template files. The AutoConfig templatefile cannot be customized if the “LOCK” keyword appears in the template file’s entryin the product driver file.
AutoConfig ignores custom template files that are marked with “LOCK”.
For example, the following entry in /admin/driver/adtmpl.drv would preventcustomization of the file adconfig.txt:
adadmin/template adconfig.txt INSTE8 /admin adconfig.txt 600 LOCK
Create the custom template directoryCreate a directory named “custom” at thelocation where the AutoConfig template file resides.
For example, if you want to customize $FND_TOP/admin/template/appsweb.cfg,execute the following command as the applmgr user: mkdir$FND_TOP/admin/template/custom
Copy the AutoConfig template fileCopy the AutoConfig template file to the customtemplate file.
Execute the following command as the applmgr user:
cp -i$FND_TOP/admin/template/appsweb.cfg \ $FND_TOP/admin/template/custom/appsweb.cfg
Edit the custom template file Edit the custom template file with a text editor withrequired customizations.
Note: Do not edit the original template files. It will violate your support contract withOracle support.
Latest posts by Nagulu Polagani (see all)
- ORA-65500: could not modify DB_UNIQUE_NAME, resource exists - December 13, 2017
- OPW-00019: Failed to update the CRS resource with DB password file location - December 13, 2017
- ORA-16698: LOG_ARCHIVE_DEST_n parameter set for object to be added - December 13, 2017