Upgrading from Wildfire to Openfire?

Check out the Wildfire to Openfire Upgrade Guide. The document below describes upgrading to Wildfire 3.2, so if you're already on 3.2 looking to get to 3.3.0 or later, see the Wildfire to Openfire Upgrade Guide.

Looking for upgrade instructions for the Wildfire Enterprise plug-in? A brief guide is available.

Upgrading Wildfire to 3.2, Including Plugins and Certificates

Upgrading Wildfire must be completed in the following sequence:

Upgrade Wildfire
Upgrade Wildfire Enterprise
Run the manual steps to move the update the Fastpath data for the new Enterprise plugin.

Do not upgrade plugins prior to upgrading Wildfire itself or the plugins will stop working.

Windows EXE

Upgrading Wildfire on a Windows machine can be accomplished by following these steps.

Stop Wildfire.
Backup the Wildfire installation directory. The default is C:\Program Files\Wildfire
Backup the Wildfire database. Note that the embedded database is backed up in step 2.
Run the installer for the new version of Wildfire (note that the installer MUST point to the base installation directory of the previous version).
http://www.igniterealtime.org/downloads/download-landing.jsp?file=wildfire/wildfire_3_2_0.exe
Complete the installer process.
Start Wildfire.

The new version of Wildfire will be installed over the existing version and all settings and data will be retained.

Linux RPM

Upgrading Wildfire on Linux with an RPM can be accomplished by following these steps.

Stop Wildfire.
Backup the Wildfire installation directory. This step is critical because the data will be overwritten with the new RPM install.
Backup the Wildfire database. Note that the embedded database is backed up in step 2.
Install the RPM.
http://www.igniterealtime.org/downloadServlet?filename=wildfire/wildfire_3_2_0.rpm
Copy the conf directory from the backup to the installation directory.
Copy the embedded-db directory from the backup to the installation directory.
Copy the enterprise directory from the backup to the installation directory, if it exists.
Copy the plugins directory from the backup to the installation directory except for plugins/admin.
Copy the resources/security/keystore file from the backup to the installation directory.
Copy the resources/security/truststore file from the backup to the installation directory if you modified this file.
Start Wildfire.

Mac OS X DMG

Upgrading Wildfire on an OS X machine can be accomplished by following these steps.

Stop Wildfire.
Backup the Wildfire installation directory. The default is /usr/local/wildfire.
Backup the Wildfire database. Note that the embedded database is backed up in step 2.
http://www.igniterealtime.org/downloads/download-landing.jsp?file=wildfire/wildfire_3_2_0.dmg
Open the installer for the new version of Wildfire.
Complete the installer process.

The new version of Wildfire will be installed over the existing version and all settings and data will be retained.

ZIP or TAR.GZ

Upgrading with a ZIP or TAR.GZ file is can be accomplished by following these steps.

Stop Wildfire.
Backup the Wildfire installation directory. This step is critical because the data will be overwritten with the new .tar.gz install.
Backup the Wildfire database. Note that the embedded database is backed up in step 2.
http://www.igniterealtime.org/downloadServlet?filename=wildfire/wildfire_3_2_0.tar.gz
Install the .tar.gz file (extract it over the current directory).
Copy the conf directory from the backup to the installation directory.
Copy the embedded-db directory from the backup to the installation directory.
Copy the enterprise directory from the backup to the installation directory, if it exists.
Copy the plugins directory from the backup to the installation directory except for plugins/admin.
Copy the resources/security/keystore file from the backup to the installation directory.
Copy the resources/security/truststore file from the backup to the installation directory if you modified this file.
Start Wildfire

FreeBSD Port

See the FreeBSD Port Guide for more information on this operating system.

Plugins

After successfully installing Wildfire, start the service and ensure your users exist, and that you can still connect. Once you have done this, you need to upgrade the plugins. This is a two step process. Note that the Fastpath plugin is now included in the Wildfire Enterprise plugin.

Navigate to the plugins directory, and select to upgrade Wildfire Enterprise.
Follow the guide to migrate your Fastpath data.

Certificates

During an initial setup Wildfire will create the resources/security/keystore and resources/security/truststore files. The keystore file is where certificates of the XMPP server are stored and truststore is where certificates of trusted Certificate Authorities are stored. The keystore file is completed with self-signed certificates after the setup process has been completed. The truststore is never modified by Wildfire.

During the update process Wildfire will never overwrite the keystore and truststore files. Wildfire 3.2.0 has updated the truststore file with new trusted Certificate Authorities. Therefore, it is important to update this file in your existing installation. If you have not modified the truststore file then you can just replace it with this one. However, if you have modified your truststore file then you may want to recreate it. The suggested procedure is to download this new version and apply again your changes.