IBM E02HMLL-I Implementation Guide - Page 181

Configuring, collaboration-specific, properties

Page 181 highlights

For more information about implicit and explicit transaction bracketing, see the Collaboration Development Guide. Max event capacity As business objects are received by InterChange Server Express they are queued in memory for processing. It is possible for interfaces that have a very high volume of transactions and a low rate of processing to have so many business objects queue up that InterChange Server Express experiences a fatal out-of-memory error. You can mitigate the risk of out-of-memory errors by configuring a maximum event capacity for a collaboration object. To do so, set the Max event capacity field to a value that specifies the maximum number of events you want queued for a collaboration object. The system will not queue more events than the number configured for this property in memory; depending on how you configure the "Blocking type" property of the collaboration object, the system then responds differently to the receipt of new business objects for the collaboration. The valid range of values for this property is from 1 to 2147483647. For more information on the Blocking type property, see "Blocking type." For more information on flow control properties of connector definitions, and on how to use Connector Configurator to modify connector definitions, see Chapter 7, "Configuring connectors," on page 121. For more information on system properties related to flow control, see the System Administration Guide. Blocking type Use the "Blocking type" property in conjunction with the "Max event capacity" property to regulate the flow of business objects to a collaboration. If you enable the Blocking Type checkbox when configuring a collaboration object and the number of events in the collaboration's in-memory queue equals the number specified for its Max event capacity property, then the connector controller responsible for sending business objects to the collaboration will cease to do so. When the number of events in the collaboration's queue is no longer equal to the number specified for its Max event capacity property, then the connector controller will resume sending events to the collaboration. If you leave the Blocking Type checkbox cleared when configuring a collaboration object and the number of events in the collaboration's in-memory queue equals the number specified for its Max event capacity property, then new events submitted to the collaboration by the connector controller are stored persistently in the database. The events are then read from the database into memory as the events currently in the collaboration's queue are processed. For more information on the Max event capacity property, see "Max event capacity." For more information on system properties related to flow control, see the System Administration Guide Configuring collaboration-specific properties Collaboration developers can design collaboration templates so that they have their own individual properties that can then be used to affect the business process logic Chapter 9. Configuring collaboration objects 169

  • 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

For
more
information
about
implicit
and
explicit
transaction
bracketing,
see
the
Collaboration
Development
Guide.
Max
event
capacity
As
business
objects
are
received
by
InterChange
Server
Express
they
are
queued
in
memory
for
processing.
It
is
possible
for
interfaces
that
have
a
very
high
volume
of
transactions
and
a
low
rate
of
processing
to
have
so
many
business
objects
queue
up
that
InterChange
Server
Express
experiences
a
fatal
out-of-memory
error.
You
can
mitigate
the
risk
of
out-of-memory
errors
by
configuring
a
maximum
event
capacity
for
a
collaboration
object.
To
do
so,
set
the
Max
event
capacity
field
to
a
value
that
specifies
the
maximum
number
of
events
you
want
queued
for
a
collaboration
object.
The
system
will
not
queue
more
events
than
the
number
configured
for
this
property
in
memory;
depending
on
how
you
configure
the
“Blocking
type”
property
of
the
collaboration
object,
the
system
then
responds
differently
to
the
receipt
of
new
business
objects
for
the
collaboration.
The
valid
range
of
values
for
this
property
is
from
1
to
2147483647
.
For
more
information
on
the
Blocking
type
property,
see
“Blocking
type.”
For
more
information
on
flow
control
properties
of
connector
definitions,
and
on
how
to
use
Connector
Configurator
to
modify
connector
definitions,
see
Chapter
7,
“Configuring
connectors,”
on
page
121.
For
more
information
on
system
properties
related
to
flow
control,
see
the
System
Administration
Guide
.
Blocking
type
Use
the
“Blocking
type”
property
in
conjunction
with
the
“Max
event
capacity”
property
to
regulate
the
flow
of
business
objects
to
a
collaboration.
If
you
enable
the
Blocking
Type
checkbox
when
configuring
a
collaboration
object
and
the
number
of
events
in
the
collaboration’s
in-memory
queue
equals
the
number
specified
for
its
Max
event
capacity
property,
then
the
connector
controller
responsible
for
sending
business
objects
to
the
collaboration
will
cease
to
do
so.
When
the
number
of
events
in
the
collaboration’s
queue
is
no
longer
equal
to
the
number
specified
for
its
Max
event
capacity
property,
then
the
connector
controller
will
resume
sending
events
to
the
collaboration.
If
you
leave
the
Blocking
Type
checkbox
cleared
when
configuring
a
collaboration
object
and
the
number
of
events
in
the
collaboration’s
in-memory
queue
equals
the
number
specified
for
its
Max
event
capacity
property,
then
new
events
submitted
to
the
collaboration
by
the
connector
controller
are
stored
persistently
in
the
database.
The
events
are
then
read
from
the
database
into
memory
as
the
events
currently
in
the
collaboration’s
queue
are
processed.
For
more
information
on
the
Max
event
capacity
property,
see
“Max
event
capacity.”
For
more
information
on
system
properties
related
to
flow
control,
see
the
System
Administration
Guide
Configuring
collaboration-specific
properties
Collaboration
developers
can
design
collaboration
templates
so
that
they
have
their
own
individual
properties
that
can
then
be
used
to
affect
the
business
process
logic
Chapter
9.
Configuring
collaboration
objects
169