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 Messaging engine communication
  • 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 may also want to define aliases for authenticating messaging engines and mediations accessing the bus.
  • The bus name. It is advisable to choose bus names that are compatible with the WebSphere® MQ queue manager naming restrictions. You cannot change a bus name after the bus is created, which means that if you need to interoperate with WebSphere MQ in the future, it will be much simpler if you use compatible names. See the topic about WebSphere MQ naming restrictions in the related links.
  • When you name your buses, you must ensure that the names are unique 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.
Bus member configuration
You need to decide which servers, or in the case of some topologies, which clusters to use for 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.
Message store configuration
Each messaging engine has a single message store, which can be either a file store or a data store. See Considerations when choosing between a file store and a data store.

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

If you use a data store, the default database system for the data store is Cloudscape® Version 10.1.x (Derby). However, you might need to use a different system, such as DB2®.

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 Messaging engine communication.
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. See the topic about transactional high availability in the related links.



Related concepts
Planning issues for single-server bus topologies
Planning issues for multiple-server buses without clustering
Planning issues for multiple-server buses with clustering
Planning issues for multiple-bus topologies
Planning issues for topologies that include WebSphere MQ
Bus topologies
Single-server bus
Transactional high availability
Interconnected buses
Multiple-server bus without clustering
Multiple-server bus with clustering
Planning issues for bus topologies
Related reference
WebSphere MQ naming restrictions
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 10:47:11 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-iseries&topic=cjj0025_
File name: cjj0025_.html