An application tier file system installed and configured in this way can be used to access two or more database instances. Note: For further details of features, options, and implementation steps, see My Oracle Support Knowledge Document For details of shared application tier file system usage in the context of high availability, see Chapter 9.
Many of the parameters are specified during the install process. Running it creates a command window with the required environment settings for Oracle E-Business Suite. Some Oracle E-Business Suite utilities use your operating system's default temporary directory even if you define the environment settings listed in the previous paragraph. In a Release 12 environment, adovars. AD utility programs perform a variety of database and file management tasks.
These utilities need to know certain configuration information to run successfully. This configuration information is specified when Oracle E-Business Suite is installed, and subsequently stored in the adconfig. Once it has been created, this file is used by other Oracle E-Business Suite utilities.
Note: adconfig. It is distinct from the config. This file sets additional environment variables used by the Application Object Library. This file should not be modified: the default values are applicable for all customers. This file sets variables that let you link third-party software and your own custom-developed applications with Oracle E-Business Suite.
This allows you to compile and link custom Oracle Forms user exits and concurrent programs with Oracle E-Business Suite. Log Files Another advantage of employing the concept of an Instance Home is that log files can be stored centrally for an instance, and therefore managed more easily. The java directory Release 12 introduces some significant changes to the locations in which the various types of Java files are stored.
The util directory The util directory contains the third-party utilities licensed to ship with Oracle E-Business Suite.
The product files and directories for all products. Figure Detail of gl Directory Structure The following table summarizes product subdirectories and the types of files each one may contain. Within this directory are subdirectories for each language installed. Not all products require this directory. These files include: object files. This directory contains the. The files contain the forms messages that are displayed at the bottom of the screen or in popup windows.
Reports for each language are stored in subdirectories of the reports directory. Core Technology Directories The admin, ad, au, and fnd directories are the core technology directories.
The admin directory This directory and its subdirectories contain files and scripts used by the AD utilities during upgrade and maintenance processes. These files and scripts include: The adovars. Figure Shared Application Tier File System As well as reducing disk space needed, there are several other benefits of a shared application tier configuration: Most administration, patching, and maintenance tasks need be performed only once, on a single application tier node Changes made to the shared file system are immediately accessible on all application tier nodes Distributes processing tasks to run in parallel on multiple nodes Distributed AD Reduces overall disk requirements Makes adding additional application tier nodes easier Sharing the Application Tier File System Between Instances Capabilities for sharing the application tier file system were extended further in Release Restrictions on this are: All database instances must be patched to the same level.
Actually I was looking for the same information on internet for Oracle Cloud Applications Consultant and came across your blog. I am impressed by the information that you have on this blog. Thanks once more for all the details. Those guidelines additionally worked to become a good way to recognize that other people online have the identical fervor like mine to grasp a great deal more around this condition.
Same as your blog i found another one Oracle ADF. Actually I was looking for the same information on internet for Oracle ADF and came across your blog. Thanks a million and please keep up the gratifying work.
Post a Comment. By modern oracle dba - January 30, Basic Context file commands:. What is the naming convention for the application tier context file? If the customizations are still required, copy the new version of the AutoConfig template file to the custom template directory, and edit the custom template file with your customizations.
Important: AutoConfig checks that your custom template files are of the same versions as the AutoConfig template files, and will not run if it detects any version mismatch. Identify the name and location of the AutoConfig template file and the custom template file for a given configuration file.
To list all files that you customized in an Oracle E-Business Suite instance, use the appropriate command listed in the table below:. To list all configuration files, their AutoConfig template files and their custom template files, use the appropriate command listed in the table below:.
To identify the configuration file for a given AutoConfig template file, use the appropriate command listed in the table below:.
To identify the AutoConfig template and custom template file for a given configuration file, use the appropriate command listed in the table below:. This section discusses the limitations and restrictions that exist when using AutoConfig customizations. When running AutoConfig on the application tier, it generates tnsnames. To obtain the latest AutoConfig updates on both the applications tier and the database tier, perform the following steps in the order listed.
In Release However, it might not be enabled on the database tier in the following scenarios:. The database tier has been upgraded as part of an Oracle E-Business Suite upgrade from Release 11i to Important: If you run the adbldxml. This section gives an overview of some of the advanced AutoConfig features and utilities. AutoConfig can be run in this parallel mode by executing the following command:.
Important: When running AutoConfig simultaneously on multiple nodes, the -parallel option must be specified when running AutoConfig on each node. If it is not, the execution of AutoConfig processes on individual nodes will not be synchronized, and possibly result in inconsistent filesystem or database. The profile report comprises the following sections:. This section of the report shows the profile information for all product tops processed in the current AutoConfig run.
It shows the following:. Status : Whether or not all the templates from each product top were successfully instantiated and executed. The profile information for individual templates can be seen by drilling down into the product tops listed in the summary section. This section contains the profile information for all product templates instantiated and executed in the current AutoConfig run. Execution Summary : Contains the source and target locations of the template and the execution report of the script.
This summary can be viewed by clicking on the script name link in the detailed report. The Check Config utility adchkcfg is used to review the configuration changes that will take effect on an Oracle E-Business Suite instance during the next AutoConfig run. It identifies the potential changes to both the file system as well as the database. It can be run on both the application tier and the database tier.
This script generates both HTML and text reports. The reports provide information about all file changes, profile option changes and other important database updates that will be done during the next normal execution of AutoConfig. Information is organized under the following two tabs:.
AutoConfig Context File Changes : Displays 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 in the next AutoConfig run. In addition it also displays an HTML report highlighting the differences between the current and the new context file, if any.
Service Group Status : Displays the status of the Service Groups and the corresponding services on the applications tier. This section is present only in the report generated on the applications tier. Changed Configuration Files : Displays a list of all the files that will be changed during an AutoConfig execution. For each file, information is displayed about the location of the runtime file, the content of the currently active file, the content of the file that will be generated in the next AutoConfig run.
In addition, an HTML report highlights the differences between the current and the new configuration file, plus the location of the AutoConfig template file if applicable. New Configuration Files : Displays a list of all the new files that will be created during an AutoConfig execution.
For each file, information is displayed about the location of the runtime file, the content of the new file and the location of the AutoConfig template file. Template Customizations : Displays a list of all customized AutoConfig templates and reports the difference between the original AutoConfig template and the customized template.
Profile Value Changes : Displays details of only those profiles whose value would be changed in the next AutoConfig run. For each such profile, the current value in the Database, the new AutoConfig value that would be set for it, the Profile Level and the name of the AutoConfig script that changes the profile value is displayed. Profile Values : Displays details as in previous section for all Apps Database profiles managed by AutoConfig, irrespective of whether their value would change or not in the next AutoConfig run.
Other Database Updates : Displays details for important database updates non-profile changes that will be performed in the next AutoConfig run.
The table name, column name, current column value in the database, and new AutoConfig value are displayed, along with the name of the updating AutoConfig script and a brief description. The script also creates a zip file report, ADXcfgcheck. The ADXcfgcheck. This command line utility can be used to find out detailed information about context variables and the templates in which they are used.
The utility accepts all or part of a context variable name and generates an HTML or text report containing information about the matched context variables, including description, default vale, and current value. The variable description contains recommended settings, range of allowed values, and links to documents that provide detailed usage information. Additionally, the utility lists the configuration templates where the respective context variables are used.
After the Application tier environment file has been sourced, you can run the Context Variable Information utility as follows:. This section guides you through the steps that need to be performed when your Oracle Release This includes:.
The tnsnames. Review init. However, when no init. It is advisable to create a backup of the existing init. This will ensure that the init. Run AutoConfig on all Database tier nodes : Run AutoConfig on all database tier nodes, following the instructions given earlier.
Use the adautocfg. Your system is now AutoConfig-enabled with Oracle RAC, and the system configuration can be managed as described earlier.
Consequently, only part of the configuration of these applications and managed servers is still managed through AutoConfig. By default, all the existing application tier nodes of the Oracle E-Business Suite instance are allowed unrestricted access to Oracle WebLogic Server ports. In order to allow your administrators access to these consoles, you must specify the hosts that your administrators are using as trusted hosts for accessing the Oracle WebLogic Server Administration ports.
The following guidelines help you secure your environment by configuring trusted hosts and connection filters. Set this context variable to a list of trusted hosts that are allowed to access the consoles using the Oracle WebLogic Server Administration ports. Note: If you cannot list the specific host names or IP addresses for all your trusted hosts, then you can use alternative methods to allow access to the Oracle WebLogic Server Administration ports.
For each host, specify either the fully qualified domain name or the IP address. Use commas to separate the hosts in the list. For example:. After you save this configuration, which allows access only to trusted hosts, you will be able to access the Oracle WebLogic Server Administration Console and Fusion Middleware Control only from client browsers executed from the hosts specified in the preceding steps.
However, changes added this way will be overwritten by the next AutoConfig run. You should allow access to Oracle WebLogic Server only through your known web entry points. In this case the rules use a connection filter class for Oracle E-Business Suite called oracle. The WLS Admin Server port on the application tier in the rule for access to the Oracle WebLogic Server Administration Console will be set to the appropriate port based on whether it is on the run file system or the patch file system.
Before you add a new Oracle E-Business Suite application tier node, you must add a connection filter rule for the new node to the Oracle WebLogic Admin Server for both the run file system and the patch file system. For instructions, see:. Section 5. Caution: If you choose to configure Oracle WebLogic Server network connection filters manually, you may encounter issues when adding nodes or performing a clone with Rapid Clone. The fixes for these issues are provided in the April CPU.
If you have not applied the April CPU, perform the following steps as a workaround:. To set network connection filters at the relevant WebLogic domain, perform the following steps on the run file system when there is no active online patching cycle:. For each admin workstation that needs to access the Oracle WebLogic Server Administration Console for administration purposes, create two rules allowing access, one for the Admin Server port on the application tier for the run file system and one for the Admin Server port on the application tier for the patch file system.
Additionally, suppose that the AdminServer port on the application tier for the run file system is , the AdminServer port on the application tier for the patch file system is , and the IP address of the admin workstation is See Section 5. All configuration changes made to the run file system will be propagated to the patch file system during the prepare phase of the next online patching cycle.
If you have applied the April CPU, then Web services atomic transactions are disabled by default. If you have not applied the April CPU, you can disable Web services atomic transactions manually. To do so, perform the following steps on the run file system as the user that owns the Oracle E-Business Suite product files, usually applmgr. Then choose Go. Then choose Save. Enter a reason for the update, such as Disabling Web services atomic transactions.
Then choose OK. Information from this file is used to generate configuration files used on the database tier when AutoConfig is next run. A number of key configuration and control scripts are employed in an AutoConfig environment.
AutoConfig creates several directories for these scripts and their associated files. In addition to these configuration scripts, several additional AutoConfig scripts are used to help manage the Oracle E-Business Suite system. These are described later in this chapter, under Management Tasks.
As AutoConfig is used for a wide range of system configuration activities, from installation to maintenance, the following discussion of its operations is divided into several sections.
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 supports updates to both the application tier and database tier context files. Executing scripts or configuration tools that must complete before the AutoConfig engine starts, for example when generating the tnsnames. CVM can execute scripts or other tools to manipulate any required file on the file system, and allow the appropriate settings to be propagated as needed to both the file system and database.
For example, it is possible to update values in the context file which will then be propagated to the file system. AutoConfig does not undertake all aspects of configuration management, such as changes at operating system level that may have implications outside the context of Oracle E-Business Suite. In addition, it does not manage technology components that have their own native management tools: typically, these are components that are not specific to Oracle E-Business Suite, such as Oracle WebLogic Server.
Like the core AutoConfig components, CVM utilizes configuration files on both the application and database tiers, as shown in the following tables. As well as the context files and configuration scripts that have already been described, AutoConfig uses several other types of file in its configuration management activities.
These may themselves be divided into different categories. 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.
Templates for Management Scripts - To run all the standard processes required by Oracle E-Business Suite, Rapid Install creates scripts to start and stop each of these required processes. These scripts need configuration information in order to:. 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. AutoConfig configuration files, with a.
0コメント