IBM Support

Configure IBM Stewardship Center with MQ as the Messaging Engine

Technical Blog Post


Abstract

Configure IBM Stewardship Center with MQ as the Messaging Engine

Body

 

Author: Geetha S Pullipaty

Product: Infosphere Master Data Management.
Component: Data Stewardship and Governance.
Version: 11.5.0

Other prerequisite software: IBM Business Process Manager 8.5.6 , IBM Process Designer 8.5.6, IBM Stewardship Center 11.5.0 installed and configured.

 

Communication from MDM to BPM for IBM Stewardship Center is always via messaging.  In case of some specific events happening on MDM, the events are to be notified to BPM to create a new task. BPM can only listen to messages that are put in its event queue. To make this possible we create a link between MDM and BPM. MDM can be installed with MQ as messaging provider. BPM suggests to use only WAS default messaging provider. To be able to send messages a Customer needs to do these steps

  1. Configuration steps on MQ associated with MDM installation.
  2. Configuration steps on WAS Admin console associated with MDM installation.
  3. Configuration steps on WAS Admin console associated with BPM installation.

Configuration steps on MQ using MQ explorer

1. Create a new Sender channel under the Queue manager that is default created for MDM. installation.

image

 

 2.Create a Receiver channel  under the Queue manager that is default created for MDM.

image

 

Channel name : Could be anything. In our setup we named it BPMReceiver.

Transmission protocol : TCP

3. Create a local queue with usage type as Transmission under the Queue manager that is default created for MDM.

 

image

 

Queue name : Service Integration Bus name of BPM. In our setup the SIBus name of BPM server is BPM.ProcessCenter.Bus hence the same given.

Scope : Queue manager

Usage : Transmission

4. Create a remote queue under the Queue manager that is default created for MDM.

 

image

 

 

Queue name : Could be anything. In our setup we named it EVENTRQ.

Remote queue manager : Service Integration Bus name of BPM. In our setup the SIBus name of BPM server is BPM.ProcessCenter.Bus hence the same given.

Transmission queue : Same name as given for the queue name in previous step. It is same as Service integration bus name of BPM. In our setup it is “BPM.ProcessCenter.Bus”.

Remote queue : Destination name for which messages are to be sent on BPM Service Integration bus. Check for destination name that starts with eventqueueDestination in the list of destinations under SIBus for BPM Server.

image

 

5.  Start channels created on step 1 and step 2.  Sender channel created in step 1 should be in running state.

This completes list of steps to be done on Websphere MQ Explorer. Now we will see the list of steps to be done on MDM and BPM installations.

Configuration steps on Administrative Console of WAS where MDM is installed.

1. Create a new Queue Connection Factory with following details.

image

 

  1. Navigate to Resources -> JMS - >Queue Connection Factories. Select New to create a new one.
  2. Create it at the same scope as existing Queue Connection Factories.
  3. Select JMS resource provider : WebSphere MQ messaging provider
  4. Name : MDMBPMQueueConnectionFactory
  5. JNDI name : notification/MDMBPMQueueConnectionFactory
  6. Select ‘Enter all the required information into this wizard’
  7. Queue manager or queue sharing group name: Name of the Queue Manager that gets created from MDM installation. In our setup it is QM.E001
  8. Hostname:  Hostname of the MQ machine where this MQ is running and Queue managers are created by MDM installation. In our setup it is localhost.
  9. Port: Port number where this Queue manager created by MDM installation is listening. In our setup it is 1414.

2. Create a new Queue with following details

image

 

  1. Navigate to Resources -> JMS - >Queues . Select New to create a new one.
  2. Create it at the same scope as existing Queues.
  3. Select JMS resource provider : WebSphere MQ messaging provider
  4. Name : MDMBPMQueue
  5. JNDI name : notification/MDMBPMQueue
  6. Queue name : It should be same as the remote queue name created in previous section in step 4. In our setup it is EVENTRQ.
  7. Queue manager or Queue sharing group name : Name of the Queue Manager that gets created from MDM installation. In our setup it is QM.E001.
  8. Save all and restart WAS for these configurations to take effect.

Configuration steps on Administrative Console of WAS where BPM is installed

1.Create a new foreign bus connection to the existing Service Integration Bus of BPM.

 

image

 

  1. Navigate to Service integration > Buses > BUS_NAME > Foreign bus connections -> New
  2. Bus connection type : Direct connection
  3. Foreign bus type : WebSphere MQ
  4. Messaging engine to host the connection : Leave the default one listed.
  5. Virtual queue manager name: Name of the SIBus of BPM. In our setup it is BPM.ProcessCenter.Bus
  6. Foreign bus name: Name of the Queue Manager that gets created from MDM installation. In our setup it is QM.E001
  7. MQ link name : Could be anything. In our setup we gave it as MDM_BPM_LINK
  8. Enable Service integration bus to WebSphere MQ message flow : Select this checkbox if not already done.
  9. WebSphere MQ receiver channel name : Name of the receiver channel created on step 2 of section 1 in this document. In our setup it is BPMRECEIVER
  10. Hostname:  Hostname of the MQ machine where the MQ associated with MDM is running and Queue managers are created by MDM installation. In our setup it is localhost.
  11. Port: Port number where the Queue Manager of MQ created by MDM installation is listening. In our setup it is 1414.
  12. Enable WebSphere MQ to Service integration bus message flow : Select this checkbox if not already done.
  13. WebSphere MQ sender channel name: Name of the sender channel created on step 1 of section 1 in this document. In our setup it is BPMSENDER
  14. SIB inbound user ID : An admin user id who have the ability to put messages to BPM Queue. This could be a default admin user that gets created with BPM installation. In our setup it is “admin”.
  15. Save all and restart WAS for these configurations to take effect.

 

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSWSR9","label":"IBM InfoSphere Master Data Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

UID

ibm11142164