IBM BJ0NJML Integration Guide - Page 97

Element MXPERSON has type MXPERSONType, MXPERSON_PHONEType

Page 97 highlights

Object content Object set content Integration Schemas These elements are referenced in service level schemas and only the MXPERSON and MXPERSONSet can be outside the context of a service level schema. For example, internal applications such as Deployment Manager use schemas comparable to MXPERSON and MXPERSONSet. Integration users must use object structure services within the context of a service level schema. The following content is in the object element: T Element MXPERSON has type MXPERSONType T Complex type MXPERSONType has element PERSON (object name), which has type MXPERSON_PERSONType. T Complex type MXPERSON_PERSONType has elements for all the configured attributes of the PERSON object and elements for the child objects in the object structure (PHONE, EMAIL, and SMS). T Additional objects in the schema have a corresponding complex type like MXPERSON_PERSONType, that defines the PERSON object. Object PHONE EMAIL SMS Type MXPERSON_PHONEType MXPERSON_EMAILType MXPERSON_SMSType The following example shows the structure of the corresponding XML: . . . . . . . For the preceding MXPERSON example, MXPERSONSet replaces the MXPERSON element and MXPERSONSetType replaces the complex type MXPERSONType. Everything else remains the same. Integration XML and Schemas 83

  • 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
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330

Integration Schemas
Integration XML and Schemas
83
These elements are referenced in service level schemas and only the MXPERSON
and MXPERSONSet can be outside the context of a service level schema. For
example, internal applications such as Deployment Manager use schemas
comparable to MXPERSON and MXPERSONSet. Integration users must use
object structure services within the context of a service level schema.
Object content
The following content is in the object element:
Element MXPERSON has type MXPERSONType
Complex type MXPERSONType has element PERSON (object name), which
has type MXPERSON_PERSONType.
Complex type MXPERSON_PERSONType has elements for all the configured
attributes of the PERSON object and elements for the child objects in the
object structure (PHONE, EMAIL, and SMS).
Additional objects in the schema have a corresponding complex type like
MXPERSON_PERSONType, that defines the PERSON object.
The following example shows the structure of the corresponding XML:
<MXPERSON>
<PERSON>
<PHONE>
</PHONE>
.
.
<EMAIL>
</EMAIL>.
.
.
<SMS>
</SMS>
.
.
</PERSON>
</MXPERSON>
Object set content
For the preceding MXPERSON example, MXPERSONSet replaces the
MXPERSON element and MXPERSONSetType replaces the complex type
MXPERSONType. Everything else remains the same.
Object
Type
PHONE
MXPERSON_PHONEType
EMAIL
MXPERSON_EMAILType
SMS
MXPERSON_SMSType