Upgrading Jive package

With a new Jive package distribution, you can upgrade your existing package.

Note: Before you upgrade, uninstall all your plugins. You need to re-install them via the Admin Console after you have successfully upgraded.

Requirements

Your existing installation of the Jive package
The new Jive package you're upgrading to
SSH access to the host computer so you can copy the package there for installation.
Ability to become the root user on the host where the installation is performed, commonly via SSH

Upgrading Jive package

For more information about the commands, see Installing Jive package and starting up.

Note: Executing the rpm command to upgrade the package automatically stops Jive applications. The application is started again at the end of the upgrade.

Familiarize yourself with the system requirements, important information about software, hardware, and network requirements and recommendations, described in System requirements.
Prepare for upgrade by performing the relevant steps, as described in the following articles depending on your application version:
- Preparing for upgrade to 9.0.7.1 or later
- Preparing for upgrade from 7.0.x or 8.0.x
- Preparing for upgrade from version earlier than 7.0
Remove all plugins from your existing instance.
Note that you'll need to re-install them after you've successfully upgraded. For more information, see Customizing with plugins.
Remove custom WARs and fixpacks that might exist as provided by support.
If you are upgrading from a version later than 5.0, if possible, pull the web application servers from the load balancing pool to prevent new activity coming in. Make sure your Activity Engine queues are drained to zero. You can see the queues in the Admin Console, on the System > Settings > Activity Engine page. Note that versions before 5.0 do not use an Activity Engine.
As the jive user, stop Jive services on all of the nodes, beginning with the web application nodes, and stopping the cache services last.
```
jive stop
```
Note: You can run jive status -v to see all of the services and whether they're enabled or disabled.
Review backup and storage considerations for more on what you should be backing up, as described in Backup and storage considerations. If you are also upgrading the database, see Upgrading databases.
From the command line, access the target host as root. For example, the following illustrates using the ssh command to access the server at targethost as the root user.
```
joe@joesbox ~ $ ssh root@targetsystem
root@targethost's password:
Last login: Mon Feb 14 14:00:56 2011 from joesbox.example.com
```
If you haven't already copied the Jive application RPM to each server and application node in your Jive environment, then you should do it now.
Here's an example using the Linux scp command to copy the package from a computer named joesbox to a target system at targetsystem:
```
scp -v joe@joesbox:/Users/joe/jive.rpm root@targetsystem:/root
```

Upgrade the Jive application RPM on all nodes by using an rpm command such as the following. The U, h, and v options are provided to indicate install or upgrade with hash indicators, and to be verbose during the installation. If you have multiple cache servers in your configuration, you need to upgrade all cache servers in the cluster.

rpm -Uvh jive.rpm

Your copy of the Jive RPM file — here, jive.rpm — will have a slightly different name.

All elements of the application are upgraded, including cache services and, if you have it, Document Conversion services. The following shows console output for a successful upgrade using the preceding command.

[root@targethost ~]# rpm -Uvh jive.rpm
Preparing...                ########################################### [100%]
Stopping httpd: running stop command..stopped
Stopping webapp: running stop command..........sending SIGTERM.stopped
Stopping search: sending SIGTERM..stopped
Stopping docconverter: sending SIGTERM.........stopped
Stopping cache: sending SIGTERM...stopped
Stopping eae: sending SIGTERM.stopped
Writing upgrade version.
Wrote upgrade version.
Pre-install tasks complete.
   1:jive_sbs               ########################################### [100%]
Removing unused files...
...done.
Fixing permissions..
...done.
Fixing symlinks...
...done.
Installing init script and logrotate...
...done.
********************************************************************
*** Post-install tasks complete! To configure the Jive platform,
*** become the jive user and run 'jive setup'.
********************************************************************

If the RPM output shows that any .rpmnew or .rpmsave files were written during the upgrade, merge those changes as required.
Run jive setup as the jive user on all nodes. For more information, see Using jive setup. Do this so that the Jive CLI installer can detect any service-specific startup properties that need to be set:
```
jive setup
```
Once you get the setup ok message on all nodes, you can start the enabled services on all nodes except the web application nodes. For example, start services on the Cache nodes first, and then on the Activity Engine, Search, Ingress Replicator, and Document Conversion nodes.
```
jive start
```
Run jive start on one of the Web Application nodes as the Jive installation user.
With a supported web browser, go to http://hostname:8080, where hostname is the DNS-resolvable name of the server of the Web Application node you're using to upgrade. Once there, proceed with the upgrade by using the Admin Console.
After you've finished the upgrade, log into the Web Application node you used for the upgrade tasks and restart the application.
```
jive restart
```
If you are upgrading to the 9.0.7.1 or later, copy the files from the applications/sbs/home/crypto/* directory in WebApp1 (Node 1), then paste them to the same directory in all other nodes.
To support FIPS compliant encryption, the upgrade is converting the old crypto key files into a new format. You need to copy the new keys to all nodes.
Start the webapp and httpd services on all other webapp nodes.
```
jive start
```
You're finished upgrading and should perform post-upgrades tasks.
Re-install your plugins.
If you had any custom themes and templates, see Upgrading custom themes and templates.