WebSphere Message Brokers
File: ae24000_
Writer: Kate Hostler

Task topic

This build: July 31, 2007 21:28:31

Considering performance in the domain

When you design your broker domain, and the resources associated with its components, there are several areas where decisions that you make can affect the performance of your brokers and applications:

Message flows
A message flow includes an input node that receives a message from an application over a particular protocol (for example WebSphere MQ). The message must be parsed, although some parsers support partial parsing which might reduce processing. Other processing in a message flow that might affect performance are the amount, efficiency, and complexity of ESQL, access to databases, and how many message tree copies are made.

You need to consider how you split your business logic; how much work should the application do, and how much should the message flow do? Every interaction between an application and a message flow involves I/O and message parsing and therefore adds to processing time. Design your message flows, and design or restructure you applications, to minimize these interactions.

For more information about these factors, see Optimizing message flow response times.

Messages and message models
The type, format, and size of the messages that are processed can have a significant effect on the performance of a message flow. For example, if you process persistent messages, these have to be stored for safekeeping.

You might need to process message with a well defined structure; if so you can create MRM models for your messages. If you have no need to interrogate the structure, you can work with BLOB messages. If you are working in XML, be aware that it can be verbose, and therefore produce large messages, but XML message content is easier to understand than other formats such as CWF. Field size and order might be important; these factors can be included in your MRM model.

For more information about these factors, see Optimizing message flow response times and Performance considerations for regular expressions in TDS messages.

Broker configuration and domain topology
You can configure your broker domain to include multiple brokers, multiple systems, multiple execution groups, and so on. These can play a part in how message flows perform, and how efficiently messages can be processed.

For more information about these factors, see Optimizing message flow throughput and Performance considerations for Real-time transport.

All these factors are examined in more detail in the Designing for Performance SupportPac (IP04).

For a description of common performance scenarios, review Resolving problems with performance.

For further articles about WebSphere Message Broker and performance, review these sources:

Related concepts
Performance considerations for Real-time transport
Related tasks
Optimizing message flow throughput
Optimizing message flow response times
Resolving problems with performance
Related reference
Performance considerations when using regular expressions
Notices | Trademarks | Downloads | Library | Support | Feedback

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

ae24000_ This topic's URL is: