Professional Documents
Culture Documents
Auto Config in Apps R12
Auto Config in Apps R12
2) All the information required for configuring an Applications instance is collected into two local XML repositories, called the Applications context file and the database context file. 3) When AutoConfig runs on the application tier, it uses information from the Applications context file to generate all configuration files and update database profiles. 4) When AutoConfig runs on the database tier, it uses information from the database context file to generate all configuration files used on the database tier. 5) There is one Applications context for each application tier, and one for each database tier. Basic components of AutoConfig?
Component Applications Context Location On the application tier: <INST_TOP>/appl/admin On the database tier: <RDBMS ORACLE_HOME>/appsutil On the application tier: <PROD_TOP>/admin/template For example: <AD_TOP>/admin/template <FND_TOP>/admin/template On the database tier: <RDBMS ORACLE_HOME>/appsutil/template
On the application tier: <PROD_TOP>/admin/driver For example: <AD_TOP>/admin/driver/adtmpl.drv <FND_TOP>/admin/driver/fndtmpl.drv On the database tier: <RDBMS ORACLE_HOME>/appsutil/template
AutoConfig Scripts
Location
On the application tier: <INST_TOP>/admin/scripts On the database tier: <RDBMS ORACLE_HOME>/appsutil/ scripts/<CONTEXT_NAME>
Description
A wrapper script that calls adconfig.sh Instantiates template files with values specific to the instance (taken from the Applications for the application tier and the database context for the database tier). Updates configuration files and profile options. A wrapper script that calls adconfig.pl.
adconfig.sh
On the application tier: <AD_TOP>/bin On the database tier: <RDBMS ORACLE_HOME>/appsutil/bin/ On the application tier: <AD_TOP>/bin On the database tier: <RDBMS ORACLE_HOME>/appsutil/bin On the application tier: <AD_TOP>/bin On the database tier: <RDBMS ORACLE_HOME>/appsutil/bin
adconfig.pl
adchkcfg.sh
Generates a report that highlights differences between the original config files and AutoConfiggenerated config files. The report is named cfgcheck.html. It is located under: On the application tier: <INST_TOP>/admin/ /out/<MMDDhhmm> On the database tier: <RDBMS ORACLE_HOME>/appsutil/out/ <CONTEXT_NAME>/<MMDDhhmm>
adautocfg.sh script calls --- adconfig.sh (<AD_TOP/bin>) which in turn calls- adconfig.pl (<AD_TOP/bin>) this actually starts Autoconfig.
The Check Config utility (adchkcfg) is used to review the configuration changes that would take effect on an E-Business Suite instance during the next AutoConfig run. It identifies the potential changes to both the File system as well as the Database. It can be run on both the applications tier and the database tier. Execute the following command to run the Check Config utility.
sh <RDBMS_ORACLE_HOME>/appsutil/bin/adchkcfg.sh contextfile=<CONTEXT_FILE>
sh <AD_TOP>/bin/adchkcfg.sh contextfile=<CONTEXT_FILE>
This script generates both HTML and text reports. The reports provide information about all file changes, profile option changes and other important database updates that will be done during the next normal execution of AutoConfig. The script also creates a zip file report "ADXcfgcheck.zip" that contains all the files and reports mentioned above. The ADXcfgcheck.zip can be copied to a local desktop PC and the HTML report can be viewed there without breaking the hyper-links in the report. Please find the attachment html file
How can I roll back an AutoConfig session? All Backup Configuration files from each Autoconfig are stored in following locations.
On the application tier: <INST_TOP>/admin/out/<MMDDhhmm> On the database tier: <RDBMS ORACLE_HOME>/appsutil/out/<CONTEXT_NAME>/<MMDDhhmm> where: <MMDDhhmm> = (month, day, hour, and minute of the AutoConfig run) You can run restore.sh to rollback an Autoconfig session.
In case the <INST_TOP> has also been lost accidentally, the applications tier context file may be retrieved as follows: Execute the following command on the database tier: perl <ORACLE_HOME>/appsutil/clone/bin/adclonectx.pl retrieve On being prompted for the context file to be retrieved, select the option of retrieving the applications tier context file that has been lost. While confirming the location for the context file, set it to any existing directory with write permission. Once the context file has been generated in the specified location, move it to the location specified for the context file in the context variable 's_contextfile'. To retrieve the database tier context file. Execute the following command on the database tier: perl <ORACLE_HOME>/appsutil/clone/bin/adclonectx.pl retrieve OR perl <RDBMS_ORACLE_HOME>/appsutil/bin/adbldxml.pl
Attention: The database server instance and the database listener must remain available during the AutoConfig run. All the other database tier services should be shut down.
You want to delete an application tier Your database is upgraded/migrated resulting in a change in one of the following parameters: o Database Host o Database Port o Database Name o Database SID
How do I deregister an application tier from the Net Services Topology Data Model?
To deregister the current application tier from the Net Services Topology Data Model, invoke the following command:
perl <AD_TOP>/bin/adgentns.pl contextfile=<CONTEXT_FILE> -removeserver
How do I deregister a database tier from the Net Services Topology Data Model?
To deregister the current database tier from the Net Services Topology Data Model, invoke the following command:
perl <RDBMS ORACLE_HOME>/appsutil/bin/adgentns.pl contextfile=<CONTEXT_FILE> -removeserver
Does the database server need to be available during the AutoConfig run?
Yes. The database server and database listener must remain available when AutoConfig is run on either the database tier or application tier.
When the value is reset (empty), AutoConfig tries to connect to the database using the s_dbSid, s_dbhost and s_dbport context variables. See next question.