Use this task to plan a topology that includes WebSphere® MQ.
In addition to the planning that is common to all topologies, planning
issues include the following items:
- The distribution of destinations on different messaging engines
in each bus. You might want to define alias destinations because applications
can use an alias destination to route messages to a target destination
in the same bus or to a foreign bus (including across a WebSphere MQ link to a queue provided by WebSphere MQ). You can also
use alias destinations to manage situations where the difference in
the allowable name length of a bus destination in WebSphere MQ and the allowable name length
of a WebSphere MQ queue
could cause a problem.
- You might want to define foreign destinations so that you can
specify properties for those destinations. If you do not define either
a foreign destination or an alias destination, the properties will
have default settings.
- Which messaging engines should contain a WebSphere MQ link. You can have more than
one messaging engine with a WebSphere MQ
link in a service integration bus. Also, you can have more than one WebSphere MQ link on a single
messaging engine. For example, you might decide to have:
- One WebSphere MQ
link engine with only a sender channel and another WebSphere MQ link engine with only a receiver
channel.
- One WebSphere MQ link
to communicate with each of the gateway queue managers in the WebSphere MQ network.
Although you can have more than one WebSphere MQ link on a single messaging
engine, each WebSphere MQ
link must connect to a different WebSphere MQ
gateway queue manager.
- The broker profile and associated topic mapping settings.
- The security configuration of the topology.