Openfire (java) Plug-in Mod
My company is using Openfire 3.6.4 as an internal server to manage our XMPP/Jabber communications. We have it set so
that all messages are archived in a database presently, but need to adjust the archiving so that all conversations
are exported to an email address vs. just being stored in the database.
Openfire is open sourced and there is an existing plug-in published that does a majority of the work that is needed.
What we are looking for is someone who is comfortable with the level of java used to build this project that can take a little time to develop the plug-in we need. Delivery of the finished product will be as a plug-in that can be installed to our build.
Please read the description below. If you are interested in taking on this project, please respond with a proposal for how long it will take and compensation desired.
—————————————–
Purpose:
Provide the ability to export archived conversations from an Openfire XMPP Server (www.igniterealtime.com) as
individual SMTP email messages.
Environment:
1 – OpenFire Server 3.6.4
2 – Monitoring Service Plug-in 1.1
3 – Java
4 – MySql
Proposed Method :
OpenFire is a fully functional Jabber/XMPP server and it keeps records of all conversations in a MySql database.
The Monitoring Service plug-in provides a framework for the majority of the work that needs to be done.
Under the Archiving tab that allows you to search the database for conversations, there is a facility that assembles
the individual chats from the MySql database and formats them in a structured way. Upon checking on an individual
conversation, there is a function that will allow you to view the content of a chat as a pdf.
Taking advantage of this existing plug-in we want to modify it so that in place of exporting individual messages to a
pdf, we instead email them to a pre-defined email address, as well as being to trigger this action in bulk for a range
of messages.
We will also need to add a new table that will keep track of whether a message has been exported to email or not. This
table will employ the PK of conversationID as a reference and track date of last export and email address exported to.
The plug-in will need to have two operational modes:
1 – manual
Employ the search feature of the Monitoring Service plug-in and allow for the results to either be emailed one by one
upon clicking them (export to mail will replace ‘view as pdf’), or the entire found set can be emailed.
Upon a batch email out, each unique conversationID will be matched to an individual email.
2 – scheduled
The plug-in needs to have the ability to be triggered daily at a specified time to export all un-flagged conversations
that have been generated.
Finally the plug-in needs to be written as a self contained module and in to the framework of an openfire plug-in. Any
database adjustments need to be kept separate from the overall schema (i.e. …. adding tables preferred over adding
fields to existing tables)