R12 d49656 gc10-apps dba 16

Copyright © 2007, Oracle. All rights reserved.

AutoConfig

Copyright © 2007, Oracle. All rights reserved.1 - 2

Objectives

At the end of this module, you should be able to do the following:

• Describe the Applications context

• Describe AutoConfig

• Identify the scripts used by AutoConfig

• Run AutoConfig to configure an Oracle Applications system

• Update Applications context parameters

• Restore Applications context parameters

• Roll back an AutoConfig session

• Run AutoConfig in test mode


Module Overview

This module introduces the AutoConfig utility and the process of configuring the Oracle Applications system

This module consists of the following topics:

• Context Files

• Introduction to AutoConfig

• AutoConfig Features

• AutoConfig Operation

• Running AutoConfig from Oracle Applications Manager

• Using the Support Cart

• Restoring a Previous Configuration

• Comparing Configurations


Context Files

• Rapid Install captures all the configuration parameters associated with your installation in two context files

• Parameters for the application tier – the APPL_TOP and the Applications technology stack – are stored in the Applications context file

• Parameters for the database tier are stored in the database context file


Context Files

• You can edit the existing configuration parameters using Oracle Applications Manager (OAM) AutoConfig

• When you save the new parameters, OAM stores them in the OAM schema and automatically updates (synchronizes) the context files

• You must then run the AutoConfig script to update the system configuration files and database profiles with the new parameters


Benefits of the Context Files

• By describing all the services for a particular APPL_TOP in a single Applications context, services can be started up and shut down easily

• Use of a single Applications context allows services to be added or removed without having to modify the core startup/shutdown mechanism

• There are fewer files for Oracle Development to maintain and support, improving robustness and reliability across Oracle Applications


Applications Context File

The Applications context file:

• Is called <CONTEXT_NAME>.xml

• Is in <INST_TOP>/apps/<CONTEXT_NAME>/appl/admin for each node of the application tier

• Contains configuration information for the application tier of a specific Oracle Applications system

• Is used to configure all the other files necessary to set up and make available a particular Oracle Applications system


Database Context File

The database context file:

• Is called <CONTEXT_NAME>.xml

• Is in <RDBMS_ORACLE_HOME>/appsutil/ for the database tier

• Contains configuration information for the database tier of a particular Oracle Applications system



All Applications specific configuration information is stored in the two context files, instead of in numerous files located in directories distributed across the system

Advantages of this strategy include:

• Avoids the need for repeated configuration information

• The APPL_TOP environment is readily described in a single file

• The database environment is readily described in a single file

• Easier to integrate into the process of cloning new systems, as opposed to editing numerous files



• The XML format is easier to read and use than a variety of formats in individual configuration files

• Configuration information is represented in a platform-independent format

• The context file is able to handle Windows registry information



• Supports shared application tier file system

• Allows you to synchronize multiple nodes


Introduction to AutoConfig

The main AutoConfig script:

• Is a tool that centralizes and simplifies Oracle Applications configuration management

• Removes the need to make manual updates to configuration files, which can be tedious and prone to error if multiple files are involved

• Works in conjunction with OAM to edit and update system configuration

• Works in the same way on all platforms


AutoConfig and the Applications Context

• All the information required for configuring an Oracle Applications instance is collected in a repository, called the context file

• AutoConfig maintains the context file

• Details stored in the context file include hostname, domain name, directory structure, and port numbers used

• The OAM AutoConfig editor is used to make changes to the context file


AutoConfig and the Applications Context

• The AutoConfig script uses information from the context file to generate all Applications configuration files and update database profiles

• By supplying the configuration information in a standard location, AutoConfig simplifies procedures such as:

– Upgrading an Applications technology stack component – Starting and stopping Oracle Applications services


AutoConfig Template Files

• The AutoConfig script uses template files to determine the basic settings that are needed

• There is one template file for each configuration file

• Different versions of the template files exist for UNIX and Windows

• The template files are located in the <PROD_TOP>/admin/template directories

• For example:– <AD_TOP>/admin/template – <FND_TOP>/admin/template


AutoConfig Tasks

AutoConfig instantiation (creation) activities include:

• Instantiation of a configuration file to be used at runtime

• Instantiation of a SQL script that will set profile option values that can be either site or instance-specific

• Instantiation of a shell script or Windows command file that will run the just created SQL script via SQL*Plus, and then execute the shell script

• Instantiation of scripts to start up and shut down services such as Java server processes

Script


AutoConfig Operation

• The main AutoConfig script is adautocfg.sh (UNIX) or adautocfg.cmd (Windows)

• Located in:– <INST_TOP>/admin/scripts

(Application tier)– <RDBMS ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>

(Database tier)

• This script calls another script– <AD_TOP>/bin/adconfig.sh (UNIX)

<AD_TOP>\bin\adconfig.cmd (Windows)adautocfg.sh

adconfig.sh


AutoConfig Operation

• AutoConfig creates configuration files by reading several different types of file from various locations:


Running AutoConfig

• You must run AutoConfig for your system to make any context file updates to your system

• Doing so generates the new configuration files for the associated technology stack

• AutoConfig uses the parameters stored in the context file and system configuration templates to create new process control scripts and update system profiles

Script


Running AutoConfig

1. Log on as the appropriate user and set the environment

2. Stop all server processes

3. Run AutoConfig on the application tier to update configuration and profiles on the application tier

4. Run AutoConfig on the database tier to update configuration and profiles on the database tier

5. Start all server processes


Running AutoConfig - Application Tier

To start AutoConfig on the application tier:

• UNIX:– AutoConfig prompts for the APPS password

• Windows:– AutoConfig does not prompt for the APPS password;

you must supply it on the command line

$ <INST_TOP>/admin/scripts/adautocfg.sh

C:\> <INST_TOP>\admin\scripts\adautocfg.cmd <APPS password>


Running AutoConfig - Database Tier

To Start AutoConfig on the database tier:

• UNIX:– AutoConfig prompts for the APPS password

• Windows:– AutoConfig does not prompt for the APPS password;

you must supply it on the initial command line

$ <RDBMS_ORACLE_HOME>/appsutil/scripts/ \ <CONTEXT_NAME>/adautocfg.sh

C:\> <RDBMS ORACLE_HOME>\appsutil\scripts\ <CONTEXT_NAME>\adautocfg.cmd <APPS password>


AutoConfig Log Files

AutoConfig log files are stored under:• Application tier:

<INST_TOP>/admin/log/<MMDDhhmm>/

• Database tier:<RDBMS ORACLE_HOME>/appsutil/log/<CONTEXT_NAME>/<MMDDhhmm>

There is one log file per AutoConfig session, containing detailed information about every action that AutoConfig performed in that run

Log


Rolling Back an AutoConfig Session

The rollback script and all backup configuration files from each AutoConfig session are stored in: • Application Tier: <INST_TOP>/admin/out/<MMDDhhmm>

• Database Tier:<RDBMS_ORACLE_HOME>/appsutil/out/<CONTEXT_NAME>/<MMDDhhmm>

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


Rolling Back an AutoConfig Session

To roll back the effects of an AutoConfig run, go to the relevant directory and run the appropriate restore script:

UNIX:

Windows:

$ restore.sh

D:\> restore.cmd


Editing AutoConfig-Managed Configuration Files

• All AutoConfig generated configuration files contain the following header information

• You should not manually edit these files

• Use OAM AutoConfig to edit parameters in the Applications Context, then run AutoConfig to regenerate the configuration files


Running AutoConfig In Test Mode

• Running the AutoConfig script to propagate changes overwrites the existing configuration files

• This process may overwrite any customizations you made to the configuration files

• To prevent any unwanted changes, use the test (check) mode to determine the impact of running AutoConfig, without actually making any updates


Running AutoConfig in Test Mode – Application Tier

To run AutoConfig in test mode on the application tier, run one of the following commands:

UNIX:

Windows:

AutoConfig prompts for the location of the Applications context file and the APPS password

$ <AD_TOP>/bin/adchkcfg.sh

C:\> <AD_TOP>\bin\adchkcfg.cmd


Running AutoConfig in Test Mode –Database Tier

To run AutoConfig in test mode on the database tier:

UNIX:

Windows:

AutoConfig prompts for the location of the database context file and the APPS password

$ <RDBMS_ORACLE_HOME>/appsutil/bin/adchkcfg.sh

C:\> <RDBMS_ORACLE_HOME>\appsutil\bin\ adchkcfg.cmd


Running AutoConfig in Test Mode –AutoConfig Configuration Report

• The AutoConfig test mode script produces a configuration report that shows the changes the AutoConfig script would have made

• The configuration report, cfgcheck.html, is written to: – On the application tier:

<INST_TOP>/admin/out/<MMDDhhmm> – On the database tier:

<RDBMS_ORACLE_HOME>/appsutil/log/<CONTEXT_NAME>/<MMDDhhmm>


• AutoConfig test mode script example output (tail):

• An example of cfgcheck.html report contents is shown on the next slides

Running AutoConfig in Test Mode – AutoConfig Configuration Report (cont.)


AutoConfig Configuration Report – Example


AutoConfig Configuration Report – Example (cont.)

• AutoConfig test mode script example:


Running AutoConfig from Oracle Applications Manager






AutoConfig Main Screens


AutoConfig Main Screens


Editing Parameters


Editing Parameters


Confirming Changes


Confirming Changes


Using the Support Cart






Restoring a Previous Configuration

To view configuration history and restore a previous configuration:

1. Access AutoConfig via OAM

2. View configuration history

3. Select the configuration parameters

4. Restore configuration






Comparing Configurations


Module Summary

In this module, you should have learned how to do the following:

• Describe the Applications Context

• Update Applications Context parameters

• Restore Applications Context parameters

• Describe AutoConfig

• Run AutoConfig to configure your Oracle Applications system

• Roll back an AutoConfig session

• Identify the control scripts created by AutoConfig

• Run AutoConfig in test mode


Module Discussion

• Describe the purpose and content of the Applications Context

• What are some benefits of the Applications context?

• Describe the benefits of the Support Cart

• Outline the procedure to update an Applications context parameter

• Describe the primary benefits and usage of AutoConfig

• How are template files used by AutoConfig?

• What is the process of updating the application tier control files?


Module Practice

• Editing Applications context

• Configuring your system

• Rolling back an AutoConfig session

• Restoring a previous configuration

• Running AutoConfig in test mode

Education

R12 d49656 gc10-apps dba 16