a.Determine the AutoConfig template file you want to customize
Execute the following command to find out the corresponding AutoConfig template file for the configuration file you want to customize: Platform Tier Command
Unix Application
<AD_TOP>/bin/adtmplreport.sh contextfile=<CONTEXT> target=<configurationfile>
Database <RDBMS ORACLE_HOME>/appsutil/bin/adtmplreport.sh contextfile=<CONTEXT> target=<configurationfile>
For example, if you want to customize
$COMMON_TOP/html/bin/appsweb_$CONTEXT_NAME.cfg, execute:
On UNIX
$AD_TOP/bin/adtmplreport.sh contextfile=$CONTEXT_FILE \
target=$COMMON_TOP/html/bin/appsweb_$CONTEXT_NAME.cfg
The adtmplreport utility returns the name and location of the AutoConfig template file. For the above UNIX example it would return:
$FND_TOP/admin/template/appsweb.cfg.
we cannot customize all AutoConfig template files. The AutoConfig template file cannot be customized if the "LOCK" keyword appears in the template file's entry in the product driver file. AutoConfig ignores custom template files that are marked with "LOCK". For example, the following entry in <AD_TOP>/admin/driver/adtmpl.drv would prevent customization of the file adconfig.txt:
ad admin/template adconfig.txt INSTE8 <s_at>/admin adconfig.txt 600 LOCK
b.Create the custom template directory
Create a directory named "custom" at the location 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:
On UNIX
mkdir $FND_TOP/admin/template/custom
The custom template directory may have already been created when you migrated your customizations and migrate existing customizations.
c.Copy the AutoConfig template file
Copy the AutoConfig template file to the custom template file.
Execute the following command as the applmgr user:
On UNIX
cp -i <AutoConfig template file> <custom template file>
For example:
cp -i $FND_TOP/admin/template/appsweb.cfg \
$FND_TOP/admin/template/custom/appsweb.cfg
d.Edit the custom template file
Edit the custom template file with the editor of your choice, such as vi on UNIX.
Note: It is not supported to edit AutoConfig template files. Be sure to edit the custom template file only.
e.Verify your customizations
Execute the adchkcfg utility.
On UNIX
adchkcfg.sh contextfile=<CONTEXT>
When this utility runs, it instantiates any custom template files in place of the corresponding AutoConfig template file. The adchkcfg utility generates a report with information about all files and profile options that will be changed during the next normal execution of AutoConfig. Verify that your customizations would be applied as expected in your next AutoConfig run.
f.Run AutoConfig
Run AutoConfig and it instantiates any custom template file in place of the corresponding AutoConfig template file.
Execute the following command to find out the corresponding AutoConfig template file for the configuration file you want to customize: Platform Tier Command
Unix Application
<AD_TOP>/bin/adtmplreport.sh contextfile=<CONTEXT> target=<configurationfile>
Database <RDBMS ORACLE_HOME>/appsutil/bin/adtmplreport.sh contextfile=<CONTEXT> target=<configurationfile>
For example, if you want to customize
$COMMON_TOP/html/bin/appsweb_$CONTEXT_NAME.cfg, execute:
On UNIX
$AD_TOP/bin/adtmplreport.sh contextfile=$CONTEXT_FILE \
target=$COMMON_TOP/html/bin/appsweb_$CONTEXT_NAME.cfg
The adtmplreport utility returns the name and location of the AutoConfig template file. For the above UNIX example it would return:
$FND_TOP/admin/template/appsweb.cfg.
we cannot customize all AutoConfig template files. The AutoConfig template file cannot be customized if the "LOCK" keyword appears in the template file's entry in the product driver file. AutoConfig ignores custom template files that are marked with "LOCK". For example, the following entry in <AD_TOP>/admin/driver/adtmpl.drv would prevent customization of the file adconfig.txt:
ad admin/template adconfig.txt INSTE8 <s_at>/admin adconfig.txt 600 LOCK
b.Create the custom template directory
Create a directory named "custom" at the location 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:
On UNIX
mkdir $FND_TOP/admin/template/custom
The custom template directory may have already been created when you migrated your customizations and migrate existing customizations.
c.Copy the AutoConfig template file
Copy the AutoConfig template file to the custom template file.
Execute the following command as the applmgr user:
On UNIX
cp -i <AutoConfig template file> <custom template file>
For example:
cp -i $FND_TOP/admin/template/appsweb.cfg \
$FND_TOP/admin/template/custom/appsweb.cfg
d.Edit the custom template file
Edit the custom template file with the editor of your choice, such as vi on UNIX.
Note: It is not supported to edit AutoConfig template files. Be sure to edit the custom template file only.
e.Verify your customizations
Execute the adchkcfg utility.
On UNIX
adchkcfg.sh contextfile=<CONTEXT>
When this utility runs, it instantiates any custom template files in place of the corresponding AutoConfig template file. The adchkcfg utility generates a report with information about all files and profile options that will be changed during the next normal execution of AutoConfig. Verify that your customizations would be applied as expected in your next AutoConfig run.
f.Run AutoConfig
Run AutoConfig and it instantiates any custom template file in place of the corresponding AutoConfig template file.
No comments:
Post a Comment