Use this task to plan a topology that contains multiple buses.
Why and when to perform 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. 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 link.
- 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, see Configuring destination defaults for a foreign bus.
Alias and foreign destinations can be combined for further flexibility in
your topology.
- 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.