+

Search Tips   |   Advanced Search

 

Configure 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 JMS, and the steps take to enable a service to be invoked through JMS by a WSIF client application. This topic assumes that you installed a JMS provider when you installed WAS (either the JMS provider that is embedded in WAS, or another provider such as WebSphere MQ). If not, install one now as described in Installing and configuring a JMS provider.

 

Overview

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 console to create and configure a queue connection factory and a queue destination.

    This task is described in Configure resources for the default messaging provider or Configuring JMS resources for a generic messaging provider.

  2. Use the console to add the new queue destination to the list of JMS Server destination names for your appserver. 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.


 

Related tasks


Linking a WSIF service to a JMS-provided service

 

Related Reference


Example: Writing the WSDL extension that enables your WSIF service to access a SOAP over JMS service
Example: Writing the WSDL extensions that enable your WSIF service to access an underlying service at a JMS destination
WSIFOperation - Asynchronous interactions reference
WSIFOperation - Synchronous and asynchronous timeouts reference

 

Related information


Messaging_resources3206.html