This section contains a description of the processing in each of the use cases which are used to characterise the performance of IBM Integration Bus v10

Use case Description
Aggregation Measures the performance of an integration solution that splits an incoming XML message into 4 messages, and then performs a four message aggregation using the Aggregation nodes that are supplied with IBM Integration Bus
Coordinated request-reply Measures the performance of an integration solution that communicates through the use of WebSphere MQ messages in a request/reply processing pattern
Large messaging Measures the performance of an integration solution that processes messages that contain repeating structures and writes each repeating instance as a separate WebSphere MQ message while minimising overall memory requirements
Message routing Measures the performance of an integration solution that routes messages to WebSphere MQ queues, based on cached data stored in a database
Transforming a message Measures the performance of an integration solution that transforms a message by using ESQL
SOAP Provider Measures the performance of an integration solution that receives a SOAP request and responds with a SOAP message
SOAP Consumer Measures the performance of an integration solution that receives a SOAP over HTTP request message, makes a synchronous call to an external service provider, and delivers a reply message
File out and File in Measures the performance of an integration solution that handles files either in the middle of a flow or to initiate a transformation
ISO8583 Transformation Measures the performance of an integration solution that handles an ISO8583 message over TCPIP, communicating to a back-end application through the use of WebSphere MQ messages
Restful API Measures the performance of an integration solution that provides a Restful API to a more complex SOAP interface

Join The Discussion

Your email address will not be published. Required fields are marked *