Configuring the client and server so that a service can be invoked through JMS by a WSIF client application

The ways in which the Web Services Invocation Framework (WSIF) interacts with the Java Message Service (JMS), and the steps you need 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 JMS provider that is embedded in WebSphere Application Server, or another provider such as WebSphere MQ). If not, do so now as described in Choosing a messaging provider.

About this task

Here are the ways in which the Web Services Invocation Framework (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 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.



In this information ...


Related information

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: Sep 20, 2010 10:03:57 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-zos&topic=twsf_prjmscs
File name: twsf_prjmscs.html