IBM E02HMLL-I Implementation Guide - Page 150

ContainerManagedEvents, ControllerStoreAndForwardMode

Page 150 highlights

Setting this property to a value greater than 1 allows a connector for a source application to map multiple event business objects at the same time and deliver them to multiple collaboration instances simultaneously. This speeds delivery of business objects to the integration broker, particularly if the business objects use complex maps. Increasing the arrival rate of business objects to collaborations can improve overall performance in the system. To implement concurrent processing for an entire flow (from a source application to a destination application), you must: v Configure the collaboration to use multiple threads by setting its Maximum number of concurrent events property high enough to use multiple threads. v Ensure that the destination application's application-specific component can process requests concurrently. That is, it must be multi-threaded, or be able to use connector agent parallelism and be configured for multiple processes. Set the Parallel Process Degree configuration property to a value greater than 1. The ConcurrentEventTriggeredFlows property has no effect on connector polling, which is single-threaded and performed serially. ContainerManagedEvents This property allows a JMS-enabled connector with a JMS event store to provide guaranteed event delivery, in which an event is removed from the source queue and placed on the destination queue as a single JMS transaction. This property only appears if the DeliveryTransport property is set to the value JMS. The default value is No value. When ContainerManagedEvents is set to JMS, you must configure the following properties to enable guaranteed event delivery: v PollQuantity = 1 to 500 v SourceQueue = CONNECTORNAME/SOURCEQUEUE You must also configure a data handler with the MimeType, DHClass, and DataHandlerConfigMOName (optional) properties. To set those values, use the Data Handler tab in Connector Configurator Express. The fields for the values under the Data Handler tab will be displayed only if you have set ContainerManagedEvents to JMS. Note: When ContainerManagedEvents is set to JMS, the connector does not call its pollForEvents() method, thereby disabling that method's functionality. ControllerStoreAndForwardMode Sets the behavior of the connector controller after it detects that the destination application-specific component is unavailable. If this property is set to true and the destination application-specific component is unavailable when an event reaches InterChange Server Express, the connector controller blocks the request to the application-specific component. When the application-specific component becomes operational, the controller forwards the request to it. 138 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

Setting
this
property
to
a
value
greater
than
1
allows
a
connector
for
a
source
application
to
map
multiple
event
business
objects
at
the
same
time
and
deliver
them
to
multiple
collaboration
instances
simultaneously.
This
speeds
delivery
of
business
objects
to
the
integration
broker,
particularly
if
the
business
objects
use
complex
maps.
Increasing
the
arrival
rate
of
business
objects
to
collaborations
can
improve
overall
performance
in
the
system.
To
implement
concurrent
processing
for
an
entire
flow
(from
a
source
application
to
a
destination
application),
you
must:
v
Configure
the
collaboration
to
use
multiple
threads
by
setting
its
Maximum
number
of
concurrent
events
property
high
enough
to
use
multiple
threads.
v
Ensure
that
the
destination
application’s
application-specific
component
can
process
requests
concurrently.
That
is,
it
must
be
multi-threaded,
or
be
able
to
use
connector
agent
parallelism
and
be
configured
for
multiple
processes.
Set
the
Parallel
Process
Degree
configuration
property
to
a
value
greater
than
1
.
The
ConcurrentEventTriggeredFlows
property
has
no
effect
on
connector
polling,
which
is
single-threaded
and
performed
serially.
ContainerManagedEvents
This
property
allows
a
JMS-enabled
connector
with
a
JMS
event
store
to
provide
guaranteed
event
delivery,
in
which
an
event
is
removed
from
the
source
queue
and
placed
on
the
destination
queue
as
a
single
JMS
transaction.
This
property
only
appears
if
the
DeliveryTransport
property
is
set
to
the
value
JMS
.
The
default
value
is
No
value
.
When
ContainerManagedEvents
is
set
to
JMS
,
you
must
configure
the
following
properties
to
enable
guaranteed
event
delivery:
v
PollQuantity
=
1
to
500
v
SourceQueue
=
CONNECTORNAME/SOURCEQUEUE
You
must
also
configure
a
data
handler
with
the
MimeType,
DHClass,
and
DataHandlerConfigMOName
(optional)
properties.
To
set
those
values,
use
the
Data
Handler
tab
in
Connector
Configurator
Express.
The
fields
for
the
values
under
the
Data
Handler
tab
will
be
displayed
only
if
you
have
set
ContainerManagedEvents
to
JMS
.
Note:
When
ContainerManagedEvents
is
set
to
JMS
,
the
connector
does
not
call
its
pollForEvents()
method,
thereby
disabling
that
method’s
functionality.
ControllerStoreAndForwardMode
Sets
the
behavior
of
the
connector
controller
after
it
detects
that
the
destination
application-specific
component
is
unavailable.
If
this
property
is
set
to
true
and
the
destination
application-specific
component
is
unavailable
when
an
event
reaches
InterChange
Server
Express,
the
connector
controller
blocks
the
request
to
the
application-specific
component.
When
the
application-specific
component
becomes
operational,
the
controller
forwards
the
request
to
it.
138
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide