background image
<< DCOM Recording | User Generated >>
<< DCOM Recording | User Generated >>

Assigning a Prefix to DCOM Command IDs

Setting Script Generation Options
6-35
The type libraries for all server components accessed by the client application must
be available on the computer where DCOM session recording is performed. For
server components written in Visual Basic, the type libraries are always embedded in
the respective DLLs, and are thus readily available. For non-Visual Basic server
components, type libraries must be installed and registered on the local computer via
the installation of the COM+ application proxy (.msi file, for server components
hosted Windows 2000 and later) or Microsoft Transaction Server package (.pak, for
server components hosted on Windows NT).
Robot does not support alternative component registration methods for server
components that are not written in Visual Basic.
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 ignores method call activity on these interfaces.
The type library is always embedded within an object module for VB or Java
applications. For C++ applications, it may be a stand-alone .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 is locating and identifying the
presence of the type library. Similarly, if you receive a warning in the Generating
Scripts status window concerning Robot's inability to locate the
typelib
, locate and
deploy 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.