Interoperability Solutions for JMS

ALSB Interoperability with JMS

Overview of JMS Interoperability

Asynchronous Request-Response Messaging

Using SOAP-JMS Transport

Interoperating with BEA WebLogic Server 9.x and 10.0

Configuring the Response Queues for Cross-domain JMS Calls

Interoperating with BEA WebLogic Workshop 8.1

Interoperating with BEA WebLogic Server 8.1

Naming Guidelines for Domains, WebLogic, and JMS Servers

Specifying the JMS Type for Services

WSDL-Defined SOAP Fault Messages

Interoperability with WebSphere MQ

Understanding Message ID and Correlation ID Patterns for JMS Request/Response

Overview of JMS Request-Response and Design Patterns

Patterns for Messaging

JMS Message ID Pattern

JMS Correlation ID Pattern

Comparison of Message ID and Correlation ID Patterns

Interoperating with JAX-RPC over JMS

Invoking a JAX-RPC Web Service Using the JMS Message ID Pattern

Invoking a JMS Request-Response Proxy Service from a JAX-RPC Client

JMS Message ID Pattern Examples

Example 1: An MQ Service Uses a JMS Message ID as a Correlator of the Request-Response Message

Example 2: A JAX-RPC Client with ALSB Proxy Service

Example 3: ALSB as a Client of a WebLogic Server JAX-RPC Request/Response Service

Using the JMS Transport

Configuring Proxy Services using JMS Transport Protocol

Transport Headers

Configuring Transport Headers

Configuring Business Services using JMS Transport Protocol

Error Handling