Documente Academic
Documente Profesional
Documente Cultură
上次修订日期:
15-MAY-2007
状态:
PUBLISHED
Attention: Windows users. This document typically uses UNIX syntax when specifying
directories; please substitute the appropriate Windows syntax.
• 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:
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 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.
UNIX
Start Database listener process
addlnctl.sh start <SID>
Run AutoConfig
adautocfg.sh
Windows
Start Database listener process
addlnctl.cmd start <SID>
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.
Platform
Functionality
Command
UNIX
Start Applications processes
adstrtal.sh <APPSuser/APPSpwd>
Run AutoConfig
adautocfg.sh
Windows
Start Applications processes
adstrtal.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).
Application
<APPL_TOP>/admin/<CONTEXT_NAME>/out/<MMDDhhmm>
Database
<RDBMS ORACLE_HOME>/appsutil/out/<CONTEXT_NAME>/<MMDDhhmm>
• 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.
The AutoConfig patch delivers the infrastructure to generate a complete tnsnames.ora file
required for RAC. This includes
Complete the steps in this section (in the order listed) to migrate to AutoConfig on RAC:
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.
• 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.
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.
• 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.
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.
• 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.
Application
<AD_TOP>/bin
Database
<RDBMS ORACLE_HOME>/appsutil/bin
• 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:
Application
<COMMON_TOP>/util/editcontext/
Database
<RDBMS ORACLE_HOME>/appsutil/editcontext/
• PERL5LIB=<IAS_ORACLE_HOME>/Apache/perl/lib/5.00503:
<IAS_ORACLE_HOME>/Apache/perl/lib/site_perl/5.005:<AU_TOP>/perl
• export PERL5LIB
• export PERL5LIB