Enabling JMS message persistence
When we send messages to a JMS queue, the Message Delivery Mode option controls if a message is guaranteed to be delivered once, and if it is safely stored in the persistent store of the JMS server. There is also a non persistent option, where the messages are stored in memory and may be lost in case of a WebLogic or JMS server failure, or when the WebLogic server is rebooted.
In this recipe, we will set the delivery mode option on a JMS message with the OSB Transport Header action.
Getting ready
For this recipe, we will use a simple OSB project with one proxy and one business service:
You can import the OSB project into Eclipse from \chapter-10\getting-ready\enabling-jms-message-persistence.
How to do it...
In OPEP, perform the following steps:
Navigate to the proxy service Request.
Navigate to the Message Flow tab.
Drag a Transport Header action and drop it on the Request action lane of the Route action.
On the Properties tab of the Transport Header select Outbound...
