This article would help you particularly when you want to customize an autoconfig environment and make few instance specific changes post cloning.
1. Customizing autoconfig.
Why? - we had few profile options for FTP connectivity, which would get over written every time we run autoconfig, also we had JVM settings that required to be added in context file.
Requirement was to make sure that no other settings/profile options gets affected by enabling this setup, initially when we tried editing the context file to have these values to be populated to target files, there were other files affected by this change, proved to be a wrong move.
1.2. What are the files that could be changed to achieve this change, for JVM settings the autoconfig target file is opmn.xml (R12) clearly, now we need to find the template file which will be updated by autoconfig driver, how do we do it ??
tool --> adtmplreport.sh
Location --> $AD_TOP/bin
usage : $AD_TOP/bin/adtmplreport.sh contextfile=<contextfile_complete_path> target=<target_file_inthis_case_is_opmn.xml>
so the command would looks like,
$AD_TOP/bin/adtmplreport.sh contextfile=/u01/app/oracle/APPS/inst/apps/APPS_detr-ebs02/appl/admin/APPS_detr-ebs02.xml target=$INST_TOP/ora/10.1.3/opmn/conf/opmn.xml
o/p would be in a log file in the location where you executed this command..
===========================================================
[ INFO_REPORT ]
[FND_TOP]
TEMPLATE FILE : /u01/app/oracle/APPS/apps/apps_st/appl/fnd/12.0.0/admin/template/opmn_xml_1013.tmp
TARGET FILE : /u01/app/oracle/APPS/inst/apps/APPS_debl-ebs01/ora/10.1.3/opmn/conf/opmn.xml
===========================================================
so now, we need to create directory "custom" under /u01/app/oracle/APPS/apps/apps_st/appl/fnd/12.0.0/admin/template/custom and copy the file "opmn_xml_1013.tmp" to this custom directory and make necessary changes.
Note: When the autoconfig finds the template file inside the custom directory it would instantiate this template file rather than the original file.
2. Customizing profile option settings.
Note: This document would provide you an high level plan and purely my experience of setting up the required changes in our environment, please cross verify and ensure to try it out in test instances before making any changes to your PROD systems.
2.1 Requirement:- The below profile options were over written every time we run autoconfig and required manual intervention to re enter them.
POR : Proxy Server Name:
POR : Proxy Server Port:
2.2 :- Next step is to find the file that would update these settings, upon checking on metalink notes and little bit of search on the server, I could figure out that the template file is "icxwebprf.sql" located at "/u01/app/oracle/APPS/apps/apps_st/appl/icx/12.0.0/admin/template", update the values for the server and the port number.
Re run the autoconfig to ensure that the values are not blanked out.
3. We usually change the Site value(forms)profile option updating the instance name with the date, but how to change the Self service/Frame work login headings.
3.1 Login as SYSADMIN
3.2 Application -->function
3.3 Query the function "FWK_HOMEPAGE_BRAND".
3.4 Replace the value of the 'User Function Name' with the desired text.
3.5 Save and exit, log and log back in to see the changes.
No need to bounce the apache and clear caches.
Note : This is purely my experience, please ensure to double check every change thoroughly before moving it onto PROD environments.
RMAN Errors during DUPLICATE/Clone database.
1. Customizing autoconfig.
Why? - we had few profile options for FTP connectivity, which would get over written every time we run autoconfig, also we had JVM settings that required to be added in context file.
Requirement was to make sure that no other settings/profile options gets affected by enabling this setup, initially when we tried editing the context file to have these values to be populated to target files, there were other files affected by this change, proved to be a wrong move.
1.2. What are the files that could be changed to achieve this change, for JVM settings the autoconfig target file is opmn.xml (R12) clearly, now we need to find the template file which will be updated by autoconfig driver, how do we do it ??
tool --> adtmplreport.sh
Location --> $AD_TOP/bin
usage : $AD_TOP/bin/adtmplreport.sh contextfile=<contextfile_complete_path> target=<target_file_inthis_case_is_opmn.xml>
so the command would looks like,
$AD_TOP/bin/adtmplreport.sh contextfile=/u01/app/oracle/APPS/inst/apps/APPS_detr-ebs02/appl/admin/APPS_detr-ebs02.xml target=$INST_TOP/ora/10.1.3/opmn/conf/opmn.xml
o/p would be in a log file in the location where you executed this command..
===========================================================
[ INFO_REPORT ]
[FND_TOP]
TEMPLATE FILE : /u01/app/oracle/APPS/apps/apps_st/appl/fnd/12.0.0/admin/template/opmn_xml_1013.tmp
TARGET FILE : /u01/app/oracle/APPS/inst/apps/APPS_debl-ebs01/ora/10.1.3/opmn/conf/opmn.xml
===========================================================
so now, we need to create directory "custom" under /u01/app/oracle/APPS/apps/apps_st/appl/fnd/12.0.0/admin/template/custom and copy the file "opmn_xml_1013.tmp" to this custom directory and make necessary changes.
Note: When the autoconfig finds the template file inside the custom directory it would instantiate this template file rather than the original file.
2. Customizing profile option settings.
Note: This document would provide you an high level plan and purely my experience of setting up the required changes in our environment, please cross verify and ensure to try it out in test instances before making any changes to your PROD systems.
2.1 Requirement:- The below profile options were over written every time we run autoconfig and required manual intervention to re enter them.
POR : Proxy Server Name:
POR : Proxy Server Port:
2.2 :- Next step is to find the file that would update these settings, upon checking on metalink notes and little bit of search on the server, I could figure out that the template file is "icxwebprf.sql" located at "/u01/app/oracle/APPS/apps/apps_st/appl/icx/12.0.0/admin/template", update the values for the server and the port number.
Re run the autoconfig to ensure that the values are not blanked out.
3. We usually change the Site value(forms)profile option updating the instance name with the date, but how to change the Self service/Frame work login headings.
3.1 Login as SYSADMIN
3.2 Application -->function
3.3 Query the function "FWK_HOMEPAGE_BRAND".
3.4 Replace the value of the 'User Function Name' with the desired text.
3.5 Save and exit, log and log back in to see the changes.
No need to bounce the apache and clear caches.
Note : This is purely my experience, please ensure to double check every change thoroughly before moving it onto PROD environments.
Related Posts ::
RMAN Errors during DUPLICATE/Clone database.
