IBM Reliable Transport Extension for WebSphere sMash

Overview

The IBM Reliable Transport Extension consists of the following components:

Messaging broker

A messaging broker is a long running application that provides the messaging service to applications performing request processing.

Messaging protocol

This component provides a protocol implementation that allows an application to send and receive messages using the Connection API.

Messaging kicker and receiver

These components allow an application to monitor a queue and perform request processing when a message arrives.

Messaging external client

The external client component allows external applications to communicate with applications through the IBM Reliable Transport Extension.

The following diagram outlines a simple deployment:

1. Application code in app1 uses the Connection API to POST a message to queue1 managed by broker1.
2. The long running application, broker1, hosts the messaging broker and a messaging kicker which is monitoring queue1.
3. When a message has arrived the messaging kicker notifies the messaging receiver in app2 and this reads the message from queue1.
4. The messaging receiver fires an event to allow an onMessage() event handler containing application logic to process the message.

More information

The following topics describe the IBM Reliable Transport Extension in more detail:

• Store-and-forward processing in multiple messaging broker topologies
• Configuring the IBM Reliable Transport Extension for WebSphere sMash
• Using messaging within IBM WebSphere sMash applications
• Broker statistics API
• Using the external client
• Deployment notes and troubleshooting