Configurations that include IBM MQ

There are additional points to consider when planning a bus configuration that includes IBM MQ.

You might want to define alias destinations to map bus and destination names to targets where the bus name, or the destination name (identifier), or both, are different. You can also use alias destinations to manage situations where the difference in the name length that is allowed for a bus destination in WebSphere® Application Server and the name length that is allowed for a IBM MQ queue, might cause a problem.

You might want to define foreign destinations so that you can override the messaging defaults or security settings for specific destinations on a foreign bus. If you do not define either a foreign destination or an alias destination, the destination defaults for the foreign bus will be used.

Remember you can have more than one messaging engine with a IBM MQ link in a service integration bus. You can also have more than one IBM MQ link on a single messaging engine. There are many possible configurations, for example:
  • One IBM MQ link engine with only a sender channel and another IBM MQ link engine with only a receiver channel.
  • One IBM MQ link to communicate with a IBM MQ queue manager or queue-sharing group (known as a "gateway queue manager") in the IBM MQ network.

Although you can have more than one IBM MQ link on a single messaging engine, each IBM MQ link must connect to a different gateway queue manager.


Icon that indicates the type of topic Concept topic



Timestamp icon Last updated: March 5, 2017 17:24
File name: cjj_mq_configs.html