Remote IT Support!! Please contact us

For Any Remote Support,Implementation/Upgrade Projects,Queries,Collaborations please mail us at support@funoracleapps.com

AutoConfig Components and Tools in Oracle Apps

No comments

AutoConfig Components and Tools in Oracle Apps








AutoConfig is a tool that supports automated configuration of an Oracle E-Business Suite Release 12 instance. All the information required for configuring an Applications instance is collected into two local repositories, called the Applications context file and the database context file.  

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. 


Benefits  


  • Configuration Support: AutoConfig configures the APPL_TOP, the ORACLE_HOMEs, and the supporting technology stack.  

Configuration Management:  centralizes the configuration and re-configuration of an Application 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. 

AutoConfig Components 


Component 

Description 

Applications context File 

An XML repository located in the INST_TOP that contains information specific to the APPL_TOP. 

Database context File 

An XML repository located in the RDBMS ORACLE_HOME that contains information specific to that database tier. 

AutoConfig template files 

Files containing named tags that are replaced with instance-specific information from the appropriate context ("instantiation"). 

AutoConfig driver files 

Every Oracle E-Business Suite product maintains a driver file used by AutoConfig. The driver file lists the AutoConfig file templates and their destination locations. 

AutoConfig scripts 

A set of scripts that provide a simplified interface to the AutoConfig APIs. 

 

The Applications Release 12 application tier is AutoConfig-enabled, and has an Applications context file stored in the INST_TOP as $INST_TOP/appl/admin/<CONTEXT_NAME>.xml. The Applications Release 12 database tier created via Rapid Install is also AutoConfig-enabled, and has a database context file stored in the RDBMS ORACLE_HOME as <RDBMS ORACLE_HOME>/appsutil/<CONTEXT_NAME>.xml. When a change is made to any of the context files or any of the template files, the AutoConfig utility updates the Applications Release 12 configuration. 

 

 

AutoConfig Tools 


Script 

Location 

Utility 

adautocfg.sh 

On Applications Tier: 
<INST_TOP>/admin/scripts  
 
On Database Tier: 
<RDBMS_ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME> 

This script is used for running AutoConfig. 

adchkcfg.sh 

On Applications Tier: 
<AD_TOP>/bin 
 
On Database Tier: 
<RDBMS_ORACLE_HOME>/appsutil/bin 

This script may be run before running AutoConfig to review the changes on running AutoConfig. This will generate a report showing the differences between the existing configuration and what the configuration would be after running AutoConfig. 

GenCtxInfRep.pl 

On Applications Tier: 
<FND_TOP/patch/115/bin 
 
On Database Tier: 
<RDBMS_ORACLE_HOME>/appsutil/bin 

This script can be used to find out detailed information about context variables and the templates in which they are used, given all or part of a context variable name as a keyword. 

adtmplreport.sh 

On Applications Tier: 
<AD_TOP>/bin 
 
On Database Tier: 
<RDBMS_ORACLE_HOME>/appsutil/bin 

This script can be used to gather information regarding the location of the AutoConfig templates, provided the location of the instantiated files and vice versa. 

admkappsutil.pl 

On Applications Tier: 
<AD_TOP>/bin 

This script is used while applying patches to the database tier. Running this script generates appsutil.zip which may be copied over to the database tier to migrate the patch to the database tier. 

 


Reference:


If you like please follow and comment

No comments :

Post a Comment