IBM BJ0NJML Integration Guide - Page 125

Message Tracking Configuration, External Message ID

Page 125 highlights

Message Tracking Configuration The following attributes have dynamic values that change based on the transaction events. Attribute Current Status Status Status Date Error Value The most current processing status for the tracked message. The status that is associated with the individual message event in the transaction history. The status date for the individual message event in the transaction history. The error message for the individual error message event in the transaction history. Message Tracking Configuration You can maintain a record of processing actions for messages that are sent through publish channels or that are received from enterprise services. By using the Message Tracking action in the Publish Channels and Enterprise Services applications, you can track messages and perform the following functions: T Enable or disable transaction tracking T Store transaction messages on the application file server T Specify the message data that the Message Tracking application search function uses by using an XPATH expression T Uniquely identify messages with a single ID value by using an XPATH expression T Identify messages with a search ID value by using an XPATH expression The XPATH expressions that are associated with the external message ID values and the search ID values can identify multiple nodes in an XML file. In this case, the message ID and search ID values are registered as a comma-separated list of values. Database field lengths are applicable to external ID and search ID fields. If necessary, you can adjust the length of these fields in the Database Configuration application. External Message ID In the Message Tracking application, you can use the External Message ID attribute to locate specific messages. The syntax that you use to identify the node values should be a fully qualified XPATH expression. When you use the Message Tracking action, you can use an XPATH expression to specify the location of your message identifier in the XML message. To guarantee uniqueness in the messages that are tracked, the integration framework assigns an external message identifier. The system stores the external message identifier as the EXTMSGIDFIELDDATA attribute in the MAXINTMSGTRK table. © Copyright IBM Corp. 2007, 2008 111

  • 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
© Copyright IBM Corp. 2007, 2008
111
The following attributes have dynamic values that change based on the
transaction events.
Message Tracking Configuration
You can maintain a record of processing actions for messages that are sent
through publish channels or that are received from enterprise services. By using
the Message Tracking action in the Publish Channels and Enterprise Services
applications, you can track messages and perform the following functions:
Enable or disable transaction tracking
Store transaction messages on the application file server
Specify the message data that the Message Tracking application search
function uses by using an XPATH expression
Uniquely identify messages with a single ID value by using an XPATH
expression
Identify messages with a search ID value by using an XPATH expression
The XPATH expressions that are associated with the external message ID values
and the search ID values can identify multiple nodes in an XML file. In this case,
the message ID and search ID values are registered as a comma-separated list of
values. Database field lengths are applicable to external ID and search ID fields. If
necessary, you can adjust the length of these fields in the Database Configuration
application.
External Message ID
In the Message Tracking application, you can use the External Message ID
attribute to locate specific messages. The syntax that you use to identify the node
values should be a fully qualified XPATH expression.
When you use the Message Tracking action, you can use an XPATH expression to
specify the location of your message identifier in the XML message. To guarantee
uniqueness in the messages that are tracked, the integration framework assigns
an external message identifier. The system stores the external message identifier
as the EXTMSGIDFIELDDATA attribute in the MAXINTMSGTRK table.
Attribute
Value
Current Status
The most current processing status for the
tracked message.
Status
The status that is associated with the individual
message event in the transaction history.
Status Date
The status date for the individual message event
in the transaction history.
Error
The error message for the individual error
message event in the transaction history.