Important Changes in Autoconfig R12.2

With Oracle E-Business Suite Release 12.2, OC4J has been replaced with Oracle WebLogic Server. This has resulted in a reduced role for AutoConfig in the configuration of the Oracle HTTP Server and the oacore, oafm, forms and forms-c4ws services.This article talks about changes in Autoconfig R12.2

Up to and including Oracle E-Business Suite Release 12.1.3, AutoConfig was used to manage the entire Oracle HTTP Server configuration and OC4J instance configuration.
In Oracle E-Business Suite Release 12.2, it manages only a part of the Oracle HTTP Server configuration. It also only partially manages the configuration of the oacore, oafm, forms and forms-c4ws services. The remaining scope of AutoConfig remains the same as prior to Oracle E-Business Suite Release 12.2.

Following are the key configuration changes in Autoconfig R12.2

Configuration Activity Prior to Release 12.2 In In Release 12.2
Oracle E-Business Suite

Database, Concurrent

Processing, Oracle Developer

10g, profile options, and other

Oracle E-Business Suite


Oracle Applications Manager Oracle Applications Manager
Changes to HTTP


All HTTP configuration was

managed via AutoConfig

templates. Configuration

changes were done by editing

the respective context

variables and subsequently

running AutoConfig.

Most HTTP configuration is

managed via native Oracle

WebLogic Server tools, Fusion

Middleware Control, or

manually editing of the

configuration files. Only a

limited set of HTTP

configuration files are

maintained via AutoConfig.


Changes to configuration of

oacore, oafm, forms and

forms-c4ws services.

All configuration settings for

the oacore, oafm, forms and

forms-c4ws services were

managed via AutoConfig

templates. Configuration

changes were accomplished

by editing context variables

and running AutoConfig

Properties for the oacore,

oafm, forms and forms-c4ws

services, including the

classpath and JVM

arguments, need to be

updated through native

WebLogic tools such as

WebLogic Administration

Console. The context variable

values are used only to set the

initial values during managed

server creation.

Managing JVM instances of

the oacore, oafm, forms and

forms-c4ws services.

The number of instances of a

service was controlled via

Oracle Process Manager

(OPMN). This number could

be modified by editing the

nprocs context variable,

running AutoConfig, then

stopping and restarting the


Each JVM instance of a service

corresponds to a managed

server of that service type.

The number of instances

needs to be controlled by

explicitly creating or deleting

managed servers for the

service. More details are given

later in this chapter.


How the httpd configuration is managed in R12.2

In Oracle E-Business Suite Release 12.2, some Oracle HTTP Server configurations and WebLogic configurations are managed via AutoConfig while some are managed natively via Fusion Middleware Control and WebLogic Server Administration Console. 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’. On Applications Tier:
This script is used to explicitly pull the values of the WebLogic Server and Oracle HTTP Server configuration parameters and synchronize the corresponding context variable values accordingly.



Updating AutoConfig-Managed Oracle HTTP Server Configurations

The table below shows the Oracle HTTP Server configuration templates that are managed by AutoConfig in Oracle E-Business Suite Release 12.2. The configurations defined in these files can be customized by customizing the templates.

Template Name Configuration File
ssl_terminator_conf_FMW.tmp ssl_terminator.conf
trusted_conf_FMW.tmp trusted.conf
oracle_apache_conf_FMW.tmp oracle_apache.conf
oracle_apache_ssl_conf_FMW.tmp oracle_apache_ssl.conf
url_fw_conf_FMW.tmp url_fw.conf
url_fw_ws_conf_FMW.tmp url_fw_ws.conf
security2_dmz_conf_FMW.tmp security2_dmz.conf
custom_conf_FMW.tmp custom.conf
webgate_conf_FMW.tmp webgate.conf

Updating Seeded Oracle HTTP Server Configurations

During creation of the Oracle HTTP Server instance, AutoConfig performs the first instantiation of configuration files such as httpd.conf and mod_wl_ohs.conf. After the installation or upgrade to Release 12.2 is complete, seeded Oracle HTTP Server configurations are generally managed via Fusion Middleware Control. In certain specific cases, however, manual editing of the configuration files may be needed: this will be advised separately where required.

When modifying Oracle HTTP Server protocols or port numbers, these values must be updated in both the context file as well as in the configuration files. This is to ensure that the new values are updated in the AutoConfig-managed database profile values as well.

To modify HTTP server protocols or port numbers, perform the following steps on the run file system:

  1. Login to Oracle Fusion Middleware Control Console.
  2. Select Web Tier Target under EBS Domain.
  3. Select Administation > Advanced Configuration.
  4. Edit the relevant file to update the respective HTTP configuration parameter value.
  5. Run the following command on all application tier nodes:

$ perl <AD_TOP>/bin/ contextfile=<CONTEXT_FILE>

Run AutoConfig on all application tier nodes.

How the oacore,forms,oafm configuration are done in R12.2

The weblogic managed server are added deleted as per the below given articles

How to add the manage server in R12.2

How to delete the manage server in R12.2

General Autoconfig information which is same as pre R12.2


How to run Autoconfig in parallel

oracle apps autoconfig templates location and How to customize the template for autoconfig files

What is FND_OAM_CONTEXT_FILES used for? All about it