Maximo

Maximo

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

 View Only
  • 1.  Message Tracking - Message ID

    Posted Sun November 06, 2022 02:32 AM

    Hi all,

    Does anyone know how 'Message ID' field on 'Message Tracking' application auto-generates the numbers?
    MAXINTMSGTRK.MEAMSGID attribute do not have a sequence associated with it.


    Regards,
    KK

    ------------------------------
    KKunnuthara
    ------------------------------



    #AssetandFacilitiesManagement
    #Maximo
    #MaximoIntegrationandScripting


  • 2.  RE: Message Tracking - Message ID

    Posted Mon November 07, 2022 11:57 AM
    The table has a trigger on it for before insert:  MAXINTMSGTRK_T

    CREATE OR REPLACE TRIGGER MAXIMO.MAXINTMSGTRK_T
    NO CASCADE BEFORE INSERT
    ON MAXIMO.MAXINTMSGTRK
    REFERENCING
    NEW AS N
    FOR EACH ROW
    SET N.ROWSTAMP = NEXTVAL FOR MAXSEQ;

    ------------------------------
    Brandie White
    ------------------------------



  • 3.  RE: Message Tracking - Message ID

    Posted Mon November 07, 2022 11:57 AM
    The Sequence I have is: 

    CREATE OR REPLACE SEQUENCE MAXIMO.MAXINTMSGTRKSEQ
    AS BIGINT
    NO CACHE
    ORDER;





    ------------------------------
    Brandie White
    ------------------------------



  • 4.  RE: Message Tracking - Message ID

    Posted Sun November 13, 2022 06:48 PM
    Edited by System Admin Tue August 22, 2023 04:32 PM


    Thanks @Brandie White

    MAXINTMSGTRKSEQ is linked to MAXINTMSGTRKID attribute.
    What I am looking for is the sequence that is being used for MEAMSGID attribute.


    The issue that I am having is that for some instances, the MEAMSGID is not matching the messageID in the XML.
    See the screenshot below.









    @Steven Shull  @Jason Uppenborn  @Alex Walter any thoughts?



    Regards,




    ------------------------------
    KKunnuthara
    ------------------------------



  • 5.  RE: Message Tracking - Message ID

    Posted Mon January 16, 2023 09:38 PM
    Bumping it up. 
    We are also looking for ways to capture unique transaction ids for each message across source/middleware/target and wanted to use the out of the box field for the same. Has anyone done this. 



    ------------------------------
    RJ
    ------------------------------



  • 6.  RE: Message Tracking - Message ID

    Posted Tue January 17, 2023 08:39 AM
    The message ID we store comes from the JMS provider which gives us the unique identifier it's using to track it. If you want your own identifier you can extract something from the XML using XPath (https://www.ibm.com/support/pages/xpath-syntax-message-tracking). On a lot of tables that are commonly integrated we have a SENDERSYSID & EXTERNALREFID attribute for customers to track these references as well. 

    ------------------------------
    Steven Shull
    ------------------------------



  • 7.  RE: Message Tracking - Message ID

    Posted Fri February 17, 2023 12:56 PM

    Hi Steven,

    has the above setting provided for JSON messages too going through a publish channel ? I know it was working for the xml message, however seems its not working for JSON messages. 

    Is there any other path we have to provide in the message tracking setting in PC?



    ------------------------------
    Subhransu Sekhar Sahoo
    ------------------------------