IBM E02HMLL-I Implementation Guide - Page 83

Setting, deployment, configuration, properties

Get IBM E02HMLL-I - WebSphere Business Integration Server Express PDF manuals and user guides View all IBM E02HMLL-I manuals
Add to My Manuals
Save this manual to your list of manuals

Page 83 highlights

Table 6. Advantages and disadvantages of System Manager and repos_copy in deployment (continued) Interface Advantages Disadvantages repos_copy v There is no requirement to have v Repos_copy uses a command line components grouped together, interface. as they must be in a user project when deploying through System Manager. v You must export the components you want to deploy to a package file first, using either System v Repos_copy is Manager or repos_copy. platform-independent. v You cannot selectively deploy components in the package file. v You can only deploy a single package file at a time. Setting deployment configuration properties When you deploy a user project from System Manager to different servers, the configuration properties for some of the integration components may need to change for the new server environment. For example, an adapter in your solution may have properties that specify a database URL, a user name, and a password that are all valid for your development and testing server. But the production environment in which the solution will be deployed may require different values for these properties. Rather than manually reconfiguring the adapter (by manually using the connector configurator to change the connector configuration properties) --and other integration components that might require modification for the new environment--you can use the deployment configuration feature of System Manager. The deployment configuration feature of System Manager enables you to define a set of values for certain integration component properties and make them applicable to a specific server (or servers) that you name. The values are stored in a deployment file (with the extension .dfg) associated with an Integration Component Library. When you deploy an existing user project to one of the servers that you listed in deployment configurator, System Manager uses the property values from the deployment file to modify the existing configuration files for the relevant components of the user project. This feature can be used to modify the properties of connectors, maps, collaborations, and relationships. To create and deploy properties using the deployment configuration feature, follow these steps: v Open the deployment configuration dialog v Add one or more server names v Add integration components v Add the properties that require transformation before deployment to a particular server v Assign values to the properties, as appropriate for each server v Close and save the deployment configuration v Deploy the components Opening the deployment configuration dialog To open the deployment configuration dialog, do this: Chapter 4. Using System Manager 71

  • 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
Table
6.
Advantages
and
disadvantages
of
System
Manager
and
repos_copy
in
deployment
(continued)
Interface
Advantages
Disadvantages
repos_copy
v
There
is
no
requirement
to
have
components
grouped
together,
as
they
must
be
in
a
user
project
when
deploying
through
System
Manager.
v
Repos_copy
is
platform-independent.
v
Repos_copy
uses
a
command
line
interface.
v
You
must
export
the
components
you
want
to
deploy
to
a
package
file
first,
using
either
System
Manager
or
repos_copy.
v
You
cannot
selectively
deploy
components
in
the
package
file.
v
You
can
only
deploy
a
single
package
file
at
a
time.
Setting
deployment
configuration
properties
When
you
deploy
a
user
project
from
System
Manager
to
different
servers,
the
configuration
properties
for
some
of
the
integration
components
may
need
to
change
for
the
new
server
environment.
For
example,
an
adapter
in
your
solution
may
have
properties
that
specify
a
database
URL,
a
user
name,
and
a
password
that
are
all
valid
for
your
development
and
testing
server.
But
the
production
environment
in
which
the
solution
will
be
deployed
may
require
different
values
for
these
properties.
Rather
than
manually
reconfiguring
the
adapter
(by
manually
using
the
connector
configurator
to
change
the
connector
configuration
properties)
--and
other
integration
components
that
might
require
modification
for
the
new
environment--you
can
use
the
deployment
configuration
feature
of
System
Manager.
The
deployment
configuration
feature
of
System
Manager
enables
you
to
define
a
set
of
values
for
certain
integration
component
properties
and
make
them
applicable
to
a
specific
server
(or
servers)
that
you
name.
The
values
are
stored
in
a
deployment
file
(with
the
extension
.
dfg
)
associated
with
an
Integration
Component
Library.
When
you
deploy
an
existing
user
project
to
one
of
the
servers
that
you
listed
in
deployment
configurator,
System
Manager
uses
the
property
values
from
the
deployment
file
to
modify
the
existing
configuration
files
for
the
relevant
components
of
the
user
project.
This
feature
can
be
used
to
modify
the
properties
of
connectors,
maps,
collaborations,
and
relationships.
To
create
and
deploy
properties
using
the
deployment
configuration
feature,
follow
these
steps:
v
Open
the
deployment
configuration
dialog
v
Add
one
or
more
server
names
v
Add
integration
components
v
Add
the
properties
that
require
transformation
before
deployment
to
a
particular
server
v
Assign
values
to
the
properties,
as
appropriate
for
each
server
v
Close
and
save
the
deployment
configuration
v
Deploy
the
components
Opening
the
deployment
configuration
dialog
To
open
the
deployment
configuration
dialog,
do
this:
Chapter
4.
Using
System
Manager
71