Installing the Linux Package

What You'll Need

To install Jive SBS using the RPM, you'll need the following:

A server that meets the minimum specified hardware requirements. See the System Requirements for more information.
The host computer must have a Jive-certified Linux operating system installed. See the System Requirements for supported versions.
A copy of the application RPM. You'll also need SSH access to the host computer so you can copy the RPM there for installation.
Root access to the host where the installation is performed, commonly via SSH or less commonly through user interface access such as VNC.

Note: To use the Office integration feature that generates previews of Microsoft Office documents and PDFs, you must install the feature on a separate node.

Installation Steps

The following installation steps represent the most common approach to installing the Jive SBS Platform.

Ensure that that application database has been created as described in database prerequisites.
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@targethost
root@targethost's password:
Last login: Tue Jan 20 14:00:56 2009 from joesbox.example.com
```
If you haven't yet done so, copy the application RPM to the target host. Here's an example using the Linux scp command to copy from a computer named edda to a target host at targethost:
```
scp -v joe@joesbox:/Users/joe/jive_sbs-3.0.0-78305.x86_64.rpm root@targethost:/root
```

Set options for installation. If you want, you can set installer options (listed in the following table). Ordinarily you won't need these, but they can be useful in some cases.

To set these, use the Linux export command to set them as environment variables. All package-level variables are enabled by setting their value to a non-empty string. For example, the following example turns on debugging information:

export JIVE_DEBUG=1

You can clear the variable with a command such as the following:

unset JIVE_DEBUG

Option	Description	Default
JIVE_DEBUG	Exposes installation debugging information, listing actions the installer is performing. This is in addition to the information displayed by the RPM -v (verbose) flag.	Debugging information isn't displayed.
JIVE_APPLICATION_NOSERVICE	Prevents the package from starting Jive SBS services immediately after installation.	By default, the application starts immediately after installation; you'll be able to navigate to its setup tool using a web browser.

Install the application RPM using an rpm command such as the following. Here, the "i", “h”, and “v” options are provided to indicate install with hash indicators, and to be verbose during the installation. (Note that your copy of the RPM file -- here, jive_sbs-3.0.0-78305.x86_64.rpm -- might have a slightly different name.)

rpm -ihv jive_sbs-3.0.0-78305.x86_64.rpm

Note: You can find out more about rpm command syntax at the Fedora web site.

The following shows console output for a successful installation using the preceding command. In this case, the RPM file was in the /root directory of the target host.

[root@targethost ~]# ls -l
total 191536
drwxr-xr-x 2 root root      4096 Dec 18 15:08 Desktop
-rw-r--r-- 1 root root 195742683 Mar  9 09:14 jive_sbs-3.0.0.RHEL-5.x86_64.rpm
-rw-r--r-- 1 root root    177294 Jan  2  2008 sysstat-7.0.2-1.el5.x86_64.rpm
-rwxr-xr-x 1 root root      1707 Jan 16 10:42 updateDNS.sh
Preparing...                ########################################### [100%]
Preparing clean installation.
Pre-install tasks complete.
   1:jive_sbs               ########################################### [100%]
Writing installation version.
Wrote installation version.
Executing Jive post-install configuration.
Creating jive group jive.
Creating jive system user jive.
Marking all upgrades as complete.
Starting Jive System Daemon.
Performing Jive system configurations.

Initializing database for first use.
Starting Jive System Database.
Starting jive-database: 
server starting

Configuring scheduled database maintenance.
Configuring log rotation maintenance.
Staging Jive Application.
Validating configuration.
Staging application from template: /usr/local/jive/applications/template
Linking application to master binary at '/usr/local/jive/applications/template/application'.
Creating application configuration at: /usr/local/jive/applications/sbs/bin/instance
Application context set to '/'.
Creating proxy configuration for default HTTPD virtual host.
Staging cryptography.
Creating private key to /usr/local/jive/applications/sbs/home/crypto/sbs.pem
Creating public key to /usr/local/jive/applications/sbs/home/crypto/sbs.pub
Successfully created application at '/usr/local/jive/applications/sbs'.
Starting Jive applications.
Handling applications ['sbs']
Starting sbs...
Executing /usr/local/jive/applications/sbs/bin/manage start
sbs started successfully.
All applications started successfully (1 total).
Starting jive-httpd: 

Jive post-install configuration complete.

When it's finished, the RPM indicates that the post-install configuration has completed and that the SBS application has been started successfully.

If you'll be using a database whose driver is not included, copy its driver into the application's class path. For more information, see Database Prerequisites.
If you're doing a new installation (rather than upgrading), you're finished. 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 finish configuring the application with the setup console.
If you're upgrading, you'll find the rest of the steps you need in Upgrading from Prior to 3.0.

Troubleshooting Installation

The Jive SBS installation uses Linux RPM, a widely tested and used application that is very unlikely to fail. However, there are a few dependences that Jive SBS requires (that you are likely to have already). And if you do run into trouble, you can delete and start over as described below.

Note: You'll find the installation log files on the target computer at /usr/local/jive/var/logs.

Unsatisfied Dependencies

The application RPM depends on the presence of several low-level system packages that are common to nearly all configurations of Jive’s supported Linux distributions. Also, the application RPM depends on three high-level packages. If any of these packages (system or high-level) are not present, the RPM subsystem will warn you, then refuse to install. When you see these warnings, simply install the missing packages using RPM, then install Jive SBS as described in the instructions.

Unsatisfied dependencies appear as an error when attempting to install the RPM:

[root@targethost ~]# ls -l
total 202068
-rw-r--r-- 1 root root 206701420 Jan 20 16:03 jive_sbs-3.0.0-78310.i386.rpm
-rwxr-xr-x 1 root root      1347 Oct  7 16:14 updateDNS.sh
[root@targethost ~]# rpm -ivh jive_sbs-3.0.0-78310.i386.rpm 
error: Failed dependencies:
     bash >= 3.2 is needed by jive_sbs-3.0.0-78310.i386
     sysstat >= 7 is needed by jive_sbs-3.0.0-78310.i386

Depending on the host configuration, it may be possible to install the dependencies directly using system tools. For example, in RedHat Enterprise Linux, the “yum” command can install dependencies via network repositories. The following demonstrates how to install the dependencies shown in the error above. Note that it is necessary to type “y” for yes when prompted:

[root@targethost ~]# yum install bash-3.2 sysstat
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
extras                    100% |=========================| 1.1 kB    00:00 
updates                                                          951 B 00:00 
base                      100% |=========================| 1.1 kB    00:00 
addons                    100% |=========================|  951 B    00:00 
Reading repository metadata in from local files
primary.xml.gz            100% |=========================|  90 kB    00:00 
################################################## 295/295
primary.xml.gz                                                  369 kB 00:03 
################################################## 796/796
primary.xml.gz            100% |=========================| 853 kB    00:01 
################################################## 2458/2458
Parsing package install arguments
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for sysstat to pack into transaction set.
sysstat-7.0.2-1.el5.i386. 100% |=========================|  15 kB    00:00 
---> Package sysstat.i386 0:7.0.2-1.el5 set to be updated
---> Downloading header for bash to pack into transaction set.
bash-3.2-21.el5.i386.rpm  100% |=========================|  55 kB    00:00
---> Package bash.i386 0:3.2-21.el5 set to be updated
--> Running transaction check
Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size 
=============================================================================
Installing:
 sysstat                 i386       7.0.2-1.el5      base              168 k
Updating:
 bash                    i386       3.2-21.el5       base              1.9 M
Transaction Summary
=============================================================================
Install      1 Package(s) 
Update       1 Package(s) 
Remove       0 Package(s)
Total download size: 2.0 M
Is this ok [y/N]: y
Downloading Packages:
(1/2): sysstat-7.0.2-1.el 100% |=========================| 168 kB    00:00 
(2/2): bash-3.2-21.el5.i3 100% |=========================| 1.9 MB    00:02 
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Updating  : bash                         ######################### [1/3] 
  Installing: sysstat                      ######################### [2/3] 
  Cleanup   : bash                         ######################### [3/3]
Installed: sysstat.i386 0:7.0.2-1.el5
Updated: bash.i386 0:3.2-21.el5
Complete!

After dependencies have been resolved, the package should install as normal.

Insufficient System Memory

The Jive SBS platform requires a minimum of 3GB RAM to operate effectively for an enterprise environment. If insufficient memory is not available on the target installation system, the installer will provide a warning at installation time similar to the example below.

[root@targethost ~]# rpm -ivh jive_sbs-3.0.0-78310.i386.rpm
Preparing... ########################################### [100%]
1:jive_sbs ########################################### [100%]
Writing installation version.
Wrote installation version.
Executing Jive post-install configuration.
Creating jive group jive.
Creating jive system user jive.
useradd: warning: the home directory already exists.
Not copying any file from skel directory into it.
Marking all upgrades as complete.
WARNING: this host does not have sufficient RAM to run a production Jive SBS system.
A minimum of 3GB is required to host the application and HTTPD servers. 4GB is required to
run a locally hosted database.
Starting Jive System Daemon.
Performing Jive system configurations.
Disabling CPU frequency stepping.

Initializing database for first use.
Starting Jive System Database.
Starting jive-database:
server starting

Configuring scheduled database maintenance.
Configuring scheduled database backups.
Configuring log rotation maintenance.
Staging Jive Application.
Validating configuration.
Staging application from template: /usr/local/jive/applications/template
Linking application to master binary at '/usr/local/jive/applications/template/application'.
Creating application configuration at: /usr/local/jive/applications/sbs/bin/instance
Application context set to '/'.
Creating proxy configuration for default HTTPD virtual host.
Staging cryptography.
Creating private key to /usr/local/jive/applications/sbs/home/crypto/sbs.pem
Creating public key to /usr/local/jive/applications/sbs/home/crypto/sbs.pub
Successfully created application at '/usr/local/jive/applications/sbs'.
Starting Jive applications.
Handling applications ['sbs']
Starting sbs...
Executing /usr/local/jive/applications/sbs/bin/manage start
Failed to start application sbs. See log file at '/usr/local/jive/var/logs/sbs.out'.
Failed to start Jive applications. Please check the error logs at '/usr/local/jive/var/logs/sbs.log'.
Disabling existing Apache HTTPD server.
Starting jive-httpd:
[ OK ]
Jive post-install configuration complete.

In the above example, note the warning message “WARNING: this host does not have sufficient RAM to run a production system. A minimum of 3GB is required to host the application and HTTPD servers. 4GB is required to run a locally hosted database.”.

Despite this warning, the RPM does install correctly, however further errors are noted on the output line "Failed to start application sbs. See log file at '/usr/local/jive/var/logs/sbs.out'." Upon further examination, the contents of this log file indicate:

[root@targethost ~]# cat /usr/local/jive/var/logs/sbs.out
SCRIPT_DIR=/usr/local/jive/applications/sbs/bin
JIVE_BASE=/usr/local/jive/applications/sbs

Creating temp directory at /usr/local/jive/var/work/sbs.
Starting application sbs
Error occurred during initialization of VM
Could not reserve enough space for object heap

Starting Over

In the unlikely event that something goes wrong during installation and you want to start over, you can uninstall. When uninstalling, you don't specify the RPM file name, as you did when installing. Instead, you give the logical name by which RPM now knows the application: jive_sbs. Here's an example using the rpm command with the "-e" switch for uninstalling:

rpm -e jive_sbs

If you want to be sure you've removed all remnants of the installation, delete the destination directory created by RPM. Here's how that command looks:

rm -rf /usr/local/jive