IBM has added capability to to track synchronous messages starting latest version 7.6.1.1
In previous versions provided message tracking capabilities for asynchronous messages.
Those services are Enterprise services and Publish Channels associated with external systems using JMS queues.
The new functionality provides the capability to track web service requests, Rest calls and HTTP requests.
This would help troubleshooting and reprocessing messages and better error handling for synchronous processing.
Below steps are involved to set up required system properties :
Synchronous message tracking is enabled in the Maximo System Properties application.
The set of properties enables message tracking for each request type. You set the value to 1, save the changes, then perform a live refresh. The default value is 0 (disabled).
mxe.int.trackrestrequests - Track rest api request
mxe.int.tracksoaprequests - Track soap synchronous request
mxe.int.tracksynchttprequests - Track xml-http synchronous request
mxe.int.tracksoaprequests - Track soap synchronous request
mxe.int.tracksynchttprequests - Track xml-http synchronous request
The next set of properties determine if message details will be stored in the database. You set the value to 1, save the changes, then perform a live refresh. The default value is 0 (disabled).
mxe.int.storerestmsg - store sync http messages from MIF
mxe.int.storesoapmsg - store sync soap messages for tracking from MIF
mxe.int.storesynchttppmsg - store sync http messages from MIF
mxe.int.storesoapmsg - store sync soap messages for tracking from MIF
mxe.int.storesynchttppmsg - store sync http messages from MIF
Note enabling message tracking of asynchronous requests will have a negative impact on performance and should only be enabled if message volume is low. Further isolating these properties to the specific servers or clusters that will receive tracked requests using the maximo.properties file should considered to reduce the impact to users.
ReferenceMaximo Rest Message Tracking :