Messaging engine file store

Here’s my first post of a series looking at some of the new functionality in WebSphere Application Server Version 6.1 that has come out of the Hursley Development Lab, in particular in the area of the service integration bus.

One of the most of obvious change is the addition of a new persistence mechanism: the file store. In Version 6.0, the messaging engine data store used JDBC to store persistent messages and transactional data (amongst other things) in to a database. There were a couple of issues with this. Firstly, even for non-transactional, non-persistent messaging, it meant configuring a database and, secondly, the out-of-the-box performance with the default Cloudscape database was not great.

In Version 6.1, the default is to use a proprietary flat file in much the same way as WebSphere MQ. Although almost three times faster than using Cloudscape, the best performance can still be obtained by offloading processing to a remote DB2 instance. It may also be preferable to still use a database for other reasons such as high availability and backup and recovery.

One Response to “Messaging engine file store”

  1. […] Can I just take a moment to point my more technically-inclined readers to the weblog of one of my colleagues, David Currie – he’s posting some storming content right now on WebSphere Messaging, WAS 6.1, JMS clients… he’s a bit of a WAS and ESB guru, so if you have an interest in these topics, his blog is seriously worth reading! Technorati tags: WebSphere, JMS, messaging, IBM […]