Upgrading a Linux Package

For more detail about the commands, refer to Installing the Linux Package.

1. Be sure to read the system requirements for important information about software, hardware, and network requirements and recommendations.
2. Make sure you have read Before You Upgrade and performed the relevant steps listed there.
3. Remove all plugins from your existing instance. (You'll need to re-install them via the Admin Console after you've successfully upgraded). For a list of supported Jive plugins, see this list in the Jive Community.
4. Remove custom WARs and fixpacks that might exist as provided by support.
5. If you are upgrading from a version later than 5.0, if possible, pull the web application server(s) 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 Admin Console: System > Settings > Activity Engine. (Versions before 5.0 do not use an Activity Engine.)
6. As a jive user, stop Jive services on all of the nodes, beginning with the web application nodes, and stopping the cache services last.
   Note: You can run jive status -v to see all of the services and whether they're enabled or disabled.

   jive stop

7. Review Backup and Storage Considerations for more on what you should be backing up. If you are also upgrading the database, see Upgrading a Database.
8. From the command line, access the target host as root.

   joe@joesbox ~ $ ssh root@targetsystem
   root@targethost's password:
   Last login: Mon Feb 14 14:00:56 2011 from joesbox.example.com

9. 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

10. Upgrade the Jive application RPM on all nodes. If you have multiple cache servers in your configuration, you need to upgrade all cache servers in the cluster.

    rpm -Uvh jive.rpm

    Note: All elements of the application will be 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'.
    ********************************************************************

11. If the RPM output shows that any .rpmnew or .rpmsave files were written during the upgrade, merge those changes as needed.
12. Run jive setup as the jive user on all nodes. For more on this, see Using jive setup. Do this so the Jive CLI installer can detect any service-specific startup properties that need to be set:

    jive setup

13. 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

14. Run jive start on one of the Web Application nodes as the Jive installation user.
15. With a supported web browser, navigate 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 using the Admin Console.
16. After you've finished the upgrade, log into the Web Application node you used for the upgrade tasks and restart the application.

    jive restart

17. Start the webapp and httpd services on all other webapp nodes.

    jive start

18. You're finished upgrading. You can now re-install your plugins.
19. If you had any custom themes and templates, see Upgrading Custom Themes and Templates.