IBM E02HMLL-I Implementation Guide - Page 34

Integration, component, libraries, projects, InterChange, Server, Express, instances, Stages, - am number four

Page 34 highlights

Integration component libraries Integration component libraries are structural groupings of components in your development environment. You define a library in System Manager and System Manager creates a directory in the file system that represents the library. Within the library directory is a number of subdirectories for each type of integration component. When you create an integration component, System Manager creates a file or group of files and stores them in the proper subdirectory within the directory of the library. User projects User projects are structures within System Manager that support the need to organize integration components together so that they are viewed as belonging to an interface. User projects are collections of shortcuts to integration components in one or more libraries, so you can create one user project for each interface. Each user project might have shortcuts to some of the same components in a library because interfaces frequently share components. A customer synchronization interface and an order processing interface that both involved the SAP application, for instance, would both require the Adapter for SAP, so the user projects that correspond to those interfaces would both have shortcuts to the definition for the SAP connector. InterChange Server Express instances InterChange Server Express is an integration broker. It is the software infrastructure that provides business process integration and automation. When you install InterChange Server Express on a computer and start the server, you start a server instance. A server instance hosts the business integration system that is comprised of all the interfaces that satisfy the integration requirements of the customer. Typically you will have one instance of InterChange Server Express dedicated to developing and testing the business integration system as a whole, and one instance for hosting the production release of the system. Stages in developing an implementation Typically, the development of a business integration system involves the following stages: v "Discovery and assessment of requirements" v "Preparation of environments" on page 24 v "Design" on page 24 v "Development and configuration" on page 25 v "Validation" on page 26 v "Deployment" on page 27 Discovery and assessment of requirements This stage begins the implementation process by identifying the business goals for the project, the system requirements, and the overall scope of the development effort. The process of requirements elicitation is very specific to different organizations. This section presents some of the possible questions you will need to ask, but you should follow whatever method is appropriate for your organization. 22 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

Integration
component
libraries
Integration
component
libraries
are
structural
groupings
of
components
in
your
development
environment.
You
define
a
library
in
System
Manager
and
System
Manager
creates
a
directory
in
the
file
system
that
represents
the
library.
Within
the
library
directory
is
a
number
of
subdirectories
for
each
type
of
integration
component.
When
you
create
an
integration
component,
System
Manager
creates
a
file
or
group
of
files
and
stores
them
in
the
proper
subdirectory
within
the
directory
of
the
library.
User
projects
User
projects
are
structures
within
System
Manager
that
support
the
need
to
organize
integration
components
together
so
that
they
are
viewed
as
belonging
to
an
interface.
User
projects
are
collections
of
shortcuts
to
integration
components
in
one
or
more
libraries,
so
you
can
create
one
user
project
for
each
interface.
Each
user
project
might
have
shortcuts
to
some
of
the
same
components
in
a
library
because
interfaces
frequently
share
components.
A
customer
synchronization
interface
and
an
order
processing
interface
that
both
involved
the
SAP
application,
for
instance,
would
both
require
the
Adapter
for
SAP,
so
the
user
projects
that
correspond
to
those
interfaces
would
both
have
shortcuts
to
the
definition
for
the
SAP
connector.
InterChange
Server
Express
instances
InterChange
Server
Express
is
an
integration
broker.
It
is
the
software
infrastructure
that
provides
business
process
integration
and
automation.
When
you
install
InterChange
Server
Express
on
a
computer
and
start
the
server,
you
start
a
server
instance
.
A
server
instance
hosts
the
business
integration
system
that
is
comprised
of
all
the
interfaces
that
satisfy
the
integration
requirements
of
the
customer.
Typically
you
will
have
one
instance
of
InterChange
Server
Express
dedicated
to
developing
and
testing
the
business
integration
system
as
a
whole,
and
one
instance
for
hosting
the
production
release
of
the
system.
Stages
in
developing
an
implementation
Typically,
the
development
of
a
business
integration
system
involves
the
following
stages:
v
“Discovery
and
assessment
of
requirements”
v
“Preparation
of
environments”
on
page
24
v
“Design”
on
page
24
v
“Development
and
configuration”
on
page
25
v
“Validation”
on
page
26
v
“Deployment”
on
page
27
Discovery
and
assessment
of
requirements
This
stage
begins
the
implementation
process
by
identifying
the
business
goals
for
the
project,
the
system
requirements,
and
the
overall
scope
of
the
development
effort.
The
process
of
requirements
elicitation
is
very
specific
to
different
organizations.
This
section
presents
some
of
the
possible
questions
you
will
need
to
ask,
but
you
should
follow
whatever
method
is
appropriate
for
your
organization.
22
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide