Before you begin
You must install a Web service before you can configure SOAP over JMS transport. See Install a Web service.
Note: This section applies to JAX-WS Web services only.
Typically, Web services and clients communicate using SOAP over HTTP/S as the connection protocol. You can, however, configure a WebLogic Web service so that client applications use JMS as the transport.
Using SOAP over JMS transport, Web services and clients communicate using JMS destinations instead of HTTP connections, offering 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 handled as soon as WebLogic Server is restarted. When a client invokes a Web service, the client does not wait for a response, and the execution of the client can continue. Using SOAP over JMS transport does require slightly more overhead and programming complexity than HTTP/S.
For more information about using SOAP over JMS transport, see "Using SOAP Over JMS Transport" in Developing JAX-WS Web Services for Oracle WebLogic Server.
The following steps describe how to configure SOAP over JMS transport:
Note: Web services are deployed as part of an Enterprise application, Web application, or EJB. To understand how Web services are displayed in the Administration Console, see View installed Web services.