R12, 12.1.1 - How To Enable and Collect Debug for HTTP, OC4J and OPMN on Windows Server
(Doc ID 1197364.1)
Last updated on JANUARY 27, 2017
Applies to:Oracle Applications Technology Stack - Version 12.0 to 12.1.3 [Release 12.0 to 12.1]
Information in this document applies to only Windows platform.
Checked for relevance on 06-Oct-2016
This note is intended to be used as a debugging tool for HTTP, OC4J and OPMN issues in E-Business Suite R12 which are installed on Windows Servers. This note is based on <Note:422419.1> -- R12, 12.1.1 - How To Enable and Collect Debug for HTTP, OC4J and OPMN
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
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document