Forms Runtime Diagnostic (FRD) is a runtime event-based logging system intended to aid in the debugging of Forms applications. FRD is enabled at runtime on a user by user basis. When a form is run with FRD enabled, a combination of external user-application interactions and internal Forms processing events are written in chronological order to a log on the file system.
The following steps shows how to create a FRD (Forms Runtime Diagnostic) Log in EBusiness Suite R12 using Forms 10g
1. Make the USER value for profile option 'ICX: Forms Launcher' the same as the SITE value
e.g. copy value of ICX: Forms Launcher for the SITE
"http://testserver.oracle.com:8005/forms/frmservlet"
to be the value for the USER.
2. Append the USER value of ICX: Forms Launcher with the "?record=collect" (without the quotes)
e.g. update the value of ICX: Forms Launcher for the user to be
"http://testserver.oracle.com:8005/forms/frmservlet?record=collect"
3. Save this change at the USER level.
4. Logout and Log back in again, for this profile to take effect. When you login again, a message box pops up, which alerts you that Diagnostics is enabled.
5. Go to Help->About Oracle Applications, go to the section
----------------------------------------
Forms Server Environment Variables
----------------------------------------
There you should see a FORMS_TRACE_DIR. Note the value of this variable.
P.S: If you find that the FORMS_TRACE_DIR is not defined, then ask your sysadmin to bring down the forms server, define this environment variable in the middle tier (form tier) to point to a valid directory, and then bring the forms-sever back up .
6. Reproduce the Forms-Issue, which you are trying to diagnose.
