Multi-Noun Message And External Message Id; Search Id; Multi-Noun Message And Search Id; Stored Messages - IBM BJ0NJML - Service And Asset Management Integration Manual

Message Tracking Configuration

Multi-noun Message and External Message ID

Search ID

Multi-noun Message and Search ID

Stored Messages

112
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
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.
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
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.
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
Integration Guide