These topics contain information about planning a service
integration bus topology. This information is intended primarily for
use by solution architects and designers who are in the early stages
of planning a bus topology.
To plan a bus topology, you must consider the following issues:
- How many buses will the topology comprise?
- How will messaging engines and bus destinations be distributed?
- What are the naming conventions for buses, messaging engines,
and other service integration bus resources?
Tip: ![[aug2010]](../../delta.gif)
Each bus name in a cell must be unique. It
is advisable to use unique names for all buses, even when they are
in different cells, because you cannot connect two buses with the
same name. For example, you cannot connect two buses with the same
name in any of the following ways:
- By creating an inter-bus link between two buses with the same
name.
- By attempting to connect to a remote bus from an application running
in a remote cell where a bus with the same name is defined.
- By creating a core group bridge between two cells containing buses
with the same name.
![[aug2010]](../../deltaend.gif)
aug2010
You can find more in depth information about your chosen bus topology
in the following topics.
Remember: Your bus topology might be a combination of
the topologies described in these topics.