Configurations that include IBM MQ
There are additional points to consider when planning a bus configuration that includes IBM MQ.
We 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. We 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 an IBM MQ queue, might cause a problem.
We might want to define foreign destinations so that we can override the messaging defaults or security settings for specific destinations on a foreign bus. If we do not define either a foreign destination or an alias destination, the destination defaults for the foreign bus will be used.
Remember we can have more than one messaging engine with an IBM MQ link in a service integration bus. We 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 an IBM MQ queue manager or queue-sharing group (known as a "gateway queue manager") in the IBM MQ network.
Although we 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.
Related:
Foreign destinations and alias destinations Bus configurations Interconnected buses Foreign buses Service integration security Direct and indirect routing between service integration buses Bus topology that links to IBM MQ networks Mapping destinations to and from IBM MQ queues, topics, and destinations IBM MQ naming restrictions