Use this task to plan a topology that contains multiple buses.
About this task
In addition to the planning that is common to all topologies, planning
issues include:
- The naming of service integration buses; bus names must be unique.
- How buses are to be linked, that is, directly through a service integration
bus link, or through an indirect link. In an indirect link there may be one
or more intermediate buses. For more information, see Direct and indirect routing between service integration buses. You also need to decide on the transport chain required,
unless you want to use the default basic transport chain.
- Which messaging engines should contain the service integration bus links.
- The distribution of destinations on different messaging engines in each
bus. You may want to define alias destinations which make a destination available
by a different name, on the same bus or a foreign bus. You may also want to
define foreign destinations which enable applications on one bus to directly
access a destination on a foreign bus. If you do not define foreign destinations,
you can configure destination defaults to be used. Alias and foreign destinations
can be combined for further flexibility in your topology. For example:
Use
destination defaults if:
- you have a development environment and want things to work quickly.
- you have an application in which destination names are received at run
time in message body or headers.
Use foreign destinations if:
- you want an environment in which everything is statically defined.
- you need to override destination defaults for a particular (foreign) destination,
for example quality of service settings.
Use an alias destination if:
- you need to change the name of a destination, or move a destination to
another bus, and want existing applications to carry on working regardless.
- you need multiple names for the same destination.
- If necessary, the mapping between topic spaces on the local bus and topic
spaces on foreign buses.
- The security configuration of the topology. Security is clearly very important
when buses in different organizations are connected. You need to decide on
whether connections to a foreign bus are secured with a user ID and password,
and optionally with SSL authentication.