Autoconfig as the name says used for automatic configuration/regeneration/reconfiguration for most of/all the configuration files in Oracle Applications. This is one of the AD tools that i will be starting to detail.
Autoconfig can either be started using a shell script in Unix or cmd executable in windows under $COMMON_TOP/admin/script/$CONTEXT_NAME/adautocfg.sh for Unix
This inturn calls a shell script adconfig.sh under $AD_TOP/bin. You can either use adautocfg.sh or adconfig.sh to run autoconfig. Only difference is that you will have to supply the context file(SID_host.xml) if you run adconfig.sh.
APPS password is mandatory for autoconfig, so make sure you have apps password handy before starting autoconfig.
Follwing are the details after adconfig.sh is invoked through adautocfg.sh.
1. Check Perl version
2. Locate Perl and its libraries(For application tier or for database tier -- If application tier then locate perl in APACHE_TOP, for database tier then ORACLE_HOME)
3. Check if context file is passed else prompt for one
4. Execute adperl.pl
Once the perl script is initiated it starts writing the log file under $APPL_TOP/admin//log//adconfig.log
Following are the details once its starts running the perl script.
1. Create the log file
2. Set class path
3. Check if there is a new version of the context file, if yes then process the template and request data for new variables
(New template available under $AD_TOP/admin/template/adxmlctx.tmp)
4. Create a backup copy of the old context file under $APPL_TOP/admin//out//.xml
5. Establish database connectivity using APPS_JDBC_URL
6. Check if there are possible updates available for the context file, if yes then sync the same
Update the local context file, check for adgendbc.sh template, write the context file on the file system.
7. Synchronize product tops, this uses a top file under $APPL_TOP/admin/topfile.txt
Any update on new tops or removal of old tops are written to this file.
8. Start context value management,
This check for all the s_* parameters in the context_file, if there is no value specified and the variable is mandatory then it prompts to enter the value.
9. Run $AD_TOP/bin/adchgatname.pl
This script performs the task of validating the APPL_TOP name in context file. If the APPL_TOP name in context file is found to be invalid, it will replace it with valid name. By valid value for APPL_TOP name
it means:
- APPL_TOP name must be between 1 and 30 characters long
- APPL_TOP name must start with a letter
- APPL_TOP name must contain only alphanumeric and underscore characters
Again, if the APPL_Top name is changed, then this utility will take care of storing the old APPL_TOP name in APPL_TOP/admin/ATName.txt
10. Run $FND_TOP/patch/115/bin/txkSetConfig.pl
Script updates application configuration.
- Configuring OAMJAVASPACE settings
- Configuring JDK settings
- Configuring DISCO settings
- Configuring XMLParser settings
- Configuring MOVEJSPPAGEREPOS settings
11. Run $AD_TOP/bin/adgentns.pl
Generates the entries in to the data model and generatesthe tnsnames.ora
12. Start Configuring templates from all of the product tops
-
Autoconfig can either be started using a shell script in Unix or cmd executable in windows under $COMMON_TOP/admin/script/$CONTEXT_NAME/adautocfg.sh for Unix
This inturn calls a shell script adconfig.sh under $AD_TOP/bin. You can either use adautocfg.sh or adconfig.sh to run autoconfig. Only difference is that you will have to supply the context file(SID_host.xml) if you run adconfig.sh.
APPS password is mandatory for autoconfig, so make sure you have apps password handy before starting autoconfig.
Follwing are the details after adconfig.sh is invoked through adautocfg.sh.
1. Check Perl version
2. Locate Perl and its libraries(For application tier or for database tier -- If application tier then locate perl in APACHE_TOP, for database tier then ORACLE_HOME)
3. Check if context file is passed else prompt for one
4. Execute adperl.pl
Once the perl script is initiated it starts writing the log file under $APPL_TOP/admin/
Following are the details once its starts running the perl script.
1. Create the log file
2. Set class path
3. Check if there is a new version of the context file, if yes then process the template and request data for new variables
(New template available under $AD_TOP/admin/template/adxmlctx.tmp)
4. Create a backup copy of the old context file under $APPL_TOP/admin/
5. Establish database connectivity using APPS_JDBC_URL
6. Check if there are possible updates available for the context file, if yes then sync the same
Update the local context file, check for adgendbc.sh template, write the context file on the file system.
7. Synchronize product tops, this uses a top file under $APPL_TOP/admin/topfile.txt
Any update on new tops or removal of old tops are written to this file.
8. Start context value management,
This check for all the s_* parameters in the context_file, if there is no value specified and the variable is mandatory then it prompts to enter the value.
9. Run $AD_TOP/bin/adchgatname.pl
This script performs the task of validating the APPL_TOP name in context file. If the APPL_TOP name in context file is found to be invalid, it will replace it with valid name. By valid value for APPL_TOP name
it means:
- APPL_TOP name must be between 1 and 30 characters long
- APPL_TOP name must start with a letter
- APPL_TOP name must contain only alphanumeric and underscore characters
Again, if the APPL_Top name is changed, then this utility will take care of storing the old APPL_TOP name in APPL_TOP/admin/ATName.txt
10. Run $FND_TOP/patch/115/bin/txkSetConfig.pl
Script updates application configuration.
- Configuring OAMJAVASPACE settings
- Configuring JDK settings
- Configuring DISCO settings
- Configuring XMLParser settings
- Configuring MOVEJSPPAGEREPOS settings
11. Run $AD_TOP/bin/adgentns.pl
Generates the entries in to the data model and generatesthe tnsnames.ora
12. Start Configuring templates from all of the product tops
-
Comments