Example Scenarios

The data model is not important in this situation. The following example shows how ActiveMatrix BusinessWorks, TIBCO MDM, and the TIBCO MDM Adapter work together to add and process a new record in TIBCO MDM.

• A user adds a new record in TIBCO MDM representing a new model of car.
• TIBCO MDM processes and approves this action according to the Business Requirements.
• The last action of the workflow triggers a message that is sent through JMS to the Enterprise Messaging Bus.
• This message is posted onto the EMS server of TIBCO MDM which is bridged out (using EMS scripts) to the data highway.
• An ActiveMatrix BusinessWorks service (using a JMS topic Subscriber) picks the message up and processes it.
• The ActiveMatrix BusinessWorks service adds the new car Model to the SAP-based system. The SAP system requires you to specify the car parts required for the new model.
• After you specify the car parts required for the new model, the bundle of parts is sent back to ActiveMatrix Business Works for insertion into TIBCO MDM.
• The ActiveMatrix BusinessWorks service takes the records from SAP, using the TIBCO MDM Adapter and queries MDM to ensure that the car parts are not already specified.
• The ActiveMatrix BusinessWorks service then formats the SAP-based data so that it fits better with the TIBCO MDM data model. This may involve changes such as naming conventions or combining two data collections together to form a single view.
• The ActiveMatrix BusinessWorks service then uses the Add Record Palette to add the new record into TIBCO MDM. This creates a relationship back to the new car model record.
• TIBCO MDM does not use Business Processes to raise the new work items for new records added from the ActiveMatrix BusinessWorks user. Instead, the ActiveMatrix BusinessWorks service guarantees that all business rules are met.