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 WebSphere Application Server (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.

Why and when to perform this task

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 JMS provider resources.
  2. Use the administrative console to add the new queue destination to the list of JMS Server destination names for your application server as described in Managing JMS servers on Application Server (not part of a deployment manager cell) or Managing JMS servers in a deployment manager cell. 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:


Related tasks
Using the JMS providers
Using the SOAP over JMS provider
Using the native JMS provider
Related reference
WSIFOperation - Asynchronous interactions reference
WSIFOperation - Synchronous and asynchronous timeouts reference



Searchable topic ID:   twsf_prjmscs
Last updated: Jun 21, 2007 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/twsf_prjmscs.html

Library | Support | Terms of Use | Feedback