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. Remove all plug-ins 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.
3. If you are upgrading from a version earlier than 3.0, back up the jiveHome directory. For more information, see Transferring jiveHome.
4. 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.)
5. Stop the existing web application server(s).
6. Back up your existing database. If you are using an unsupported database, ensure that you have migrated it correctly. For more information, see Migrating Data from an Unsupported DBMS and Database Prerequisites.
7. From the command line, access the target host as root.
8. If you haven't yet done so, copy the new application package to the target host.
9. Set your desired installation options as described in Installing the Linux Package.
10. Upgrade the application package using an rpm command such as the following. Here, the U, h, and v options are provided to indicate install with hash indicators, and to be verbose during the installation. You must run this command on each cache server in your configuration.

    rpm -Uhv jive_sbs_employee-5.0.0.RHEL-5.x86_64.rpm

    Note that 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_sbs_employee-5.0.0.RHEL-5.x86_64.rpm
    Preparing...                ########################################### [100%]
    Writing upgrade version.
    Wrote upgrade version.
    Stopping Jive Applications
    Stopping Jive System Database.
    Stopping Jive HTTP Service.
    Stopping Jive JDCD Service.
    Stopping Jive JOOSD Service.
    Jive pre-upgrade configuration complete.
    Pre-install tasks complete.
       1:jive_sbs               ########################################### [100%]
    Executing Jive post-install configuration.
    Performing jive platform upgrade.
    Platform upgrade successful.
    Jive post-install upgrate configuration complete.
    Executing Jive post-install configuration.
    Jive Document Conversion Daemon activated.
    Jive Open Office Server activated.
    Starting Jive System Daemon.
    Performing Jive system configurations.
    
    Starting Jive System Database.
    server starting
    Disabling existing Apache HTTPD server.
    Starting jive-httpd: 
    
    Starting Jive applications.
    Starting jive-jdcd: 
    OK
    Starting jive-joosd: 
    OK
    Handling applications ['sbs']
    Starting sbs...
    Executing /usr/local/jive/applications/sbs/bin/manage start
    sbs started successfully.
    All applications started successfully (1 total).
    Jive post-install configuration complete.

11. With a supported web browser, navigate to http://<hostname>/, where hostname is the DNS resolvable name of the server where the RPM was installed. There, you can proceed with the upgrade using the admin console.
12. After you've finished the upgrade, you'll need to restart the application. To do this, log into the target host as the jive user and execute the following commands:

    appstop --verbose

    appstart --verbose

13. You're finished upgrading. You can now reapply any plugins you installed. Note that you may also need to reconfigure SSL support for Apache and Tomcat; some configuration files are overwritten during the upgrade.
14. If you had any custom themes and templates, see Upgrading Custom Themes and Templates.
15. See Post-Upgrading Tasks for your next steps.