Skip navigation
2941 Views 6 Replies Latest reply: Jul 2, 2009 1:45 PM by Mike RSS
Mike Bronze 4 posts since
Jun 30, 2009
Currently Being Moderated

Jun 30, 2009 7:42 AM

Monitoring Service (Archiving messages)

We've just installed the OpenFire server and Spark in the IT department (for testing) and hope to roll out to the rest of our divisions very soon. One of the deciding factors for using a new IM solution for our company was the ability to archive messages for later review. The "Monitoring Service" is an outstanding plugin and works flawlessly! However, I have a few questions: How far back will it hold messages? Is there a need to "clean it out" at some point? Our old IM software would let you archive "7 days" or "14 days" worth of messages (any number of days)... then it would clean them off the back end (oldest).

 

I'm using a local database (installed OpenFire on Windows 2003 and used the local database option). I'm just concerned about the size of this message archive once we have nearly 200 users. I am not real familiar with poking around in databases (if that's where I'd need to clean this stuff). Some friendly direction would be greatly appreciated.

 

Thanks!

 

...Mike

  • wroot KeyContributor 7,042 posts since
    Jan 24, 2005
    Currently Being Moderated
    Jul 1, 2009 12:01 PM (in response to Mike)
    Re: Monitoring Service (Archiving messages)

    Nobody else is replying so i will try, but i dont know much about it. I think Monitoring plugin doesnt have any cleaing features, it was designed just to store. So your database will grow until you hit the disk space limits. Probably with the standalone databases like MySQL you can have some exporting options and then deleting older stuff. So i recommend not to use embedded-db if you plan to store such info.

      • wroot KeyContributor 7,042 posts since
        Jan 24, 2005
        Currently Being Moderated
        Jul 2, 2009 1:53 AM (in response to Mike)
        Re: Monitoring Service (Archiving messages)

        Embedded-DB is stored in a text file in a form of INSERTS and database is created from this file on the fly when you launch Openfire. Of course you can stop Openfire, open this file and delete some lines, but it won't be very convenient. I'm not a DB guy, but i think standalone databases has more convenient ways of cleaning. I agree that embedded-db is the easiest way to start, i'm using it myself, but we are just storing our userbase.

    • wroot KeyContributor 7,042 posts since
      Jan 24, 2005
      Currently Being Moderated
      Jul 2, 2009 10:22 AM (in response to Mike)
      Re: Monitoring Service (Archiving messages)

      You can just rerun the setup. Stop the Openfire. Open /conf/openfire.xml and change <setup> tag value to false, save it and start the Openfire again. Then connect to the Admin Console and repeat setup steps. Of course you will have to create your users again with the new database.

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points