Open Archive: Server side message archive with support for XEP-0136.

Document created by Stefan Reuter Champion on Sep 4, 2007Last modified by Stefan Reuter Champion on Jan 18, 2008
Version 8Show Document
  • View in full screen mode



Open Archive is a XEP-0136 complient server side message archive for the Openfire XMPP server.


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.


Open Archive requires either MySQL or the embedded HSQLDB, support for other databases might be added at a later point.

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


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.