With a new package distribution in hand, you can easily upgrade your existing package to the later one.
To upgrade using the package, you'll need the following:
The following instructions are very similar to those for installing the package. For more detail on the commands, refer to Installing the Linux Package.
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.
[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).
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.