Hi Rudra,

message tracking is strictly reserved for asynchronous messages processing which involves queues (JMS, Kafka). So whenever message goes through the queue then you may expect an entry in MAXINTMSGTRK table.

For synchronous messages processing (Web Service and/or REST API calls) you need to rely on a request logging mechanism. In essence there are system properties which you can use to enable requests tracking and storing request/response payloads. All this information becomes available in the REQUESTLOG table. You can read more about this in this tech note.

Hi Andrzej,

Thanks for the clarification regarding the use of MAXINTMSGTRK for asynchronous messages only.

To move forward, I want to ensure that our REST API-based service order receipts are tracked via the REQUESTLOG table as suggested. Could you please let me know the steps/settings required to enable request/response logging in our Maximo system.

Thanks,

Hi Rudra,

message tracking is strictly reserved for asynchronous messages processing which involves queues (JMS, Kafka). So whenever message goes through the queue then you may expect an entry in MAXINTMSGTRK table.

For synchronous messages processing (Web Service and/or REST API calls) you need to rely on a request logging mechanism. In essence there are system properties which you can use to enable requests tracking and storing request/response payloads. All this information becomes available in the REQUESTLOG table. You can read more about this in this tech note.

Hi Rudra,

it's really as simple as setting system property mxe.int.trackrestrequests=1 to get the requests logged and mxe.int.storerestmsg=1 if you would like to store request messages.
Obviously for GET request only the URL (REQUESTLOG.RESOURCEPATH) and parameters  (REQUESTLOG.QUERYPARAMS) are stored, not the response content itself. Request payload gets stored (when enabled) only for PUT/POST requests (REQUESTLOG.MSGDATA).

There is no standard UI to explore the REQUESTLOG content. You need to use SQL client or build it on your own.

IMPORTANT: As clearly specified in the mentioned earlier tech 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.

Hi Andrzej,

Thanks for the clarification regarding the use of MAXINTMSGTRK for asynchronous messages only.

To move forward, I want to ensure that our REST API-based service order receipts are tracked via the REQUESTLOG table as suggested. Could you please let me know the steps/settings required to enable request/response logging in our Maximo system.

Thanks,

Hi Rudra,

message tracking is strictly reserved for asynchronous messages processing which involves queues (JMS, Kafka). So whenever message goes through the queue then you may expect an entry in MAXINTMSGTRK table.

For synchronous messages processing (Web Service and/or REST API calls) you need to rely on a request logging mechanism. In essence there are system properties which you can use to enable requests tracking and storing request/response payloads. All this information becomes available in the REQUESTLOG table. You can read more about this in this tech note.

Hi Andrzej,

I see the option to enable the tracking for specific api routes in Object Structure application in MAS 9.1. https://www.ibm.com/docs/en/maximo-manage/cd?topic=structures-rest-api-route-tracking

However, the payload is not stored for this specific route. Is there a way to store the payload also? Appreciate any feedback.

Thanks

Hi Rudra,

it's really as simple as setting system property mxe.int.trackrestrequests=1 to get the requests logged and mxe.int.storerestmsg=1 if you would like to store request messages.
Obviously for GET request only the URL (REQUESTLOG.RESOURCEPATH) and parameters  (REQUESTLOG.QUERYPARAMS) are stored, not the response content itself. Request payload gets stored (when enabled) only for PUT/POST requests (REQUESTLOG.MSGDATA).

There is no standard UI to explore the REQUESTLOG content. You need to use SQL client or build it on your own.

IMPORTANT: As clearly specified in the mentioned earlier tech 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.

Hi Andrzej,

Thanks for the clarification regarding the use of MAXINTMSGTRK for asynchronous messages only.

To move forward, I want to ensure that our REST API-based service order receipts are tracked via the REQUESTLOG table as suggested. Could you please let me know the steps/settings required to enable request/response logging in our Maximo system.

Thanks,

Hi Rudra,

message tracking is strictly reserved for asynchronous messages processing which involves queues (JMS, Kafka). So whenever message goes through the queue then you may expect an entry in MAXINTMSGTRK table.

For synchronous messages processing (Web Service and/or REST API calls) you need to rely on a request logging mechanism. In essence there are system properties which you can use to enable requests tracking and storing request/response payloads. All this information becomes available in the REQUESTLOG table. You can read more about this in this tech note.

Hi Ritu,

yes, you can store the payload as well but you still need to enable this explicitly (globally, rather than per OS) by setting the mxe.int.storerestmsg system property to true or 1.

Again, just like in my original reply, request payload gets stored (when enabled) only for PUT/POST requests (REQUESTLOG.MSGDATA).

Hi Andrzej,

I see the option to enable the tracking for specific api routes in Object Structure application in MAS 9.1. https://www.ibm.com/docs/en/maximo-manage/cd?topic=structures-rest-api-route-tracking

However, the payload is not stored for this specific route. Is there a way to store the payload also? Appreciate any feedback.

Thanks

Hi Rudra,

it's really as simple as setting system property mxe.int.trackrestrequests=1 to get the requests logged and mxe.int.storerestmsg=1 if you would like to store request messages.
Obviously for GET request only the URL (REQUESTLOG.RESOURCEPATH) and parameters  (REQUESTLOG.QUERYPARAMS) are stored, not the response content itself. Request payload gets stored (when enabled) only for PUT/POST requests (REQUESTLOG.MSGDATA).

There is no standard UI to explore the REQUESTLOG content. You need to use SQL client or build it on your own.

IMPORTANT: As clearly specified in the mentioned earlier tech 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.

Hi Andrzej,

Thanks for the clarification regarding the use of MAXINTMSGTRK for asynchronous messages only.

To move forward, I want to ensure that our REST API-based service order receipts are tracked via the REQUESTLOG table as suggested. Could you please let me know the steps/settings required to enable request/response logging in our Maximo system.

Thanks,

Hi Rudra,

message tracking is strictly reserved for asynchronous messages processing which involves queues (JMS, Kafka). So whenever message goes through the queue then you may expect an entry in MAXINTMSGTRK table.

For synchronous messages processing (Web Service and/or REST API calls) you need to rely on a request logging mechanism. In essence there are system properties which you can use to enable requests tracking and storing request/response payloads. All this information becomes available in the REQUESTLOG table. You can read more about this in this tech note.

Hi Andrzej

We tested this configuration, however, it did not store the payload for the specific api route being tracked.  This may be a bug? 

Hi Ritu,

yes, you can store the payload as well but you still need to enable this explicitly (globally, rather than per OS) by setting the mxe.int.storerestmsg system property to true or 1.

Again, just like in my original reply, request payload gets stored (when enabled) only for PUT/POST requests (REQUESTLOG.MSGDATA).

Hi Andrzej,

I see the option to enable the tracking for specific api routes in Object Structure application in MAS 9.1. https://www.ibm.com/docs/en/maximo-manage/cd?topic=structures-rest-api-route-tracking

However, the payload is not stored for this specific route. Is there a way to store the payload also? Appreciate any feedback.

Thanks

Hi Rudra,

it's really as simple as setting system property mxe.int.trackrestrequests=1 to get the requests logged and mxe.int.storerestmsg=1 if you would like to store request messages.
Obviously for GET request only the URL (REQUESTLOG.RESOURCEPATH) and parameters  (REQUESTLOG.QUERYPARAMS) are stored, not the response content itself. Request payload gets stored (when enabled) only for PUT/POST requests (REQUESTLOG.MSGDATA).

There is no standard UI to explore the REQUESTLOG content. You need to use SQL client or build it on your own.

IMPORTANT: As clearly specified in the mentioned earlier tech 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.

Hi Andrzej,

Thanks for the clarification regarding the use of MAXINTMSGTRK for asynchronous messages only.

To move forward, I want to ensure that our REST API-based service order receipts are tracked via the REQUESTLOG table as suggested. Could you please let me know the steps/settings required to enable request/response logging in our Maximo system.

Thanks,

Hi Rudra,

message tracking is strictly reserved for asynchronous messages processing which involves queues (JMS, Kafka). So whenever message goes through the queue then you may expect an entry in MAXINTMSGTRK table.

For synchronous messages processing (Web Service and/or REST API calls) you need to rely on a request logging mechanism. In essence there are system properties which you can use to enable requests tracking and storing request/response payloads. All this information becomes available in the REQUESTLOG table. You can read more about this in this tech note.