IBM E02HMLL-I Implementation Guide - Page 86

Export, import, deployment, configuration, properties

Page 86 highlights

v Export within a package Deployment configuration files are included within the package that is created when you export either user projects or individual ICLs to a repository package file, as described in "Exporting components to a package using System Manager" on page 68. When you do this for an ICL, any deployment configuration file (*.dfg file) that you created on that ICL will be included in the package. When you do this for a user project, the deployment configuration files that were created on any of the ICLs in the user project will be included in the package. If you selectively choose only certain components from an included ICL when you export the user project as a package, the deployment configuration file corresponding to that ICL will include properties and values for only those selected components. v Export to a deployment configurator file You can export a file of deployment configuration properties, as described in "Export and import of deployment configuration properties." This is especially useful if you are exporting a repository file package from an InterChange Server Express repository, as described in Chapter 6, "Using repos_copy," and you want to include deployment configuration properties. When you create a deployment configuration file, the file resides within System Manager, not within the InterChange Server Express repository. Consequently, when you use repos_copy to create a package from an InterChange Server Express repository, the deployment configuration file is not included. To add it, you can export the deployment configurator file using the Export Property Descriptor dialog, and then copy the configuration content into the repos_copy package file, using this syntax: repos_copy -sserverName -uusername -ppassword -ireposcopyfile -ixdideploymentdescriptorfile When you export an ICL or User Project from System Manager , the deployment descriptor.dfg file with the relevant entries will be included with the repository jar file. You can then use the repos_copy utility to repos copy the .jar file into the server. The values for the configuration file inside the .jar file will be automatically applied to the components before being deployed to the server. If you do not want the transformations to happen, you can suppress them using the following option: repos_copy -sserverName -uusername -ppassword -ireposcopyfile -xdn The -xdn option ignores the .dfg file inside the repository .jar file and sends the deployment package to the server without changing the property values. Export and import of deployment configuration properties After deployment configuration properties have been created in Deployment Configurator for one server, you can export those properties to a file, and then import that file as the starting point for the deployment configuration properties of another server. To do so, right-click in a field in the Property Name column, and choose Import. The Import Properties dialog appears, providing the following choices: v Overwrite Property Descriptor This selection is the default. If you use this selection, all the server names, integration components, properties, and values established in the existing deployment configuration file will be removed, all the server names and properties and values established in the file being imported will be added. In effect, you are replacing the entire content of the original file with the entire content of the file being imported. 74 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
Export
within
a
package
Deployment
configuration
files
are
included
within
the
package
that
is
created
when
you
export
either
user
projects
or
individual
ICLs
to
a
repository
package
file,
as
described
in
“Exporting
components
to
a
package
using
System
Manager”
on
page
68.
When
you
do
this
for
an
ICL,
any
deployment
configuration
file
(*.dfg
file)
that
you
created
on
that
ICL
will
be
included
in
the
package.
When
you
do
this
for
a
user
project,
the
deployment
configuration
files
that
were
created
on
any
of
the
ICLs
in
the
user
project
will
be
included
in
the
package.
If
you
selectively
choose
only
certain
components
from
an
included
ICL
when
you
export
the
user
project
as
a
package,
the
deployment
configuration
file
corresponding
to
that
ICL
will
include
properties
and
values
for
only
those
selected
components.
v
Export
to
a
deployment
configurator
file
You
can
export
a
file
of
deployment
configuration
properties,
as
described
in
“Export
and
import
of
deployment
configuration
properties.”
This
is
especially
useful
if
you
are
exporting
a
repository
file
package
from
an
InterChange
Server
Express
repository,
as
described
in
Chapter
6,
“Using
repos_copy,”
and
you
want
to
include
deployment
configuration
properties.
When
you
create
a
deployment
configuration
file,
the
file
resides
within
System
Manager,
not
within
the
InterChange
Server
Express
repository.
Consequently,
when
you
use
repos_copy
to
create
a
package
from
an
InterChange
Server
Express
repository,
the
deployment
configuration
file
is
not
included.
To
add
it,
you
can
export
the
deployment
configurator
file
using
the
Export
Property
Descriptor
dialog,
and
then
copy
the
configuration
content
into
the
repos_copy
package
file,
using
this
syntax:
repos_copy
-s
serverName
-u
username
-p
password
-ireposcopyfile
-ixdi
deploymentdescriptorfile
When
you
export
an
ICL
or
User
Project
from
System
Manager
,
the
deployment
descriptor.dfg
file
with
the
relevant
entries
will
be
included
with
the
repository
jar
file.
You
can
then
use
the
repos_copy
utility
to
repos
copy
the
.jar
file
into
the
server.
The
values
for
the
configuration
file
inside
the
.jar
file
will
be
automatically
applied
to
the
components
before
being
deployed
to
the
server.
If
you
do
not
want
the
transformations
to
happen,
you
can
suppress
them
using
the
following
option:
repos_copy
-s
serverName
-u
username
-p
password
-ireposcopyfile
-xdn
The
-xdn
option
ignores
the
.dfg
file
inside
the
repository
.jar
file
and
sends
the
deployment
package
to
the
server
without
changing
the
property
values.
Export
and
import
of
deployment
configuration
properties
After
deployment
configuration
properties
have
been
created
in
Deployment
Configurator
for
one
server,
you
can
export
those
properties
to
a
file,
and
then
import
that
file
as
the
starting
point
for
the
deployment
configuration
properties
of
another
server.
To
do
so,
right-click
in
a
field
in
the
Property
Name
column,
and
choose
Import.
The
Import
Properties
dialog
appears,
providing
the
following
choices:
v
Overwrite
Property
Descriptor
This
selection
is
the
default.
If
you
use
this
selection,
all
the
server
names,
integration
components,
properties,
and
values
established
in
the
existing
deployment
configuration
file
will
be
removed,
all
the
server
names
and
properties
and
values
established
in
the
file
being
imported
will
be
added.
In
effect,
you
are
replacing
the
entire
content
of
the
original
file
with
the
entire
content
of
the
file
being
imported.
74
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide