Currently it supports automated message archiving and message retrieval through XEP-0136 compliant Jabber clients and a web UI for the administrator. Support for manual archiving and preferences is planned for future releases.
Update: Now we also support PostgreSQL and you can find a MSSQL DDL snippet in the comments below.
To install the plugin just rename it to archive.jar, place it into the plugins folder of your Openfire server and enable it in the Openfire console at Server Settings/Archive Settings.
The plugin is available at http://maven.reucon.com/projects/public/archive/
License: GNU General Public License, Version 2.0
If you are looking for compliance features see the Enterprise Edition which also includes support from Jive Software.
Why am I getting duplicates of all conversations?
In contrast to the archiving feature of the Enterprise Edition that is targeted at archiving logs for compliance Open Archive is user centeric. Open Archive stores all conversations with a reference to a local user that owns the record. Users are allowed to retrieve and manage all conversations that they own.
This model results in a conversation between two local users to be stored twice because each of the users owns one copy of the conversation.
You can think of Open Archive as a server side implementation of the "history" that your Jabber clients usually store locally.
Why am I not getting correct localized texts in the admin UI but "???property???" instead?
Rename the plugin jar file to archive.jar before deploying it.