Configure the SOAP over JMS transport for JAX-WS web services

Subtopics

• SOAP over JMS protocol
  The web services engine supports the use of an emerging industry standard SOAP over Java Message Service (JMS)-compliant messaging transport as an alternative to HTTP for communicating SOAP messages between clients and servers.
• JMS endpoint URL syntax
  As part of an emerging industry-standard SOAP over JMS protocol, a Java Message Service (JMS) endpoint URL syntax has been defined. 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.
• IBM proprietary SOAP over JMS protocol (deprecated)
  Use a SOAP over JMS transport as an alternative to HTTP for communicating SOAP messages between clients and servers. The web services engine supports the use of an IBM proprietary implementation as well as the industry standard implementation.
• IBM proprietary JMS endpoint URL syntax (deprecated)
  A Java Message Service (JMS) endpoint URL is used to access JAX-WS or JAX-RPC web services with the JMS transport. This proprietary URL specifies the Java Message Service (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.

• Invoking web service requests transactionally using SOAP over JMS transport
  Use the enableTransactionalOneWay property to ensure that one-way and two-way asynchronous web service requests using the industry standard SOAP over JMS transport will be sent to the destination queue or topic transactionally.

• Invoking one-way JAX-RPC web service requests transactionally using the JMS transport (deprecated)
  Use the enableTransactionalOneWay property to ensure that one-way JAX-RPC web service requests using the IBM proprietary JMS transport will be sent to the destination queue or topic transactionally.

• Configure SOAP over JMS message types
  We can configure your SOAP over Java Message Service (JMS) request or response messages to use either BytesMessage or TextMessage objects.