IBM E02HMLL-I Implementation Guide - Page 177

Effective, transaction, level, Minimum, System, trace

Page 177 highlights

Effective transaction level The effective transaction level is a range between the highest maximum transaction level of all collaboration objects and the lowest maximum transaction level of all connectors that are bound to the object. You can lower the effective transaction level of a collaboration if you need to bind to a connector that does not support a certain transaction level. To change the effective transaction level, choose the desired value from the Effective transaction level drop-down list and then click OK. Note: You cannot bind objects whose transaction levels are incompatible. If you need to bind such objects to a collaboration, you must adjust the supported transaction levels accordingly. Minimum transaction level The minimum transaction level specifies the lowest transaction level of the collaboration template and any collaboration objects based on it. For instance, if the developer of the collaboration template specified a minimum transaction level of Best Effort for the template, then all objects based on the template must operate at Best Effort or Stringent. As described in the section on "Effective transaction level," all components bound to the collaboration object must support its effective transaction level. The minimum transaction level is, then, a way for the collaboration template developer to dictate the lowest transaction level at which the entire interface in which collaboration objects based on the template will execute. The Minimum transaction level field is read-only when configuring a collaboration object; it can only be changed in the collaboration template. For more information about making changes to collaboration templates, see the Collaboration Development Guide. System trace level You can configure collaboration objects so that information about the execution of the collaboration is reported in the server output. To do so, select the desired value in the System trace level drop-down menu. Table 16 describes the different levels and the types of information reported at each: Table 16. System trace levels System trace level 0 - No Tracing 1 - Collaboration operations 2 - And collaboration events 3 - And state transactions 4 - And incoming/outgoing messages Reported information No information is traced at this level Traces the receipt of business objects from connectors and the starting of scenarios Prints messages for level 1, as well as the start and completion of each scenario, including both forward execution and rollback Prints messages for levels 1 and 2, as well as the execution of each scenario decision block or action node Prints messages for levels 1 through 3, as well as the sending and receipt of each business object by each scenario Chapter 9. Configuring collaboration objects 165

  • 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

Effective
transaction
level
The
effective
transaction
level
is
a
range
between
the
highest
maximum
transaction
level
of
all
collaboration
objects
and
the
lowest
maximum
transaction
level
of
all
connectors
that
are
bound
to
the
object.
You
can
lower
the
effective
transaction
level
of
a
collaboration
if
you
need
to
bind
to
a
connector
that
does
not
support
a
certain
transaction
level.
To
change
the
effective
transaction
level,
choose
the
desired
value
from
the
Effective
transaction
level
drop-down
list
and
then
click
OK
.
Note:
You
cannot
bind
objects
whose
transaction
levels
are
incompatible.
If
you
need
to
bind
such
objects
to
a
collaboration,
you
must
adjust
the
supported
transaction
levels
accordingly.
Minimum
transaction
level
The
minimum
transaction
level
specifies
the
lowest
transaction
level
of
the
collaboration
template
and
any
collaboration
objects
based
on
it.
For
instance,
if
the
developer
of
the
collaboration
template
specified
a
minimum
transaction
level
of
Best
Effort
for
the
template,
then
all
objects
based
on
the
template
must
operate
at
Best
Effort
or
Stringent
.
As
described
in
the
section
on
“Effective
transaction
level,”
all
components
bound
to
the
collaboration
object
must
support
its
effective
transaction
level.
The
minimum
transaction
level
is,
then,
a
way
for
the
collaboration
template
developer
to
dictate
the
lowest
transaction
level
at
which
the
entire
interface
in
which
collaboration
objects
based
on
the
template
will
execute.
The
Minimum
transaction
level
field
is
read-only
when
configuring
a
collaboration
object;
it
can
only
be
changed
in
the
collaboration
template.
For
more
information
about
making
changes
to
collaboration
templates,
see
the
Collaboration
Development
Guide
.
System
trace
level
You
can
configure
collaboration
objects
so
that
information
about
the
execution
of
the
collaboration
is
reported
in
the
server
output.
To
do
so,
select
the
desired
value
in
the
System
trace
level
drop-down
menu.
Table
16
describes
the
different
levels
and
the
types
of
information
reported
at
each:
Table
16.
System
trace
levels
System
trace
level
Reported
information
0
-
No
Tracing
No
information
is
traced
at
this
level
1
-
Collaboration
operations
Traces
the
receipt
of
business
objects
from
connectors
and
the
starting
of
scenarios
2
-
And
collaboration
events
Prints
messages
for
level
1,
as
well
as
the
start
and
completion
of
each
scenario,
including
both
forward
execution
and
rollback
3
-
And
state
transactions
Prints
messages
for
levels
1
and
2,
as
well
as
the
execution
of
each
scenario
decision
block
or
action
node
4
-
And
incoming/outgoing
messages
Prints
messages
for
levels
1
through
3,
as
well
as
the
sending
and
receipt
of
each
business
object
by
each
scenario
Chapter
9.
Configuring
collaboration
objects
165