Applies to:
Oracle Applications Technology Stack - Version: 12.0 to 12.0.3
Information in this document applies to any platform.

Purpose
This note is intended to be used as a debugging tool for HTTP, OC4J and OPMN issues in E-Business Suite R12

Important Considerations
The steps in this note are specific to debugging the OACORE application. The steps for OAFM (Oracle Applications Fusion Middleware) and FORMS are not included here. One can adjust the steps to collect data for oafm or forms if required. Please contact the author if you need assistance. This was done to reduce the number of files collected and the impact of logging.

The configuration changes to enable debug are of the highest detail. This has been done to collect as much information as possible. You may wish to reduce logging levels

All changes should be reverted once the information is collected. The performance impact of such changes is not great (approx 2 -5%) but Oracle does not recommend detailed logging be turned on for extended periods, especially in production

Last Review Date
April 5, 2007
Instructions for the Reader
A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.
Troubleshooting Details
- Do the following on ALL middle tiers

- Shutdown the http server, oc4j and opmn services
adapcctl.sh stop adoacorectl.sh stop adformsctl.sh stop adoafmctl.sh stop adopmnctl.sh stop

Backup existing log files in:
$LOG_HOME/ora/10.1.3/Apache
$LOG_HOME/ora/10.1.3/j2ee
$LOG_HOME/ora/10.1.3/opmn

- If the issue is easily reproducible it is safe to delete the log files (unless otherwise required)

Enable HTTP/OC4J/OPMN debug logging

Enable http ODL logging
-----------------------------
Edit httpd.conf file, add the following to the end of file $ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf/httpd.conf

OraLogMode oracle OraLogSeverity TRACE:32 OraLogDir $LOG_HOME/ora/10.1.3/Apache/oracle
Please use the full path to $LOG_HOME e.g.
OraLogDir /u01/inst/apps/JCB_atg/logs/ora/10.1.3/Apache/oracle
Make the following directory which will be where the Apache ODL log files are created
mkdir $LOG_HOME/ora/10.1.3/Apache/oracle

Increase OC4J logging
----------------------------
edit j2ee-logging.xml adjust the following in file:
$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/config/j2ee-logging.xml

edit orion-web.xml adjust the following in file:
$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/application-deployments/oacore/html/orion-web.xml

param-name>debug_mode
true

Increase OPMN Logging
-------------------------------
edit opmn.xml adjust the following in file:
$ORA_CONFIG_HOME/10.1.3/opmn/conf/opmn.xml

- Startup the http server, oc4j and opmn (reverse the startup sequence above)

- Reproduce the issue

- Access the following urls and inform support if the url was successful or unsuccessful:

.:/OA_HTML/ServletPing">http://.:/OA_HTML/ServletPing
.:/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE">http://.:/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE
.:http://.:>
.:/OA_HTML/OAInfo.jsp">http://.:/OA_HTML/OAInfo.jsp
.:/OA_HTML/jsp/fnd/aoljtest.jsp">http://.:/OA_HTML/jsp/fnd/aoljtest.jsp
.:/OA_MEDIA/FNDLOGOL.gif">http://.:/OA_MEDIA/FNDLOGOL.gif
.:/forms/frmservlet">http://.:/forms/frmservlet
:/OA_HTML/fndvald.jsp?username=sysadmin&password=http://:/OA_HTML/fndvald.jsp?username=sysadmin&password=>

- Shutdown the http server, oc4j and opmn

Run these commands to zip up the required log files:

zip -r /tmp/`uname -n`_`date +%m%d%y.%H%M`_iAS_HTTP.zip
$LOG_HOME/ora/10.1.3/Apache/*log* $LOG_HOME/ora/10.1.3/Apache/*lock*
$LOG_HOME/ora/10.1.3/Apache/oracle $INST_TOP/pids/10.1.3/Apache

zip -r /tmp/`uname -n`_`date +%m%d%y.%H%M`_iAS_OC4J.zip $LOG_HOME/ora/10.1.3/j2ee/ $LOG_HOME/appl/rgf/*log*

zip -r /tmp/`uname -n`_`date +%m%d%y.%H%M`_iAS_OPMN.zip $LOG_HOME/appl/admin/log/ $LOG_HOME/ora/10.1.3/opmn/

The commands will create zip files in the /tmp directory named after the server name and date. Please now run the following script to comile the 3 zip files into 1 zip. Upload the resulting zip file to the associated service request.

zip -r /tmp/`uname -n`_`date +%m%d%y.%H%M`_iAS_Debug.zip /tmp/*zip*
Run the following command as the applmgr user to collect the version of JDK (Java) being used by R12 Ebusiness Suite. Upload the results to your Metalink SR

sh -c "`awk -F= '$1 ~ /^JSERVJAVA.*$/ {print $2}' $ADMIN_SCRIPTS_HOME/java.sh` -version;"

Important: Revert the changes and re-start the services

Configuration Files: You may also want to provide configuration file information. If this is the case please see Note 443671.1 R12 - Collecting Configuration Information for HTTP, OC4J and OPMN

If you wish to enable Execution Context ID's in the access_log see Note 427848.1 How to Enable Execution Context ID (ECID) in the R12 access_log

------------------------------------------------------------------------
Key Words: R12 Debug, debug, R12, 12.0, oc4j, opmn, http, ias, 10.1.3, ebusiness suite, R 12