Up to Discussions in Openfire Support

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (5 pts)
1,691 Views 2 Replies Last post: Jun 4, 2009 10:26 AM by jefferai RSS
Bronze
Tom Callahan
3 posts since
Nov 14, 2006
Currently Being Moderated

Apr 15, 2008 10:58 AM

Migrate from JabberD 1.4 to Openfire..help?

I've been searching for tips or ways to migrate from the spool based JabberD 1.4 to OpenFire, and have come up dry so far. Does anyone have any scripts or insights they have found on ways to migrate your users, contact lists, etc from JabberD 1.4 to Openfire?

 

Thanks,

Tom Callahan

Tags: openfire, migrate, jabberd, 1.4, convert
Benjamin Reed Bronze
Benjamin Reed
1 posts since
Jul 23, 2008
Currently Being Moderated
Jul 23, 2008 3:14 PM in response to: Tom Callahan
Re: Migrate from JabberD 1.4 to Openfire..help?

I was looking for a way to do this as well, and came to the conclusion that no one had written something to do it, so I did so myself.  =)  I'm attaching it to this response.

 

It will convert a jabber spool directory into an XML file compatible with the "User Import Export" plugin for OpenFire.  Just run:

 

  ./convert-jabber-spool.pl /var/lib/jabber > /tmp/openfire.xml

 

You'll need the XML::Twig and Tie::IxHash perl modules through CPAN or your distribution.

 

The spool format is missing email address and name, (I just set name to the username), and I stubbed out most of the presence stuff in the roster bits, but I was able to get users/passwords/etc. imported into a jabberd -> openfire migration with this, and all seems to work.

Attachments:
jefferai Bronze
jefferai
1 posts since
Jun 4, 2009
Currently Being Moderated
Jun 4, 2009 10:26 AM in response to: Benjamin Reed
Re: Migrate from JabberD 1.4 to Openfire..help?

I found that the script as posted has a number of drawbacks:

 

* doesn't carry over the 'name' attribute

* doesn't carry over the 'email' attribute

* doesn't handle the multiple locations where passwords might be located

 

This was producing output that openfire was barfing on as invalid, because the schema requires at least username and password attributes.  So I reworked the script, and it's posted below.  Hope it helps someone.

Attachments:

More Like This

  • Retrieving data ...

Bookmarked By (0)