IBM E02HMLL-I Implementation Guide - Page 267

Performing, using, Integrated, Environment

Page 267 highlights

4. Click OK. Performing a test using Integrated Test Environment Whereas most of this chapter described subtasks you perform as part of a test or specific interface elements of the Integrated Test Environment perspective, this section describes the workflow you typically follow to perform a test. It incorporates most of the subtasks and involves most of the interface elements. It recommends the most efficient and effective techniques in situations where there are multiple ways of accomplishing a subtask. Do the following to test an interface using Integrated Test Environment: 1. Although you can deploy components to an InterChange Server Express instance by using Integrated Test Environment, it is recommended that you perform all deployment activities beforehand for the following reasons: v You avoid having to compile maps and collaboration templates as part of the testing process. v You can start the components prior to the testing stage as well; components must be deployed before they can be started. When you deploy connectors you must restart the server to start them, and almost any interface involves a connector, so it is typically not efficient to deploy the components for an interface as part of the testing process. v If you have to test several interfaces you can do a single deployment prior to testing, rather than having to make sure you oversee the proper deployment for each interface during testing. For information on deploying components using System Manager, see "Deploying components to a server" on page 70. For information on deploying components using repos_copy, see Chapter 6, "Using repos_copy," on page 109. For information on deploying components by using Integrated Test Environment (which is not recommended), reference one of the following sections: v "Managing the repository using the Outline view" on page 217 v "Using the Task Manager view" on page 220 v "Managing the repository using the Test Unit view" on page 231 2. Ensure that all of the components required to test the interface are in an active state. To start components, use one of the following interfaces: v System Monitor, as described in the System Administration Guide v InterChange Server Component Management view, as described in "Managing component states in the repository" on page 84 v Outline view, as described in "Managing component states using the Outline view" on page 217 v "Managing component states using the Test Unit view" on page 231 3. Register the InterChange Server Express you want to test with as a "Local Test Server", as described in "Registering an InterChange Server Express instance" on page 43. 4. Start the Integrated Test Environment perspective as described in "Starting Integrated Test Environment" on page 202. 5. Select the server you want to test with as described in "Selecting a server configuration" on page 204. Chapter 12. Using Integrated Test Environment 255

  • 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

4.
Click
OK
.
Performing
a
test
using
Integrated
Test
Environment
Whereas
most
of
this
chapter
described
subtasks
you
perform
as
part
of
a
test
or
specific
interface
elements
of
the
Integrated
Test
Environment
perspective,
this
section
describes
the
workflow
you
typically
follow
to
perform
a
test.
It
incorporates
most
of
the
subtasks
and
involves
most
of
the
interface
elements.
It
recommends
the
most
efficient
and
effective
techniques
in
situations
where
there
are
multiple
ways
of
accomplishing
a
subtask.
Do
the
following
to
test
an
interface
using
Integrated
Test
Environment:
1.
Although
you
can
deploy
components
to
an
InterChange
Server
Express
instance
by
using
Integrated
Test
Environment,
it
is
recommended
that
you
perform
all
deployment
activities
beforehand
for
the
following
reasons:
v
You
avoid
having
to
compile
maps
and
collaboration
templates
as
part
of
the
testing
process.
v
You
can
start
the
components
prior
to
the
testing
stage
as
well;
components
must
be
deployed
before
they
can
be
started.
When
you
deploy
connectors
you
must
restart
the
server
to
start
them,
and
almost
any
interface
involves
a
connector,
so
it
is
typically
not
efficient
to
deploy
the
components
for
an
interface
as
part
of
the
testing
process.
v
If
you
have
to
test
several
interfaces
you
can
do
a
single
deployment
prior
to
testing,
rather
than
having
to
make
sure
you
oversee
the
proper
deployment
for
each
interface
during
testing.
For
information
on
deploying
components
using
System
Manager,
see
“Deploying
components
to
a
server”
on
page
70.
For
information
on
deploying
components
using
repos_copy,
see
Chapter
6,
“Using
repos_copy,”
on
page
109.
For
information
on
deploying
components
by
using
Integrated
Test
Environment
(which
is
not
recommended),
reference
one
of
the
following
sections:
v
“Managing
the
repository
using
the
Outline
view”
on
page
217
v
“Using
the
Task
Manager
view”
on
page
220
v
“Managing
the
repository
using
the
Test
Unit
view”
on
page
231
2.
Ensure
that
all
of
the
components
required
to
test
the
interface
are
in
an
active
state.
To
start
components,
use
one
of
the
following
interfaces:
v
System
Monitor,
as
described
in
the
System
Administration
Guide
v
InterChange
Server
Component
Management
view,
as
described
in
“Managing
component
states
in
the
repository”
on
page
84
v
Outline
view,
as
described
in
“Managing
component
states
using
the
Outline
view”
on
page
217
v
“Managing
component
states
using
the
Test
Unit
view”
on
page
231
3.
Register
the
InterChange
Server
Express
you
want
to
test
with
as
a
“Local
Test
Server”,
as
described
in
“Registering
an
InterChange
Server
Express
instance”
on
page
43.
4.
Start
the
Integrated
Test
Environment
perspective
as
described
in
“Starting
Integrated
Test
Environment”
on
page
202.
5.
Select
the
server
you
want
to
test
with
as
described
in
“Selecting
a
server
configuration”
on
page
204.
Chapter
12.
Using
Integrated
Test
Environment
255