Administration Console Online Help

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.

Configure the source WebLogic Server instance:
1. Invoke the Administration Console for the domain in which the source WebLogic Server is running.
2. Click the Lock & Edit button in the top left corner of the console to enable changes to the WebLogic Server configuration.
3. Create a persistent store that will be used by the source WebLogic Server to store internal reliable messaging information. Target the persistent store to the source WebLogic Server instance. For details, see Create file stores or Create JDBC stores, depending on the type of persistent store you want to create.
4. Create a JMS server that uses the persistent store you created in the preceding step. Target this JMS server to the source WebLogic Server instance. For details, see Create JMS servers.
5. Create a Store-and-Forward (SAF) agent that uses the persistent store you created in a previous step. Target the SAF agent to the source WebLogic Server instance. For details, see Create Store-and-Forward agents.
  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.
6. Click the Activate Changes button in the top left corner of the Console to activate your changes.
Configure the destination WebLogic Server instance by following these steps:
1. Invoke the Administration Console for the domain in which the destination WebLogic Server is running.
2. Click the Lock & Edit button in the top left corner of the console to enable changes to the WebLogic Server configuration.
3. Create a persistent store that will be used by the destination WebLogic Server to store internal reliable messaging information. Target the persistent store to the destination WebLogic Server instance. For details, see Create file stores or Create JDBC stores, depending on the type of persistent store you want to create.
4. Create a JMS server that uses the persistent store you created in the preceding step. Target this JMS server to the destination WebLogic Server instance. For details, see Create JMS servers.
5. Create a JMS module, of type 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.
6. Create a Store-and-Forward (SAF) agent that uses the persistent store you created in a previous step. Target the SAF agent to the destination WebLogic Server instance. For details, see Create Store-and-Forward agents.
  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.
7. Click the Activate Changes button in the top left corner of the console to activate your changes.
To enable and configure Web service reliable messaging at the Web service endpoint (port) level:
1. In the left pane of the Administration Console, select Deployments.
2. In the right pane, navigate within the Deployments table until you find the Web service for which you want to view the configuration.
  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.
3. In the Deployments table, click the name of the Web service.
4. Select Configuration > Ports, then click the name of the Web service endpoint that you want to configure.
5. Select the Reliable Messaging tab.
6. Click Customize Reliable Message Configuration.
7. Set the reliable messaging properties, as required.
8. Click Save.

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.

Administration Console Online Help

Configure Web service reliable messaging