IBM E02HRLL-G Administration Guide - Page 71

Mapping of XML element with Console, Element name in XML, Console view

Page 71 highlights

For a UNIX system, the invocation is similar, except you use bcgmigrate.sh instead of bcgmigrate.bat. Once the import is completed, the logs are written to the file BCGMigration.log. If the -r option is not specified for an import, then the output will be placed in the directory configured in -f option. For a Windows system, Once the import is completed, the logs are written to the file BCGMigration.log. If the -r option is not specified for an import, then the output will be placed in the directory configured in -f Mapping of XML element with Console The exported file or the file to be imported will be in XML format. The XML elements may not depict the exact name on the console. The following table shows the mapping between console screen and root elements in the XML file. The table contains only the views and element names and not the individual fields on the screen. If the element name is a link in the view, it is represented in italics. Table 9. Map of XML element with Console Element name in XML Console view EnveloperSchedulingInfo Hub Admin > Hub Configuration > EDI > Enveloper. TransportTypeInfo Hub Admin > Hub Configuration > Receivers > Manage Transport Types and Account Admin > Partner > Destinations > Manage Transport Types. DestinationTypeInfo Account Admin > Partner > Destinations > create destination . Operation Mode is represented by DestinationTypeInfo. HandlerInfo Hub Admin > Hub Configuration > Handlers. There are four more sub menus Action, Fixed Workflow, Destination, and Receiver. FixedWorkflowStepInfo Hub Admin > Hub Configuration > Fixed Workflow > Inbound and Hub Admin > Hub Configuration > Fixed Workflow > Outbound. Each step is represented as FixedWorkflowStepInfo. WorkflowInfo Hub Admin > Hub Configuration > Actions. Each Action in the list page is represented as WorkflowInfo EnvelopeProfileInfo Hub Admin > Hub Configuration > EDI > Envelope Profile. Each envelope profile in the list page is represented by EnvelopeProfileInfo. MapInfo Hub Admin > Hub Configuration > Maps > Validation Maps. Each map in the list page is represented as MapInfo. There will be an inner tag routingNameList. It represent the routing object names to which the validation map is linked. TransformMapInfo Hub Admin > Hub Configuration > Maps > Transformation Maps. Each map in the list page is represented as TransformMapInfo. FAMapInfo Hub Admin > Hub Configuration > Maps > FA Maps. Each map in the list page is represented as FAMapInfo. There will be an inner tag routingNameList. It represents the routing object names to which the FA map is linked. Chapter 6. Administering partner migration 65

  • 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

For a UNIX system, the invocation is similar, except you use
bcgmigrate.sh
instead
of
bcgmigrate.bat
. Once the import is completed, the logs are written to the file
BCGMigration.log
. If the
-r
option is not specified for an import, then the output
will be placed in the directory configured in
-f
option. For a Windows system,
Once the import is completed, the logs are written to the file
BCGMigration.log
. If
the
-r
option is not specified for an import, then the output will be placed in the
directory configured in
-f
Mapping of XML element with Console
The exported file or the file to be imported will be in XML format. The XML
elements may not depict the exact name on the console. The following table shows
the mapping between console screen and root elements in the XML file. The table
contains only the views and element names and not the individual fields on the
screen. If the element name is a link in the view, it is represented in italics.
Table 9. Map of XML element with Console
Element name in XML
Console view
EnveloperSchedulingInfo
Hub Admin > Hub Configuration > EDI >
Enveloper.
TransportTypeInfo
Hub Admin > Hub Configuration > Receivers >
Manage Transport Types
and Account Admin >
Partner > Destinations >
Manage Transport Types
.
DestinationTypeInfo
Account Admin > Partner > Destinations >
create
destination
. Operation Mode is represented by
DestinationTypeInfo.
HandlerInfo
Hub Admin > Hub Configuration > Handlers.
There are four more sub menus Action, Fixed
Workflow, Destination, and Receiver.
FixedWorkflowStepInfo
Hub Admin > Hub Configuration > Fixed
Workflow > Inbound and Hub Admin > Hub
Configuration > Fixed Workflow > Outbound.
Each step is represented as
FixedWorkflowStepInfo.
WorkflowInfo
Hub Admin > Hub Configuration > Actions. Each
Action in the list page is represented as
WorkflowInfo
EnvelopeProfileInfo
Hub Admin > Hub Configuration > EDI >
Envelope Profile. Each envelope profile in the list
page is represented by EnvelopeProfileInfo.
MapInfo
Hub Admin > Hub Configuration > Maps >
Validation Maps. Each map in the list page is
represented as MapInfo. There will be an inner tag
routingNameList. It represent the routing object
names to which the validation map is linked.
TransformMapInfo
Hub Admin > Hub Configuration > Maps >
Transformation Maps. Each map in the list page is
represented as TransformMapInfo.
FAMapInfo
Hub Admin > Hub Configuration > Maps > FA
Maps. Each map in the list page is represented as
FAMapInfo. There will be an inner tag
routingNameList. It represents the routing object
names to which the FA map is linked.
Chapter 6. Administering partner migration
65