E-Business Suite Release 12 includes Oracle Application Server 10g components for Forms and Java, each hosted in their own ORACLE_HOMEs.  A couple of colleagues in my team have published a pair of complementary Metalink Notes about debugging, diagnostic, and tracing tools in E-Business Suite Release 12.  It’s high time that I got around to profiling those notes here.

Release 12 Techstack Overview: Overview of three-tier logical architecture for E-Business Suite Release 12, including the database, application server, and desktop tiers. 


Debugging Java Components in Release 12

The first Note highlights a series of Java-related problem scenarios that you might encounter with Release 12:
 This useful document highlights possible symptoms, log files, useful scripts and other tools that can be used to change logging levels to track down issues with:
  • Oracle Process Manager and Notification Server (OPMN)
  • Oracle HTTP Server (Apache)
  • Oracle Containers for J2EE (OC4J)
  • Configured Application Modules, including:
    • OACORE – Core Application Modules
    • OAFM – Oracle Transport Agent, MapViewer
    • FORMS – Forms (using Servlet Mode)
Some common problem scenarios highlighted:
  • OPMN errors at startup
  • HTTP Server fails at startup
  • OC4J Applications Modules (e.g. oacore, forms, oafm) fail at startup
  • HTML requests complete but Java requests fail
  • HTML and Java requests complete but Applications Login page fails
  • Applications Login page is displayed but login fails
It also provides pointers to ways of monitoring or debugging the following components:
  • OPMN
  • Java Object Cache Monitor
  • Applications Server Forms Servlets
  • Class Loaders
The Note wraps up with useful summaries of all of the relevant log files used by OPMN, Oracle HTTP Server (OHS), and the various J2EE Applications modules.

Debugging Forms Components in Release 12

The second Note covers the Forms part of that territory:
This document highlights techniques for using Forms Trace as part of your diagnostic toolkit.  Forms Trace offers detailed data collection and other features to help drill down into Forms runtime problems.  The Note covers:
  • Activating Forms Trace via Application profiles
  • Defining Trace Groups to isolate problems more efficiently
  • Tips on interpreting Trace Files
  • Tips on using the legacy Forms Runtime Diagnostics (FRD) utility
Both of these documents are useful additions to any R12 sysadmin’s toolkit.  If you have feedback or questions about these documents, feel free to post your thoughts here.  If we’re lucky, you might get a chance to interact directly with the Notes’ authors.

Related Articles