IBM E02HRLL-G Administration Guide - Page 68

B2B Capabilities for partners, Execute

Page 68 highlights

When you run the command line script to start the utility, it obtains the system environment variable JAVA_HOME for this location. If JAVA_HOME is undefined, then the script will prompt for you to enter the home location for Java 5. For example, you can use the copy of Java 5 that is installed for use by WebSphere Application Server. To do this, you would use the value \java. Another system environment variable named MIGRATION_PATH can be set to point to the location where BCGMigrationUtil.zip was extracted. If the MIGRATION_PATH is undefined, then the script will prompt you to enter a path to this directory. The directory that MIGRATION_PATH points to is the directory called bcgmigrate under the directory where the .zip file is extracted. For example, if you want to extract the files to the directory c:\IBM\migration, then you should set MIGRATION_PATH to c:\IBM\migration\bcgmigrate. Note: Ensure that you have Execute file permission for bcgmigrate.bat/ bcgmigrate.sh to run bcgmigrate command. This is applicable for UNIX platform. 3. If you are exporting data, an export options file is required. The export options file specifies what types of data are to be extracted by the utility. Configuration data can be exported for the following items in a system: v Enveloper schedules v Event codes v Transport and operation modes v Handler definitions (metadata only, user-written executable code jar files are transferred manually) v Fixed workflow definitions (metadata only, user-written executable code jar files are transferred manually) v Variable workflow definitions (metadata only, user-written executable code jar files are transferred manually) v Proxy configurations and Envelope profiles v Connection profiles and Validation maps and Transformation maps v FA maps and Receiver instance data v XML document families and formats v Routing definitions (packages, protocols, and document types) v Partner profile data (including contacts, addresses, EDI control number data, and destination data) v B2B Capabilities for partners v Partner connections v Alert notifications v Group configuration v User configuration v FTP user configuration v Certificates v Error flow configuration v System admin properties v Archiver configuration A sample export options file named export.zip is available in the directory migration utility root/samples/export. This file exports all of the supported configuration data types from a system. The options file can be an XML file or 62 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration 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

When you run the command line script to start the utility, it obtains the system
environment variable JAVA_HOME for this location. If JAVA_HOME is
undefined, then the script will prompt for you to enter the home location for
Java 5. For example, you can use the copy of Java 5 that is installed for use by
WebSphereApplication Server. To do this, you would use the value
<
WebSphere
Install Dir
>\java
.
Another system environment variable named MIGRATION_PATH can be set to
point to the location where
BCGMigrationUtil.zip
was extracted. If the
MIGRATION_PATH is undefined, then the script will prompt you to enter a
path to this directory. The directory that MIGRATION_PATH points to is the
directory called
bcgmigrate
under the directory where the .zip file is extracted.
For example, if you want to extract the files to the directory
c:\IBM\migration
,
then you should set MIGRATION_PATH to
c:\IBM\migration\bcgmigrate
.
Note:
Ensure that you have
Execute
file permission for bcgmigrate.bat/
bcgmigrate.sh to run bcgmigrate command. This is applicable for UNIX
platform.
3.
If you are exporting data, an export options file is required. The export options
file specifies what types of data are to be extracted by the utility. Configuration
data can be exported for the following items in a system:
v
Enveloper schedules
v
Event codes
v
Transport and operation modes
v
Handler definitions (metadata only, user-written executable code jar files are
transferred manually)
v
Fixed workflow definitions (metadata only, user-written executable code jar
files are transferred manually)
v
Variable workflow definitions (metadata only, user-written executable code
jar files are transferred manually)
v
Proxy configurations and Envelope profiles
v
Connection profiles and Validation maps and Transformation maps
v
FA maps and Receiver instance data
v
XML document families and formats
v
Routing definitions (packages, protocols, and document types)
v
Partner profile data (including contacts, addresses, EDI control number data,
and destination data)
v
B2B Capabilities for partners
v
Partner connections
v
Alert notifications
v
Group configuration
v
User configuration
v
FTP user configuration
v
Certificates
v
Error flow configuration
v
System admin properties
v
Archiver configuration
A sample export options file named
export.zip
is available in the directory
migration utility root
/samples/export
. This file exports all of the supported
configuration data types from a system. The options file can be an XML file or
62
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide