IBM E02HMLL-I Implementation Guide - Page 254

Sending, business, object, requests, synchronously, batch

Page 254 highlights

response business object is typically processed by the integration broker. The default mode for a Client Simulator view is asynchronous. To send a business object asynchronously, do the following: 1. Create the request business object instance, as described in "Creating request business objects" on page 241. 2. Click the down arrow in the right-hand corner of the title bar of the Client Simulator view and select Server > Mode > Asynchronous. Note: The Client Simulator view operates in "Asynchronous" mode by default, so you only have to perform this step if you previously were sending synchronous requests from the view. You do not have to set the mode before sending each request. 3. Do one of the following to send the request: v Click the down arrow in the right-hand corner of the title bar of the Client Simulator view and select Server > Send. v Click the Send BO button in the toolbar of the Client Simulator view. Sending business object requests synchronously When a source client 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. 1. Create the request business object instance, as described in "Creating request business objects" on page 241. 2. Click the down arrow in the right-hand corner of the title bar of the Client Simulator view and select Server > Mode > Synchronous to set the Client Simulator view to synchronous mode. 3. Do one of the following to send the request: v Click the down arrow in the right-hand corner of the title bar of the Client Simulator view and select Server > Send. v Click the Send BO button in the toolbar of the Client Simulator view. 4. When presented with the "Select Collaboration" dialog, 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 business object requests in batch mode In batch mode, the Client Simulator view 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. The Client Simulator view copies the business object as many times as you have specified, incrementing the value of the single attribute you specified for each instance, and then sends each instance. 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. 242 IBM WebSphere Business Integration Server Express and Express Plus: System Implementation Guide

  • 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

response
business
object
is
typically
processed
by
the
integration
broker.
The
default
mode
for
a
Client
Simulator
view
is
asynchronous.
To
send
a
business
object
asynchronously,
do
the
following:
1.
Create
the
request
business
object
instance,
as
described
in
“Creating
request
business
objects”
on
page
241.
2.
Click
the
down
arrow
in
the
right-hand
corner
of
the
title
bar
of
the
Client
Simulator
view
and
select
Server
>
Mode
>
Asynchronous
.
Note:
The
Client
Simulator
view
operates
in
“Asynchronous”
mode
by
default,
so
you
only
have
to
perform
this
step
if
you
previously
were
sending
synchronous
requests
from
the
view.
You
do
not
have
to
set
the
mode
before
sending
each
request.
3.
Do
one
of
the
following
to
send
the
request:
v
Click
the
down
arrow
in
the
right-hand
corner
of
the
title
bar
of
the
Client
Simulator
view
and
select
Server
>
Send
.
v
Click
the
Send
BO
button
in
the
toolbar
of
the
Client
Simulator
view.
Sending
business
object
requests
synchronously
When
a
source
client
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.
1.
Create
the
request
business
object
instance,
as
described
in
“Creating
request
business
objects”
on
page
241.
2.
Click
the
down
arrow
in
the
right-hand
corner
of
the
title
bar
of
the
Client
Simulator
view
and
select
Server
>
Mode
>
Synchronous
to
set
the
Client
Simulator
view
to
synchronous
mode.
3.
Do
one
of
the
following
to
send
the
request:
v
Click
the
down
arrow
in
the
right-hand
corner
of
the
title
bar
of
the
Client
Simulator
view
and
select
Server
>
Send
.
v
Click
the
Send
BO
button
in
the
toolbar
of
the
Client
Simulator
view.
4.
When
presented
with
the
“Select
Collaboration”
dialog,
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
business
object
requests
in
batch
mode
In
batch
mode,
the
Client
Simulator
view
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.
The
Client
Simulator
view
copies
the
business
object
as
many
times
as
you
have
specified,
incrementing
the
value
of
the
single
attribute
you
specified
for
each
instance,
and
then
sends
each
instance.
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.
242
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide