Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Whenever users experiences an error, request a screen shot of the error and any further error
details that they can report. But in the case of non reproducible, enable the following middle tier
debug settings following these steps:
NOTE - If you have configured a Shared Application Tier File System then
please substitute $IAS_CONFIG_HOME for the $IAS_ORACLE_HOME values below.
1. Shut down iAS 10222 (Apache) using the adapcctl.sh (or adstpall.sh) script
After making a copy of these files, please archive these files into a separate directory, or remove
them completely if not needed. This enables new log files to be created when the applications
server is restarted and will help you to focus on the current problem.
NOTE : In the following section AutoConfig users should modify the < CONTEXT >.xml file as
noted below then run AutoConfig to recreate the configuration files. If you are not using
AutoConfig you can manually update the configuration file directly
Manual update
Modify $IAS_ORACLE_HOME/Apache/Apache/conf/httpd.conf
LogLevel debug
Manual update
Modify $IAS_ORACLE_HOME/Apache/Jserv/etc/jserv.conf
ApJServLogLevel debug
Manual update
Modify $IAS_ORACLE_HOME/Apache/Jserv/etc/jserv.properties
log=true
log.channel=true
log.channel.info=true
log.channel.debug=true
This step is only relevant if you have implemented Forms Listener Servlet as
described in Note 201340.1 "Using Forms Listener Servlet with Oracle Applications 11i"
and the reported problem is to do with the Core Forms
AutoConfig variable
s_oaformslog Change to "true" Default value is "false"
Manual update
Modify $IAS_ORACLE_HOME/Apache/Jserv/etc/forms.properties
log=true
log.channel=true
log.channel.info=true
log.channel.debug=true
7. AutoConfig users should now run AutoConfig to update the configuration files
8. Restart iAS 10222 for these changes to take effect using the adapcctl.sh (or adstrtal.sh) script
10. Review the log files for errors and warning messages relevant to the reported issue
a) Configuration Files
All files located in the $IAS_ORACLE_HOME/Apache/Apache/conf directory**
** ensure you do not include any subdirectories such as ssl.key
All files located in the $IAS_ORACLE_HOME/Apache/Jserv/etc directory
$IAS_ORACLE_HOME/Apache/Apache/bin/java.sh
The following files from the $IAS_ORACLE_HOME/Apache/modplsql/cfg directory
plsql.cfg
wdbsvr.app
$FND_TOP/secure/< SID>_< Hostname>/< SID>.dbc
$IAS_ORACLE_HOME/Apache/Apache/bin/httpd -v
NOTE - For shared APPL_TOP customers this is the actual $IAS_ORACLE_HOME and not
$IAS_CONFIG_HOME.
c) Java Version
With the latest versions of AutoConfig for Unix platforms, the jserv.properties file
"wrapper.bin=" entry will point to a java.sh script (normally
$IAS_ORACLE_HOME/Apache/Apache/bin/java.sh), which was implemented in order to allow
the capture of the stdout and stderr output. Refer to this java.sh file to find the explicit path to the
java binary, which is referred to as JSERVJAVA in the script.
On Windows platform the "wrapper.bin=" will point directly to the java.exe binary.
Run the following command to identify the version of Java being used :-
/java -version
You may be able to use the following script on Unix platforms to automate the above step
sh -c "`awk -F= '$1 ~ /^JSERVJAVA.*$/ {print $2}'
$IAS_ORACLE_HOME/Apache/Apache/bin/java.sh` -version;"