Configure resources for reliable SOAP messaging

Reliable SOAP messaging is a framework whereby an application running on one application server can reliably invoke a Web Service running on another application server. Reliable is defined as the ability to guarantee message delivery between the two applications.

Reliable SOAP messaging occurs between two application servers that implement the WS-ReliableMessaging specification, such as WebLogic Server. In the case of WebLogic Server, both server instances must be configured with certain JMS resources before an application on one server can reliably invoke a Web Service on the other server. The two WebLogic Server instances can exist within the same domain or different domains.

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 SOAP messaging.

See Using Reliable SOAP Messaging for additional details about creating and invoking a reliable Web Service.

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. If you have not done so, create a persistent store that will be used by the source WebLogic Server to store internal reliable SOAP 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. If you have not done so, 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. If you have not done so, 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.
  Caution: Be sure when you create the SAF agent that you set the Agent Type field to Both to enable both sending and receiving agents.
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. If you have not done so, create a persistent store that will be used by the destination WebLogic Server to store internal reliable SOAP 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. If you have not done so, 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:
  - Targetted to the JMS server, which itself has been targetted 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 SOAP 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. IIf you have not done so, 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.
  Caution: Be sure when you create the SAF agent that you set the Agent Type field to Both to enable both sending and receiving agents.
7. Click the Activate Changes button in the top left corner of the console to activate your changes.

After you finish

Optionally associate a WS-Policy file that contains reliable SOAP messaging policy assertions with the Web Service. See Associate a WS-Policy file with a Web Service.