 |
Home |  |
Using DataLoad | |
Macro Loads | |
Browser Control | |
Forms Playback |  |
Scripting | |
Problems |  |
Please read and apply the relevant section on this page before using forms
playback. This page is regularly updated, please check the web site version for latest changes. Oracle E-Business systems at this software level will only record/play FLD files in a single directory and by default that is the following location:
$ORACLE_HOME/forms60/log
That is the 8.0.6 Oracle Home on the application server. When you record a file it will be created in that location and your playback file must be copied to that directory. It is possible to use an alternative directory for your record and playback files - please click here for more details.
The ICX: Forms launcher profile option will already contain an entry similar to one of the following at Site level on your system:-
http://host.domain:port/dev60cgi/f60cgi (UNIX application servers)
http://host.domain:port/dev60cgi/ifcgi60.exe (Windows application servers, note the difference after the final "/")
If you are setting up recording or playback for a particular user then copy this value from Site level to User level of this profile option. Now edit the profile option to turn on either recording or playback.
To record a Forms Playback file the following should be added to the end of the user's profile option value:
?record=[filename]
where [filename] is replaced with the file name (just the file name, a directory path must not be included) to be used for the recorded file.
For example, to record to 'record.fld' on your UNIX server change the value to be as follows:-
http://host.domain:port/dev60cgi/f60cgi?record=record.fld
The profile option value for a Windows application server would be:
http://host.domain:port/dev60cgi/ifcgi60.exe?record=record.fld
To playback a file add the following to the end of the profile value:
?record=[filename]%20play=[filename]&code=oracle.forms.engine.MainRT
Again, [filename] must be replaced by the file names (just the file names, directory paths must not be included) of the files to record the log to and playback from.
For example, on UNIX (beginning of value removed for clarity):
...f60cgi?record=reclog.fld%20play=play.fld&code=oracle.forms.engine.MainRT
For a Windows application server your entry would look similar to the following (beginning of value removed for clarity):
...ifcgi60.exe?record=reclog.fld%20play=play.fld&code=oracle.forms.engine.MainRT
In both these examples you would playback from play.fld and the playback session would be recorded to reclog.fld.
Hint The order of the parameters in the playback profile value is critical, i.e."record=" must be used and it must appear before "play=". Furthermore, these two parameters must be separated by "%20" and nothing else.
Hint Directory paths must not be included in the record= and play= parameters. In this version of Oracle the files can only be located in one directory ($ORACLE_HOME/forms60/log) and specifying a directory path can stop record and playback from working.
Hint The record= and play= file names in the playback profile option must be different otherwise the playback file is overwritten with the log file when the load starts and the load immediately stops.
Hint In the playback examples above the 'record=' parameter is still used. This is essential for playback to work without having to change some of the server based setup files. However, it also has two other benefits. First, a log of what was loaded will be recorded and that can be validated by opening the recorded file in DataLoad after the load. Second, the Oracle Forms have been found to be more reliable and stable during playback if they record at the same time as playing a session back.