IBM BJ0NJML Integration Guide - Page 110

Location of Interface Tables, Names of Interface Tables, Interface Queue Tables

Page 110 highlights

Location of Interface Tables Location of Interface Tables The endpoint definition for an external system or a publish channel points to the database where its interface tables are stored. The database can be a local database or a remote database. The predefined interface table endpoint (MXIFACETABLE) points to the local database, and you can add endpoints for remote databases. Names of Interface Tables The integration framework registers interface table names to an enterprise service or a publish channel. You must configure the object structure that is associated with the enterprise service or publish channel to support flat files. The Support Flat Structure check box must be selected on the object structure. Default names for interface table are not provided. The following guidelines apply names for interface tables: T Publish channels and enterprise services that use the same object structure can use the same interface table name or different interface table names. T Publish channels and enterprise services that use a different object structure must use different interface table names. Interface Queue Tables The interface queue tables identify the sequence in which a receiving system should process the records in the respective interface tables. Two queue tables exist, one for inbound transactions and the other for outbound transactions. Interface Queue Table MXOUT_INTER_TRANS MXIN_INTER_TRANS Direction Outbound Inbound Some transactions depend on the successful processing of a previous transaction. For example, a PO record for an employee must be processed before the PO receipt record. The receiving system must process the records in the same sequence in which the sending system created the records. All inbound and outbound transactions must have a record that is inserted into the corresponding inbound or outbound queue table. This record contains a unique sequential identifier called TRANSID, which is a value that identifies the interface table to which the transaction data is written. The corresponding interface table uses the TRANSID value to identify the record or records that are associated with the transaction. You can identify the contents of a transaction by looking up all the records with a given TRANSID value in the corresponding interface table. 96 Integration 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
  • 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

Location of Interface Tables
96
Integration Guide
Location of Interface Tables
The endpoint definition for an external system or a publish channel points to the
database where its interface tables are stored. The database can be a local
database or a remote database.
The predefined interface table endpoint (MXIFACETABLE) points to the local
database, and you can add endpoints for remote databases.
Names of Interface Tables
The integration framework registers interface table names to an enterprise service
or a publish channel. You must configure the object structure that is associated
with the enterprise service or publish channel to support flat files. The Support
Flat Structure check box must be selected on the object structure.
Default names for interface table are not provided. The following guidelines
apply names for interface tables:
Publish channels and enterprise services that use the same object structure
can use the same interface table name or different interface table names.
Publish channels and enterprise services that use a different object structure
must use different interface table names.
Interface Queue Tables
The interface queue tables identify the sequence in which a receiving system
should process the records in the respective interface tables. Two queue tables
exist, one for inbound transactions and the other for outbound transactions.
Some transactions depend on the successful processing of a previous transaction.
For example, a PO record for an employee must be processed before the PO
receipt record. The receiving system must process the records in the same
sequence in which the sending system created the records.
All inbound and outbound transactions must have a record that is inserted into
the corresponding inbound or outbound queue table. This record contains a
unique sequential identifier called TRANSID, which is a value that identifies the
interface table to which the transaction data is written. The corresponding
interface table uses the TRANSID value to identify the record or records that are
associated with the transaction. You can identify the contents of a transaction by
looking up all the records with a given TRANSID value in the corresponding
interface table.
Interface Queue Table
Direction
MXOUT_INTER_TRANS
Outbound
MXIN_INTER_TRANS
Inbound