This document shows how to use Forms Runtime Diagnostics using Profile Option at user level.

1. First verify if Forms using Socket or Servlet.

• Login on to Application Server, and check the cfg file to verify the “serverURL=”And “connectMode=” settings.

• In Servlet Mode:
  serverURL=/forms/lservlet
  connectionMode=servlet
• In Socket Mode:
  serverURL=<blank>
  connectionMode=Socket

2. Enable Forms Runtime Diagnostics (FRD)

FRD can be enabled in one of the following methods:

• Option 1: Obtain FRD Trace Using Profile Options
• Option 2: Obtain FRD Trace Using Appsweb.cfg
• Option 3: Obtain FRD in an ADHOC way

We will be using method “Obtain FRD Trace Using Profile Options” in this example.

To start tracing, please modify Profile Option ‘ICX: Forms Launcher’ at USER level to include the Forms parameters required for FRD logging (Note: This should not set at SITE LEVEL)

2.1: Add the trace value “ ‘?record=collect’  “ to Apps URL for profile option ‘ICX: Forms Launcher’

In Servlet Mode:https://hostname.domain:port/forms/frmservlet?record=collect
in Socket Mode:https://hostname.domain:port/OA_HTML/frmservlet?record=collect

Copy the site level value for profile option ‘ICX: Forms Launcher’ and append values’?record=collect’. Past it at the user level.

Ex. Site Value: http://bpiebsprds.brakepartsinc.com:80/forms/frmservlet
Modified Value: http://bpiebsprds.brakepartsinc.com:80/forms/frmservlet?record=collect

Copy the modified value to the User level and Save.

3. Login into Oracle Applications and launch forms via self-service. Navigate through the steps to capture trace.

Should get below prompt when you login to Form.

4. Obtain the Trace File. It’s in $FORMS_TRACE_DIR, where<pid> is the process identifier.

Ex: $FORMS_TRACE_DIR/collect_6540

<Sample Output file>

Source:R12: Forms Runtime Diagnostics (FRD), Tracing And Logging For Forms In Oracle Applications (Doc ID 438652.1)