IBM E02HMLL-I Implementation Guide - Page 43

connectivity, application-specific, business, objects

Page 43 highlights

then re-configure the connector definition to add support for the business object definitions and associate the required maps. See the guide for your adapter for information about its application-specific properties. See Chapter 7, "Configuring connectors," on page 121 for information about connector standard properties and information on how to use Connector Configurator. Test connectivity and application-specific business objects Once you have developed the application-specific business object and added support for it to a connector definition you should unit-test the business object to make sure that the connector can use it to exchange data with the application successfully. You do not need the generic objects, maps, or collaboration template that the interface will eventually use in order to perform this test. Do the following to unit-test an application-specific business object: 1. Create a pass-through collaboration template (see the Collaboration Development Guide) with the following design: v The collaboration template has two ports-one named From and one named To. v The From and To ports both support the application-specific business object definition. v The collaboration template has a single scenario named Main. v The From port is configured to be the triggering port for the Main scenario for all of the verbs belonging to the business object definition. v The Main scenario has the following elements: - A Start node that is connected to an Action node by a transition link. - A Service Call node that is attached to the Action node and that has the following characteristics: - The Port drop-down menu in the "Regular service call" pane is set to the To port. - The Verb drop-down menu in the "Regular service call" pane is set to the Create verb (or whatever the primary verb for the business object in question is). - The BO Variable field in the "Regular service call" pane is set to the value triggeringBusObj, which is the variable that can be used to reference the business object that triggers the collaboration. - An End Success node that is connected to the Action node by a transition link. For more information about creating collaboration templates, see the Collaboration Development Guide. 2. Configure the properties of the connector definition, add support for the business object definition, and enable the Agent Support checkbox for the business object definition. 3. Add support for the application-specific business object to another "dummy" connector definition. You do not have to configure this connector definition completely because you will only emulate it with testing tools. Ensure that the Agent Support checkbox is enabled for the business object definition. 4. If the connector is responsible for event notification, do the following: v Create a collaboration object based on the pass-through template with the connector to be tested bound to the From port and the "dummy" connector bound to the To port. Chapter 3. Developing business process interfaces 31

  • 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

then
re-configure
the
connector
definition
to
add
support
for
the
business
object
definitions
and
associate
the
required
maps.
See
the
guide
for
your
adapter
for
information
about
its
application-specific
properties.
See
Chapter
7,
“Configuring
connectors,”
on
page
121
for
information
about
connector
standard
properties
and
information
on
how
to
use
Connector
Configurator.
Test
connectivity
and
application-specific
business
objects
Once
you
have
developed
the
application-specific
business
object
and
added
support
for
it
to
a
connector
definition
you
should
unit-test
the
business
object
to
make
sure
that
the
connector
can
use
it
to
exchange
data
with
the
application
successfully.
You
do
not
need
the
generic
objects,
maps,
or
collaboration
template
that
the
interface
will
eventually
use
in
order
to
perform
this
test.
Do
the
following
to
unit-test
an
application-specific
business
object:
1.
Create
a
pass-through
collaboration
template
(see
the
Collaboration
Development
Guide
)
with
the
following
design:
v
The
collaboration
template
has
two
ports—one
named
From
and
one
named
To
.
v
The
From
and
To
ports
both
support
the
application-specific
business
object
definition.
v
The
collaboration
template
has
a
single
scenario
named
Main
.
v
The
From
port
is
configured
to
be
the
triggering
port
for
the
Main
scenario
for
all
of
the
verbs
belonging
to
the
business
object
definition.
v
The
Main
scenario
has
the
following
elements:
A
Start
node
that
is
connected
to
an
Action
node
by
a
transition
link.
A
Service
Call
node
that
is
attached
to
the
Action
node
and
that
has
the
following
characteristics:
-
The
Port
drop-down
menu
in
the
“Regular
service
call”
pane
is
set
to
the
To
port.
-
The
Verb
drop-down
menu
in
the
“Regular
service
call”
pane
is
set
to
the
Create
verb
(or
whatever
the
primary
verb
for
the
business
object
in
question
is).
-
The
BO
Variable
field
in
the
“Regular
service
call”
pane
is
set
to
the
value
triggeringBusObj
,
which
is
the
variable
that
can
be
used
to
reference
the
business
object
that
triggers
the
collaboration.
An
End
Success
node
that
is
connected
to
the
Action
node
by
a
transition
link.
For
more
information
about
creating
collaboration
templates,
see
the
Collaboration
Development
Guide
.
2.
Configure
the
properties
of
the
connector
definition,
add
support
for
the
business
object
definition,
and
enable
the
Agent
Support
checkbox
for
the
business
object
definition.
3.
Add
support
for
the
application-specific
business
object
to
another
“dummy”
connector
definition.
You
do
not
have
to
configure
this
connector
definition
completely
because
you
will
only
emulate
it
with
testing
tools.
Ensure
that
the
Agent
Support
checkbox
is
enabled
for
the
business
object
definition.
4.
If
the
connector
is
responsible
for
event
notification,
do
the
following:
v
Create
a
collaboration
object
based
on
the
pass-through
template
with
the
connector
to
be
tested
bound
to
the
From
port
and
the
“dummy”
connector
bound
to
the
To
port.
Chapter
3.
Developing
business
process
interfaces
31