The JMS providers - Configuring the client and server

 

Before you begin

This topic assumes that you installed a Java Message Service (JMS) provider when you installed WAS (either the JMS provider that is embedded in WebSphere Application Server, or another provider such as WebSphere MQ). If not, install one now as described in Installing and configuring a JMS provider.

 

Overview

To enable a service to be invoked through JMS by a Web Services Invocation Framework (WSIF) client application, complete the following steps:

1. Use the administrative console to create and configure a queue connection factory and a queue destination as described in Configuring resources for the default messaging provider or Configuring JMS resources for a generic messaging provider.

2. Use the administrative console to add the new queue destination to the list of JMS Server destination names for your application server. Ensure that the Initial State is started.

3. Put the JNDI names of the queue destination and queue connection factory, as well as your JNDI configuration, in the WSDL file.

You should also understand the specific ways in which WSIF interacts with JMS:

• Only input JMS properties are supported.

• WSIF needs two queues when invoking an operation: one for the request message and one for the reply. The replyTo queue is by default a temporary queue, which WSIF creates on behalf of the application. We can specify a permanent queue by setting the JMSReplyTo property to the JNDI name of a queue.

• WSIF uses the default values for properties set by the JMS implementation. However in MQSeries and in some other JMS implementations, messages are persistent by default, and the default temporary queue is of type temporary dynamic and cannot have persistent messages written to it. Therefore your JMS listener can fail to write a persistent response message to the temporary replyTo queue.

  Note:

  • If you are using MQSeries, we need to create a temporary model queue that is of type permanent dynamic, then pass this model as the tempmodel of your queue connection factory. This will ensure that persistent messages are written to a temporary replyTo queue that is of type permanent dynamic.

  • If your client is running on an application server that is migrated from WebSphere Application Server V5 to V6, you might get basic authentication errors and therefore need to modify your security settings. For more information see Troubleshooting the Web Services Invocation Framework.

---

 

Related Tasks

Using the SOAP over JMS provider
Using the native JMS provider

 

See Also

WSIFOperation - Asynchronous interactions reference
WSIFOperation - Synchronous and asynchronous timeouts reference

 

Related Information

Java Message Service (JMS) resources

 

---