Using JMS file persistence
JMS is a candidate SOA Suite endpoint destination, either for consumption or production of messages. WebLogic also provides JMS resources for SOA Suite Event Delivery Network, reliable Web Service Messaging, or for bridging to SOA Suite service hosting tiers such as Oracle Service Bus.
In this recipe, we'll configure WebLogic's JMS resources to use file-based persistence over database persistence.
Getting ready
You will need to have Oracle SOA Suite 11g installed on a server as we'll be working in the area configured for the default JMS Persistence Stores used by SOA Suite.
How to do it…
The following steps will allow us to configure JMS persistence to use a file store:
Open the SOA Suite WebLogic administration console and log in as administrator. If you have issues locating the console, see steps 1 and 2 in the Tuning global transactions recipe in Chapter 6, Platform Tuning.
Navigate to the Persistent Stores section by performing either of the following actions:
Click...
