askMLabs

How To Collect And Use Forms Trace (FRD) in Oracle Applications Release 12:

Forms Runtime Diagnostics (FRD) :

It is a method used to capture all the events that occur in a form session. It is a combination of external user-application interactions and internal Forms processing events.

FRD can be activated in 3 ways ......

1. Using profile option


2. Using appsweb.cfg


3. In an ADHOC way

Action steps for "Using Profile Option" :
1) Login to application as sysadmin user
2) Note the profile value for "ICX: Forms Launcher" at site level
3) Change the profile value for "ICX: Forms Launcher" at user level

 http://hostname.domain:port/forms/frmservlet?record=collect+log=frdtrace.log  --> In servlet mode

 http://hostname.domain:port/OA_HTML/frmservlet?record=collect+log=frdtrace.log --> In socket mode

4) Bounce the apache services
5) Login into Oracle Applications and launch forms via self-service
6) Collect the log file from location $FORMS_TRACE_DIR
NOTE : You can also use the profile "Forms Runtime parameters" to pass the run time parameters.

Action steps for "Using appsweb.cfg" :

1) Edit the appsweb.cfg file pointed by environment variable "FORMS_WEB_CONFIG_FILE"

 record=collect

 log=formstrace.log

Edit in  section with heading "ENVIRONMENT SPECIFIC PARAMETERS "
2) Bounce the apache services
3) Login into Oracle Applications and launch forms via self-service
4) Collect the log file from location $FORMS_TRACE_DIR

Action steps for "In an ADHOC way":

1) Access forms using following urls directly and collect the log files in $FORMS_TRACE_DIR

http://hostname.domain:port/forms/frmservlet?record=collect+log=frdtrace.log  --> In servlet mode
http://hostname.domain:port/OA_HTML/frmservlet?record=collect+log=frdtrace.log --> In socket mode

2) Collect the log files from $FORMS_TRACE_DIR

Forms Trace Diagnostics Utility :

Forms Trace allows you to record information about a precisely defined part of forms functionality or a class of user actions. It provides detailed data collection and other features to assist the user in diagnosing and investigating forms runtime problems. Additional to old FRD logging, forms trace promises to have more structured logging with additional event which can be traced.

Action Steps
============
1) Edit the appsweb.cfg file pointed by environment variable "FORMS_WEB_CONFIG_FILE"

 record=collect

 tracegroup=medium

Edit in  section with heading "ENVIRONMENT SPECIFIC PARAMETERS "

2) Bounce the apache services

3) Login into Oracle Applications and launch forms via self-service

4) Collect the trace file from location $FORMS_TRACE_DIR and convert it either to xml or html file

With ADHOC
==========

1) Access forms using following urls directly and collect the log files in $FORMS_TRACE_DIR

 http://hostname.domain:port/forms/frmservlet?record=forms tracegroup=full  --> In servlet mode

 http://hostname.domain:port/OA_HTML/frmservlet?record=forms tracegroup=full --> In socket mode

2) Collect the trace file from location $FORMS_TRACE_DIR and convert it either to xml or html file

Converting the forms trace file to xml or html format  .....

To convert the binary file into XML format:

<JDK_HOME>/bin/java -cp <10.1.2 ORACLE_HOME>/forms/java/frmxlate.jar
oracle.forms.diagnostics.Xlate datafile=$1.trc outputfile=$1.xml outputclass=WriteOut

To convert the binary file into HTML format:

<JDK_HOME>/bin/java -cp <10.1.2 ORACLE_HOME>/forms/java/frmxlate.jar
oracle.forms.diagnostics.Xlate datafile=$1.trc outputfile=$1.html outputclass=WriteOutHTML

Ref : Note 373548.1

Servlet Logging
===============
1) Edit the appsweb.cfg file pointed by environment variable "FORMS_WEB_CONFIG_FILE"

 serverURL=/forms/lservlet/<parameter>

  Where parameter = /session or /sessionperf or /perf or /debug

2) Collect the log file :
$LOG_HOME/ora/10.1.3/j2ee/forms/forms_default_group_1/application.log