In Oracle Applications 11i & R12 (12i) all the configuration parameters are captured in two context files:
Application context file called the <CONTEXT_NAME>.xml contains the configuration information for the application tier & is located in $APPl_TOP/admin for each node of application tier.
Database context file called the <CONTEXT_NAME>.xml contains the configuration information for the database tier & is located in $ORACLE_HOME/appsutil/.
Details stored in the context file contains host names,domain name , directory structure, port numbers used ……
The AutoConfig feature of Oracle application manager(OAM) is used to update & manage context files.
Updating Context file
Suppose we want to update the active port from <original port no.> to 80 , for this we will edit the application context file as follows:
Step 1 :Start all services
$ $COMMON_TOP/admin/scripts/<context_name>/adstrtal.sh APPS/<apps password>
Step 2 :log on to OAM & click site map.
Step 3:Click AutoConfig from the list of System Configuration features in the Administration tab.
Step 4 : Click the Edit Parameter button for the application tier context file to access the Context File Parameters page & then click the system tab.
Step 5 : Click the Focus icon (blue triangle) for oa_web_server. This expands oa_web_server and shows the web server related parameters.
Step 6:Update the Web Port (s_active_webport) parameter from < Original port number> to 80.
Step 7 : Save it & answer the tab.Then logout of OAM
AutoConfig Script
The autoconfig script uses information from the context file to generate all applications configuration files & updates database profiles. It is located in
Application tier: $COMMON_TOP/admin/scripts/CONTEXT_NAME/adautoconfig.sh
Database tier: $ORACLE_HOME/appsutil/scripts/CONTEXT_NAME/adautoconfig.sh
Now we run the autoconfig script to reconfigure the oracle application system with the updated Applications context.
Step 1 : Stop all services
$ $COMMON_TOP/admin/scripts/<context_name>/adstpall.sh APPS/<apps password>
Step 2:Run the autoconfig script, $adautocfg.sh & respond to the prompts.
Step 3:Check log files for any errors.log file for autoconfig is adconfig.log & is located in
<APPL_TOP>/admin/<context_name>/log/MMDDhhmm/
Step 4: Restart all services :
$ $COMMON_TOP/admin/scripts/<context_name>/adstrtal.sh APPS/<apps password>
Rolling back an autoconfig session
Each execution of AutoConfig creates a roll back script in case you want to revert back to the previous configuration settings. For this we perform the following steps:
Step 1 :Shut down all services:
$ cd $COMMON_TOP/admin/scripts/<context_name>
$ adstpall.sh APPS/<APPS password>
Step 2:Restore AutoConfig session.
$ cd $APPL_TOP>/admin/<context_name>/out/MMDDhhmm
$ restore.sh
Step 3 : Restart all services:
$ $COMMON_TOP/admin/scripts/<context_name>/adstrtal.sh APPS/<APPS password>
Restoring the AutoConfig updated files and restarting the services allows you to log on to OAM.
Restoring the previous configuration
Now we run OAM AutoConfig to restore the Applications Context.
Step 1 :Log on to the Oracle Application Manager (OAM) & click site map.You will be able to log on but some services will be down.
Step 2: Click AutoConfig from the list of System Configuration features in the Administration tab.
Step 3 : Click the Show History button for the application tier context file to access the Context File History page.
Step 4 :Click the Show Differences from Current Configuration button to see the recently updated parameters & Select Restore Previous Value for the Web Port and Discoverer Port parameters.
Step 5 :Save & respond the tabs. Log out of OAM.
Step 6 :Shut down all services:
$ cd $COMMON_TOP/admin/scripts/<context_name>
$ adstpall.sh APPS/<APPS password>
Step 7 :Run the AutoConfig script, adautocfg.sh & Respond to the prompts.
Step 8 : View the log file and check for any errors.
Step 9 : Restart all services:
$ $COMMON_TOP/admin/scripts/<context_name>/adstrtal.sh APPS/<APPS password>
Step 10 :Log on to the Oracle Application Manager (OAM)
If the status of some services appears to be down, click the Refresh icon to update the
status.
Related : Metalink Notes
218089.1 Autoconfig FAQ
165195.1 Using AutoConfig to Manage System Configurations with Oracle Applications 11i
387859.1 Using AutoConfig to Manage System Configurations in Oracle Applications Release 12
270519.1 Customizing an AutoConfig Environment
364927.1 How To Run Autoconfig On Database Tier (DB-Tier)
341322.1 How to change the hostname of an Applications Tier using AutoConfig
338003.1 How to change the hostname and/or port of the Database Tier using AutoConfig
315674.1 How To Verify if Autoconfig is Enabled on 11.5.x
391406.1 How to get a clean Autoconfig Environment
Other Related Posts
Autoconfig Basics
Unwrapping XML/Context File
Autoconfig Basics
Did you get a chance to download 6 Docs Every Apps DBA Must Read for EBS R12.2 ? If not, then get it now by clicking on link below.
If you need to learn more about Oracle Apps DBA (Architecture, Installation, WebLogic, Patching, Cloning and other maintenance tasks with the upgrade of Oracle E-Business Suite 12.2.0 to 12.2.4 then have a look at our Oracle Apps DBA Training