IBM E02HMLL-I Implementation Guide - Page 58

Changing, InterChange, Server, Express, password

Page 58 highlights

object definition that has a child object into the repository, but the child object does not exist yet, then an InterChange Server Express in production mode would cause the import to fail to protect the integrity of the repository. An InterChange Server Express in design mode, however, would allow you to proceed so that you can assemble your integration components in a way that best suits your development approach. Furthermore, compiling maps and collaboration templates when deploying a package to a design-mode server is optional. In production mode, the server automatically compiles all maps and collaboration templates. Design mode is particularly useful when you are importing components from another environment. You may not be aware of all the dependencies yourself, so being able to incrementally import components without the import operations failing due to unresolved dependencies is very helpful. To start InterChange Server Express in design mode, use the -design parameter when starting the server. To do so, edit the Windows shortcut for InterChange Server Express, adding the parameter-design at the end of the path shown in the Target field. Later, when you wish to use Production mode, edit the shortcut again, and remove the -designparameter from the path in the Target field. Production mode In production mode, InterChange Server Express is designed to guarantee the integrity of the repository. It will not allow you to deploy a package with unresolved dependencies to the repository, and it automatically compiles all maps and collaboration templates in the deployment package. These restrictions guarantee that the server environment is in a state in which its components can execute properly. If there were components with unresolved dependencies or uncompiled components in the server environment at runtime then any transactions that involved those components would fail. Although that is an acceptable situation in a development environment, where it is presumed that you are still creating the required components, it is not considered acceptable in a production environment, so these restrictions enforce safe deployment procedures. Production mode is the default mode for InterChange Server Express, so you do not have to take any configuration steps to start it in production mode. If you want to start it in production mode, however, be sure that you have not taken steps to start it in design mode and confirm its mode in the InterChange Server Express Component Management view of System Manager. Changing the InterChange Server Express password You can change the password for the user account that is used to connect to InterChange Server Express. Do the following to change the password: 1. Right-click the entry for the InterChange Server Express instance in the InterChange Server Express view and choose Change Password from the context menu. The "Change InterChange Server Express Password" dialog displays. 2. Type the current password in the Old Password field. 3. Type the new password in the New Password field. 4. Type the new password again in the Confirm Password field. 5. Click OK. 46 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

object
definition
that
has
a
child
object
into
the
repository,
but
the
child
object
does
not
exist
yet,
then
an
InterChange
Server
Express
in
production
mode
would
cause
the
import
to
fail
to
protect
the
integrity
of
the
repository.
An
InterChange
Server
Express
in
design
mode,
however,
would
allow
you
to
proceed
so
that
you
can
assemble
your
integration
components
in
a
way
that
best
suits
your
development
approach.
Furthermore,
compiling
maps
and
collaboration
templates
when
deploying
a
package
to
a
design-mode
server
is
optional.
In
production
mode,
the
server
automatically
compiles
all
maps
and
collaboration
templates.
Design
mode
is
particularly
useful
when
you
are
importing
components
from
another
environment.
You
may
not
be
aware
of
all
the
dependencies
yourself,
so
being
able
to
incrementally
import
components
without
the
import
operations
failing
due
to
unresolved
dependencies
is
very
helpful.
To
start
InterChange
Server
Express
in
design
mode,
use
the
-design
parameter
when
starting
the
server.
To
do
so,
edit
the
Windows
shortcut
for
InterChange
Server
Express,
adding
the
parameter
-design
at
the
end
of
the
path
shown
in
the
Target
field.
Later,
when
you
wish
to
use
Production
mode,
edit
the
shortcut
again,
and
remove
the
-design
parameter
from
the
path
in
the
Target
field.
Production
mode
In
production
mode,
InterChange
Server
Express
is
designed
to
guarantee
the
integrity
of
the
repository.
It
will
not
allow
you
to
deploy
a
package
with
unresolved
dependencies
to
the
repository,
and
it
automatically
compiles
all
maps
and
collaboration
templates
in
the
deployment
package.
These
restrictions
guarantee
that
the
server
environment
is
in
a
state
in
which
its
components
can
execute
properly.
If
there
were
components
with
unresolved
dependencies
or
uncompiled
components
in
the
server
environment
at
runtime
then
any
transactions
that
involved
those
components
would
fail.
Although
that
is
an
acceptable
situation
in
a
development
environment,
where
it
is
presumed
that
you
are
still
creating
the
required
components,
it
is
not
considered
acceptable
in
a
production
environment,
so
these
restrictions
enforce
safe
deployment
procedures.
Production
mode
is
the
default
mode
for
InterChange
Server
Express,
so
you
do
not
have
to
take
any
configuration
steps
to
start
it
in
production
mode.
If
you
want
to
start
it
in
production
mode,
however,
be
sure
that
you
have
not
taken
steps
to
start
it
in
design
mode
and
confirm
its
mode
in
the
InterChange
Server
Express
Component
Management
view
of
System
Manager.
Changing
the
InterChange
Server
Express
password
You
can
change
the
password
for
the
user
account
that
is
used
to
connect
to
InterChange
Server
Express.
Do
the
following
to
change
the
password:
1.
Right-click
the
entry
for
the
InterChange
Server
Express
instance
in
the
InterChange
Server
Express
view
and
choose
Change
Password
from
the
context
menu.
The
“Change
InterChange
Server
Express
Password”
dialog
displays.
2.
Type
the
current
password
in
the
Old
Password
field.
3.
Type
the
new
password
in
the
New
Password
field.
4.
Type
the
new
password
again
in
the
Confirm
Password
field.
5.
Click
OK
.
46
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide