AutoConfig Template Rollup Patch M Now Available

This one's hot off the presses, also.  One of the major products from our team is AutoConfig, which I plan to devote a few future posts to.  For now, those of you who are already using AutoConfig in your E-Business Suite environments will be pleased to hear that the latest AutoConfig Template Rollup Patch has been released.


The TXK (FND) AutoConfig Template Rollup Patch M (Patch 4709948)  for April 2006 has just been released to Metalink.

This patch contains additional content on top of TXK AutoConfig Template Rollup Patch L (Patch 4489303).  This latest patch contains the latest enhancements and fixes to the actual AutoConfig engine, also.

For complete details about the patch's contents, see the README.

For details about AutoConfig, see, "Using AutoConfig to Manage System Configurations with Oracle Applications 11i" (Metalink Note 165195.1).

Related Article:

Comments:

Steven,

Thank you for valuable information. It is really useful for mee to now that new TXK patch is released.
I think AutoConfig is a grate tool, a spatially after you have introduced easy way to customize templates ($MOD_TOP/admin/templates/custom directory).
.
Just few thing that you can comment on or address in your future posts:

In APPL_TOP shared configuration often apps DBA requested to run the AutoConfig on all hosts sharing the same software.
Single AutoConfig run takes 15-20 min in our environment. We have got 4 apps servers. As the result just to change in official way one simple value (in the httpd.conf file for example) We need to take whole environment down for 60-75 min.
First 3 things that come to my mind how it can be speedup:
- Divide all actions in two categories. 1. Common for all servers sharing the same APPL_TOP (things like changes to fnd_profile_option_values, common ZIP files generation etc.) 2. Actions specific for a particular server. It would be possible to run first category actions just ones and second category actions on all others apps servers. Sure that common actions are most time consuming (please correct me if I am wrong)
- Divide actions by different modules (apache, jserv, pl/sql, concurrent managers, forms server, profile values etc.). In the same manner as Oracle AS 10G R2 works (it has got ohs, opnm, oc4j related configuration). Then introduce a parameter which would instruct AutoConfig which actions to execute. In case Apps DBA would like to change just Apache parameter it would be possible to implement the change much quicker then it is possible now.
- Categorize actions in actions which can be executed on started environment (for example changes in a httpd.conf file can be done while Apache is up, Apache processes can be restarted) and actions which can be done only on shut down system. At the moment as far as know we suppose to run AutoConfig on a stopped environment (please correct me if I am wrong).

I would really appreciate your comments,
Thank you in advance,
Yury

Posted by Yury Velikanov on May 07, 2006 at 10:06 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
4
5
6
7
8
9
10
11
12
13
14
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today