Configure Oracle Forms to record and replay keystrokes and mouse clicks for your Oracle Apps version.
Oracle Forms supports a record and playback feature, available in every version of Oracle Forms. When you run Oracle Forms in record mode, it records every keystroke and mouse click and writes everything to a file you specify. When you want to repeat the recorded activity on another system, run Oracle Forms in playback mode, specifying that file, and the forms will do whatever is specified in it.
For example, if you enter a purchase order in an order entry system while in record mode, and you want to re-enter this purchase order in another system, just play back that file on the other system and the purchase order is loaded into it.
The steps below show how to enable the record and playback feature in Oracle Forms, depending on your Oracle Apps release.
Login as Sysadmin and navigate to Profiles > System, then select the profile ICX:Forms Launcher and the username for whom you want to turn on recording, and click "Find". You'll see this profile setting at Site Level, Responsibility Level, Application Level, and User Level. The Site Level Profile option already contains a value used to launch forms. To turn on recording at the user level, copy this value from the Site Level Profile option to the User Level profile option and append the "record=" option at the end, as shown below.
If Forms Server is running in Unix:
Before Edit:
After Edit:
This will make Forms record all the keystrokes in the file myrecord.fdl in the default location $INST_TOP/logs/ora/[FORMS Version Number]/forms. For example, if the mount point of APPS_TIER is /u02/applmgr, the recorded files will be located at:
In Oracle EBS R12.2.3 / R12.2.4 the files will be located at:
Note: In R12 you have to specify the play=dummy.fdl option, otherwise Oracle Forms will not record any data.
Important Note: Edit the profile setting at Site Level, Application Level, or User Level depending on which level you want to enable recording. We recommend turning on recording at the user level for the user who will be running the load.
It is recommended that you create special user accounts for recording and playback, for example:
SAMRECORD — for recording purpose
SAMPLAY — for playback purpose
Then edit the ICX:Forms Launcher profile option with "record=" at the SAMRECORD user level and "play=" at the SAMPLAY user level, instead of setting the record and playback option at site level.
Oracle Forms can record and playback at the same time. This is good for knowing how much data Oracle Forms has processed while playing the file. Always use different filenames for recording and playback — otherwise Oracle Forms will overwrite the play file and the load will get stuck.
For Record and Playback in Unix
In the above, Oracle will record in the file recplay.fdl and the file it will play is play.fdl.
Go to the $INST_TOP/logs/ora/[FORMS Version Number]/forms directory and open a new file dummy.fdl in any text editor, and write the following line:
For example, if the mount point of APPS_TIER is /u02/applmgr:
Write the following line and save the file:
In Oracle EBS R12.2.3 / R12.2.4 the dummy.fdl should be located here (assuming /u02/applmgr is the mount point):
That's it — now Oracle Forms will record all keystrokes and mouse clicks whenever you log in to a user account for whom you specified the record= option in the profile setting.
A detailed step by step guide for enabling Forms Record and Playback in R12 is also available here.
To enable Forms for recording, you have to make changes to the Forms Configuration file appsweb.cfg, located in the $OA_HTML/bin directory. Make a backup of the file before editing it.
Open the Forms Configuration file (appsweb.cfg) and enter the following code at the end of the file in the Customizations section, as shown below:
If $OA_HTML/bin/appsweb_{$ORACLE_SID}_{$HOSTNAME}.cfg also exists, edit this file too and make the same changes as in appsweb.cfg. It's always better to make a backup before editing.
After making the changes, save the file.
Login as sysadmin and navigate to Profiles > System, then select the profile ICX:Forms Launcher and the username for whom you want to turn on recording, and click OK. You'll see this profile setting at Site Level, Responsibility Level, Application Level, and User Level. The Site Level Profile option already contains a value used to launch forms. To turn on recording at the user level, copy this value from Site Level to User Level and append "record=" at the end, as shown below.
If Forms Server is running in Unix:
Before Edit:
After Edit:
If Forms Server is running in Windows:
Before Edit:
After Edit:
This will make Forms record all keystrokes in the file myrecord.fdl in the default location {$8.0.6_HOME}/forms60/log directory in Unix, and $8.0.6_HOME/forms60/bin in Windows.
If you don't see the recorded file in that location, also check $COMMON_TOP/admin/log/[Context_Name] — Oracle sometimes creates recorded files there.
If you're having problems recording, please check the Frequently Asked Questions section for troubleshooting.
Important Note: Edit the profile setting at Site Level, Application Level, or User Level depending on which level you want to enable recording. We recommend turning on recording at the user level for the user who will be running the load.
We recommend creating special user accounts for recording and playback, for example:
SAMRECORD — for recording purpose
SAMPLAY — for playback purpose
Then edit the ICX:Forms Launcher profile option with "record=" at the SAMRECORD user level and "play=" at the SAMPLAY user level, instead of setting the record and playback option at site level.
Oracle Forms can record and playback at the same time. Always use different filenames for recording and playback — otherwise Oracle Forms will overwrite the play file and the load will get stuck.
For Record and Playback in Unix
For Record and Playback in Windows
In the above, Oracle will record in the file rec.fdl and the file it will play is myplay.fdl.
That's it — now Oracle Forms will record all keystrokes and mouse clicks whenever you log in to a user account for whom you mentioned the record= option in the profile setting.
Edit the ICX:Forms Launcher Profile setting. Login as sysadmin and navigate to Profiles > System, then select the profile ICX:Forms Launcher and the username for whom you want to turn on recording, and click OK.
You'll see this profile setting at Site Level, Responsibility Level, Application Level, and User Level. The Site Level Profile option already contains a value used to launch forms. To turn on recording at the user level, copy this value from Site Level to User Level and append the "record=" option at the end, as shown below.
If Forms Server is running in Unix:
Before Edit:
After Edit:
If Forms Server is running in Windows:
Before Edit:
After Edit:
This will make Forms record all keystrokes in the file myrecord.fdl in the default location {$8.0.6_HOME}/forms60/log directory in Unix, and $8.0.6_HOME/forms60/bin in Windows.
Important Note: Edit the profile setting at Site Level, Application Level, or User Level depending on which level you want to enable recording. We recommend turning on recording at the user level for the user who will be running the load.
We recommend creating special user accounts for recording and playback, for example:
SAMRECORD — for recording purpose
SAMPLAY — for playback purpose
Oracle Forms can record and playback at the same time. Always use different filenames for recording and playback — otherwise Oracle Forms will overwrite the play file and the load will get stuck.
For Record and Playback in Unix
For Record and Playback in Windows
In the above, Oracle will record in the file rec.fdl and the file it will play is myplay.fdl.
That's it — now Oracle Forms will record all keystrokes and mouse clicks whenever you log in to a user account for whom you mentioned the record= option in the profile setting.
Note: If you can directly open forms without going through sign-on pages, you can type the record and play file in the address itself, for example:
In Unix:
In Windows:
From Oracle Apps Ver. 11.5.10, by default you cannot directly open forms without going through sign-on pages. Oracle has done this for added security. If you want to open forms directly, follow these steps:
$APPL_TOP/admin/<SID>_<hostname>.xmls_appserverid_authentication from SECURE to OFF