I need to import or export from Jive Messager 2.3.1. How do I do that?
Do you need to import/export it as a way to update to a latest Wildfire version? If you are planning to update to Wildfire then you may skip this step and just back up the database and your conf/messenger.xm file. These are the steps we described to perform an upgrade:
Steps for upgrading Jive Messenger to Wildfire
The following document identifies the steps that an admin should follow in order to upgrade an existing Jive Messenger installation to Wildfire 2.4.0.
Stop Jive Messenger.
Make a back of your database and current installation. Note that embedded database is stored in the embedded-db folder.
Install wildfire to new location (e.g. c:
Wildfire or /opt/wildfire)
Copy existing conf/jive-messenger.xml from old version to conf/wildfire.xml in the new installation
Replace out-of-the-box SSL certificates with previous ones by copying the files located in resources/security of the old version to the new installation
Copy existing messenger-service.exe.vmoptions to wildfire-service.exe.vmoptions in the new installation
If on internal db, copy the files located in embedded-db to new location renaming the items in embedded-db to have a “wildfire” prefix instead of a “jive-messenger” prefix.
If using LDAP, update your wildfire.xml (was jive-messenger.xml) config and change all references from org.jivesoftware.messenger to org.jivesoftware.wildfire.
If JM was installed as a service you will have to uninstall it (messenger-service /uninstall) and then install wildfire as a service (wildfire-service /install).
Existing plugins must be updated to latest version. Download latest version from: http://www.jivesoftware.org/wildfire/plugins.jsp. This includes updating the SparkManager plugin that can be downloaded from http://www.jivesoftware.com/products/wildfire/sparkmanager.jsp.
Upgrading using PostgreSQL 7.x[/b]
Wildfire will automatically try to upgrade the database schema. However, the provided scripts may not always work for all database versions. Such is the case with PostgreSQL where the provided script works fine for PostgreSQL 8.x but not for PostgreSQL 7.x. If you are using PostgreSQL 7.x then you will need to replace the line:
ALTER TABLE jiveGroupUser ALTER COLUMN username TYPE VARCHAR(100) NOT NULL;[/code]
ALTER TABLE jiveGroupUser RENAME TO jiveGroupUser23;
ALTER TABLE jiveGroupUser23 DROP CONSTRAINT jiveGroupUser_pk;
CREATE TABLE jiveGroupUser (
groupName VARCHAR(50) NOT NULL,
username VARCHAR(100) NOT NULL,
administrator INTEGER NOT NULL,
CONSTRAINT jiveGroupUser_pk PRIMARY KEY (groupName, username, administrator)
INSERT INTO jiveGroupUser (groupName, username, administrator)
SELECT groupName, username, administrator FROM jiveGroupUser23;
DROP TABLE jiveGroupUser23;[/code]
Of course, be sure to back up your database prior to running any upgrade script in the event that a restore is necessary.