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.

MDM data model - Repo tables and SQLs to fetch the details

In Informatica Master Data Management (MDM), the "C_REPOS" tables are core repository tables used to store configuration metadata and runtime information for the MDM Hub.

Data Model Repos Tables

C_REPOS_TABLES: Stores metadata about all the tables in the MDM Hub. C_REPOS_COLUMNS: Contains metadata about the columns in each table. C_REPOS_INDEXES: Holds information about indexes created on the tables. SQL:- select * from c_repos_table where type_ind=1; Conditions:- type_ind=1 for Base Object Tables type_ind=2 for Staging Tables type_ind=3 for Internal System Tables type_ind=4 for Lookup Tables type_ind=5 for Cross-Reference Tables To learn more about objects in the ORS Data Model, including Base Object tables and their corresponding columns, data types, and lengths, use the following SQL query. SQL:- select t.table_name, t.display_name, c.column_name, case when c.column_name like '%ROWID_OBJECT%' then 'Rowid_object' else c.display_name end column_display_name, case when c.column_name like '%ROWID_OBJECT%' then 'Y' end pk, c.data_type, c.data_length From c_repos_table t inner join c_repos_column c on t.table_name=c.table_name where t.type_ind=1 order by t.table_name;

Informatica MDM Job Control Tables: Essential SQL Queries for Daily Operations

In Informatica Master Data Management (MDM), the "C_REPOS" tables are core repository tables used to store configuration metadata and runtime information for the MDM Hub.

Job Control Tables:

C_REPOS_JOB_CONTROL:- This table keeps track of information related to batch jobs, including job statuses, execution times, and control parameters: SQL:- select * from c_repos_job_control where run_status=2; Conditions:- Run_Status = 2 --> Batch Job is Processing/Running. Run_Status = 0 --> Batch Job completed successfully. Run_Status = 1 --> Batch Job completed with Errors. Run_Status = 3 --> Batch Job Failed. SQL- If Jobs which are stuck or Interrupted. select * from c_repos_job_control where end_run_date is null and status_Message is null order by start_run_date desc; C_REPOS_JOB_GROUP_CONTROL: This table stores the job runs that are triggered via Batch group job from the Hub Console. SELECT * FROM c_repos_job_group_control ORDER BY start_run_date DESC; C_REPOS_APPLIED_LOCK:- This table is used to manage and store information about locks applied to records during various operations. Column "LOCK_QUERY_SQL" will provide the details on which table lock is applied. select * from c_repos_applied_lock where lock_query_sql like '%C_BO_PRTY%';