Upgrading a Linux Package

With a new package distribution in hand, you can easily upgrade your existing package to the later one.

What You'll Need

To upgrade using the package, you'll need the following:

Upgrading the Package

The following instructions are very similar to those for installing the package. For more detail on the commands, refer to Installing the Linux Package.

Note: Executing the rpm command to upgrade the package will automatically stop Jive applications. The application will be started again at the end of the upgrade.
  1. 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.
  2. If you haven't yet done so, copy the new application package to the target host.
  3. Set options for installation as described in Installing the Linux Package.
  4. 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.
    rpm -Uhv jive_sbs_employee-4.0.2.RHEL-5.x86_64.rpm

    The following shows console output for a successful upgrade using the preceding command.

    [root@targethost ~]# rpm -Uvh jive_sbs_employee-4.0.2.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.
  5. 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 upgrade console.
  6. After you've finished the upgrade with the upgrade console, you'll need to restart the application. To do this, log into the target host as the jive user and execute the following commands:
    [1520][root@targethost:~]$ appstop --verbose
    Stopping sbs...
    Executing /usr/local/jive/applications/sbs/bin/manage stop
    sbs stopped successfully.
    All applications stopped successfully (1 total).
    [1520][root@targethost:~]$ appstart --verbose
    Starting sbs...
    Executing /usr/local/jive/applications/fsbs/bin/manage start
    sbs started successfully.
    All applications started successfully (1 total).
  7. You're finished!

Troubleshooting Upgrade

Unable to Log in After Upgrading from Version 3 to version 4

If you're getting an error 404 after upgrading, you might need to update your license file before starting the application. For example, if you upgrade on SuSE Linux from version 3.0.9 to a revision of version 4.0, you might not be able to log in to continue the upgrade using the admin console.

After upgrading the software, stop the application with appstop, then replace the Jive license file with the one you received for use with the new version. On Linux, you'll find the file at /usr/local/jive/applications/<appname>/home/jive.license

After replacing the file, start the application as described in appstart Command.