IBM E02HMLL-I Implementation Guide - Page 288

Running, specific, event, Working, variables

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 288 highlights

v Give focus to the "Collaboration template" editor and select Collaboration Debugger > Run from the menu bar v Give focus to the "Collaboration template" editor and use the keyboard shortcut F8 Running to a specific node When you perform a "run to this node" operation on a flow, InterChange Server Express resumes the paused flow and allows processing to continue either to the node on which you performed the operation, or to a node with an active breakpoint set on it. Do one of the following to run a paused flow to a specific node: v Right-click the node to which you want execution to run and choose Run to this node from the context menu v Select the node to which you want execution to run and click Run to in the toolbar v Select the node to which you want execution to run and select Collaboration Debugger > Run to from the menu bar Running an event When you perform a "run event" operation, InterChange Server Express resumes the paused flow and allows processing to continue, bypassing any breakpoints in the business process even if the breakpoints are active. Do one of the following to run an event: v Right-click the event in the "Events" view and choose Run from the context menu v Select the event in the "Events" view and select Collaboration Debugger > Run Event(s) from the context menu v Select the event in the "Events" view and click Run Event(s) in the toolbar Working with variables The "Variables" view displays the value of any variable that is declared in the "Declarations" tab of the collaboration template definition. This includes the business objects that are automatically declared by Process Designer Express to be associated with each port that you create on the "Ports and Triggering Events" tab, as well as any variables you add to the "Declarations" tab yourself. When you display an event as described in "Displaying an event" on page 270 or manage a flow as described in "Performing debugging operations" on page 274, the "Variables" view updates the variable information it shows. You can expand any variables of BusObj type to view their attributes. There is currently no way to display the triggeringBusObj variable. This is a system-declared variable that references the original flow that triggered execution of the collaboration object, and is typically very significant. If you want to maintain a record of the values of the triggeringBusObj variable, you can declare a new BusObj variable in the "Declarations" section of the collaboration template, then initialize it to the value of the triggeringBusObj variable in the first node of the scenario. 276 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
v
Give
focus
to
the
“Collaboration
template”
editor
and
select
Collaboration
Debugger
>
Run
from
the
menu
bar
v
Give
focus
to
the
“Collaboration
template”
editor
and
use
the
keyboard
shortcut
F8
Running
to
a
specific
node
When
you
perform
a
“run
to
this
node”
operation
on
a
flow,
InterChange
Server
Express
resumes
the
paused
flow
and
allows
processing
to
continue
either
to
the
node
on
which
you
performed
the
operation,
or
to
a
node
with
an
active
breakpoint
set
on
it.
Do
one
of
the
following
to
run
a
paused
flow
to
a
specific
node:
v
Right-click
the
node
to
which
you
want
execution
to
run
and
choose
Run
to
this
node
from
the
context
menu
v
Select
the
node
to
which
you
want
execution
to
run
and
click
Run
to
in
the
toolbar
v
Select
the
node
to
which
you
want
execution
to
run
and
select
Collaboration
Debugger
>
Run
to
from
the
menu
bar
Running
an
event
When
you
perform
a
“run
event”
operation,
InterChange
Server
Express
resumes
the
paused
flow
and
allows
processing
to
continue,
bypassing
any
breakpoints
in
the
business
process
even
if
the
breakpoints
are
active.
Do
one
of
the
following
to
run
an
event:
v
Right-click
the
event
in
the
“Events”
view
and
choose
Run
from
the
context
menu
v
Select
the
event
in
the
“Events”
view
and
select
Collaboration
Debugger
>
Run
Event(s)
from
the
context
menu
v
Select
the
event
in
the
“Events”
view
and
click
Run
Event(s)
in
the
toolbar
Working
with
variables
The
“Variables”
view
displays
the
value
of
any
variable
that
is
declared
in
the
“Declarations”
tab
of
the
collaboration
template
definition.
This
includes
the
business
objects
that
are
automatically
declared
by
Process
Designer
Express
to
be
associated
with
each
port
that
you
create
on
the
“Ports
and
Triggering
Events”
tab,
as
well
as
any
variables
you
add
to
the
“Declarations”
tab
yourself.
When
you
display
an
event
as
described
in
“Displaying
an
event”
on
page
270
or
manage
a
flow
as
described
in
“Performing
debugging
operations”
on
page
274,
the
“Variables”
view
updates
the
variable
information
it
shows.
You
can
expand
any
variables
of
BusObj
type
to
view
their
attributes.
There
is
currently
no
way
to
display
the
triggeringBusObj
variable.
This
is
a
system-declared
variable
that
references
the
original
flow
that
triggered
execution
of
the
collaboration
object,
and
is
typically
very
significant.
If
you
want
to
maintain
a
record
of
the
values
of
the
triggeringBusObj
variable,
you
can
declare
a
new
BusObj
variable
in
the
“Declarations”
section
of
the
collaboration
template,
then
initialize
it
to
the
value
of
the
triggeringBusObj
variable
in
the
first
node
of
the
scenario.
276
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide