IBM BJ0NJML Integration Guide - Page 245

Alternate Keys, Required Fields, Specifying an alternate, Persistent Fields

Page 245 highlights

Alternate Keys Specifying an alternate key Required Fields Persistent Fields Nonpersistent Fields Object Structure Creations 3 Repeat the preceding steps for the remaining required objects. Indicate the relationship between those two objects. Define PERSON as the parent to EMAIL and as the parent to SMS. An inbound message normally uses the primary key of an object to look up and process records in the system. However, sometimes a primary key is an internally generated value that is not available to an external system. In such cases, the external system passes an alternate key, and the system uses that value to process the object. To specify an alternate key for your object: 1 Identify the fields that comprise the alternate key and create a unique index on the object. 2 Specify the new index as the alternate key of your object. When you use an alternate key, inbound messages can fail if you change or drop the alternate key index. For example, the primary key of the PERSON object consists of PHONE and EMAIL. The system normally tries to find the PERSON object by using the PHONE and EMAIL values on an inbound message. If the object structure indicates an alternate key, the system uses that value, instead of the primary key, to access the object. The integration framework and the external system exchange a subset of the data columns in the objects within the object structure. Subject to certain restrictions, you can add nonpersistent object structure columns and exclude persistent object structure columns. By default, the system includes in object structures all persistent columns in the component objects. A persistent column is a data field that an object uses to write data to a database table after processing. You can exclude persistent columns that you are not mapping. Only the included persistent columns are written to the XML message for outbound messages. For inbound messages, only the object columns that are included in the object structure are updated. Do not exclude any column that is part of a primary or alternate key. By default, the system excludes most nonpersistent columns in the component objects. A nonpersistent column is a temporary data field that an object uses for calculations or temporary storage. You can include additional nonpersistent columns in the object structure. For example, objects that contain the persistent column DESCRIPTION also contain the nonpersistent column DESCRIPTION_LONGDESCRIPTION. The object structure includes the former persistent column and excludes the latter nonpersistent column. Integration Component Additions and Modifications 231

  • 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

Object Structure Creations
Integration Component Additions and Modifications
231
3
Repeat the preceding steps for the remaining required objects. Indicate the
relationship between those two objects. Define PERSON as the parent to
EMAIL and as the parent to SMS.
Alternate Keys
An inbound message normally uses the primary key of an object to look up and
process records in the system. However, sometimes a primary key is an internally
generated value that is not available to an external system. In such cases, the
external system passes an alternate key, and the system uses that value to process
the object.
Specifying an alternate
key
To specify an alternate key for your object:
1
Identify the fields that comprise the alternate key and create a unique index
on the object.
2
Specify the new index as the alternate key of your object.
When you use an alternate key, inbound messages can fail if you change or drop
the alternate key index.
For example, the primary key of the PERSON object consists of PHONE and
EMAIL. The system normally tries to find the PERSON object by using the
PHONE and EMAIL values on an inbound message. If the object structure
indicates an alternate key, the system uses that value, instead of the primary key,
to access the object.
Required Fields
The integration framework and the external system exchange a subset of the data
columns in the objects within the object structure. Subject to certain restrictions,
you can add nonpersistent object structure columns and exclude persistent object
structure columns.
Persistent Fields
By default, the system includes in object structures all persistent columns in the
component objects. A persistent column is a data field that an object uses to write
data to a database table after processing. You can exclude persistent columns that
you are not mapping.
Only the included persistent columns are written to the XML message for
outbound messages. For inbound messages, only the object columns that are
included in the object structure are updated.
Do not exclude any column that is part of a primary or alternate key.
Nonpersistent Fields
By default, the system excludes most nonpersistent columns in the component
objects. A nonpersistent column is a temporary data field that an object uses for
calculations or temporary storage. You can include additional nonpersistent
columns in the object structure.
For example, objects that contain the persistent column DESCRIPTION also
contain the nonpersistent column DESCRIPTION_LONGDESCRIPTION. The
object structure includes the former persistent column and excludes the latter
nonpersistent column.