DCOM Recording
Setting Recording Options
6-28
DCOM Recording
Robot records DCOM client applications that are constructed with Visual Basic
(compiled executables), Java (compiled executables), or C++, with the restriction
that the C++ interfaces are useable by VB - they must use attributes that conform
to the OLE Automation attribute. No preprocessing of the application is necessary
before recording begins.
For VB script recording, the VB IDE should be used as the script editor.
Type Library Requirement for DCOM Recording
For Robot to get data type information from DCOM components during recording,
the
type library
type library
type library
type library
must be present. If Robot does not locate the type library for a
particular interface, it is unable to understand method signatures (the number of
parameters and their data types), and will ignore method call activity on these
interfaces.
The type library will always be embedded within an object module for VB or Java
applications. For C++ applications, it may be a standalone .tlb file.
After DCOM recording, if script generation completes with a
no scriptable protocol
no scriptable protocol
no scriptable protocol
no scriptable protocol
is found
is found
is found
is found
error, the first troubleshooting method should be locating and identifying
the presence of the type library.
Assigning a Prefix to DCOM Command IDs
If you are recording DCOM requests, you can have Robot automatically assign an
identifying prefix to DCOM emulation command IDs. Emulation command IDs
consist of a prefix and a three-digit numeric suffix. Robot automatically increments
the numeric suffix by a value of 1, which allows each command to be uniquely
identified.
To assign an identifying prefix :
1. Click
Tools
Tools
Tools
Tools
>
Session Record Options
Session Record Options
Session Record Options
Session Record Options
.
2. Click the
Generator per protocol
Generator per protocol
Generator per protocol
Generator per protocol
tab.
3. Select
DCOM
DCOM
DCOM
DCOM
at the
Protocol
Protocol
Protocol
Protocol
section, and then select an event label. The label you
select determines the prefix of the emulation command IDs in your script.
User Generated
User Generated
User Generated
User Generated
. Lets you generate a command ID prefix. After you select
this option, click the
Command ID prefix
Command ID prefix
Command ID prefix
Command ID prefix
in the
Generator
Generator
Generator
Generator
tab, and then enter
the prefix that you want generated. If you do not enter a prefix, the
command ID follows the name of your script. For example, if you do not
enter a prefix and the your script is named Accounting, the command IDs
are
[ACCOUNT~001]
,
[ACCOUNT~002]
, and so forth.
