Enabling a WSIF client to invoke a Web service through JMS

The ways in which the Web Services Invocation Framework (WSIF) interacts with the Java™ Message Service (JMS), and the steps to take to enable a service to be invoked through JMS by a WSIF client application.

Before you begin

This topic assumes that you chose and configured a JMS provider when you installed WebSphere® Application Server (either the default messaging provider, or another provider such as the WebSphere MQ messaging provider). If not, do so now as described in Choosing a messaging provider.

About this task

Here are the ways in which WSIF interacts with JMS:

To enable a service to be invoked through JMS by a WSIF client application, complete the following steps:

Procedure

  1. Use the administrative console to create and configure a queue connection factory and a queue destination for your chosen messaging provider.

    For more information, see Configuring resources for the default messaging provider, Configuring JMS resources for the WebSphere MQ messaging provider or Managing messaging with a third-party or (deprecated) V5 default messaging provider.

    Note: In WebSphere MQ and some other JMS implementations, messages are persistent by default. The WSIF replyTo temporary queue is of type temporary dynamic by default, which means that your JMS provider cannot write a persistent response message to this queue. If you are using the WebSphere MQ messaging provider, create a temporary model queue that is of type permanent dynamic, then pass this model as the tempmodel of your queue connection factory. This ensures that persistent messages are written to a temporary replyTo queue that is of type permanent dynamic.
  2. Use the administrative console to add the new queue destination to the list of JMS 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 Web Services Description Language (WSDL) file.
  4. Optional: If your client is running on an application server that has been migrated from WebSphere Application Server Version 5, you might get basic authentication errors and therefore have to modify your security settings. For more information see Web Services Invocation Framework troubleshooting tips.



In this information ...


Related concepts

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 7:37:48 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v701sca&product=was-nd-mp&topic=twsf_prjmscs
File name: twsf_prjmscs.html