Reducing memory usage in WebSphere Business Integration Message Broker

Splitting large messages using ESQL in WebSphere Business Integration Message Broker

From the developerWorks archives

Dominic Storey

Date archived: July 8, 2017 | First published: May 25, 2005

Messages are routed and transformed by message flows within WebSphere Business Integration Message Broker. As a message passes through the message flow, it is manipulated by message processing nodes typically using a language called Extended Structured Query Language. The message is in the form of a message tree, which is created from the input message bitstream, and serialized into an output bitstream, by a parser. There are several parsers supplied by the broker, the most common being Message Repository Manager, XML and XML namespaces.

When you handle large messages within the WebSphere Business Integration Message Broker, memory used for storing the message tree and parsing time can become expensive if you use the wrong techniques.

This article provides a proven method by which you can quickly and efficiently parse a large message and propagate out smaller messages in a sequence. Memory usage is also addressed so that the minimum of physical resource is used during a parse. The method described is suitable for use with the Message Repository Manager, XML and XML namespaces parsers.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Middleware
ArticleID=83864
ArticleTitle=Reducing memory usage in WebSphere Business Integration Message Broker
publish-date=05252005