WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

► WebSphere Application Server V5 default messaging provider
The WebSphere Application Server V5 default messaging provider is
supported for migration purposes only.
10.4 Messaging topologies: How can I use messaging?
Choosing a topology depends largely on the answers to questions about the
topology of the application and your own messaging requirements. Some of the
more important questions are as follows:
► What is the topology of my application?
► Can I break it up into logical parts that can be separately deployed?
► Which parts need to communicate with which others?
► Are there natural divisions within the application that are autonomous,
needing separate communication channels?
► Does my application need to communicate with external systems?
► Do I need to balance the messaging workload for each part?
► Are there any critical parts that need to have high availability?
► Will I need application server clustering, or do I have it already?
The following sections outline what topology best fits your needs (depending on
the answers to the previous questions). In most cases, the topology will not be
clear cut because there will be many different ways to implement a messaging
application. However, the simpler, the better.
Note: This section provides a high-level look at messaging topologies,
focusing on the default messaging provider. Before designing anything, even
the simplest topology for messaging, it is important that you understand how
the default messaging provider handles messages.
340 WebSphere Application Server V7.0: Concepts, Planning, and Design