Skip to main content

AutoConfig Components and Tools in Oracle Apps

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
Labels:

Comments

Post a Comment

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
Post a Comment
Read more

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...
Post a Comment
Read more

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...
Post a Comment
Read more