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.
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.
The following steps will allow us to configure JMS persistence to use a file store: