IBM E02HMLL-I Implementation Guide - Page 282

Working, events, Displaying, event

Page 282 highlights

Click the pencil icons associated with the different interface elements to set the desired line color for those elements. At the "Color" dialog, select the color you would like the Test Unit view to use for the background of that component type, then click OK. 5. Click OK. Working with events Events are the flows that trigger the execution of a collaboration object. Collaborations execute business process logic to manage event data, manipulating it and coordinating it among enterprise software resources. You use Collaboration Debugger primarily to pause the processing of an event so that you can inspect its data at significant points in the business logic. Displaying an event When a new flow is delivered for processing to a collaboration object that you are debugging it is assigned a number and is listed beneath the collaboration object in the "Events" view. Figure 87 shows an event that has been received by a collaboration object and is displayed in the "Events" view. Figure 87. An event displayed in the Events view When you display an event, Collaboration Debugger gives focus to the node where processing is paused in the "Collaboration template" editor; black squares appear in each corner of the node, indicating that it is selected, and a flag icon labeled with the event instance is displayed in the upper-left-hand corner of the node. Figure 88 shows a node where processing of the event is paused in the Collaboration template editor. Figure 88. An event displayed in the Collaboration template editor If there are active breakpoints set in the collaboration, the flow suspends processing while it waits for you to perform a debugging operation, and a flag icon is drawn on the node where processing is broken to represent the event as well. You display an event to locate it in the collaboration diagram and to populate the "Variables" view with the current data in the flow. The "Variables" view dynamically updates as you perform debugging operations, so you typically only need to display an event in the following situations: v When the collaboration object first receives the flow for processing 270 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

Click
the
pencil
icons
associated
with
the
different
interface
elements
to
set
the
desired
line
color
for
those
elements.
At
the
“Color”
dialog,
select
the
color
you
would
like
the
Test
Unit
view
to
use
for
the
background
of
that
component
type,
then
click
OK
.
5.
Click
OK
.
Working
with
events
Events
are
the
flows
that
trigger
the
execution
of
a
collaboration
object.
Collaborations
execute
business
process
logic
to
manage
event
data,
manipulating
it
and
coordinating
it
among
enterprise
software
resources.
You
use
Collaboration
Debugger
primarily
to
pause
the
processing
of
an
event
so
that
you
can
inspect
its
data
at
significant
points
in
the
business
logic.
Displaying
an
event
When
a
new
flow
is
delivered
for
processing
to
a
collaboration
object
that
you
are
debugging
it
is
assigned
a
number
and
is
listed
beneath
the
collaboration
object
in
the
“Events”
view.
Figure
87
shows
an
event
that
has
been
received
by
a
collaboration
object
and
is
displayed
in
the
“Events”
view.
When
you
display
an
event,
Collaboration
Debugger
gives
focus
to
the
node
where
processing
is
paused
in
the
“Collaboration
template”
editor;
black
squares
appear
in
each
corner
of
the
node,
indicating
that
it
is
selected,
and
a
flag
icon
labeled
with
the
event
instance
is
displayed
in
the
upper-left-hand
corner
of
the
node.
Figure
88
shows
a
node
where
processing
of
the
event
is
paused
in
the
Collaboration
template
editor.
If
there
are
active
breakpoints
set
in
the
collaboration,
the
flow
suspends
processing
while
it
waits
for
you
to
perform
a
debugging
operation,
and
a
flag
icon
is
drawn
on
the
node
where
processing
is
broken
to
represent
the
event
as
well.
You
display
an
event
to
locate
it
in
the
collaboration
diagram
and
to
populate
the
“Variables”
view
with
the
current
data
in
the
flow.
The
“Variables”
view
dynamically
updates
as
you
perform
debugging
operations,
so
you
typically
only
need
to
display
an
event
in
the
following
situations:
v
When
the
collaboration
object
first
receives
the
flow
for
processing
Figure
87.
An
event
displayed
in
the
Events
view
Figure
88.
An
event
displayed
in
the
Collaboration
template
editor
270
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide