DCOM Recording
Setting Recording Options
6-34
ญญ
ญญ
Include original IORs in iiop_bind commands
Include original IORs in iiop_bind commands
Include original IORs in iiop_bind commands
Include original IORs in iiop_bind commands
Select this check box to make the
ior
argument of every scripted
iiop_bind
emulation command contain the stringified form of the IOR
originally recorded for that object reference. The
ior
argument is required
by the IOR bind modus. Clearing this box shortens scripts, but you must
manually enter the
ior
argument value when using the IOR bind modus.
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. DCOM recording captures distributed, inter-
computer traffic and generates a VB script.
For VB script recording, the VB IDE is used as the script editor.
In the
Session Recording Options
Session Recording Options
Session Recording Options
Session Recording Options
of Robot, DCOM is an available protocol; however,
DCOM refers to any distributed COM calls, such as the older DCOM/MTS
packaging or the newer COM+ packaging.
When you record DCOM scripts, do not use commandID prefix strings with spaces.
Scriptgen may have difficulty interpreting the spaces and cause Robot to hang.
Robot does not support client applications and server components written in the
following languages:
s
Visual Basic for Applications (VBA)
s
Visual Basic 5
s
Visual J++
Robot does not support server components written in C/C++ that cannot be called
by a Visual Basic 6 application.
For Robot session recording of DCOM scripts, use of data types other than OLE
Automation data types is not supported. If the application-under-test uses data types
other than OLE Automation data types, the data types are not reflected in the test
script; therefore, the test script will not contain a complete representation of all calls
from the client to the server. If Robot session recording detects non-OLE
Automation data types, a message appears during script generation to that effect.
The DCOM session recorder works only with DCOM applications that use either
OLE32.dll or OLEAUT32.dll for DCOM communications.
NOTE: If you are recording the DCOM protocol, Visual Basic version 6 must be
installed on your Local computer.
