If a base object message trigger definition uses a message queue, the

MDM Hub

displays the following message:

The message queue is currently in use by message triggers.

In this case, you cannot edit the properties of the message queue. Instead, you must create another message queue to make the required changes.

The

MDM Hub

installer creates a default JMS queue called

siperian.sif.jms.queue

. If you use this queue when you configure a message trigger, the

MDM Hub

generates an error.

Message triggers apply to just one base object, and they run only when a specific action occurs directly on that base object. If you have two tables that are in a parent-child relationship, you must explicitly define message queues for each table separately. The

MDM Hub

detects specific changes made to a base object, such as load INSERT or PUT. Changes to a record of the parent table can cause a message trigger to run for the parent record only. If changes in the parent record affect associated child records, you must explicitly configure a separate message trigger for the child table.