![]() ![]() ![]() ![]() |
Note: This topic applies to JAX-RPC Web services only.
Web service reliable messaging is a framework that enables an application running on one application server to reliably invoke a Web service running on another application server, assuming that both servers implement the WS-ReliableMessaging specification. Reliable is defined as the ability to guarantee message delivery between the two Web services in the presence of software component, system, or network failures.
WebLogic Web services conform to the WS-ReliableMessaging (February 2009) specification, which describes how two Web services running on different application servers can communicate reliably. In particular, the specification describes an interoperable protocol in which a message sent from a source endpoint (or client Web service) to a destination endpoint (or Web service whose operations can be invoked reliably) is guaranteed either to be delivered, according to one or more delivery assurances, or to raise an error.
For more information about creating and invoking reliable Web services, see Using Web Services Reliable Messaging.
The following procedure describes the high-level main steps for configuring the source WebLogic Server instance (which hosts the application invoking the reliable Web service) and the destination WebLogic Server instance (which hosts the reliable Web service) for reliable messaging. It also describes how to customize the reliable messaging configuration at the Web service endpoint level.
Note: Be sure when you create the SAF agent that you
set the Agent Type field to Both
to
enable both sending and receiving agents. The SAF agent should
be targeted to only non-migratable targets.
Queue
, with the
following characteristics:
- Targeted to the JMS server, which itself has been targeted to the destination WebLogic Server instance.
- If your reliable Web service uses the default Web services
JMS queue, set the JNDI name to
weblogic.wsee.DefaultQueue
. If your Web service
uses the @BufferQueue
JWS annotation to specify
a different JMS queue from the default, enter its JNDI name in
the JNDI name field.
Note: If you are using the reliable messaging feature in a cluster, you must still create a local queue rather than a distributed queue. In addition, you must explicitly target this queue to each server in the cluster.
Note: Be sure when you create the SAF agent that you
set the Agent Type field to Both
to
enable both sending and receiving agents. The SAF agent should
be targeted to only non-migratable targets.
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.
After you finish
Attach a WS-Policy file that contains reliable messaging policy assertions with the Web service. See Attach a WS-Policy file to a Web service.
![]() |