In this blog I am going to explain new Autoconfig changes in the Oracle applications version 12.2 release as compared to the earlier EBS (12.1) release. Autoconfig extracts value from context and template files to generate the configuration files and also updates profile options into database.
As we all know Autoconfig is a tool in Oracle apps (11i,R12.x) to Automate Configuration of the Oracle E-Business Suite Database and Application Nodes. Autoconfig extracts value from context and template files to generate the configuration files and also updates profile options into database. This way it is helpful for Apps DBA’s to maintain the application and database configuration. In the latest Oracle Apps Release 12.2, Autoconfig remains the same however has a few restrictions. In this blog I am going to explain new Autoconfig changes in the Oracle applications version 12.2 release as compared to the earlier EBS (12.1) release. The Autoconfig changes in 12.2file system are given below:
Image Source: - https://blogs.oracle.com/stevenChan/entry/glimpses_of_e_business_suite
- Oracle home 10.1.3 (AS) has been replaced with Oracle Fusion middleware.
- OC4J has been replaced with Weblogic Server (WLS).
- In the earlier release (12.1) AutoConfig was used to manage http and OC4j configuration fully. However, in 12.2 Autoconfig is able to manage http server configuration partially - such as session timeout, log file rotation size, and log file rotation time. Each of these deployment plans is delivered in an AutoConfig template, containing a very limited set of context variables.
The following OHS configuration files are not controlled by autoconfig but are controlled by WEB LOGIC SERVER (WLS) console:-
Weblogic has its own Admin console to manage the services as shown below:
Let’s learn how weblogic changes sync with the context file? See below:
Run SyncContext on the Application Tier:
A new mechanism has been introduced to keep the context variables and the OHS configuration parameters (where applicable) in synchronization. This mechanism is called the 'Feedback Loop'. The SyncContext tool is one of the tools used for explicit synchronization of the context variables with the WLS configuration parameters.
This tool can be run on all application tier nodes as follows:
perl <AD_TOP>/bin/adSyncContext.pl contextfile=<CONTEXT_FILE>
We did some configuration changes by using Fusion Middleware Admin console.
These changes require that you be in sync with the context file.
You will need to run the following steps on all application nodes:
- Go to cd $AD_TOP/bin/
- perl <AD_TOP>/bin/adSyncContext.pl contextfile=<CONTEXT_FILE>
This will read the WLS configuration parameter values and synchronize them with the context variables.
- Run The Autoconfig on All App Nodes.
Autoconfig is a very powerful tool in Oracle EBS to maintain configuration. However, in version 12.2 it has some limitations due to the new configuration changes. Apps DBAs should keep the changes in mind while using this in EBS version 12.2, as we cannot do all the configuration related changes in web logic server using Autoconfig. If incase, we have done any changes manually in weblogic server we can sync those changes by using adSyncContext.pl with context file manually. Click below for any questions: