📄 rp_setup.htm
字号:
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>DataLoad V4 Users Guide</title>
<base target="_self">
<link rel="stylesheet" type="text/css" href="comstar.css">
</head>
<body>
<h1>Oracle Forms Record and Play - Setup</h1>
<p>Before Oracle sessions can be recorded or the DataLoad file played back,
Oracle Forms must be setup to use this file. This is achieved by adding the
appropriate parameter to the Oracle Forms command line, which for NCA is
controlled by the URL. Since users will still want to be able to use the system
without using record or playback, multiple command lines are required, each
accessed via a different icon or browser link. At a minimum, in addition to the
normal command line one extra will be required for recording and another for
playback. On an NCA system where multiple users are using the same command line,
which is in the HTML file on the middle tier, you may require multiple files for
recording and multiple files for playing if more than one user wants to use this
functionality at the same time.
<p><font color="#FF0000"><b>Hint</b></font> Oracle Forms can record and play at
the same time. This can be useful for validating what a load has done. For
instance, if you record into a new file while playing back from a DataLoad
produced file, when the load completes you could open the recorded file in
DataLoad to see what the playback did. Doing so means you can leave a forms
playback unattended and still be able to verify what was loaded at a later date.
<p><font color="#FF0000"><b>Hint</b></font> Recording while playing also makes
playback in Forms 6i much more stable! Just by turning recording on various
stability issues are resolved. Comstar recommends that recording is always
turned on while a file is being played back.
<p>The changes in setup required depend upon the version of Oracle Forms you are
using. Follow the appropriate link below for instructions to setup your version
of Forms.
<p>
<div align="center">
<center>
<table border="1" width="100%">
<tr>
<td width="50%" align="center"><a href="#Forms45">Forms 4.5</a></td>
<td width="50%" align="center"><a href="#Forms6">Forms 6.x</a></td>
</tr>
</table>
</center>
</div>
<a name="Forms45">
<h2>Forms 4.5 Setup</h2>
</a>
<p>For Oracle Forms 4.5, the setup required is effectively the same whether the
system is NCA or SmartClient . To enable Forms 4.5 recording the following
parameter must be added to the Forms command line:
<blockquote>
<p><font face="Courier New">record=[PATH FILENAME]</font>
</blockquote>
<p>An example of a possible parameter on Windows NT is
<blockquote>
<p><font face="Courier New">record=c:\dataload\record.fld</font>
</blockquote>
<p>or, on UNIX this may be:
<blockquote>
<p><font face="Courier New">record=/home/dataload/record.fld</font>
</blockquote>
<p>For NCA, a new HTM file must be created for recording and another for
playback. The HTM file should edited and the following line found:
<blockquote>
<p><font face="Courier New"><PARAM name=serverArgs"
value="module=... userid=... fndnam=apps"></font>
</blockquote>
<p>The record parameter should then be added to the end of this line, between
the "fndnam=apps" parameter and the closing double quote. For
instance:
<blockquote>
<p><font face="Courier New"><PARAM name=serverArgs"
value="module=... userid=... fndnam=apps record=c:\temp\record.fld"></font>
</blockquote>
<p>The filename and path after the record parameter can be anything appropriate
to your system. DataLoad uses the file extension ".fld" for forms
playback files (<b>F</b>orm <b>L</b>oad<b>D</b>) so it is a good idea to use
that extension. To get Oracle Forms to replay your forms playback file another
HTM file must be created. To this you add a parameter in the same way as before
but it is called "play", as in the following example:
<blockquote>
<p><font face="Courier New"><PARAM name=serverArgs"
value="module=... userid=... fndnam=apps play=c:\temp\record.fld"></font>
</blockquote>
<p>NCA users will require different URLs to access the different HTM files,
whereas Smart Client users should add these parameters to their end of their
F45RUN32.exe command line(s).
<p> <a name="Forms6">
<h2>Forms 6.x Setup</h2>
</a>
<p>To setup Forms record and playback in Oracle Forms 6.x two files need to be
edited, appsweb.cfg and appsbase.htm, then a parameter is added to the URL used
to access the Applications. This parameter controls recording or playback and
defines where the DataLoad forms load file is located. The steps to setup Forms
6.x forms playback are as follows:
<p>Edit the $OA_HTML/bin/appsweb.cfg file.
<p>By default, Forms 6i does not display the actual forms in the client session,
it only displays the parent window. This is to facilitate server capacity
testing, however for DataLoad playback it is very useful to be able to see what
the load is doing. To enable this the code parameter must be changed. Find the
section called '; 2) Java Client Code Parameters'. This section will contain the
following line:</p>
<blockquote>
<p><font face="Courier New">code=oracle.forms.engine.Main</font></p>
</blockquote>
<p>Rather than using 'Main' we need to use 'MainRT', so the line should be
edited to resemble the following:
<blockquote>
<p><font face="Courier New">code=oracle.forms.engine.MainRT</font></p>
</blockquote>
<p>The playback will now be shown in the client session.
<p>Next, in the section called '6) Special Functionality Parameters' make sure
the record parameter has no value, as below:
<blockquote>
<p><font face="Courier New">record=</font>
</blockquote>
<p>By setting this parameter to have no value forms recording is enabled but not
automatically turned on. A play parameter also needs to be added so that
playback is enabled but not automatically run. Again this should have no value
and will be as follows:
<blockquote>
<p><font face="Courier New">play=</font>
</blockquote>
<p>Whereas the record parameter may already be in the appsweb.cfg file the play
parameter probably won't be, however this is dependant on what Oracle are
shipping.
<p>Next, the HTML file must be edited. The name and location of this file is
defined by the the baseHTML parameter in the appsweb.cfg file, but by default
will be $OA_HTML/US/appsbase.htm. Open this file in your preferred text editor
and find the following lines:
<blockquote>
<p><font face="Courier New">// Special Function Parameters<br>
// ---------------------------<br>
var xrecord =
"%record%"</font>
</blockquote>
<p>Now add a variable for the play parameter immediately below the xrecord
variable. This should be as follows:
<blockquote>
<p><font face="Courier New">var xplay
= "%play%"</font>
</blockquote>
<p>The xplay variable will hold the value of the play parameter used in the URL.
The HTML file now needs to be altered to use this variable. Find the following
line in the HTML file:
<p><font face="Courier New">MAChtml += '<' + 'PARAM name="serverArgs"
value="module=' + xmodule + ' userid='+ xuserid + ' fndnam=' + xfndnam + '
record=' +xrecord;</font>
<p>If the code "<font face="Courier New">+ ' record=' +xrecord</font>"
is included in this line then it should be removed, as shown below:
<p><font face="Courier New">MAChtml += '<' + 'PARAM name="serverArgs"
value="module=' + xmodule + ' userid=' + xuserid + ' fndnam=' + xfndnam ;</font>
<p>This code is removed because the record or play parameters should be added
when one of them has a value. Oracle appear to have shipped some versions of the
HTML code which contain the 'record' parameter included but others do not. If
the parameter is included it should be removed.
<p>Once the record parameter has been removed code needs to be inserted which
will add the record or play parameter to the HTML if either parameter has a
value, i.e. if either xrecord or xplay is not empty. Insert the following code
to achieve this:
<blockquote>
<p><font face="Courier New">if (xrecord != "") {<br>
MAChtml += ' record=' + xrecord;<br>
}</font>
<p><font face="Courier New">if (xplay != "") {<br>
MAChtml += ' play=' + xplay;<br>
}</font>
</blockquote>
<p>Certain HTML files shipped by Oracle already contain the first of these
statements, i.e. the files that do not contain the record parameter in the
MAChtml line will contain the first of these statements. Whatever is shipped,
ensure the two statements shown above are included in the file.
<p>The changes made so far will affect Macintosh users. These changes now need
to be made for Internet Explorer and Netscape users. These sections can be
identified by the use of the variable IEhtml and NShtml, for Internet Explorer
and Netscape respectively, instead of MAChtml.
<p>Finally, a change needs to be made for users who are using their browser's
native Java Runtime and not JInitiator. Locate the following line in the HTML
file:
<p><font face="Courier New"><PARAM name=serverArgs
value="module=%prodTop%/forms/%lang%/%formName% userid=%userid%
record=%record% log=%log% fndnam=%fndnam% %form_params%"></font>
<p>In some versions of the HTML file the line won't contain the text '
record=%record%', in which case it will look like the following:
<p><font face="Courier New"><PARAM name=serverArgs
value="module=%prodTop%/forms/%lang%/%formName% userid=%userid%
log=%log% fndnam=%fndnam% %form_params%"></font>
<p>Whatever is currently included in that line, you need to ensure it contains
both the record and play parameters. Once those parameters have been added the
line will be as follows:
<p><font face="Courier New"><PARAM name=serverArgs
value="module=%prodTop%/forms/%lang%/%formName% userid=%userid%
record=%record% play=%play% log=%log% fndnam=%fndnam% %form_params%"></font>
<p>If all these changes are made then record and playback will work and will be
available for all clients.
<p>To record a forms playback file the record parameter should be added to the
end of your base URL. The base URL will resemble the following:
<blockquote>
<p><a href="http://host.domain.com:8000/dev60cgi/f60cgi">http://host.domain.com:8000/dev60cgi/f60cgi</a>
</blockquote>
<p>To record a file the following should be added to the end of the URL, where
[filename] should be replaced with a real filename:
<blockquote>
<p><font face="Courier New">?record=[filename]</font>
</blockquote>
<p>The following shows an example format of a typical record URL:
<blockquote>
<p><a href="http://host.domain.com:8000/dev60cgi/f60cgi">http://host.domain.com:8000/dev60cgi/f60cgi?record=record_file.fld</a></p>
</blockquote>
<p>To then playback what was previously recorded the following URL would be
used:
<blockquote>
<p><a href="http://host.domain.com:8000/dev60cgi/f60cgi">http://host.domain.com:8000/dev60cgi/f60cgi?play=record_file.fld</a></p>
</blockquote>
<p>The file named in the URL will be located in the directory where the forms
server was started. If the file should be in a different directory then the full
directory path should be included in addition to the file's name.</p>
<p>It can be useful to record a file at the same time as playing. This provides
a record of your load which can be checked later to ensure the load was
successful. Extra parameters, such as record, can be added to the URL if they
are preceded by a '&'. The following URL is an example which would playback
from one file while recording to another:</p>
<blockquote>
<p><a href="http://host.domain.com:8000/dev60cgi/f60cgi?play=suppliers.fld&record=suppliersloaded.fld">http://host.domain.com:8000/dev60cgi/f60cgi?play=suppliers.fld&record=suppliersloaded.fld</a></p>
</blockquote>
<p>Finally, if you wanted to log the playback as well as recording, perhaps in
case there is an intermittent forms error you want to capture, then the
following URL could be used:</p>
<blockquote>
<p><a href="http://host.domain.com:8000/dev60cgi/f60cgi?play=suppliers.fld&record=suppliersloaded.fld&log=suppliers.log">http://host.domain.com:8000/dev60cgi/f60cgi?play=suppliers.fld&record=suppliersloaded.fld&log=suppliers.log</a></p>
<p> </p>
</blockquote>
</body>
</html>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -