IBM E02HRLL-G Administration Guide - Page 76

Dependent configuration items, FA Map links

Page 76 highlights

v Proxy configurations v Validation maps v FA Maps v Partners v System admin properties It is important to note that validation maps and FA maps are independent items when considered individually. But to be useful, they have to be linked to routing object definitions in the system. If the routing objects are not imported, the maps might exist in the system without the links. Because this is an indirect dependency, the migration utility can export and import map types without the routing object that refer to them. Dependent configuration items First level dependent items are the configurable items that have dependency on independent items or on one of first level dependent items. The import may either fail or generate unexpected runtime behavior if the dependent items are not imported. The following configuration types are First level dependent items: v Routing objects Routing objects are dependent on import of envelope profile and FA Map. The validation map is imported as a part of routing objects. If the routing objects of the source system has association with any of the profiles or maps, the runtime behavior may not be as expected. If the routing objects of the source system do not have any association with envelope profiles and FA maps, the runtime behavior will be as expected even if the envelope profiles and FA Maps are not imported. v Handlers Transport types v FA Map links FA Map links require FA Map import and routing object import. If the routing objects are not imported, the links will be created with the existing routing objects. If the routing object does not exist, the link will not be created. v Validation map links Validation map links require Validation map import and routing object import. If the routing objects are not imported, the links will be created with the existing routing objects. If the routing object does not exist, the link will not be created v Fixed workflow Handlers v Variable workflow (actions) Handlers v Contacts Partners v Addresses Partners v Control number initialization Partners v XML families and format Routing objects v Destinations Transport types, destination types, and handlers 70 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

v
Proxy configurations
v
Validation maps
v
FA Maps
v
Partners
v
System admin properties
It is important to note that validation maps and FA maps are independent items
when considered individually. But to be useful, they have to be linked to routing
object definitions in the system. If the routing objects are not imported, the maps
might exist in the system without the links. Because this is an indirect dependency,
the migration utility can export and import map types without the routing object
that refer to them.
Dependent configuration items
First level dependent items are the configurable items that have dependency on
independent items or on one of first level dependent items. The import may either
fail or generate unexpected runtime behavior if the dependent items are not
imported. The following configuration types are First level dependent items:
v
Routing objects
Routing objects are dependent on import of envelope profile and FA Map. The
validation map is imported as a part of routing objects. If the routing objects of
the source system has association with any of the profiles or maps, the runtime
behavior may not be as expected. If the routing objects of the source system do
not have any association with envelope profiles and FA maps, the runtime
behavior will be as expected even if the envelope profiles and FA Maps are not
imported.
v
Handlers
Transport types
v
FA Map links
FA Map links require FA Map import and routing object import. If the routing
objects are not imported, the links will be created with the existing routing
objects. If the routing object does not exist, the link will not be created.
v
Validation map links
Validation map links require Validation map import and routing object import. If
the routing objects are not imported, the links will be created with the existing
routing objects. If the routing object does not exist, the link will not be created
v
Fixed workflow
Handlers
v
Variable workflow (actions)
Handlers
v
Contacts
Partners
v
Addresses
Partners
v
Control number initialization
Partners
v
XML families and format
Routing objects
v
Destinations
Transport types, destination types, and handlers
70
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide