I tried this procedure from the document link you sent me and it failed miserably using OpenFire 3.4.5. There are still numerous references to wildfire in different files that are being copied over. Even afteer changing referneces of wildfire to openfire it still starts but has errors and starts me over again with setup if I login to the web admin page. After about the first 4 or 5 clicks it bombs with a java error.
I see you updated the post to include links to OpenFire 3.2.0 so I’ll try it now instead of 3.4.5.
I am frustrated enough with the programmer’s apparent lack of giving a damn about people upgrading from older versions that I may dump this software altogether and go with another jabber server product.
Stop the server
Back up setup
Run rpm -ivf openfire_3_3_0.rpm
Go to /opt/openfire and copy configuration from old setup
Copy conf/wildfire.xml and rename it to conf/openfire.xml
Search for org.jivesoftware.wildfire. and replace with org.jivesoftware.openfire. in conf/openfire.xml
If using embedded database then copy and rename embedded-db\wildfire* files to embedded-db\openfire*
Copy new version of plugins to opt/openfire/plugins (except admin folder)
Copy old certificates from resources/security/ to same location in openfire
If running as a service update service to use new scripts located in bin
Start up the server using new launch scripts located in bin
OK I found a copy of 2.5.1 and created a couple test users so I could monkey around with it. It looks like they tweaked the JIVEUSER table to support plain and encrypted passwords somewhere along the line.
This is what worked for me for “importing” users, I haven’t messed with rosters or anything yet.
Setup a clean install of Openfire and run through the configuration wizard and then stop the service - we need to modify the openfire.script later.
Open your wildfire.script in the embedded-db folder and look for “INSERT INTO JIVEUSER VALUES…” entries and copy them to a blank text file.
INSERT INTO JIVEUSER VALUES(‘dummy’,‘password’,‘Dummy Account’,‘email@example.com’,‘001207322786877’,‘001207322786877’)
Then you need to add a “NULL” entry between the password field and the account name field for each user. This NULL is a place holder for encrypted passwords.
Will look like this
INSERT INTO JIVEUSER VALUES(‘dummy’,‘password’,NULL,‘Dummy Account’,‘firstname.lastname@example.org’,‘001207322786877’,‘001207322786877’)
Once all the entries are modified copy them to your openfire.script in the embedded-db folder after the admin entry.
Start Openfire and all your users should be in place. Also once they change their passwords they will be encrypted and the plain text field will be a NULL.
This is a wee bit different than your scenario however, I figured I’d post to help anybody else having these issues. I couldn’t find(or just didn’t see) an answer to this one, so I’ll post it here. I was/am upgrading from WildFire 3.2.x to OpenFire 3.5.2, and when doing a mass user/group import, I kept getting a scheme update error. I noticed in the XML file, it stated . I changed that to and it worked fine.