IBM E02HRLL-G Administration Guide - Page 70

Example command for export, is the debug level from 1 to 5 where 5 provides the most debug output.

Get IBM E02HRLL-G - WebSphere Partner Gateway Express PDF manuals and user guides View all IBM E02HRLL-G manuals
Add to My Manuals
Save this manual to your list of manuals

Page 70 highlights

Note: The user should either belong to Hubadmin group or another group under Operator that has the migration module permission enabled. If you issue the script with no arguments, a help prompt is displayed with the required arguments and syntax. The command line invocation syntax for Windows is as follows: bcgmigrate [-h hostname:bootstrap_port] [-a import|export] [-f filename with path] [-u userid] [-p password] [-r root_path [-o] [-d 1..5] ] For a UNIX system, the invocation is similar, except you use bcgmigrate.sh instead of bcgmigrate. Legend: v -h is the hostname:bootstrap port where the console component is running v -a is the activity (which can be either import or export). By default, it is export. v -f is the fully qualified file name of the export option file or the import configuration file. v -u is the WebSphere Partner Gateway user ID that has migration permission v -p is the WebSphere Partner Gateway user password v -o is the overwrite option Note: The overwrite option is only used by the import activity. If you do not include -o then only new configurations are created and existing configuration data is not changed. Including -o means existing configuration may be overwritten if they are different within the imported data. v -d is the debug level from 1 to 5 where 5 provides the most debug output. The -d argument is optional and can be omitted. If it is omitted, only errors are logged. v -r is the root path where exported data is stored and the log file is written. The -r argument is optional and can be omitted. If it is omitted, exported data is written under the directory specified by the -f option. Example command for export The following is an example command for export on a Windows system: bcgmigrate -h localhost:58809 -a export -f D:\partnerMigration\export.xml -u hubadmin -p admin123 -r d:\partnermigration\output -d 5 For a UNIX system, the invocation is similar, except you use bcgmigrate.sh instead of bcgmigrate.bat and directory path has forward slash. The output for the example is saved under the root directory specified by the -r option. The output is written to a .zip file named BCGMigration_.zip. Logs are written to the file BCGMigration.log. If the -r option is not specified for an export, then the output will be placed in the directory configured in -f option. Example command for import The following is an example command for import on a Windows system: bcgmigrate.bat -h localhost:58809 -a import -f D:\partnerMigration\BCGMigration_localhost.zip -u hubadmin -p admin123 -r d:\partnermigration\output -d 5 64 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
Note:
The user should either belong to Hubadmin group or another group under
Operator that has the migration module permission enabled.
If you issue the script with no arguments, a help prompt is displayed with the
required arguments and syntax.
The command line invocation syntax for Windows is as follows:
bcgmigrate [-h hostname:bootstrap_port] [-a import|export] [-f
filename with path
]
[-u
userid
] [-p
password
] [-r
root_path
[-o] [-d 1..5] ]
For a UNIX system, the invocation is similar, except you use
bcgmigrate.sh
instead
of
bcgmigrate
.
Legend:
v
-h
is the hostname:bootstrap port where the console component is running
v
-a
is the activity (which can be either import or export). By default, it is export.
v
-f
is the fully qualified file name of the export option file or the import
configuration file.
v
-u
is the WebSphere Partner Gateway user ID that has migration permission
v
-p
is the WebSphere Partner Gateway user password
v
-o
is the overwrite option
Note:
The overwrite option is only used by the import activity. If you do not
include
-o
then only new configurations are created and existing configuration
data is not changed. Including
-o
means existing configuration may be
overwritten if they are different within the imported data.
v
-d
is the debug level from 1 to 5 where 5 provides the most debug output. The
-d
argument is optional and can be omitted. If it is omitted, only errors are
logged.
v
-r
is the root path where exported data is stored and the log file is written. The
-r
argument is optional and can be omitted. If it is omitted, exported data is
written under the directory specified by the
-f
option.
Example command for export
The following is an example command for export on a Windows system:
bcgmigrate -h localhost:58809 -a export -f D:\partnerMigration\export.xml
-u hubadmin -p admin123 -r d:\partnermigration\output -d 5
For a UNIX system, the invocation is similar, except you use
bcgmigrate.sh
instead
of
bcgmigrate.bat
and directory path has forward slash.
The output for the example is saved under the root directory specified by the
-r
option.
The output is written to a .zip file named
BCGMigration_<
IP or host name
provided in -h option
>.zip
. Logs are written to the file
BCGMigration.log
. If the
-r
option is not specified for an export, then the output will be placed in the
directory configured in
-f
option.
Example command for import
The following is an example command for import on a Windows system:
bcgmigrate.bat -h localhost:58809 -a import
-f D:\partnerMigration\BCGMigration_localhost.zip -u hubadmin -p admin123
-r d:\partnermigration\output -d 5
64
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide