Interoperability Solutions Guide

Interoperability with JMS

AquaLogic Service Bus is certified against the following JMS implementations:

WebLogic Server 9.0 JMS
IBM WebSphere MQ/JMS 5.3

How to configure proxy services and business services to use the JMS transport is described in the Proxy Services and Business Services sections of the AquaLogic Service Bus Console Online Help.

All of the AquaLogic Service Bus service types support the JMS transport. For information about the AquaLogic Service Bus service types and the transports for each of the service types, see "Selecting a Service Type" in Modeling Message Flow in AquaLogic Service Bus in the BEA AquaLogic Service Bus User Guide.

For information about WebLogic Server 9.0 JMS, see the following resources:

Managing Your Applications in Programming WebLogic JMS
Configure JMS Servers in the WebLogic Server Administration Console Online Help

This section includes the following additional JMS interoperability topics:

Asynchronous Request/Response

For information about designing asynchronous request/response messaging, including the use of the JMS Correlation ID to link the request and response messages, see "Asynchronous Request/Response" in Modeling Message Flow in AquaLogic Service Bus in the BEA AquaLogic Service Bus User Guide.

Naming Guidelines for WebLogic Servers, JMS Servers, and Domains

Unique naming rules apply to all WebLogic Server deployments if more than one domain is involved. Therefore, make sure of the following:

WebLogic Server instances and domain names are unique.
WebLogic JMS server names are uniquely named across domains.
If a JMS file store is being used for persistent messages, the JMS file store name must be unique across domains.

Regarding JMS Server names:

You cannot have duplicate JMS server names within the same domain. If you do, when messages are sent to a destination at a particular JMS server, it is ambiguous as to which server the message should be sent.
If you are using Store and Forward (SAF), having duplicate JMS Server names in different domains does not pose a problem.
In the case of cross-domain communication, having duplicate JMS Server names can be a problem when using the ReplyTo function. For a scenario in which two domains each have a JMS Server with the same name, a ReplyTo message sent from a given domain is returned to the JMS server on the same domain that received the message instead of being returned to the domain that sent the original message.

For more information about configuring and managing WebLogic JMS, see:

Managing Your Applications in Programming WebLogic JMS
Configure JMS Servers in the WebLogic Server Administration Console Online Help

For information about WebLogic Server Domains, see Understanding Domain Configuration.

Specifying the JMS Type for Services

To support interoperability with heterogeneous endpoints, AquaLogic Service Bus allows you to control the content type used, the JMS type used, and the encoding used when configuring message flows. The JMS type can be byte or text. For more information, see "Content Types, JMS Type, and Encoding" in Modeling Message Flow in AquaLogic Service Bus in the BEA AquaLogic Service Bus User Guide.

AquaLogic Service Bus and MQ/JMS Interoperability

For information about AquaLogic Service Bus and MQ/JMS interoperability, see Interoperability with WebSphere MQ.