AutoConfig is a tool that centralizes and simplifies Oracle Applications configuration management. It works with Oracle Applications Manager to edit the Applications context file, which contains all configuration parameters. AutoConfig then generates configuration files and updates profiles by reading templates and the Applications context. Running AutoConfig propagates changes to both the application and database tiers. Its logs and rollback files allow monitoring runs and restoring previous configurations.
ILT Schedule: Timing Topic 60 minutes Lecture 60 minutes Practice 120 minutes Total
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> - AutoConfig A fresh installation of Oracle E-Business Suite Release 12 includes AutoConfig as a standard (and required) configuration management tool.
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> - AutoConfig Operation AutoConfig template files are used as the starting point for creating site-specific configuration files. AutoConfig evaluates the context variables in a template file, determines the actual values required, and creates a configuration file with these values substituted. This process, described in more detail later in this chapter, is called instantiation. There is one template file for each configuration file. Template files are located in the various <PROD>_TOP/admin/template directories on the application tier, and in the <RDBMS_ORACLE_HOME>/appsutil/template directory on the database tier. AutoConfig driver files are used to list the corresponding template files and locations, and specify the commands to be executed. For example, the commands might update profile options. Driver files are located in each <PROD>_TOP/admin/driver directory on the application tier, and in the <RDBMS_ORACLE_HOME>/appsutil/template directory on the database tier. AutoConfig configuration files, such as httpd.conf, are created as a result of AutoConfig instantiating the corresponding template files. Configuration files contain values corresponding to the settings specified for a particular site. After AutoConfig has been run, numerous configuration files will have been created in various directories.
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> - Running AutoConfig – Application Tier Instructor Note: On Windows, a command is entered as a single line of text, which wraps to the next screen line if needed.
<Course name> <Lesson number> - Running AutoConfig – Database Tier Instructor Note: The \\ (backslash) character on UNIX denotes that the command is continued on the following line. There is no equivalent on Windows.
<Course name> <Lesson number> - AutoConfig Log Files Log file directories are named <MMDDhhmm>, according to the month, day, hour, and minute of the AutoConfig run.
<Course name> <Lesson number> - Rolling Back an AutoConfig Session Each execution of AutoConfig creates a rollback script in case you need to revert to the previous configuration settings.
AutoConfig Created Configuration Files All AutoConfig generated configuration files have the header information seen in this slide. 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 with the updated information.
<Course name> <Lesson number> - AutoConfig - Test Mode The AutoConfig test mode script, adchkcfg.sh (UNIX) or adchkcfg.cmd (Windows), is located in <AD_TOP>/bin on the application tier and in <RDBMS ORACLE_HOME>/appsutil/bin on the database tier. This utility generates a report that highlights differences between existing configuration files and the new ones that AutoConfig will generate. The report is called cfgcheck.html. Running adchkcfg.sh is useful both in carrying out a test run before a planned environment change is made, and when investigating problems.
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> - AutoConfig Configuration Report <MMDDhhmm> represents the month, day, hour, and minute of the AutoConfig test mode script session.
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> - Accessing OAM The AutoConfig feature of Oracle Applications Manager (OAM) is used to update and manage the context files. Log in to Oracle Applications from a suitable account.
<Course name> <Lesson number> - Accessing AutoConfig The OAM Dashboard appears. Click the Site Map tab. OAM displays a list of available links in the site. The AutoConfig link is located under the System Configuration heading of the Administration tab. Click on AutoConfig.
<Course name> <Lesson number> - OAM AutoConfig OAM displays the main AutoConfig page. For each node, the following information is shown: Name – shows the nodename Host – shows the hostname Last Synchronized Date – indicates when the database values and file values were last synchronized. Last Updated Date – indicates when the values in the database was last updated. Tier – shows the tier (database or Applications) for which the context file contains parameters. Synchronized – indicates whether the file and the system have been synchronized Node status – indicates whether the node is online. View – displays the context file Show History – displays history of changes made to the context file Edit Parameters – opens the Edit Parameters page
<Course name> <Lesson number> - OAM AutoConfig Click on the name of the node or the name of the host to filter the list of information. Expand the Details column for your selection by clicking on the plus (+) sign. AutoConfig displays information about the version, creation date, path of the file, and name of the user who last made updates. The Status information corresponds to the Synchronized column value. ‘Write succeeded’ indicates that the synchronization between the OAM database and the context file was successful. Click on Edit Parameters to see the existing configuration parameters grouped by these categories: Global, System, Local, Environments, OA_Ports, OA_Services, and Custom.
<Course name> <Lesson number> - Edit Parameters Page The initial Parameters page displays existing Global parameters. Information shown on all parameters pages includes: variable title, internal name (OA_VAR), change status indicator, value, and a short description. Clicking a category link displays the parameters associated with that category.
<Course name> <Lesson number> - Edit Parameters Page For example, click the System tab to see the parameters associated with Oracle Applications system. You can also search for a specific parameter by entering its title (name), OA_ VAR (internal name), value, or description in the Search field. Choose the appropriate group of parameters and make necessary changes in the Value field. Click Save.
<Course name> <Lesson number> - Confirmation Page AutoConfig displays a confirmation page and provides a space for comments. It also displays the entire contents of the context file, including the changed values. Notice that values are displayed in groups of 25. Click the arrows to move forward and back through the pages. Click OK to save the changes. Oracle Applications Manager automatically stores the new values and updates the context file. After updating the context file, run the AutoConfig script to generate new system configuration files that are propagated with the new values.
<Course name> <Lesson number> - Confirmation Page AutoConfig reminds you to run the AutoConfig script to instantiate new configuration files and update the database profiles.
<Course name> <Lesson number> - Support Cart Many pages throughout OAM have an Add to Support Cart button. The Support Cart feature allows you to save Oracle Applications Manager pages with their data, and then zip them into a file to send to Oracle Support, who can then view your pages in the Oracle Applications Manager display format.
<Course name> <Lesson number> - Support Cart When you click the Add to Support Cart button, the page is added to the Support Cart. If you have filtered or sorted the data, your manipulated view is submitted.
<Course name> <Lesson number> - Support Cart To view the contents of the Support Cart, click on the Support Cart icon from any page. The Support Cart Contents page lists each page placed in the cart and its Application Name. You can filter the list by Page or Application Name. Click the View icon to view a page in a separate window. Click on Save Cart to save the contents to a zip file that you can send to Oracle Support. Any contents of the cart that have not been saved are automatically deleted when you log out of Oracle Applications Manager. To restore a saved cart, click Restore Cart to browse your directory for the saved cart. Select a cart file from the list displayed, or use the Browse button to select a file from the directory. Click Restore.
Restoring a Previous Configuration With OAM AutoConfig, you can view a history of system configuration parameters stored by OAM. You can display the current configuration or previous ones, and request a comparison between the current configuration and a previous one. If necessary, AutoConfig can restore a previous set of configuration parameters, if an update was made in error, or did not suit your business requirements.
<Course name> <Lesson number> - Restoring a Previous Configuration Click Show History in the AutoConfig initial page to access the Context File History page.
<Course name> <Lesson number> - Restoring a Previous Configuration The Context File History page lists other configurations stored in OAM. It shows the version number, last synchronized date, last update date, the user who last updated the configuration, and any comments for each configuration. You can delete a previous configuration from the database by selecting it and clicking the Delete button. To see a contrast between the current configuration and one that you have used in the past, select a previous version from the list and click Show Differences from Current Configuration.
<Course name> <Lesson number> - Comparing Configurations The Show Differences from Current Configuration page lists the parameters that differ in value between the previous configuration and the current one. To restore an individual value, select Restore Previous Value. This action replaces the value in the current configuration. On the next page you can enter comments regarding your change.
<Course name> <Lesson number> -
<Course name> <Lesson number> -
<Course name> <Lesson number> - Refer to Practice - Editing Applications Context [LAB4205Y] Refer to Practice - Modifying your System [LAB4207Y] Refer to Practice - Rolling Back an AutoConfig Session [LAB4208Y] Refer to Practice - Restoring a Previous Configuration [LAB4209Y] Refer to Practice - Running AutoConfig in Test Mode [LAB420AY]