IBM E02HMLL-I Implementation Guide - Page 207

Request, Sending, request, business, objects, synchronously, Synchronous, Collaboration, batch,

Page 207 highlights

synchronous requests from the connector. Furthermore, you do not have to set the mode before sending each request. 2. Select Request > Send from the menu bar. If the broker specified in the connector definition is InterChange Server Express then the business object request is sent to the server for processing. If the broker specified in the connector definition is one of the supported message brokers or WebSphere Application Server then the business object is placed on the queue specified in the RequestQueue standard property. Sending request business objects synchronously: When a source connector sends a request business object synchronously, it expects to get back a response business object from the integration broker after any destination applications have processed the request. In synchronous mode, Test Connector puts the response business object on the queue specified by the source connector's Synchronous Request Queue property. The default mode for Test Connector is asynchronous. 1. Set Test Connector to synchronous mode by selecting Request > Mode > Synchronous from the menu bar. 2. Select Request > Send from the menu bar. 3. If the broker specified in the connector definition is InterChange Server Express then the "Select Collaboration" dialog is displayed. Select the collaboration to which the business object should be sent from the Collaboration drop-down menu and click OK. The business object request is sent to the configured port of the collaboration object chosen for processing. Sending request business objects in batch mode: In batch mode, Test Connector lets you specify the number of instances of a particular business object you want to send, as well as one attribute in the top-level object -a primary key attribute, for example-that you want set to a unique value for each instance. Test Connector copies the business object as many times as you have specified, incrementing the value of the single attribute you specified, and sends each business object. This option allows you to create a large number of business objects quickly and easily. If the selected attribute is a key field that participates in dynamic cross-referencing as part of an identity relationship, then you must guarantee that the initial value and all those that follow it are unique. Otherwise, the cross-referencing logic will fail, causing the request business objects to fail. To ensure that the values are unique, you can use Relationship Manager or execute SQL statements against the table for the relationship participant as follows. v Determine the highest current value for the participant and set the Initial Value field to an even higher value. The first business object instance in the batch and all those that follow will then be unique. v Delete the existing table entries for the participant, thus guaranteeing that no entries have the same attribute value as any of the batch business objects. To send business objects in batch mode, do the following: 1. Select the name of the business object you would like to send from the BOType drop-down menu. 2. Select Request > Send Batch from the menu bar. Chapter 11. Using Test Connector 195

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302

synchronous
requests
from
the
connector.
Furthermore,
you
do
not
have
to
set
the
mode
before
sending
each
request.
2.
Select
Request
>
Send
from
the
menu
bar.
If
the
broker
specified
in
the
connector
definition
is
InterChange
Server
Express
then
the
business
object
request
is
sent
to
the
server
for
processing.
If
the
broker
specified
in
the
connector
definition
is
one
of
the
supported
message
brokers
or
WebSphere
Application
Server
then
the
business
object
is
placed
on
the
queue
specified
in
the
RequestQueue
standard
property.
Sending
request
business
objects
synchronously:
When
a
source
connector
sends
a
request
business
object
synchronously,
it
expects
to
get
back
a
response
business
object
from
the
integration
broker
after
any
destination
applications
have
processed
the
request.
In
synchronous
mode,
Test
Connector
puts
the
response
business
object
on
the
queue
specified
by
the
source
connector’s
Synchronous
Request
Queue
property.
The
default
mode
for
Test
Connector
is
asynchronous.
1.
Set
Test
Connector
to
synchronous
mode
by
selecting
Request
>
Mode
>
Synchronous
from
the
menu
bar.
2.
Select
Request
>
Send
from
the
menu
bar.
3.
If
the
broker
specified
in
the
connector
definition
is
InterChange
Server
Express
then
the
“Select
Collaboration”
dialog
is
displayed.
Select
the
collaboration
to
which
the
business
object
should
be
sent
from
the
Collaboration
drop-down
menu
and
click
OK
.
The
business
object
request
is
sent
to
the
configured
port
of
the
collaboration
object
chosen
for
processing.
Sending
request
business
objects
in
batch
mode:
In
batch
mode,
Test
Connector
lets
you
specify
the
number
of
instances
of
a
particular
business
object
you
want
to
send,
as
well
as
one
attribute
in
the
top-level
object
—a
primary
key
attribute,
for
example—that
you
want
set
to
a
unique
value
for
each
instance.
Test
Connector
copies
the
business
object
as
many
times
as
you
have
specified,
incrementing
the
value
of
the
single
attribute
you
specified,
and
sends
each
business
object.
This
option
allows
you
to
create
a
large
number
of
business
objects
quickly
and
easily.
If
the
selected
attribute
is
a
key
field
that
participates
in
dynamic
cross-referencing
as
part
of
an
identity
relationship,
then
you
must
guarantee
that
the
initial
value
and
all
those
that
follow
it
are
unique.
Otherwise,
the
cross-referencing
logic
will
fail,
causing
the
request
business
objects
to
fail.
To
ensure
that
the
values
are
unique,
you
can
use
Relationship
Manager
or
execute
SQL
statements
against
the
table
for
the
relationship
participant
as
follows.
v
Determine
the
highest
current
value
for
the
participant
and
set
the
Initial
Value
field
to
an
even
higher
value.
The
first
business
object
instance
in
the
batch
and
all
those
that
follow
will
then
be
unique.
v
Delete
the
existing
table
entries
for
the
participant,
thus
guaranteeing
that
no
entries
have
the
same
attribute
value
as
any
of
the
batch
business
objects.
To
send
business
objects
in
batch
mode,
do
the
following:
1.
Select
the
name
of
the
business
object
you
would
like
to
send
from
the
BOType
drop-down
menu.
2.
Select
Request
>
Send
Batch
from
the
menu
bar.
Chapter
11.
Using
Test
Connector
195