AUTOCONFIG

INSTALATION   -->check driver file and find the location of templatefiles

SETUP  -->from template file it will check the xml values and update it configuration files

PROFILE   -->update the profiles


###PROCESS OF EXECUTION AUTOCONFIG###

These template directory are under each top as well as under $FND_TOP/admin/template . In order to explain here I am taking example on how Apache (Oracle Web Server) related files are created when you run Autoconfig.

If you go to $FND_TOP/admin/template directory, all template files related to iAS ORACLE HOME like http.conf , jserv.conf, zone.properties .. are stored in this their respective directories under template directory.

So template file to create httpd.conf is stored in $FND_TOP/admin/template
similarly template file for jserv.conf will be in
$FND_TOP/admin/template

In these directories you will see file like httpd.conf or jserv.conf with parameter like
ApJServGroup OACoreGroup 1 1 %s_weboh_oh%/Apache/Jserv/etc/jserv.properties (in jserv.conf under template directory)
or
ServerAdmin applmgr@%s_domainname% ( in httpd.conf under template directory)

Now when Autoconfig executes , its picks up these files & replaces parameters like
%s_weboh_oh% & %s_domainname% from Autoconfig Configuration File i.e. Context file or XML file of format SID_HOSTNAME.xml (Discussed in previous post)

So in my case for vision instance in xml file has these values
s_weboh_oh is /u01/applmgr/VIS11i/ora9/iAS
s_domainname is co.in

that’s how all my configuration files are created on execution of Autoconfig .

$AD_TOP/bin/adconfig.sh -nocustom contextfile=<context file  -->not using customfile

$AD_TOP/bin/adtmplreport.sh contextfile= listcustom  -->list of customizations

before ad f version we used beging and end customizations

now we are using custom directory under template file of each directory

Ebiz Configuration with Autoconfig and Context File.



Application context it can be created by executing the following script

This script will evaluate the environment in order to generate the context file.

$ ./$AD_TOP/bin/adbldxml.sh

Take backup of your current context file if you have any before you execute this script.



You can edit context file.

• Using editcontext

• Using OAM

• Using a standard text editor (vi) [ for experts only ]





If you want to revert back an adconfig.sh you need to execute the $APPL_TOP/admin/$CONTEXT_NAME/out/MMDDhhmm/restore.sh

script and its counterpart on the database server is in $ORACLE_HOME/appsutil/out/$CONTEXT_NAME/MMDDhhmm directory

MM for month, DD for date , hh is hour, and mm is minute of autocongic execution.





Adconfig and Customization :

If you are below AD minipack version F,

then the "# Begin customization" and "# End customization" tags needs to be added to the configuration file.

Customizations can be added by editing the application configuration file with a standard text editor.



e.g. adovars.env

# Begin customizations

NAVE_TOP=/pnavei/applmgr/CUSTOM/xbol/12.0.0

export NAVE_TOP

# End customizations



The adconfig utility, when executed, will keep customizations that are marked with in customization tags.

If customization tags are not used, the customizations will not be there in new file.



If you are on later versions of autoconfig, customizations can be implemented by using custom templates instead of adding tags.

custom templates must be stored in $FND_TOP/admin/template/custom



For E.g

A) Lock file:

1)Open httpd.conf. The first few lines will contain a header file.

That is the name of the template file.



For httpd.conf, the template file is httpd_conf_1013.tmp (R12)

Template files will be available in $FND_TOP/admin/template

2)Go to $FND_TOP/admin/template.

e.g. /pnavei/applmgr/1200/fnd/12.0.0/admin/template/



4)Create a dir called "custom" inside it if it is not present.

e.g. /pnavei/applmgr/1200/fnd/12.0.0/admin/template/custom

4)Copy httpd_conf_1013.tmp into custom dir

5)Edit httpd_conf_1013.tmp inside the custom dir and make changes as follows:



From:

====

LockFile %s_iASconfig_home%/Apache/Apache/logs/httpd.lock



To:

===

LockFile /tmp/%s_dbSid%_httpd.lock



Note:

======

As far as possible we need to use place holders and not hard coded values. If you use hard coded values, it will create problems after refresh.

In the above case %s_dbSid% is a place holder for SID.



Usually when its a value that you need to change its done in context file, and when its a format change its done in template.



You can also migrate any customization tags from the manual configuration files to the custom template, using adcustomizer.sh script