Autoconfig template

This can allow access to things like usernames and other system information. For example, including. Other preferences that lock buttons include:. The AutoConfig file can be managed centrally. To do so, the location of a secondary AutoConfig file in the primary AutoConfig file:.

The URL can be any protocol supported by Firefox, including the file: protocol to point to a file on a networked drive. The format of the remote AutoConfig file is the same as the AutoConfig file on the client, except that the first line is not ignored.

There are other preferences that control aspects of AutoConfig. The autoadmin. There are also preferences related to how offline mode is handled, including autoadmin. If the preference autoadmin. If the preference is set to true , it simply uses the cached file and continues. The top level of the report displays a summarized view that lists all the product tops, along with the total instantiation and execution time of the templates within each product top.

You can drill down into the report to view additional details, including the source and target location of each template, the time taken to instantiate and execute individual template scripts, and the execution report for each template script. In addition to the above utilities, AutoConfig's service management infrastructure has been enhanced with dependency information between service groups and services.

This dependency information is stored as metadata in the context file. The following XML attributes were added in Release For example, Forms Socket mode and Forms Servlet mode are mutually incompatible. Note: During the instantiation phase, locking is done at script level. Note: When using parallel mode, AutoConfig must be invoked with the —parallel option on all nodes of the relevant tier.

Using an Applications context has a number of advantages: Simplifies overall management of an Oracle E-Business Suite system Allows easier startup and shutdown of applications services Permits services to be installed or deinstalled independently of others Integrates seamlessly with a shared application tier file system see Chapter 9 Enables use of Oracle Applications Manager for configuration management see Chapter 7 Facilitates support for Oracle Real Application Clusters see Chapter 4 Before AutoConfig and the Applications context were introduced, configuration management tasks could be time-consuming and prone to error, in some cases requiring manual changes to be made to several configuration files.

Information stored includes: Name and location of the database Port numbers for Forms and Web services Product-specific port numbers Information about application tier services controlled by AutoConfig The values of the context variables that make up the context file are in part determined by the choices you make when you run Rapid Install. AutoConfig Scripts and Directories A number of key configuration and control scripts are employed in an AutoConfig environment. AutoConfig Directories Several directories are created by AutoConfig, as shown in the following table.

Context Value Management Context Value Management CVM is an AutoConfig component that is used to manage the values of variables in the context file, and automate required updates to it.

CVM actions include: Adding new variables to a context file Updating values of variables in an existing context file Applying new versions of context file templates Executing scripts or configuration tools that must complete before the AutoConfig engine starts, for example when generating the tnsnames. Template Files AutoConfig template files are used as the starting point for creating site-specific configuration files. These scripts need configuration information in order to: Create the correct environments for each process Start the processes with the correct parameters Point the processes at the correct database instance if applicable Driver Files AutoConfig driver files are used to list the corresponding template files and locations, and specify the commands to be executed.

Configuration Files AutoConfig configuration files, such as httpd. Figure illustrates the relationship between the different types of file AutoConfig uses. Figure Relationship Between AutoConfig Files Instantiation As mentioned earlier, instantiation is the process whereby AutoConfig creates a configuration file with contents tailored for a specific environment. Execution of Scripts As well as its instantiation activities, AutoConfig may execute other scripts, depending on the requirements of the specific Oracle E-Business Suite system.

Phases of Operation As AutoConfig parses the driver files, it carries out a series of actions, grouped into several distinct phases: INSTE8 - Instantiates AutoConfig template files to the AutoConfig configuration files specified in the relevant template driver files. Management Tasks There are several areas in which an administrator can use AutoConfig to update, control, and monitor an Oracle E-Business Suite system. Managing the Context Oracle Applications Manager see Chapter 7 enables you to edit the Applications context as required.

Build Context Utility The adblxml utility, introduced in Release Checking the System Several other scripts facilitate system management in an AutoConfig-managed environment such as Release Configuration Check Utility adchkcfg. Maybe other readers might have an answer!! This post might come a bit late and may have been placed somewhere else by now. Edit the template file in your custom directory and run autoconfig. You can also seen metalinnk note: Ashok Use adtmplreport.

Share Tweet Share. Autoconfig in Apps template files Contd…. Anonymous says October 9, Hi Atul, What is the difference between template files eg, httpd. Arunkumar says October 9, Hi Atul, Not sure how i commented as anonymous in my previous comment. JVM Out of memory issue. Page access tracking. Printer Argument. Printer OS requirement. Printer removal. Printer Setup.

Cache clear in R ORA Parameters for R OC4J instead of Jserv. Shared App file system. Oracle Application Server. SSO Server. Database Level. Listener Level. Tracing a running report. Session Level. User level.

Add disk to diskgroup. ASM new things in 11g. Data Domain. Hot backup. RMAN Backup. Incremental Backup. RMAN Crosscheck commands. RMAN convert database. RMAN convert datafile. RMAN convert tablespace. RMAN Format. RMAN recovery. RMAN Scripts. RMAN setup. Case sensitive password - 11g. Gather Statistics.

Hardware Load Balancing. Software Load Balancing. Materialized View Log. Materialized view refresh. Monitor materialized views.