IBM E02HMLL-I Implementation Guide - Page 283

Suspending, event, Running, Working, breakpoints

Get IBM E02HMLL-I - WebSphere Business Integration Server Express PDF manuals and user guides View all IBM E02HMLL-I manuals
Add to My Manuals
Save this manual to your list of manuals

Page 283 highlights

v If you have navigated elsewhere in Collaboration Debugger (to display a breakpoint, for example) and need to locate the event again Do one of the following to display an event: v Right-click the event in the "Events" view and choose Display from the context menu v Select the event in the "Events" view and select Collaboration Debugger > Display from the menu bar Suspending an event When you run an event, as described in "Running an event" on page 276, the flow of execution proceeds as it would normally, without pausing on any breakpoints. If you decide that you want to resume debugging the flow, you can suspend the event. Once you have instructed Collaboration Debugger to run an event, it typically processes too quickly for you to suspend it, though service calls provide this opportunity. When a business object is sent out a service call, the business process blocks until a response is received; this provides enough time to suspend the flow prior to replying to the request, so that debugging resumes when the response is received by the collaboration. Do one of the following to suspend an event: v Right-click the event in the "Events" view and choose Suspend from the context menu v Select the event in the "Events" view and select Collaboration Debugger > Suspend from the menu bar Running an event For more information on running an event, see "Running an event" on page 276. Working with breakpoints Breakpoints are instructions that Collaboration Debugger uses to pause the execution of a collaboration object. You set breakpoints at node in the business process where you want to inspect the data of a flow to observe its transformation and troubleshoot problems. You can set breakpoints on the following types of nodes: v Action node v Subdiagram node v Iterator node v End success node v End failure node v Iterator node v Break node You can not set a breakpoint on a decision node. For more information about the different types of nodes in a collaboration template, see the Collaboration Development Guide. Chapter 13. Using Collaboration Debugger 271

  • 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
v
If
you
have
navigated
elsewhere
in
Collaboration
Debugger
(to
display
a
breakpoint,
for
example)
and
need
to
locate
the
event
again
Do
one
of
the
following
to
display
an
event:
v
Right-click
the
event
in
the
“Events”
view
and
choose
Display
from
the
context
menu
v
Select
the
event
in
the
“Events”
view
and
select
Collaboration
Debugger
>
Display
from
the
menu
bar
Suspending
an
event
When
you
run
an
event,
as
described
in
“Running
an
event”
on
page
276,
the
flow
of
execution
proceeds
as
it
would
normally,
without
pausing
on
any
breakpoints.
If
you
decide
that
you
want
to
resume
debugging
the
flow,
you
can
suspend
the
event.
Once
you
have
instructed
Collaboration
Debugger
to
run
an
event,
it
typically
processes
too
quickly
for
you
to
suspend
it,
though
service
calls
provide
this
opportunity.
When
a
business
object
is
sent
out
a
service
call,
the
business
process
blocks
until
a
response
is
received;
this
provides
enough
time
to
suspend
the
flow
prior
to
replying
to
the
request,
so
that
debugging
resumes
when
the
response
is
received
by
the
collaboration.
Do
one
of
the
following
to
suspend
an
event:
v
Right-click
the
event
in
the
“Events”
view
and
choose
Suspend
from
the
context
menu
v
Select
the
event
in
the
“Events”
view
and
select
Collaboration
Debugger
>
Suspend
from
the
menu
bar
Running
an
event
For
more
information
on
running
an
event,
see
“Running
an
event”
on
page
276.
Working
with
breakpoints
Breakpoints
are
instructions
that
Collaboration
Debugger
uses
to
pause
the
execution
of
a
collaboration
object.
You
set
breakpoints
at
node
in
the
business
process
where
you
want
to
inspect
the
data
of
a
flow
to
observe
its
transformation
and
troubleshoot
problems.
You
can
set
breakpoints
on
the
following
types
of
nodes:
v
Action
node
v
Subdiagram
node
v
Iterator
node
v
End
success
node
v
End
failure
node
v
Iterator
node
v
Break
node
You
can
not
set
a
breakpoint
on
a
decision
node.
For
more
information
about
the
different
types
of
nodes
in
a
collaboration
template,
see
the
Collaboration
Development
Guide
.
Chapter
13.
Using
Collaboration
Debugger
271