Isode R14.4: Audit Database - switch to full JDBC operation
This one of a series of a messages describing new features in Isode R14.4, scheduled to ship in April 2009. You can see all of the messages on this blog relating to R14.4 by clicking on this link
Isode's audit database is used to hold message audit information, derived from M-Switch audit logs on one or more servers.
The audit database supports Isode management tools that provide statistics, message tracking, and quarantine management. Although some tools use JDBC, others are specific to the Postgres database.
R14.4 contains a significant upgrade to our audit database integration and tools, so that all of our tools and components access the audit database using JDBC. We continue to support Postgres, but the Isode products are now essentially independent of Postgres.
In a future release, we plan to support an additional simple SQL database that we will bundle with the Isode release. This will be ideal for demonstrations and evaluations.
We may support additional SQL databases. Because of minor variations of JDBC between database implementations, careful testing with any databases that we choose to support is vital, and we will need to run copies at Isode for effective support. Because of this, we will need to consider carefully which of the many available databases we support. Our choice of databases will primarily be driven by the requirements of Isode customers.