Using SOAP over JMS to transport web services (deprecated)
You can use the SOAP over Java™ Message Service (JMS) transport protocol as an alternative to SOAP over HTTP for communicating SOAP messages between clients and servers.
Before you begin
A web service must be implemented as an enterprise bean for accessibility through the JMS transport.
About this task
This product supports an emerging industry standard SOAP over JMS protocol. The SOAP over JMS specification provides a standard set of interoperability guidelines for using a JMS-compliant transport with SOAP messages to enable interoperability between the implementations of different vendors. Using this standard, a mixture of client and server components from different vendors can interoperate when exchanging SOAP request and response messages over the JMS transport for both Java API for XML Web Services (JAX-WS) and Java API for XML-based RPC (JAX-RPC) web services. By using the JMS transport, your enterprise beans based web service clients and servers can communicate through JMS queues and topics instead of through HTTP connections.
- Reliable messaging transport for communicating request and response messages.
- Flexible one-way requests for clients and servers. For example, the server does not have to be active when the client sends the one-way request. Simultaneous one-way requests can be sent to multiple servers through the use of a topic.
- Synchronous two-way requests are supported for both Java API for XML-Based Web Services (JAX-WS) and Java API for XML-based RPC (JAX-RPC) clients.
- Asynchronous requests are supported for JAX-WS clients.
The SOAP over JMS specification defines a JMS endpoint URI syntax for specifying JMS destinations. A JMS endpoint URL is used to access JAX-WS or JAX-RPC web services with the JMS transport. This URL specifies the JMS destination and connection factory, as well as the port component name for the web service request. This endpoint URL is similar to the HTTP endpoint URL, which specifies the host and port as well as the context root and port component name.
Procedure
Results
You have a web service that is configured to use SOAP over JMS to transport the requests.
What to do next
Develop a web services client.