WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Linking a WSIF service to a JMS-provided service

The JMS providers enable a WSIF service to be invoked through JMS.

Why and when to perform this task

The Java Message Service (JMS) is an API for transport technology. The mapping to a JMS destination is defined during deployment and maintained by the container.

The JMS destination endpoint for a Web service can be realized in any of the following ways:

The JMS destination endpoint must respect the interaction model expected by the client and defined by the WSDL. It must return a response if one is required.

When the JMS destination endpoint creates the JMS response message the following rules must be followed:

The client does not see any of these headers. The container receives the JMS message and (for SOAP over JMS) removes the SOAP message to send to the client.

What to do next

See also the following topics:




Sub-topics
Linking a WSIF service to a SOAP over JMS service
Linking a WSIF service to a service provided at a JMS destination
The JMS providers - Configuring the client and server
JMS message header: The TimeToLive property reference

Related tasks
Linking a WSIF service to a SOAP over HTTP service
Linking a WSIF service to a local Java application
Linking a WSIF service to a service implemented as an enterprise bean
Linking a WSIF service to the underlying implementation of the service

Task topic    

Terms of Use | Feedback

Last updated: Dec 11, 2005 4:07:15 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/twsf_prjms.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)