IBM E02HMLL-I Implementation Guide - Page 38

Validation

Page 38 highlights

v Collaboration Development Guide v Chapter 7, "Configuring connectors," on page 121 v Chapter 9, "Configuring collaboration objects," on page 155 Validation After you have deployed an interface to your local InterChange Server Express instance, you should test the interface to verify that it meets your requirements. For more information on testing, see Chapter 11, "Using Test Connector," on page 189 and Chapter 12, "Using Integrated Test Environment," on page 201. In a typical implementation, two instances of InterChange Server Express are available to you. You use one instance for developing the interface, and another as the production server that will handle the live data in your completed business integration system. You can use either of these instances for testing, but the typical approach will be to test on your development instance, and then migrate the successfully tested business integration system to the production instance. During this stage, you perform functional, performance, and regression testing as required: v Functional Testing You perform functional testing to ensure that the interfaces in the business integration system satisfy the business process automation and integration goals of the project. v Performance Testing You perform performance testing to ensure that the throughput, response time, and latency are within expectations. Depending on your specific circumstances, you may decide to migrate the business integration system into a different environment (other than your original production environment) for performance testing. If you find that performance is not satisfactory, then some components might need modification or re-configuration. v Regression Testing If you modify any components as a result of the functional or performance testing (for instance, you modify a collaboration template that did not satisfy the business requirement), then you must perform regression testing to ensure that the changes made did not cause the component to violate requirements in some new way. Overall, in completing the validation stage, you typically need to perform the following tasks: v Create a requirements matrix that documents all functional and performance requirements. v Prepare a system testing environment. v Identify and develop a series of test cases that will address the functional and performance requirements. v Depending on your specific capabilities and licensing, migrate the business integration system from the development integration environment to a test environment. v Assign specific tests for each test matrix item. v Execute the functional and performance tests described in the test matrices. v Identify, document, and resolve defects or inadequacies revealed by the testing. 26 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
Collaboration
Development
Guide
v
Chapter
7,
“Configuring
connectors,”
on
page
121
v
Chapter
9,
“Configuring
collaboration
objects,”
on
page
155
Validation
After
you
have
deployed
an
interface
to
your
local
InterChange
Server
Express
instance,
you
should
test
the
interface
to
verify
that
it
meets
your
requirements.
For
more
information
on
testing,
see
Chapter
11,
“Using
Test
Connector,”
on
page
189
and
Chapter
12,
“Using
Integrated
Test
Environment,”
on
page
201.
In
a
typical
implementation,
two
instances
of
InterChange
Server
Express
are
available
to
you.
You
use
one
instance
for
developing
the
interface,
and
another
as
the
production
server
that
will
handle
the
live
data
in
your
completed
business
integration
system.
You
can
use
either
of
these
instances
for
testing,
but
the
typical
approach
will
be
to
test
on
your
development
instance,
and
then
migrate
the
successfully
tested
business
integration
system
to
the
production
instance.
During
this
stage,
you
perform
functional,
performance,
and
regression
testing
as
required:
v
Functional
Testing
You
perform
functional
testing
to
ensure
that
the
interfaces
in
the
business
integration
system
satisfy
the
business
process
automation
and
integration
goals
of
the
project.
v
Performance
Testing
You
perform
performance
testing
to
ensure
that
the
throughput,
response
time,
and
latency
are
within
expectations.
Depending
on
your
specific
circumstances,
you
may
decide
to
migrate
the
business
integration
system
into
a
different
environment
(other
than
your
original
production
environment)
for
performance
testing.
If
you
find
that
performance
is
not
satisfactory,
then
some
components
might
need
modification
or
re-configuration.
v
Regression
Testing
If
you
modify
any
components
as
a
result
of
the
functional
or
performance
testing
(for
instance,
you
modify
a
collaboration
template
that
did
not
satisfy
the
business
requirement),
then
you
must
perform
regression
testing
to
ensure
that
the
changes
made
did
not
cause
the
component
to
violate
requirements
in
some
new
way.
Overall,
in
completing
the
validation
stage,
you
typically
need
to
perform
the
following
tasks:
v
Create
a
requirements
matrix
that
documents
all
functional
and
performance
requirements.
v
Prepare
a
system
testing
environment.
v
Identify
and
develop
a
series
of
test
cases
that
will
address
the
functional
and
performance
requirements.
v
Depending
on
your
specific
capabilities
and
licensing,
migrate
the
business
integration
system
from
the
development
integration
environment
to
a
test
environment.
v
Assign
specific
tests
for
each
test
matrix
item.
v
Execute
the
functional
and
performance
tests
described
in
the
test
matrices.
v
Identify,
document,
and
resolve
defects
or
inadequacies
revealed
by
the
testing.
26
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide