This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, go to

Guaranteed Delivery

This section explains, through an example scenario, how the Guaranteed Delivery EIP can be implemented using the ESB profile of WSO2 EI. The following topics are covered:

Introduction to Guaranteed Delivery

The Guaranteed Delivery EIP ensures safe delivery of a message by storing it locally and transmitting it to the receiver's data store. Even when the receiver is offline, the EIP ensures that the message goes through when the receiver comes online. For more information, go to Guaranteed Delivery.

Figure 1: Guaranteed Delivery EIP

Sample scenario

This example is a stock quote service where a stock quote request is sent to a specific endpoint when the receiver is offline. An Axis2 server acts as the receiver. The ESB profile stores the request message in a JMS message store provided by the ESB profile. In this scenario a Message Broker acts as the JMS message store. Here, the Message Broker can either be the Message Broker profile of WSO2 EI or ActiveMQ. 
The ESB profile periodically checks whether the receiver is online using a Message Forwarding Processor and delivers the message to the endpoint when the receiver comes online.

The existing sample expalins connecting to MB or activeMQ as a store. Since this is a sample we are using a inmemory message store.

The diagram below depicts how to simulate the example scenario using the ESB profile.

Figure 2: Example Scenario of the Guaranteed Delivery EIP

Before digging into implementation details, let's take a look at the relationship between the example scenario and the Guaranteed Delivery EIP by comparing their core components.

Guaranteed Delivery EIP (Figure 1)Guaranteed Delivery Example Scenario (Figure 2)
SenderStock Quote Client
StoreMessage Store
ReceiverStock Quote Service Instance

Setting up the environment

  1. Download and install the ESB profile of WSO2 Enterprise Integrator (EI). For a list of prerequisites and step-by-step installation instructions, go to Installing the Product in WSO2 EI Documentation.
  2. Start an instance of Sample Axis2 server. For instructions, go to Starting the Axis2 server in WSO2 EI Documentation.
  3. Deploy the back-end service SimpleStockQuoteService. For instructions on deploying sample back-end services, go to Deploying sample back-end services in WSO2 EI Documentation.
  4. Start the Message Broker profile of WSO2 EI (or ActiveMQ). For instructions, go to Starting the Message Broker profile in WSO2 EI Documentation.
  5. Start the ESB profile and log in to its Management Console. For instructions, see Starting the ESB profile in WSO2 EI Documentation.
  6. In the Management Console, navigate to the Main menu and click Source View in the Service Bus section. 
  7. Click the required tab based on the Message Broker you are using, and then copy and paste the relevant configuration to the source view.

Simulating the sample scenario

  1. Stop the Axis2 server instance.
  2. Execute the following command to send a message to the ESB profile requesting a stock quote using the Stock Quote Client:
    ant stockquote -Dtrpurl=http://localhost:8280/services/GuaranteedDeliveryProxy
    For information on the Stock Quote Client and its operation modes, go to Stock Quote Client in the WSO2 EI Documentation.
  3. Start the Axis2 server instance. Observe in the server Console that the message that you sent when it was offline is now successfully delivered.

When you send the first request with the Axis2 server started the output is as follows:

Axis2 server: :: Generating quote for : IBM

ESB Console: 

LogMediator Standard :: Stock price = $147.72637392119628

When you shut down the Axis2 Server the ESB Console shows this (no other output in other consoles)

INFO - ScheduledMessageProcessor Successfully deactivated the message processor [GuaranteedProcessor]

Axis2client will get

org.apache.axis2.AxisFault: The input stream for an incoming message is null.

Becuase by adding FORCE_SC_ACCEPTED we respond to the clint immediately with empty body

Send a few requests while the Axis2 server is shut down. Then, restart the Axis2 server and activate the message processor via the Management Console the output are as follows:

You need to activate the message processor because when the Axis2 server is shut down, it retries for 4 attempts as defined by maxdeliveryattempts property, and then deactivates the message processor.

You view the responses for all the requests you sent while the Axis2 server was shut down:

Tue Nov 14 19:04:50 IST 2017 :: Generating quote for : IBM

Tue Nov 14 19:04:51 IST 2017 :: Generating quote for : IBM

Tue Nov 14 19:04:52 IST 2017 :: Generating quote for : IBM

ESB Console output:

[2017-11-14 19:04:50,854] [EI-Core]  INFO - LogMediator Standard :: Stock price = $164.73457775331943

[2017-11-14 19:04:51,421] [EI-Core]  INFO - LogMediator Standard :: Stock price = $174.99872641177635

[2017-11-14 19:04:52,417] [EI-Core]  INFO - LogMediator Standard :: Stock price = $178.85450091915658

How the implementation works

Let's investigate the elements of the configuration in detail. The line numbers below are mapped with the configuration above.

  • proxy [line 2 in config] - This service allows you to abstract the routing logic from the client. Whatever the request is, the client sends it only to the exposed service. 
  • inSequence [line 6 in config] -  When the service is invoked through the client, this sequence receives the message and sends it to the routing logic.
  • sequence [line 17 in config] - The sequence mediator defines a sequence block, callable by its key (defined in the name attribute). 
  • enrich [line 20 in config] - The enrich mediator processes messages based on the source configuration and performs the action on the target configuration. 
  • store [line 35 in config] - Saves the message using the message store defined by the name JMS Store. 
  • messageStore [line 49 in config] - Defines the message store to use and the parameters used to connect to the message store. In this example, the connection is made to an external JMS store. 
  • messageProcessor [line 56 in config] - Defines the message processing algorithm to use, the period of time to retry sending messages in case of a failure, and the maximum number of retry attempts.