Wednesday, June 10, 2009
Autoconfig Tool in Oracle Apps
AutoConfig is a tool that supports automated configuration of an Applications instance.All of the information required for configuring an Applications instance is collected into two local repositories, called the Applications Context and the Database Context. When AutoConfig runs on the Application tier, it uses information from the Applications Context file to generate all configuration files and update database profiles. 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.
There are several major benefits provided by AutoConfig:
• Configuration Support: AutoConfig configures the APPL_TOP, the ORACLE_HOME(s) and its supporting technology stack.
• Configuration Management: AutoConfig centralizes the configuration and re-configuration
of an Applications instance.
• Configuration Delivery and Patching: The uptake of new technology is simplified,
as new configurations and configuration changes can be provided in the form of a patch
Once an APPL_TOP is enabled for AutoConfig, it has an Applications Context file stored in
the APPL_TOP as /admin/.xml. Once the Database is enabled for AutoConfig, it has a Database Context file stored in the RDBMS ORACLE_HOME as /appsutil/.xml. When a change is made to any of the Context files or any of the templates, the AutoConfig utility updates the Applications 11i configuration. AutoConfig can also start and stop all Applications system processes that it manages.
Patches required for Autoconfig
********************************
1.AD minipack Requirements. If you are not on AD minipack F or later, apply the latest AD minipack from OracleMetaLink.
2.Apply TXK AutoConfig Template patch
Update the Oracle Applications file system with the AutoConfig files by applying patch 5985992
to all application tier nodes in the Applications instance. Apply the unified driver.
5985992 to all application tier nodes in the Applications instance. Apply the unified driver
Migrate to Autoconfig
********************************
1. Apply autoconfig mini pack
2.Apply TXK autoconfig patch
3. Generate appsutil.zip at application side.
cd $AD_TOP/bin
4.appsutil.zip will be created in $APPL_TOP/admin/out
5.copy appsutil.zip to RDBMS oracle home
6.unzip the appsutil.zip
7.Generate your Database Context File
cd $ORACLE_HOME/appsutil/bin
perl adbldxml.pl tier=db appsuser=apps appspasswd=apps
8.run autoconfig on DB tier
adconfig.sh contextfile=file appspass=apps
9.Generate your application Context File
cd $AD_TOP/bin
perl adbldxml.pl tier=apps appsuser=apps appspasswd=apps
10.run autoconfig on Appl tier.
Roll back autoconfig
*********************************
DB--$ORACLE_HOME/appsutil/out//MMDDhhmm---restore.sh
APPL--$APPL_TOP/admin//out/MMDDhhmm
Configuration check run of autoconfig
*************************************************************
$AD_TOP/bin adchkcfg.sh contextfile=file appspass=apps
$APPL_TOP/admin/_ /out//cfgcheck.txt.
cfgcheck.txt have the summary for customization changes. This file contains the list of files that will under go a change during the next autoconfig run. In the report there will be three sections for each report.
· Existing File
· New File
· Diff File
To check env is autoconfig enabled ot not
*******************************************
adcfginfo.sh contextfile= show=enabled
Source:--Matalink Note:165195.1
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment