August 17

Using AutoConfig to Manage System Configurations with Oracle

Applications 11i
文档 ID:
注释:165195.1
类型:
WHITE PAPER

上次修订日期:
15-MAY-2007
状态:
PUBLISHED

Using AutoConfig to Manage System Configurations with Oracle Applications 11i

May 2007
This document provides an overview of AutoConfig, instructions for migration to AutoConfig,
instructions for configuring an Oracle Applications 11i environment using AutoConfig, and a
discussion of the management of configuration customizations. It is important that you read
and follow this document in its entirety before migrating. The most current version of this
document is published in Note 165195.1 on Oracle Metalink . An FAQ is also available in
Note 218089.1 on Oracle Metalink .

Attention: Windows users. This document typically uses UNIX syntax when specifying
directories; please substitute the appropriate Windows syntax.

This document contains the following sections:

• Section 1: Overview
Use AutoConfig to manage your system configurations.
• Section 2: Pre-requisites
Pre-requisites for migrating to AutoConfig.
• Section 3: Maintaining System Configuration
Maintain the configuration of your Oracle Applications Release 11i environment.
• Section 4: Managing Configuration Customizations
Customize AutoConfig generated configurations.
• Section 5: Migrating to AutoConfig
Migrate to AutoConfig for the configuration management of your Oracle Applications
Release 11i environment.
• Section 6: Migrating to AutoConfig on RAC
Migrate to AutoConfig for the configuration management of your 11i RAC environment.
• Section 7: Migrating to AutoConfig on the Database Tier
Migrate to AutoConfig for the configuration management of your Oracle Applications
Release 11i environment on the Database Tier.
• Section 8: Migrating to AutoConfig on the Application Tier
Migrate to AutoConfig for the configuration management of your Oracle Applications
Release 11i environment on the Application Tier.
• Section 9: Known Issues
Known issues with the configuration management of your Oracle Applications Release 11i
environment.
Conventions
Convention
Meaning

APPLMGR
User who owns the applications file system (APPL_TOP and application tier technology stack)

ORACLE
User who owns the database file system (RDBMS ORACLE_HOME and database files).

CONTEXT_NAME
Logical name for your Context. Default: <SID>_<hostname>
In earlier versions the default was set to <SID>

CONTEXT
Full path to the Context File (either Applications Context File or Database Context File).
Default:
<APPL_TOP>/admin/<CONTEXT_NAME>.xml and
<RDBMS ORACLE_HOME>/appsutil/<CONTEXT_NAME>.xml

APPSpwd
Applications database user password

APPSuser/APPSpwd
Applications database

Monospace Text
Represents command line text. Type this command exactly as shown.

<>
Text enclosed in angle brackets represents a variable. Substitute a value for the variable
text. Do not type the angle brackets.

Section 1: Overview
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.
AutoConfig consists of several components:
Component
Description

Applications Context
An XML repository located in the APPL_TOP containing information specific to that APPL_TOP.

Database Context
An XML repository located in the RDBMS ORACLE_HOME containing information specific to
that Database tier.

AutoConfig File Templates

Template files that include named tags, which are replaced with instance-specific
information from the according Context (this process is called "instantiation").

AutoConfig Driver File

Every product in the E-Business Suite 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.

Once an APPL_TOP is enabled for AutoConfig, it has an Applications Context file stored in the
APPL_TOP as <APPL_TOP>/admin/<CONTEXT_NAME>.xml. Once the Database is enabled for
AutoConfig, it 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 templates, the AutoConfig utility updates the Applications 11i
configuration.

AutoConfig can also start and stop all Applications system processes that it manages.

Section 2: Pre-requisites
Complete the steps in this section (in the order listed) before you migrate to AutoConfig. If
you have already migrated to AutoConfig, verify that the pre-requisites are met before
applying the latest AutoConfig patch.
1. AD minipack Requirements. If you are not on AD minipack F or later, apply
the latest AD minipack from OracleMetaLink.
2. Verify software versions
The following software component versions must exist on the application tier and/or
on the database tier. The tier column indicates the node where the software
component must be present.
Software
Minimum Version
Tier
Details

JRE
1.3.1
Database tier
Must install JRE 1.3.1_1.5 or higher into the <RDBMS ORACLE_HOME>/jre/1.3.1
 directory. This directory will be used by the AutoConfig java utility. See Appendix A
for installation instructions.

JDK
1.3.1
Application tier
Refer to Upgrading to JDK 1.3 with Oracle Applications 11i on OracleMetaLink for
instructions.

Zip
2.3
Application tier and database tier
Download from InfoZip. Zip must be in your PATH.

UnZip
5.x
Application tier
Download from InfoZip. UnZip must be in your PATH.

Perl
5.004
Application tier and database tier
You can use the Perl shipped with iAS1022 and RDBMS 9i or download it from
Perl.com. Perl must be in the PATH when running AutoConfig. The PERL5LIB
environment variable must be defined. See Appendix D for details.

Perl
5.6
TRU64 customers ONLY -
Application tier and database tier
Download Perl 5.6 from Perl.com. Perl must be in the PATH for running AutoConfig.

3. Special Requirements for 11i1. If the instance was created with an 11.5.1
Rapid Install, then complete the following steps:
• Migrate to Apache 1.0.2.2.2.
Refer to Note 146468.1 on Oracle Metalink .
4. For Windows customers ONLY. Download and apply the Windows
AutoConfig Updates:
• 2237858 - Provide support for long file names (8.3)
• 4617175 - Provide specific Windows executables
• 4445697 - Provide the Windows Service Control Wrapper (OaMkSvc)
For patch application follow the instructions in the Readme.

Section 3: Maintaining System Configuration

This section describes how to apply latest AutoConfig patch and manage your Oracle
Applications Release 11i if your Instance is AutoConfig enabled. In addition to re-configuring
your system, AutoConfig can be used to review changes made to the configuration files, to
start and stop Applications processes and to start and stop Database processes.
1. Commands to maintain System Configurations on the Database Tier
All scripts listed below are located in
<RDBMS ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>.
Platform
Functionality
Command

UNIX
Start Database listener process
addlnctl.sh start <SID>

Start Database process

addbctl.sh start

Stop Database listener process

addlnctl.sh stop <SID>

Stop Database process

addbctl.sh stop

Run AutoConfig
adautocfg.sh

Windows
Start Database listener process
addlnctl.cmd start <SID>

Start Database process

addbctl.cmd start

Stop Database listener process

addlnctl.cmd stop <SID>

Stop Database process

addbctl.cmd stop

Run AutoConfig
adautocfg.cmd

Note: Running AutoConfig might change your existing environment files. After
running AutoConfig, you should always set the environment before you run any
Applications utilities in order to apply the changed environment variables.

2. Commands to maintain System Configurations on the Application Tier

All scripts listed below are located in
<COMMON_TOP>/admin/scripts/<CONTEXT_NAME>.

Platform
Functionality
Command
UNIX
Start Applications processes
adstrtal.sh <APPSuser/APPSpwd>

Stop Appliations processes

adstpall.sh <APPSuser/APPSpwd>

Run AutoConfig
adautocfg.sh

Windows
Start Applications processes
adstrtal.cmd <APPSuser/APPSpwd>

Stop Appliations processes

adstpall.cmd <APPSuser/APPSpwd>

Run AutoConfig
adautocfg.cmd

Note: Running AutoConfig might change your existing environment files. After
running AutoConfig, you should always set the environment before you run any
Applications utilities in order to apply the changed environment variables.

3. Patching AutoConfig
If you were instructed to apply the latest AutoConfig patch, perform the following
steps in the order listed:
• Review the Pre-Requisites
• Apply TXK AutoConfig Template patch
Update the Oracle Applications file system with the AutoConfig files by applying
patch 5759055 to all application tier nodes in the Applications instance. Apply the
unified driver.
5759055 to all application tier nodes in the Applications instance. Apply the unified
driver.

If you are running on SUSE Linux Enterprise Server 10, apply patch 5949373 to all
application tier nodes in the Applications instance.

Note: ADX and TXK rollup patches for configuration management have been
combined. The first combined patch is TXK Autoconfig Template Rollup Patch M
(4709948), which includes the last ADX minipack ADX.F (3453499).

• Copy AutoConfig to the RDBMS ORACLE_HOME

Update the RDBMS ORACLE_HOME file system with the AutoConfig files by
performing the following steps:
• On the Application Tier (as the APPLMGR user):
• Log in to the APPL_TOP environment (source the environment
file)
• Create appsutil.zip file
perl <AD_TOP>/bin/admkappsutil.pl
 • This will create appsutil.zip in $APPL_TOP/admin/out .
• On the Database Tier (as the ORACLE user):
• Copy or FTP the appsutil.zip file to the <RDBMS ORACLE_HOME>
• cd <RDBMS ORACLE_HOME>
unzip -o appsutil.zip
• Run AutoConfig on the Database Tier
Run AutoConfig on the database tier node. Use the adautocfg.sh/.cmd command
described in Section 3, Task 1.
Attention: The database server and the database listener must remain available
during the AutoConfig run. All the other database tier services should be shut
down.

• Run AutoConfig on the Application Tiers

Run AutoConfig on all application tier nodes. Use the adautocfg.sh/.cmd command
described in Section 3, Task 2.
Attention: The database server and the database listener must remain available
during the AutoConfig run. Only the application tier servers should be shut down.

4. Making changes to your configuration

There are three ways to change your configuration:
• Apply a patch from Oracle that adds or changes the variables in your Context,
AutoConfig template files, or AutoConfig driver files.
• Run the Context Editor to change the variables in your Context. For
instructions on how to download and use the Context Editor, refer to Appendix C.
• If you have Oracle Applications Manager (OAM) H or higher installed, we
recommend using the web based Context Editor to perform configuration updates
to your Applications Context. OAM provides advanced features for context file
editing. Refer to Oracle Applications Manager 11i Availability for instructions on
installing OAM. Refer to Oracle Applications Maintenance Procedures - Section
Managing Configuration Parameters for information on how to use the OAM
Context Editor. Oracle Applications Maintenance Procedures - Section Managing
Configuration Parameters for information on how to use the OAM Context Editor.
Note: Configuration changes will not take effect until you run AutoConfig and
restart your server processes.

5. Rolling back an AutoConfig session

Each execution of AutoConfig creates a rollback script in case you need to revert to
the previous configuration settings. The script and all backup configuration files from
each AutoConfig session are stored in:
Tier
Directory

Application
<APPL_TOP>/admin/<CONTEXT_NAME>/out/<MMDDhhmm>

Database
<RDBMS ORACLE_HOME>/appsutil/out/<CONTEXT_NAME>/<MMDDhhmm>

where:<MMDDhhmm> = (month, day, hour, minute of AutoConfig run)

 To roll back an AutoConfig session:

• On UNIX
restore.sh
• On Windows
restore.cmd
6. Reviewing AutoConfig Log files
AutoConfig logfiles are stored under:
Tier
Directory

Application
<APPL_TOP>/admin/<CONTEXT_NAME>/log/<MMDDhhmm>

Database
<RDBMS ORACLE_HOME>/appsutil/log/<CONTEXT_NAME>/<MMDDhhmm>

There will be one log file per AutoConfig session, and it will contain exact information
for every action that AutoConfig performed.

Section 4: Managing Configuration Customizations

All files managed by AutoConfig are marked by the following note:
######################################################
##########
#
# This file is automatically generated by AutoConfig. It will be read and
# overwritten. If you were instructed to edit this file, or if you are not
# able to use the settings created by AutoConfig, refer to Metalink
# document 165195.1 for assistance.
#
######################################################
##########

If the files maintained by AutoConfig require customization, refer to Note 270519.1 on

Oracle Metalink .

Section 5: Migrating to AutoConfig

Complete the steps in this section (in the order listed) to migrate to AutoConfig. If your have
already migrated to AutoConfig, refer to Section 3 to learn about maintaining your system
configuration using AutoConfig:
1. Apply TXK AutoConfig Template patch
Update the Oracle Applications file system with the AutoConfig files by applying
patch 5759055 to all application tier nodes in the Applications instance. Apply the
unified driver. 5759055 to all application tier nodes in the Applications instance.
Apply the unified driver.
If you are running on SUSE Linux Enterprise Server 10, apply patch 5949373 to all
application tier nodes in the Applications instance. 5949373 to all application tier
nodes in the Applications instance.
 2. Migrate to AutoConfig on the Database Tier
Follow the steps in Section 7 to migrate to AutoConfig on the Database Tier. If you
have already migrated to AutoConfig on the Database Tier, then you can omit that
section.
3. Migrate to AutoConfig on the Application Tier
Follow the steps in Section 8 to migrate to AutoConfig on the Application Tier. If you
have already migrated to AutoConfig on the Application Tier, then you can omit that
section.
Your system is now AutoConfig enabled. Refer to Section 3 on information on
maintaining system configurations.

Section 6: Migrating to AutoConfig on RAC

This section guides you through the steps that need to be performed when your Oracle 11i
instance is running on RAC and you want to enable AutoConfig.
Note: If your 11i instance is running on a non-RAC database and you decide to migrate to
RAC, follow the steps described in Note 279956.1 on Oracle Metalink .

The AutoConfig patch delivers the infrastructure to generate a complete tnsnames.ora file
required for RAC. This includes

• Instance aliases for each AutoConfig enabled database tier node

• Load balance aliases with address lists for each AutoConfig enabled database tier
node
• FNDSM and FNDFS aliases (used by the CP Service Manager) for each AutoConfig
enabled application tier node.
The tnsnames.ora file is dynamically generated using the Net Services Topology Data Model.
The Net Services Topology Data Model stores the entire topological information about a
single Oracle Application instance.

Complete the steps in this section (in the order listed) to migrate to AutoConfig on RAC:

1. Apply TXK AutoConfig Template patch

Update the Oracle Applications file system with the AutoConfig files by applying
patch 5759055 to all application tier nodes in the Applications instance. Apply the
unified driver.
5759055 to all application tier nodes in the Applications instance. Apply the unified
driver.

If you are running on SUSE Linux Enterprise Server 10, apply patch 5949373 to all
application tier nodes in the Applications instance.
5949373 to all application tier nodes in the Applications instance.

2. Review init.ora
AutoConfig will not overwrite your existing init.ora file. However, AutoConfig will
generate a RAC conforming init.ora file when no init.ora file exists. We recommend
creating a backup of the existing init.ora file and let AutoConfig generate a new
init.ora file. This will ensure that the init.ora file conforms to the Oracle's standards
(for example usage of DB_Name as the service name or handling local and remote
listeners).
 3. Migrate to AutoConfig on the Database Tier
Follow the steps in Section 7 to migrate to AutoConfig on the Database Tier. If you
have already migrated to AutoConfig on the Database Tier, then you can omit that
section.
4. Restart the Database listener
Stop and Start your Database listener.
5. Run AutoConfig on the Database tier
Run AutoConfig on the database tier node. Use the adautocfg.sh/.cmd command
described in Section 7, Task 1.
Attention: The database server and the database listener must remain available
during the AutoConfig run. All the other database tier services should be shut down.

6. Migrate to AutoConfig on the Application Tier

Follow the steps in Section 8 to migrate to AutoConfig on the Application Tier. If you
have already migrated to AutoConfig on the Application Tier, then you can omit that
section.
7. Run AutoConfig on the Application tier
Run AutoConfig on each application tier. Use the adautocfg.sh/.cmd command
described in Section 7, Task 2.
Attention: The database server and the database listener must remain available
during the AutoConfig run.

Your system is now AutoConfig enabled. Refer to Section 3 for information on

maintaining system configurations.

Section 7: Migrating to AutoConfig on the Database Tier

Complete the steps in this section (in the order listed) to migrate to AutoConfig on the
Database Tier. If you have already migrated to AutoConfig on the Database Tier omit this
section.
1. Copy AutoConfig to the RDBMS ORACLE_HOME
Update the RDBMS ORACLE_HOME file system with the AutoConfig files by
performing the following steps:
• On the Application Tier (as the APPLMGR user):
• Log in to the APPL_TOP environment (source the environment file)
• Create appsutil.zip file
perl <AD_TOP>/bin/admkappsutil.pl
• This will create appsutil.zip in $APPL_TOP/admin/out .
• On the Database Tier (as the ORACLE user):
• Copy or FTP the appsutil.zip file to the <RDBMS ORACLE_HOME>
• cd <RDBMS ORACLE_HOME>
unzip -o appsutil.zip
2. Generate your Database Context File
If your Applications system was created with the Release 11.5.9 Rapid Install or later,
go to Task 3 in this section.
If your Applications system was created with the Release 11.5.8 Rapid Install or
earlier, execute the following commands to create your Database Context File:

• On UNIX
cd <RDBMS ORACLE_HOME>
 . <CONTEXT_NAME>.env
cd <RDBMS ORACLE_HOME>/appsutil/bin
perl adbldxml.pl tier=db appsuser=<APPSuser> appspasswd=<APPSpwd>
• On Windows
Source the cmd Window using <RDBMS ORACLE_HOME>\<CONTEXT_NAME>.cmd
cd /d <RDBMS ORACLE_HOME>\appsutil\bin
perl adbldxml.pl tier=db appsuser=<APPSuser> appspasswd=<APPSpwd>
Attention: adbldxml uses your current environment settings to generate the
context file. Therefore ensure that your environment is correctly sourced.

Attention: If you build the context file for an 11i instance that runs on RAC, all your
RAC instances have to be up and running while executing the adbldxml utility. The
utility connects to all RAC instances to gather information about the configuration.

3. Prepare for AutoConfig

Complete the following AutoConfig steps.
• Review Prior Manual Configuration Changes
The Database Context File may not include manual post-install configuration
changes made after the Rapid Install completed. Before running the AutoConfig
portion of this patch, review any modifications to specific configuration files and
reconcile them with the Database Context file.
Note: Prior modifications include any changes made to configuration files as
instructed in patch READMEs or other accompanying documents.

Appendix B describes how to review and resolve manual configuration changes.

4. Generate and Apply AutoConfig Configuration files

Attention: This step performs the conversion to AutoConfig. Once completed, the
previous configuration will not be available.

Attention: The database server and the database listener must remain available
during the AutoConfig run. All the other database tier services should be shut down.

Execute the following commands:

• On UNIX
cd <RDBMS ORACLE_HOME>/appsutil/bin
adconfig.sh contextfile=<CONTEXT> appspass=<APPSpwd>
• On Windows
cd /d <RDBMS ORACLE_HOME>\appsutil\bin
adconfig.cmd contextfile=<CONTEXT> appspass=<APPSpwd>
Warning: Running AutoConfig on the database node will update the RDBMS network
listener file. Be sure to review the configuration changes from step 3. The new
AutoConfig network listener file supports the use of IFILE to allow for values to be
customized or added as needed.

Note: Running AutoConfig on the database tier will NOT overwrite any existing
init.ora file. If no init.ora file exists in your instance, AutoConfig will generate an
init.ora file for you.
 Note: Running AutoConfig might change your existing environment files. After
running AutoConfig, you should always set the environment before you run any
Applications utilities in order to apply the changed environment variables.

Section 8: Migrating to AutoConfig on the Application Tier

Complete the steps in this section (in the order listed) to migrate to AutoConfig on the
Application Tier. If you have already migrated to AutoConfig on the Application Tier omit this
section.
1. Find or generate your Oracle Applications Context File
Look for the following file in the APPL_TOP:
<APPL_TOP>/admin/<CONTEXT_NAME>.xml

If this file exists, go to Task 2 in this section.

If this file does not exist, then set your environment and execute the following
command to create your Applications Context File:

• On UNIX
cd <AD_TOP>/bin
perl adbldxml.pl tier=apps appsuser=<APPSuser> appspasswd=<APPSpwd>
• On Windows
cd /d <AD_TOP>\bin
perl adbldxml.pl tier=apps appsuser=<APPSuser> appspasswd=<APPSpwd>
Attention: adbldxml uses your current environment settings to generate the
context file. Therefore ensure that your environment is correctly sourced.

Attention: If you build the context file for an 11i instance that runs on RAC, all your
RAC instances have to be up and running while executing the adbldxml utility. The
utility connects to all RAC instances to gather information about the configuration.

2. Prepare for AutoConfig

• 11i1 UNIX user: Change ownership of the application tier
ORACLE_HOME(s)
In 11.5.1 the application tier ORACLE_HOME(s) were owned by ORACLE, while the
APPL_TOP was owned by APPLMGR. These application tier ORACLE_HOME(s) need
to be owned by APPLMGR. Run the following command to change the owner of
these directories:
• <AD_TOP>/bin/adownmt.sh
• 11i user: Apply OHS patch
Run the following command to find the OHS rollup version:
• On UNIX:
cd <IAS_ORACLE_HOME>/Apache/Apache/bin
httpd -v
• On Windows:
cd <IAS_ORACLE_HOME>\Apache\Apache
apache.exe -V
If you have iAS 1.0.2.2.2, you must patch the Oracle HTTP Sever (OHS)
component. Apply OHS patch 2674529.
You must update the oprocmgr_port value in the Applications Context file with a
free port number. Review the <IAS_HOME>/Apache/Apache/conf/httpd.conf file,
 under the <IfModule mod_oprocmgr.c> section, and use the port already chosen
there. Refer to Section 7 for more information on how to edit your configuration.
• Review Prior Manual Configuration Changes
The Applications Context File may not include manual post-install configuration
changes made after the Rapid Install completed. Before running the AutoConfig
portion of this patch, review any modifications to specific configuration files and
reconcile them with the Applications Context file.
Note: Prior modifications include any changes made to configuration files as
instructed in patch READMEs or other accompanying documents.

Appendix B describes how to review and resolve manual configuration changes.

3. Shut Down Services

Shut down the application tier services that are running on the node where the patch
was applied.
Attention: The database server and the database listener must remain available
during the AutoConfig run. Only the application tier servers should be shut down.

4. Generate and Apply AutoConfig Configuration files

Attention: This step performs the conversion to AutoConfig. Once completed, the
previous configuration will not be available.

Execute the following command:

• On UNIX
<AD_TOP>/bin/adconfig.sh contextfile=<CONTEXT> appspass=<APPSpwd>
• On Windows
<AD_TOP>\bin\adconfig.cmd contextfile=<CONTEXT> appspass=<APPSpwd>
Note: Running AutoConfig might change your existing environment files. After
running AutoConfig, you should always set the environment before you run any
Applications utilities in order to apply the changed environment variables.

Section 9: Known Issues

This section contains known issues with the configuration management of your Oracle
Applications Release 11i environment.

1. Application 11i Login page fails with Internal 500 error

Update the context variable s_directory_index with "index.html" and run AutoConfig
on each application tier node in the Applications instance.
Appendix A: Install JRE 1.3.1 into <RDBMS ORACLE_HOME>
Perform the following steps:

1. Download JRE 1.3.1_15 or higher from Sun Microsystems.

2. Follow the installation instructions.
3. When prompted for the location to install jre, click browse and enter the
location:
<RDBMS ORACLE_HOME>\jre\1.3.1_<version number> where version number is
15 or higher.
4. Accept the default plug-in options.
JRE 1.3.1_<version number> will be installed in <RDBMS ORACLE_HOME>\jre\1.3.1_<version
number>

Appendix B: Review and Resolve Manual Configuration Changes

1. The AutoConfig check utility is located at:
Tier
Command

Application
<AD_TOP>/bin

Database
<RDBMS ORACLE_HOME>/appsutil/bin

Check the AutoConfig configuration files by executing the following command:

• On UNIX
adchkcfg.sh contextfile=<CONTEXT> appspass=<APPSpwd>
• On Windows
adchkcfg.cmd contextfile=<CONTEXT> appspass=<APPSpwd>
This script will generate a graphical html report that provides information about all
files and profile options that will be changed during the next normal execution of
AutoConfig. The report consists of two tabs:

• File System Changes (See a Snapshot)

This report provides information about all files that will be changed during the next
normal execution of AutoConfig. The report is divided into these sections:
• AutoConfig Context File Changes
Here you find information about the location of the context file, the content of
the currently active context file, the content of the context file that will be
generated when you run AutoConfig and a graphical representation of the
differences.
• Changed Configuration Files
Displays a list of all the files that will be changed during an AutoConfig
execution. For every file you find information about the location of the runtime
file, the content of the currently active file, the content of the file that will be
generated when you run AutoConfig, a graphical representation of the
differences and the location of the AutoConfig template file.
• New Configuration Files
Displays a list of all the new files that will be created during an AutoConfig
execution. For every file you find information about the location of the runtime
file, the content of the new file and the location of the AutoConfig template file.
• Database Changes (See a Snapshot)
This report provides information about all the profile options that get changed
during the next normal execution of AutoConfig. For every profile option there is
information about the current value in the database, the changed value and the
AutoConfig script that changes the profile option.
Resolve any reported differences between your existing files and the files AutoConfig
will create.
 The script will also create a zip file report "ADXcfgcheck.zip" that contains all the files
and reports mentioned above, so that you can copy the ADXcfgcheck.zip to a local
desktop PC and view the html report from there without breaking the hyper-links in
the report.

Appendix C: Context Editor

The Applications Context Editor and the Database Context Editor allow you to change
configuration values.
1. Download the Context Editor as patch 2873456. Follow the instructions in
Readme.
2. The Context Editor is located at:
Tier
Directory

Application
<COMMON_TOP>/util/editcontext/

Database
<RDBMS ORACLE_HOME>/appsutil/editcontext/

3. To run the Context Editor:

• On UNIX
editcontext
• On Windows
EditContext.cmd

The Context Editor contains the following three screens:

• The first screen is used to locate your Context File and read it into the editor.
Enter the path to your Context File and click Next.
• The second screen shows the current values in your context and allows you to
edit them. The values displayed on this screen are the main values in the Context
File. Click Detail to display all of the editable values in the Context File. Move the
mouse over the field titles to display a more detailed description of the field.
Change values as needed and click Next.
• The third screen allows you to save the changes to your Context File. To save
your changes, enter the path to your Context File and click Finish. If you do not
want to save the changes, click Cancel.
4. Propagate your configuration changes
After you saved the changes to your context file, refer to Section 7 and run
AutoConfig to propagate your configuration changes to all the configuration files.
Appendix D: Define the PERL5LIB environment variable
On the Application Tier:

• PERL5LIB=<IAS_ORACLE_HOME>/Apache/perl/lib/5.00503:
<IAS_ORACLE_HOME>/Apache/perl/lib/site_perl/5.005:<AU_TOP>/perl

• export PERL5LIB

On the Database Tier:

• PERL5LIB=<ORACLE_HOME>/Apache/perl/lib/5.00503:
<ORACLE_HOME>/Apache/perl/lib/site_perl/5.005:<ORACLE_HOME>/appsutil/perl

• export PERL5LIB