IBM E02HMLL-I Implementation Guide - Page 243

Managing, repository, using, component, states, Using, showing, closing, Client, Simulator, views

Page 243 highlights

Management view in System Manager, the Server Context Overlay will still reflect the state of the component prior to the change. You must refresh the Server Context Overlay to update it with current state information. To refresh the Server Context Overlay, right-click the background of the Test Unit view and select Refresh Server Context Overlay from the context menu. Managing the repository using the Test Unit view All of the components required for an interface must be deployed to the server repository to test the interface. The Outline view provides a way to work with the InterChange Server Express repository to ensure that it contains the required components. To deploy a component when it already exists in the server repository, right-click the component in the Test Unit view and choose Deploy with overwrite from the context menu. To deploy a component if it does not already exist in the server repository, right-click the component in the Test Unit view and choose Deploy from the context menu. If the selected components already exist in the server repository and you use the Deploy option then the deployment will fail. To remove a component from the server repository using the Test Unit view, right-click the component in the view and choose Remove from server from the context menu. Entries are written to the Integrated Test Environment Console and InterChange Server Express Console indicating whether the deployment was successful or not. Managing component states using the Test Unit view You can change the state of a component using the Test Unit view. This allows you to resolve problems you discover during testing-you can deactivate the component, modify it, re-deploy it, and re-activate it without using System Manager, repos_copy, or System Monitor. To change the state of a component, right-click its icon in the Server Context Overlay and choose the desired state operation-Start, Pause, or Stop. Not all component types have all state operations available. For information on component states, see the System Administration Guide. Using, showing, and closing Client Simulator views using the Test Unit view You use Client Simulator views to emulate connectors and access clients when testing an interface. Client Simulator views provide interfaces to create business object instances with test data, send them as business object requests, and reply to them as business object responses. To load the profile for a connector into a particular Client Simulator view, right-click the icon for the connector in the Test Unit view and select Use Client Simulator x, where x is the number of the Client Simulator view position you want to use for that connector. Chapter 12. Using Integrated Test Environment 231

  • 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

Management
view
in
System
Manager,
the
Server
Context
Overlay
will
still
reflect
the
state
of
the
component
prior
to
the
change.
You
must
refresh
the
Server
Context
Overlay
to
update
it
with
current
state
information.
To
refresh
the
Server
Context
Overlay,
right-click
the
background
of
the
Test
Unit
view
and
select
Refresh
Server
Context
Overlay
from
the
context
menu.
Managing
the
repository
using
the
Test
Unit
view
All
of
the
components
required
for
an
interface
must
be
deployed
to
the
server
repository
to
test
the
interface.
The
Outline
view
provides
a
way
to
work
with
the
InterChange
Server
Express
repository
to
ensure
that
it
contains
the
required
components.
To
deploy
a
component
when
it
already
exists
in
the
server
repository,
right-click
the
component
in
the
Test
Unit
view
and
choose
Deploy
with
overwrite
from
the
context
menu.
To
deploy
a
component
if
it
does
not
already
exist
in
the
server
repository,
right-click
the
component
in
the
Test
Unit
view
and
choose
Deploy
from
the
context
menu.
If
the
selected
components
already
exist
in
the
server
repository
and
you
use
the
Deploy
option
then
the
deployment
will
fail.
To
remove
a
component
from
the
server
repository
using
the
Test
Unit
view,
right-click
the
component
in
the
view
and
choose
Remove
from
server
from
the
context
menu.
Entries
are
written
to
the
Integrated
Test
Environment
Console
and
InterChange
Server
Express
Console
indicating
whether
the
deployment
was
successful
or
not.
Managing
component
states
using
the
Test
Unit
view
You
can
change
the
state
of
a
component
using
the
Test
Unit
view.
This
allows
you
to
resolve
problems
you
discover
during
testing—you
can
deactivate
the
component,
modify
it,
re-deploy
it,
and
re-activate
it
without
using
System
Manager,
repos_copy,
or
System
Monitor.
To
change
the
state
of
a
component,
right-click
its
icon
in
the
Server
Context
Overlay
and
choose
the
desired
state
operation—
Start
,
Pause
,
or
Stop
.
Not
all
component
types
have
all
state
operations
available.
For
information
on
component
states,
see
the
System
Administration
Guide
.
Using,
showing,
and
closing
Client
Simulator
views
using
the
Test
Unit
view
You
use
Client
Simulator
views
to
emulate
connectors
and
access
clients
when
testing
an
interface.
Client
Simulator
views
provide
interfaces
to
create
business
object
instances
with
test
data,
send
them
as
business
object
requests,
and
reply
to
them
as
business
object
responses.
To
load
the
profile
for
a
connector
into
a
particular
Client
Simulator
view,
right-click
the
icon
for
the
connector
in
the
Test
Unit
view
and
select
Use
Client
Simulator
x
,
where
x
is
the
number
of
the
Client
Simulator
view
position
you
want
to
use
for
that
connector.
Chapter
12.
Using
Integrated
Test
Environment
231