Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

  • 1.  Issue with Integration Message Tracking Not Triggering When Receiving Service Orders via API

    Posted 06/18/25 01:17 PM

    Hello Team,

    I am facing an issue while using the Maximo REST API to receive service orders.

    When we manually receive a service order via the Maximo UI, an Integration Message Tracking entry gets created as expected. However, when we perform the same operation via API (using the endpoint .../rest/os/MXAPIRECEIPT), no message tracking entry is generated.

    Here is a sample API call I'm making (see attached screenshot for reference):

    • Endpoint: POST /maxrest/os/MXAPIRECEIPT

    • Content-Type: x-www-form-urlencoded

    • Payload includes: ORGID, SITEID, PONUM, POLINENUM, QTYTORECEIVE, etc.

    Despite receiving a 200 OK response and the record getting updated correctly in Maximo, the Integration framework seems to be bypassed, and no tracking message is logged.

    Could you please help me understand:

    • Is there a specific flag or parameter that needs to be passed in the API call to trigger the Integration framework?

    • Is there any configuration or processing class that needs to be enabled or invoked for this behavior?

    • How does the manual receive process differ under the hood compared to the API POST?

    Attached:

    1. Screenshot of the API call

    2. Screenshot showing Message Tracking entry for manual receive

    Thanks in advance!



    ------------------------------
    Rudra Uppe
    ------------------------------


  • 2.  RE: Issue with Integration Message Tracking Not Triggering When Receiving Service Orders via API

    Posted 06/19/25 12:59 AM

    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.



    ------------------------------
    If this post helps, please consider accepting it as a solution to help other members find it more quickly.

    Andrzej Więcław
    Maximo Technical SME
    ZNAPZ B.V.
    Wrocław, Poland
    ------------------------------



  • 3.  RE: Issue with Integration Message Tracking Not Triggering When Receiving Service Orders via API

    Posted 06/19/25 02:44 AM

    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,



    ------------------------------
    Rudra Uppe
    ------------------------------

    Original Message


  • 4.  RE: Issue with Integration Message Tracking Not Triggering When Receiving Service Orders via API

    Posted 06/19/25 06:49 AM

    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.



    ------------------------------
    If this post helps, please consider accepting it as a solution to help other members find it more quickly.

    Andrzej Więcław
    Maximo Technical SME
    ZNAPZ B.V.
    Wrocław, Poland
    ------------------------------

    Original Message


  • 5.  RE: Issue with Integration Message Tracking Not Triggering When Receiving Service Orders via API

    Posted 07/03/25 07:29 AM
    Edited by Kat Jarvis 07/03/25 08:35 AM

    Hi Rudra,

    I completely agree with Andrzej's comments. Additionally, I would suggest checking one more thing - whether the record you're trying to trigger via the integration is being blocked by the event filter. Specifically, the MaximoEventFilter class may be preventing the recurrence.

    You can find more references in these articles - https://medium.com/eamstream/what-is-maximo-recurrence-of-inbound-transactions-and-how-to-use-it-1f50bbf0c5aa

    https://www.ibm.com/support/pages/integration-framework-recurrence-inbound-transactions-using-event-filter-class



    ------------------------------
    Vijayalakshmi Mane
    Technical Consultant
    Bentley Systems Netherlands BV
    sHertogenbosch, The Netherlands
    ------------------------------



Related Content