OpenFire Upgrade Guide

Original: http://www.liuhaihua.cn/archives/355.html

Upgrading OpenFire is almost as simple as installing openfire from the beginning. As part of the upgrade process, it is strongly recommended that you back up the current installation and database first. Having a backup can make it easy to roll back to a previous state and ensure that you don't lose important information. The remainder of the document describes common steps to perform a successful upgrade. All settings and data for the existing version of the new version of the OpenFire installation will be retained.

Standard Upgrade

exe for Windows

1. Stop the OpenFire.
2. Back up the OpenFire installation directory. The default value is _c:\ program files file \ openfire_
3. Back up the OpenFire database. In the 2nd step, you need to be aware of the embedded database backup.
4. Run the OpenFire (note that Setup must point to the previous version of the Basic installation directory) of the new version of the installer.
5. Complete the installation process.
6. Start OpenFire.

rpm– Redhat-based UNIX system (Rhel,centos, fedora, etc.)

1. stop openfire.  
2. backup openfire installation directory
3. backup OpenFire database. In the 2nd step, you need to be aware of the embedded database backup.
4. install the new RPM. Perform an update for RPM-UVF openfire-3.3.3-1.i386.rpm the current installation
5. starts OpenFire. Remember that the server can start manual or automatic mode. Execute   /opt/openfire/bin/openfire.sh   Start in manual mode or execute//etc/init.d/openfire start to start the server as a service. Execute   /etc/init.d/openfire Stop stops the server's services.
   Things to be aware of

• the new RPM installation OpenFire as a service. This means that the server will stop when the server starts and shuts down when the OS starts. The
• /opt/openfire/bin/openfire no longer exists. This is the install4j generated by a start/stop script. Since we no longer use install4j, it needs to go. Instead, we now have a/etc/init.d/openfire of a more standard Linux init script.
• can now use the ' adjust ' parameters of/openfire in/etc/sysconfig, such as paths and so on. For more information, see the file.
• The daemon that is now owned by the entire directory tree. We abandoned a new user requirement and insisted on using a standard UNIX system account.  RPM will take care of owning everything when you install it.
• /etc/init.d/openfire stop and start OpenFire, in addition to having a chkconfig command-compatible label, it is automatically added by turning to enable the OpenFire startup server to start.
• rpm will no longer overwrite:  conf/openfire.xml, Resources/security/keystore or Resources/security/truststore.

Mac OS X DMG

1. Stop the OpenFire.
2. Back up the OpenFire installation directory. By default, it is /usr/local/wildfire.
3. Back up the OpenFire database. In the 2nd step, you need to be aware of the embedded database backup.
4. Open the new version of OpenFire for the installer:
5. Complete the installation process

ZIP or TAR. GZ

1. Stop OpenFire.
2. Back up the OpenFire installation directory. This step is very important because the data will be overwritten with the new one. Installation of tar.gz
3. Back up the OpenFire database. In the 2nd step, you need to be aware of the embedded database backup.
4. Installation. tar.gz file (unzip in current directory).
5. Copy the Conf directory from the backup installation directory.
6. Copy the embedded database directory back into the installation directory.
7. Enterprise directory replication Backup to the installation directory if it exists
8. Copy the plugins directory that was backed up to the installation directory in addition to _plugins/admin_.
9. Back up the modified files to the installation directory/security
10. Start OpenFire

OpenFire Upgrade Guide