WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Planning issues common to all bus topologies

Some planning issues apply to all types of service integration bus topology. This topic guides you through the common decisions you must make about your bus topology.

Service integration bus configuration
You need to consider the following:
  • The volume of messages that the bus will handle. Depending on the volume of messages anticipated, you may need to adjust the High message threshold setting for a bus or messaging engine.
  • The transport chain to be used for communication between messaging engines. For more information, see Selecting transport options
  • Whether bus security is required. When bus security is enabled, access to the bus itself and to all destinations on the bus must be authorized. If you enable bus security, you might want to define aliases for authentication of messaging engines and mediations accessing the bus.
Bus member configuration
You need to decide which servers, or in the case of some topologies, which clusters are required as the bus members that host the messaging engines.
Messaging engine configuration
You might need to adjust the High message threshold setting for a messaging engine depending on the volume of messages anticipated.
Data store configuration
By default, the database system for the data store is Cloudscape, but you may need to use a different system such as DB2.

You need to consider the sizes of messages. Larger messages will increase the space a data store requires.

You can select different data store topologies depending on your requirements; for more information see Planning the configuration of a messaging engine to use a data store.

Bus destinations and their configuration
You need to decide on the number and type of destination, mediations, destination routing path, and quality of service for the destination.

For point-to-point messaging you define bus destinations as queues, and for publish/subscribe messaging you define bus destinations as topic spaces. For point-to-point messaging, only you must select one bus member, as the assigned bus member that is to hold messages for the queue. This action automatically defines a queue point for each messaging engine in the assigned member.

You can also define alias destinations to provide a level of abstraction between applications and the underlying target bus destinations. Applications interact with the alias destination, so the target bus destination can be changed without changing the application

The reliability quality of service for messages on a destination has implications for performance and the amount of space required for a data store. Higher levels of reliability impact on performance and increase the space a data store requires because fewer messages are discarded.

You should decide how you want to use the bus destinations because you can configure a bus destination to prevent producers sending messages to the destination, or consumers receiving messages from the destination.

Application environment
An application attaches as a client to a messaging engine on the bus, either by an in-process call or across a network using a remote client. A remote client can run in either the J2EE application client environment or the J2EE application server environment. Various transport chains can be used. You might decide to provide samples for use with an application.
Application connections
The way that a messaging engine is selected, and the mechanism that an application uses to reach it is configured on a JMS connection factory. You need to decide which messaging engines the applications should connect to and on the transport chain to be used. For more information on connection factories, see Configuring resources for the default messaging provider and on transport options, see Selecting transport options.
WebSphere MQ client links
You might want to define WebSphere MQ client links to enable WebSphere Application Server Version 5 JMS clients to use messaging resources on the bus. A WebSphere MQ client link is an optional component of a messaging engine that presents a messaging engine, and thereby the bus, as a WebSphere MQ queue manager to which WebSphere MQ clients can attach.
Transaction logs
You need to plan where transaction logs will be placed.
Related concepts
Bus topologies
Single-server bus
Multiple bus topology
Multiple-server bus without clustering
Multiple-server bus with clustering
Related tasks
Planning a single-server bus topology
Planning a multiple-server bus without clustering
Planning a multiple-server bus with clustering
Planning a multiple-bus topology
Planning a topology that includes WebSphere MQ

Task topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tjj0025_.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)