8
Using JMS Transport as the Connection Protocol 8-1
8
Using JMS Transport as the Connection Protocol
The following sections provide information about using JMS transport as the connection protocol:
■
Section 8.1, Overview of Using JMS Transport
■
Section 8.2, Using JMS Transport Starting From Java: Main Steps
■
Section 8.3, Using JMS Transport Starting From WSDL: Main Steps
■
Section 8.4, Configuring the Host WebLogic Server Instance for the JMS Transport Web Service
■
Section 8.5, Using the WLJmsTransport JWS Annotation
■
Section 8.6, Using the WLJmsTransport Child Element of the jwsc Ant Task
■
Section 8.8, Invoking a WebLogic Web Service Using JMS Transport
8.1 Overview of Using JMS Transport
Typically, client applications use HTTPS as the connection protocol when invoking a WebLogic Web service. You can, however, configure a WebLogic Web service so that
client applications use JMS as the transport instead.
Using JMS transport offers the following benefits: reliability, scalability, and quality of service. As with Web service reliable messaging, if WebLogic Server goes down while
the method invocation is still in the queue, it will be dealt with as soon as WebLogic Server is restarted. When a client invokes a Web service, the client does not wait for a
response from the invoke, and the execution of the client can continue. Using JMS transport does require slightly more overhead and programming complexity than
HTTPS.
You configure transports using either JWS annotations or child elements of the jwsc Ant task, as described in later sections. When a WebLogic Web service is configured to
use JMS as the connection transport, the endpoint address specified for the corresponding port in the generated WSDL of the Web service uses jms: in its URL
rather than http:. An example of a JMS endpoint address is as follows:
jms:myHost:7001transportsJMSTransport?URI=JMSTransportQueue The URI=JMSTransportQueue section of the URL specifies the JMS queue that has
been configured for the JMS transport feature. Although you cannot invoke the Web service using HTTP, you can view its WSDL using HTTP, which is how the
clientgen is still able to generate JAX-RPC stubs for the Web service.
8-2 Programming Advanced Features of JAX-RPC Web Services for Oracle WebLogic Server
For each transport that you specify, WebLogic Server generates an additional port in the WSDL. For this reason, if you want to give client applications a choice of transports
they can use when they invoke the Web service JMS, HTTP, or HTTPS, you should explicitly add the transports using the appropriate JWS annotations or child elements
of jwsc.
8.2 Using JMS Transport Starting From Java: Main Steps
