Showing posts with label enable. Show all posts
Showing posts with label enable. Show all posts

Friday, July 31, 2009

How to run Forms Runtime Diagnostics (FRD) in 10gR2 Forms.

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. These events
can then be analyzed by both application developers, and Oracle support staff. FRD is not
intended to be used as a performance benchmarking tool or as a mechanism for gauging code
coverage.
FRD generates extensive output useful for analysis and debugging, and it is therefore
recommended FRD be utilized as a logging mechanism only when specific issues are
encountered.

To implement FRD do the following:

In the $ORACLE_HOME/forms/server/default.env (or whatever env file you are using), add the environment variable FORMS_TRACE_DIR specifying a physical directory on the Application Server machine. The FRD log file will be written into the directory specified.

In the formsweb.cfg create a config section something like: [my_frd] otherparams=record=collect log=my_frd.txt form=my_form.fmx

Then call this from a url using the config section.
Example: http://my_machine:my_port/forms/frmservlet?config=my_frd

Thursday, July 30, 2009

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
Another method is to set the "Forms Runtime Parameters" profile option with a value of "record=collect" (without quotes)

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.

If you find that the FORMS_TRACE_DIR is not defined, then ask your system administrator to:
- bring down the Forms server- define the "s_forms_trace_dir" context variable in the middle tier (Forms tier) to point to a valid directory. For this the preferred method is to use Oracle Applications Manager => Site Map link => System Configuration section => AutoConfig => for the Applications tier, click the Edit Parameters => System tab => click the + sign to expand the "oa_forms_server". In this expanded area, look for Title = "Forms runtime file directory location" (OA_VAR = "s_forms_trace_dir"). On this line, you can see the text box where the current value exists (if any).Enter/modify the value as desired here, and save.- run Autoconfig- then bring back up the Forms sever.


6. Reproduce the Forms-Issue, which you are trying to diagnose.

7. Go to the directory specified in the FORMS_TRACE_DIR variable. List the latest files. The FRD Log should be the one with the string "collect" in its name.

Monday, April 6, 2009

How to start the Output Post Processor (OPP)?

To activate the OPP follow these setps

The Profile Option "Concurrent: GSM Enabled" must be set to Y

Then:

1. Login to Apps with sysadmin responsibility
2. Navigate to: Concurrent -> Managers -> Define
3. Query for
Manager = 'Output Post Processor'
or Short Name = FNDCPOPP
4. Check the checkbox "Enable" .
5. Click on 'Work Shifts button
6. see Work Shift of the OPP and
Set
Processes = 1
and
Parameters = oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=5
and
Sleep Second = 30
7. Save
8. Navigate to:_ Concurrent -> Managers -> Administer
9. Make sure the Output Post Processor Status is not 'Deactivate'
Set Status to 'Activate' if necessary.

10. Stop and Start the Concurrent Managers using
adcmctl.sh

Tuesday, December 30, 2008

Creating FRD (Forms Runtime Diagnostic) log in Oracle Applications R12

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.


7. Go to the directory specified in the FORMS_TRACE_DIR variable. List the latest files. The FRD Log should be the one with the string "collect" in its name.