IBM BJ0NJML Integration Guide - Page 126

Multi-noun Message and External Message ID, Search ID, Multi-noun Message and Search ID

Page 126 highlights

Message Tracking Configuration To find all messages for the MXPERSONInterface enterprise service, create the following fully qualified XPATH expression as the External Message ID: /{http://www.ibm.com/maximo}SyncMXPERSON/@messageID Multi-noun Message and External Message ID When a multi-noun inbound message is received, the integration framework uses the enterprise service External Message ID XPATH to identify the message. If the path expression points to an element included in each one of the nouns in the inbound message, the integration framework creates a multi-noun, commaseparated list of external identifiers. Search ID When you use the Message Tracking action, you can use an XPATH expression to specify the location of an identifier in the inbound XML message. The syntax that you use to identify the node values must be a fully qualified XPATH expression. The nodes that are identified by the XPATH expression let you perform efficient multi-noun searches. The system stores the search identifier in the SEARCHFIELDDATA field in the MAXINTMSGTRK table. To find all messages for the MXPERSONInterface enterprise service, create the following fully qualified XPATH expression as the Search ID: /{http://www.ibm.com/maximo}SyncMXPERSON/{http://www.ibm.com/ maximo}MXPERSONSet/{http://www.ibm.com/maximo}PERSON/{http:// www.ibm.com/maximo}PERSONID Multi-noun Message and Search ID When a multi-noun inbound message is received, the integration framework uses the enterprise service Search ID XPATH to identify the message. If the path expression points to an element included in each one of the nouns in the inbound message, the integration framework creates a multi-noun, comma-separated list of search identifiers. Stored Messages You can save the original message that you receive from an enterprise service or a publish channel definition. The system stores files in the txndata folder in the system global directory. Define the global directory location in the mxe.int.globaldir system property, in the System Properties application. The naming convention of the stored messages is: ExternalSystemName_IntegrationComponent_UniqueId.xml 112 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

Message Tracking Configuration
112
Integration Guide
To find all messages for the MXPERSONInterface enterprise service, create the
following fully qualified XPATH expression as the External Message ID:
Multi-noun Message and External Message ID
When a multi-noun inbound message is received, the integration framework uses
the enterprise service External Message ID XPATH to identify the message. If the
path expression points to an element included in each one of the nouns in the
inbound message, the integration framework creates a multi-noun, comma-
separated list of external identifiers.
Search ID
When you use the Message Tracking action, you can use an XPATH expression to
specify the location of an identifier in the inbound XML message. The syntax that
you use to identify the node values must be a fully qualified XPATH expression.
The nodes that are identified by the XPATH expression let you perform efficient
multi-noun searches. The system stores the search identifier in the
SEARCHFIELDDATA field in the MAXINTMSGTRK table.
To find all messages for the MXPERSONInterface enterprise service, create the
following fully qualified XPATH expression as the Search ID:
www.ibm.com/maximo}PERSONID
Multi-noun Message and Search ID
When a multi-noun inbound message is received, the integration framework uses
the enterprise service Search ID XPATH to identify the message. If the path
expression points to an element included in each one of the nouns in the inbound
message, the integration framework creates a multi-noun, comma-separated list
of search identifiers.
Stored Messages
You can save the original message that you receive from an enterprise service or a
publish channel definition. The system stores files in the txndata folder in the
system global directory. Define the global directory location in the
mxe.int.globaldir system property, in the System Properties application.
The naming convention of the stored messages is:
ExternalSystemName_IntegrationComponent_UniqueId.xml