Rational Robot Tutorial: Assigning a Prefix to IIOP Command IDs

<< TUXEDO Command IDs | DCOM Recording >>

Assigning a Prefix to IIOP Command IDs

Setting Script Generation Options

6-27

Assigning a Prefix to IIOP Command IDs and Including IORs in

IIOP_bind

If you are recording IIOP requests, you can have Robot automatically assign an
identifying prefix to IIOP emulation command IDs. You can also include the
original IORs in

iiop_bind

commands.

To assign an identifying prefix or to include the original IORs in

iiop_bind

commands:
1. Click

Tools

Session Record Options

2. Click the

Generator per protocol

tab.

3. Select

IIOP

at the

Protocol

section, and then select one or more of the following:

Use operation name to prefix emulation command IDs

Select this check box to have Robot automatically prefix the command IDs
with the operation being invoked. This applies to the

iiop_invoke

command. The prefix allows TestManager reports to be filtered by
operation. The prefix that you set here overrides the

Command ID prefix

the

Generator

tab.

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 will shorten scripts, but you will
have to manually enter the

ior

argument value when using the IOR bind

modus.

tux_tpconnect

tcon

tux_tpsubscribe

tsub

tux_tpdequeue

tdeq

tux_tpsuspend

tsus

tux_tpdisconnect

tdis

tux_tpterm

tter

tux_tpenqueue

tenq

tux_tpunsubscribe

tuns

tux_tpgetrply

tget

Command

Prefix

Command

Prefix

tacaR

applies when

tux_tpacall

involves a request only. When

tux_tpacall

involves both a request and the reply (request/reply turnaround), the prefix is

tacaT

. This

is used for asynchronous request timing only and is never assigned to an emulation

command.