<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Monitoring Plugin Readme</title>
<style type="text/css">
BODY {
font-size : 100%;
}
BODY, TD, TH {
font-family : tahoma, verdana, arial, helvetica, sans-serif;
font-size : 0.8em;
}
H2 {
font-size : 10pt;
font-weight : bold;
}
A:hover {
text-decoration : none;
}
H1 {
font-family : tahoma, arial, helvetica, sans-serif;
font-size : 1.4em;
font-weight: bold;
border-bottom : 1px #ccc solid;
padding-bottom : 2px;
}
TT {
font-family : courier new;
font-weight : bold;
color : #060;
}
PRE {
font-family : courier new;
font-size : 100%;
}
#datatable TH {
color : #fff;
background-color : #2A448C;
text-align : left;
}
#datatable TD {
background-color : #FAF6EF;
}
#datatable .name {
background-color : #DCE2F5;
}
</style>
</head>
<body>
<h1>
Monitoring Plugin Readme
</h1>
<h2>Overview</h2>
<p>
The monitoring plugin adds support for chat archiving and server statistics to
Openfire. It provides support for generating various reports on the server
statistics, as well as managing, viewing, and reporting on chat logs.
</p>
<p>As of version 1.3 this plugin combines Stefan Reuter's
<a href="https://blogs.reucon.com/srt/tag/open_archive/">Open Archive</a> plugin
to provide XEP-0136 automated archiving and message retrieval for one-to-one and MUC chat.
Starting with 1.4.6 version it also supports newer XEP-0313: Message Archive Management protocol.</p>
<h2>Installation</h2>
<p>
Copy monitoring.jar into the plugins directory of your Openfire installation.
The plugin will then be automatically deployed. To upgrade to a new version,
copy the new monitoring.jar file over the existing file.
</p>
<h2>Upgrading from Enterprise</h2>
<p>
If you are upgrading from the Enterprise plugin, and wish to keep your old
statistics and logs, you will need to manually run some database scripts to
perform the migration. Note, if you don't care about your previous
statistics and chat logs, you don't have to worry about these steps.
</p>
<p>
First, you will need to shut down your Openfire server and remove the
enterprise plugin. To do this, perform the following steps:
<ol>
<li>Shut down your Openfire server</li>
<li>Remove the <b>enterprise.jar</b> file and the <b>enterprise</b> directory from the plugins directory in your Openfire install root</li>
<li>Install this plugin, <b>monitoring.jar</b> by copying it into the plugins directory.</li>
<li>At this point, you will need to start up Openfire and let it extract and install the <b>monitoring</b> plugin. You can watch for this to occur by looking under the Plugins tab in the Openfire admin console. Once it appears in the list, continue to the next step.</li>
<li>Shut the server back down again.</li>
<li>Go into your plugins/monitoring/database directory. There you will see
some scripts prefixed with <b>import_</b>. Log into your database, switch
to the Openfire's database as you configured during setup (you can find
this information in conf/openfire.xml if you don't remember it), and run
the script that matches the database you are using. Note that the embedded
database is hsqldb and you can use the script in bin/extra from the Openfire
install root (bin/extra/embedded-db-viewer.sh or
bin/extra/embedded-db-viewer.bat, depending on whether you are using Windows)
to access your embedded database.</li>
<li>Once the script has completed, you can start Openfire back up and all of your settings should be the way they were when you were running the Enterprise plugin.</li>
</ol>
</p>
<h2>Configuration</h2>
<p>
Chat archiving is enabled by default. However, only information about
who is communicating and at what time is stored unless chat transcript
archiving is enabled. To enable chat transcript archiving or group chat
archiving, you will need to log into the admin console and go to:<br />
Server --> Archiving --> Archiving Settings
</p>
</body>
</html>