Use this task to plan a topology that includes WebSphere MQ.
Why and when to perform this task
In addition to the planning that is common to all topologies, planning
issues include:
- 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 overcome the differences in allowable name length between WebSphere MQ
queues and the WebSphere MQ link.
- Whether foreign destinations are required. A foreign destination is a
type of bus destination that identifies a destination on another bus, and
enables applications on one bus to access directly the destination on another
bus. If you do not define foreign destinations, you can determine the values
that are appropriate for destination defaults.
- 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 may 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.