Integrated WebSphere Business Events and WebSphere MQ Low latency messaging

Brief introduction

WebSphere MQ Low Latency Messaging (hereinafter called MQ LLM) is an IBM messaging product that delivers high-capacity, low-latency, reliable messaging on a variety of network architectures, designed to be published in a message-oriented middleware/ Subscription provides a One-to-many data transfer or Many-to-many data exchange. It also enables a combination of extremely high message capacity and millisecond delay requirements. The current version of MQ LLM is designed primarily to meet messaging needs for financial institutions.

In this article, we'll show you how to use the MQ LLM message with the WebSphere Business events (hereinafter called the Business events). The integration of this article is based on the Java Connector Architecture (JCA).

For more information on how Business events interacts with various IBM products, refer to the Business event handling (developerworks,2009 year) series using the WebSphere Business events. This series describes how the Business Events are used by WebSphere Enterprise Service Bus, WebSphere Monitor, WebSphere message Broker, and WebSphere Proce SS-generated messages as events.

Business Scenario

Let's look at an example of a stock exchange that uses algorithmic trading to automatically enter a sell and buy order. In this case, the timing, price, or order quantity is determined by the computer program algorithm. This type of transaction is a common pension or mutual fund and other forms of investment. Transactions are governed by financial rules designed to protect clients, identify and prosecute market misconduct, such as insider trading, that violate relevant laws.

Stock transactions can be automatically traded using MQ LLM, or you can add the Business Events event mode feature to identify any investment and illegal activities in real time. This allows the stock Exchange to act quickly in such cases.

You should consider that MQ LLM is a product dedicated to High-volume messaging, and Business Events are not designed for this scenario. The only way to compensate for this deficiency is to filter all MQ LLM messages using the message selector on the activation specification, sending only messages related to the recognized event pattern to Business events. We will introduce this selection mechanism later. Alternatively, you can filter the MQ LLM message before it is sent to the event mode using the Business events eXtreme Scale.

By pooling the high capacity, low-latency messaging capabilities of MQ LLM, and event pattern recognition for Business event, you can create a compelling solution for the client environment that requires these features.

Big picture

Let's take a look at the architecture-based integration scenario described in the JCA specification. The specification defines a standard contract that allows communication between an enterprise application and an Enterprise information System (EIS) such as an MQ LLM. For details on how to implement this feature, refer to JCA 1.5, part 3rd: Message Inflow (developerworks,2005 year), which describes how to build and configure a resource adapter that can invoke a non-JMS message-driven Bean (MDB) method.

In this article, we will apply this technology to the MQ LLM case. Focus on the steps that are specific to this information system. Figure 1 describes the architecture of our solution:

Figure 1. Business Events ' MQ LLM adapters

We will describe how to build an inbound Java connector adapter that connects the MQ LLM as an asynchronous reliable multicast messaging (RMM) receiver. The configuration of the receiver, including the topic name, is provided by a J2C activation specification defined using the WebSphere management console. We'll show you how to install and configure the application, and how to build an application like this.