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:
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.
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.
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:
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ae24000_ |