IBM E02HMLL-I Implementation Guide - Page 37

Development, configuration

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

the Collaboration Capacity Pack, will be useful in your interface. The capacity packs are separately available as optional additions to IBM WebSphere Business Integration Server Express Plus. Evaluate each component both individually and in terms of how it relates to other components in the overall interface. You cannot complete the design of one component until you have also begun the design of the components with which it interacts in the interface. For detailed information about designing components, see the following guides: v Business Object Development Guide v Map Development Guide v Collaboration Development Guide Development and configuration In this stage you develop integration components according to the specifications that were derived in the "Design" on page 24 stage. To develop the interface, you modify (if necessary) existing components that are available, such as collaboration templates and business objects, and create new components that are environment-specific (such as maps). You define an integration component library to store your component definitions and a user project to represent your interface. You then create and store the integration components for your interface in the library and add shortcuts for them to the user project as you do so. These tasks are described in more detail in "Working with integration component libraries" on page 48 and "Working with user projects" on page 50. The development and configuration stage is iterative and you may have to re-develop components and modify configurations as you progress. It is recommended that you unit test components as you develop them to ensure that they satisfy their roles in the interface as you have designed it. After you have developed and unit-tested all of the components in the interface, you perform string tests to validate that the interface as a whole works as designed. Development and configuration is typically performed in a prescribed sequence of steps, as described in Chapter 3, "Developing business process interfaces," on page 29. While you are developing the integration components, they only exist in your local file system. When the interface is complete, you deploy it as a user project to an InterChange Server Express instance, where the component definitions are stored in the repository. For more information on deploying user projects, see "Exporting components to a package using System Manager" on page 68. For detailed information about developing components, see the following guides: v Chapter 3, "Developing business process interfaces," on page 29 v The specific guide for any adapter you are using v Business Object Development Guide v Map Development Guide Chapter 2. The development model and process 25

  • 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
the
Collaboration
Capacity
Pack,
will
be
useful
in
your
interface.
The
capacity
packs
are
separately
available
as
optional
additions
to
IBM
WebSphere
Business
Integration
Server
Express
Plus.
Evaluate
each
component
both
individually
and
in
terms
of
how
it
relates
to
other
components
in
the
overall
interface.
You
cannot
complete
the
design
of
one
component
until
you
have
also
begun
the
design
of
the
components
with
which
it
interacts
in
the
interface.
For
detailed
information
about
designing
components,
see
the
following
guides:
v
Business
Object
Development
Guide
v
Map
Development
Guide
v
Collaboration
Development
Guide
Development
and
configuration
In
this
stage
you
develop
integration
components
according
to
the
specifications
that
were
derived
in
the
“Design”
on
page
24
stage.
To
develop
the
interface,
you
modify
(if
necessary)
existing
components
that
are
available,
such
as
collaboration
templates
and
business
objects,
and
create
new
components
that
are
environment-specific
(such
as
maps).
You
define
an
integration
component
library
to
store
your
component
definitions
and
a
user
project
to
represent
your
interface.
You
then
create
and
store
the
integration
components
for
your
interface
in
the
library
and
add
shortcuts
for
them
to
the
user
project
as
you
do
so.
These
tasks
are
described
in
more
detail
in
“Working
with
integration
component
libraries”
on
page
48
and
“Working
with
user
projects”
on
page
50.
The
development
and
configuration
stage
is
iterative
and
you
may
have
to
re-develop
components
and
modify
configurations
as
you
progress.
It
is
recommended
that
you
unit
test
components
as
you
develop
them
to
ensure
that
they
satisfy
their
roles
in
the
interface
as
you
have
designed
it.
After
you
have
developed
and
unit-tested
all
of
the
components
in
the
interface,
you
perform
string
tests
to
validate
that
the
interface
as
a
whole
works
as
designed.
Development
and
configuration
is
typically
performed
in
a
prescribed
sequence
of
steps,
as
described
in
Chapter
3,
“Developing
business
process
interfaces,”
on
page
29.
While
you
are
developing
the
integration
components,
they
only
exist
in
your
local
file
system.
When
the
interface
is
complete,
you
deploy
it
as
a
user
project
to
an
InterChange
Server
Express
instance,
where
the
component
definitions
are
stored
in
the
repository.
For
more
information
on
deploying
user
projects,
see
“Exporting
components
to
a
package
using
System
Manager”
on
page
68.
For
detailed
information
about
developing
components,
see
the
following
guides:
v
Chapter
3,
“Developing
business
process
interfaces,”
on
page
29
v
The
specific
guide
for
any
adapter
you
are
using
v
Business
Object
Development
Guide
v
Map
Development
Guide
Chapter
2.
The
development
model
and
process
25