WebSphere MQ integration overview

The Java™ Message Service (JMS) API enables access to rule services. To use a message-driven rule bean, you must create the necessary resources under the WebSphere® MQ JMS provider. Both the publish-and-subscribe and the point-to-point models are supported.

A Decision Server rule service can be accessed by an asynchronous invocation pattern that uses the Java Message Service (JMS) API. When a JMS message arrives, the EJB container calls a message-driven rule bean (MDB). The MDB can reside locally or remotely from the client application. In turn, the message-driven rule bean calls the rulesets that are running in the execution unit (XU). The real call to the rule engine is delegated to a simple rule session.

In WebSphere Application Server, the client application is the scenario running in WebSphere Application Server that calls the rule service, the server is the application server where Rule Execution Server is installed. Rule Execution Server is usually running remotely to the client application.

To use a Decision Server message-driven rule bean, you must create the necessary resources under the WebSphere MQ JMS provider at the proper scope for both the client and the server side to make them visible for the client application and the Decision Server MDB respectively. Decision Server implements both standards of asynchronous messaging: the Publish-and-Subscribe Model and the Point-to-Point Model. The following procedure demonstrates how to set up both a point-to-point messaging model and a publish-and-subscribe model. If you need only one of them, you can comment out the resource reference in the deployment descriptor of Decision Server MDB.

Before installation, you must create the following resources in WebSphere MQ:

Use these resources to submit rule execution requests and obtain execution results.

You must perform the following tasks to integrate WebSphere MQ in WebSphere Application Server:

  1. Creating the WebSphere MQ queue connection factory
    To create the WebSphere MQ queue connection factory, you create the queue, then you configure the connection factory by following the connection factory wizard.
  2. Creating the WebSphere MQ input queue
    After you have created the WebSphere MQ queue connection factory, you can now create the JMS queue destination for receiving a request message. To do so, you set the scope to node or server level, you select the provider, name the queue, and finally save the configuration.
  3. Creating the WebSphere MQ output queue
    After you have created the input queue for request messages, you must also create the JMS queue destination for sending a response message. To do so, you set the scope to node or server level, select the provider, name the queue, and save.
  4. Creating a topic connection factory
    After you have created the queue factory, input queue, and output queue, you must create a topic connection factory. To do so, you set the scope to node or server, select the provider and JNDI name, enter the connection details, test the connection, and save.
  5. Creating the WebSphere MQ input topic
    After you have created the WebSphere MQ topic connection factory, you can create the JMS topic destination for receiving a request message. To do so, you set the scope to node or server level, select the provider, set the JNDI and input topic names, and save.
  6. Creating the WebSphere MQ output topic
    After you have created the WebSphere MQ topic connection factory and input topic, you must also create the JMS queue destination for sending a response message. To do so, you set the scope to node or server level, select the provider, set the JNDI and output topic names, and save.
  7. Creating the WebSphere MQ queue activation specification
    After you have configured WebSphere MQ queues, you create the queue activation specification.
  8. Creating the WebSphere MQ topic activation specification
    After you have created the queue activation specification, you create the topic activation specification.
  9. Installing the message-driven rule bean
    After you have created the queue and topic activation specifications, you install the Decision Server message-driven rule bean (MDB) in WebSphere Application Server as an enterprise application. To do so, you create a new enterprise application.
  10. Enabling server-wide Last Participant Support
    To complete the integration of WebSphere MQ, you enable Last Participant Support.
Parent topic: Integrating WebSphere MQ in WebSphere Application Server to support asynchronous execution