Everything You Ever Wanted to Know About AutoConfig Variables

Luckily, you were not afraid to ask. AutoConfig supports the automated configuration of  E-Business Suite technology stack components, but tracking down specific AutoConfig variables in their associated configuration files can be a daunting task.  The AutoConfig Search Utility (formally known as the TXK Context Variable Information Utility) scans your AutoConfig infrastructure for a requested string and generates a detailed report about the relevant AutoConfig variables and their usage. The report contains, among other things, the following information about relevant AutoConfig variables:

  1. Description
  2. Current value
  3. Default value
  4. Relevant AutoConfig template files

You can use the utility to search for:

  • A complete context variable name
  • A string that contains the partial context variable name
  • A string that is mentioned in the context variable definition, default value, or templates

For example you can enter either "s_contextfile" or even the word "context."  If you search for just a word the report will include information on all context variables that have the given word in their name or in their definition.

We delivered the first version of the AutoConfig Search Utility in E-Business Suite Release 11i and 12.0.x.  We've enhanced and updated Phase II of the tool in Release 12.1.1.

In the first version, the scope of the AutoConfig Search Utility is limited to AD and FND products. In the latest version included with Release 12.1.1, we've expanded the tool's scope to include ALL product tops.  We've also enhanced the 12.1.1 version to allow you to drill down into all configuration files that include the variable.  The tool generates the report in HTML format on the application and database tier.

Running the AutoConfig Search Utility

Here's an example report generated when running the AutoConfig Search Utility from the Application tier for the search string "java" using the following command:

perl <FND_TOP>/bin/txkrun.pl -script=GenCtxInfRep -keyword=jdbc -outfile= txkContext_Apps.html

The 12.1.1 report looks like this:

Screenshot of sample EBS AutoConfig Search Utility report

Obtaining the AutoConfig Search Utility

You can download the AutoConfig Search Utility via the following patches:

Utility Version Release Patch Number and Description
Phase I 11i 6372396: TXK AUTOCONFIG AND TEMPLATES ROLLUP PATCH S (APRIL/MAY 2008)
Phase I 12.0 7207440:  R12.TXK.A - TXK - 12.0.4 Consolidated Patch 1
Phase II 12.1.1

R12.1.1 Rapid Install or 7303030: 12.1.1 Maintenance Pack

References

Related Articles

Comments:

Hi,

Nice summary for autoconfig search for R12. Is there a way to modify a context variable for R12 without using the OAM interface? I understand that Oracle wants us to use it instead of editing the XML file directly for autoconfig.

Regards,
Ben

Posted by Ben Prusinski on May 25, 2009 at 04:45 AM PDT #

You can edit the XML directly, but shouldn't do it that way as AFAIK, its not really supported anymore.

OAM is the proper way to do it, thats the way we do it now, even if it is a rather labourious process.

The big advantage of OAM though is that you can put comments against updates and keep a history of updates. Its easy enough to pull them out of FND_OAM_CONTEXT_FILES later.

Its a pitty FND_OAM_CONTEXT_CUSTOM doesn't have the same ability to track changes for completness.

Posted by Richard Halford on May 26, 2009 at 02:15 AM PDT #

Hi,

It doesn't work on 11.5.10.2 with ATG RUP6, TXK Rollup S:

$ perl $FND_TOP/bin/txkrun.pl -script=GenCtxInfRep -keyword=jdbc -outfile=txkContext_Apps.html
*******FATAL ERROR*******
PROGRAM : (/gpsesp76/erpapp/appl/fnd/11.5.0/bin/txkrun.pl)
TIME : Wed Jun 3 14:18:12 2009
FUNCTION: [ Level 1 ]
ERRORMSG: -script $FND_TOP/patch/115/bin/txkGenCtxInfRep.pl does not exist
$ ls -ltr $FND_TOP/patch/115/bin/txkGenCtxInfRep.pl
$FND_TOP/patch/115/bin/txkGenCtxInfRep.pl: No such file or directory
$ sqlplus /nolog

SQL*Plus: Release 8.0.6.0.0 - Production on Wed Jun 3 14:18:26 2009

(c) Copyright 1999 Oracle Corporation. All rights reserved.

SQL> conn apps/apps
Connected.
SQL> select bug_number
2 from ad_bugs
3 where bug_number='6372396';

BUG_NUMBER
------------------------------
6372396

SQL>

- Vikram

Posted by Vikram Das on June 03, 2009 at 03:22 AM PDT #

Hi, Vikram,

Can you log a formal Service Request for the issue that you're encountering? I'd like to investigate this more systematically.

Regards,
Steven

Posted by Steven Chan on June 03, 2009 at 04:54 AM PDT #

Vikram,
Command works in 1159. When typing "-script=GenCtxinfRep" below notice that GenCtxinfRep uses 'i' in lower case.

perl txkrun.pl -script=GenCtxinfRep -keyword=jdbc -outfile= txkContext_Apps.html

Posted by Rajai Sukhon on June 09, 2009 at 11:58 PM 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