Configuring JMS Message Queues on the Hub Server

Message triggers in Informatica MDM allow the system to automatically generate and send messages based on specific events or conditions. These triggers are configured for base objects within the Hub Console, specifying which events (e.g., insert, update, delete) will initiate the message. They are essential for integrating MDM with other systems, ensuring timely data synchronization and communication across the enterprise. Proper configuration includes creating message queues, setting up triggers, and defining the associated events and columns.

Here’s a step-by-step workflow on how to configure message queues in the Informatica MDM Hub Console:

• Create a Message Queue in App Server(JBOSS)
    Set up a message queue on your application server, Go to Standalone-full.xml and make a entry something like below and bounce the app server

jms-queue name="queue/customqueue" 
      entries="queue/customqueue jboss/exported/queue/customqueue"

• Register the Message Queue
    In the Hub Console, go to the Configuration Workbench ->Message Queue -> register the message queue. use "Test" button to check if queue is successful.
   

• Create the Package
    Go to Model Workbench ->Packages ->Create a Query and Package for the selected base object(e.g.,C_PRTY), Make sure package is enabled Secure under SAM(Security Access Manager).

    

• Select Base Object
    Go to Model Workbench ->Schema ->Choose the base object (e.g., C_PRTY)
• Setup Message Trigger
    Under "Message Trigger Setup," click the plus sign to create a new message trigger.

 
• Configure Message Trigger
    Provide a name for the message trigger, assign the package, and associate the queue.

• Assign Event, System, and Columns
    Select the "Event(Add, Update etc)," "System," and choose columns for the message trigger.

 

• Generate and Deploy SIF APIs
    Go to "Sif Manager" under the Utilities section and select the package and click "Generate and Deploy ORS-Specific SIF APIs."

   

• Save and Restart
    Save the changes and bounce the application server to apply the configuration.

Repo Table to monitor message queue:

C_REPOS_MQ_DATA_CHANGE - This table is used to store information about data changes that are captured for message queues.Column "Sent_state_ind" tells if the message sucessfuly published to the queue or not.

select * from c_repos_mq_data_change where sent_state_ind=1 
order by create_date desc;

If you're looking to see the xml message published to the queue, head over to the C_REPOS_AUDIT table. To view Message queue details, visit C_REPOS_MQ_RULE. You can link this table with C_REPOS_TABLE to obtain comprehensive information such as Rule Name, System, Events, Package name, and more. The join condition is C_REPOS_MQ_RULE.ROWID_TABLE = C_REPOS_TABLE.ROWID_TABLE

Notes:
• Incase if you don't see xml message in C_REPOS_AUDIT table, then follow below steps:
    Go to Utilities workbench --> Audit Manager -->Message Queues
    select "Enable Audit" and "Include XML" options for the queue you are interested.