WebSphere Message Brokers
File: ac37000_
Writer: Karen Cameron

Task topic

This build: July 31, 2007 21:20:37

Using WebSphere MQ to store state in aggregation nodes

Before you start:

Read the concept topic about message flow aggregation.

To use WebSphere MQ to store state in aggregation nodes, perform the following steps:
  1. Migrate an existing broker or create a new broker.
  2. Configure the broker environment to use WebSphere MQ for aggregation nodes.
When you have performed these steps, aggregation will function as it did before, but you might notice the following differences:
  • Aggregation is much faster.
  • Error messages reflect the use of WebSphere MQ instead of a database table.
  • No control messages are sent between the request flow and the reply flow. If required, you can force a control message to be sent. It is no longer necessary to connect the AggregationControl node control terminal to the AggregationReply node control terminal.
Related concepts
Message flows overview
Message flow aggregation
Related tasks
Migrating a broker for use with aggregation nodes
Configuring a broker environment to use WebSphere MQ for aggregation nodes
Configuring a broker environment to send control messages
Creating a broker
Configuring aggregation flows
Developing message flows
Designing a message flow
Creating a message flow
Defining message flow content
Related reference
AggregateControl node
AggregateReply node
AggregateRequest node
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:20:37

ac37000_ This topic's URL is: