What are the basic components of
AutoConfig?
Components
|
Location
|
Description
|
Applications
Context
|
On the application tier:
On the database tier:<APPL_TOP>/admin <RDBMS ORACLE_HOME>/appsutil |
An XML
repository (<Context_name>.xml) contains information specific to that
Applications instance. Can be updated by running the Context Editor.
Do not manually update this file! |
AutoConfig
Template Files
|
On the application tier:
On the database tier:<PROD_TOP>/admin/template For example: <AD_TOP>/admin/template <FND_TOP>/admin/template <RDBMS ORACLE_HOME>/appsutil/template |
Include named
tags which are replaced with instance-specific information from the
Applications Context. There is one template file for each configuration file.
For example: apps_nt.conf apps_ux.conf |
AutoConfig File
Driver
|
On the application tier:
On the database tier:<PROD_TOP>/admin/driver For example: <AD_TOP>/admin/driver/adtmpl.drv <FND_TOP>/admin/driver/fndtmpl.drv <RDBMS ORACLE_HOME>/appsutil/template |
Used by
AutoConfig to list the AutoConfig Template Files, their destination
locations, and the commands to be executed, for example, the commands to
update profile options. Every Product Top contains its own AutoConfig File
Driver.
|
AutoConfig
Scripts
|
On the application tier:
On the database tier:<AD_TOP>/bin <RDBMS ORACLE_HOME>/appsutil/bin |
Provide a
simplified
interface to the AutoConfig APIs. For example: adautocfg.sh / adautocfg.cmd adconfig.sh / adconfig.cmd |
