Installing the Solaris Package

What You'll Need

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

Installation Steps

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

  1. Ensure that that application database has been created as described in database prerequisites.
  2. From the command line, access the target host as root.
  3. If you haven't yet done so, copy the application package to the target host.
  4. Unzip the package file using the gunzip command.
    bash-3.00# /usr/bin/gunzip JiveSBS-3.0.5-SunOS-5.10-sparcv9.gz
  5. Set options for installation. If you want, you can set installer options (listed in the table below). Ordinarily you won't need these, but they can be useful in some cases.

    To set these, use the 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. 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.
  6. As root, execute the pkgadd command with the -d option and the decompressed package file from the previous step as an argument. (Note that your copy of the package file -- here, JiveSBS-3.0.5-SunOS-5.10-sparcv9 -- might have a slightly different name.)

    When executing the command, the system will prompt for the package to process, enter "all" or press return to select the default of all.

    The pkgadd command will then prompt that the /usr/local/jive/httpd/bin/suexec file will be installed with setuid and/or setgid permissions. Enter 'y' to accept.

    Finally, pkgadd will ask if it should continue with installation of the JiveSBS package. Enter 'y' to accept.

    Console output should appear similar to the following:

    bash-3.00# pkgadd -d JiveSBS-3.0.5-SunOS-5.10-sparcv9 
    
    The following packages are available:
      1  JiveSBS     JiveSBS for SunOS 5.10 sparcv9
                     (sun4u) 3.0.0
    
    Select package(s) you wish to process (or 'all' to process
    all packages). (default: all) [?,??,q]: 
    
    Processing package instance <JiveSBS> from </root/JiveSBS-3.0.5-SunOS-5.10-sparcv9>
    
    JiveSBS for SunOS 5.10 sparcv9(sun4u) 3.0.0
    Jive Software, Inc.
    ## Executing checkinstall script.
    ## Processing package information.
    ## Processing system information.
       1 package pathname is already properly installed.
    ## Verifying package dependencies.
    ## Verifying disk space requirements.
    ## Checking for conflicts with packages already installed.
    ## Checking for setuid/setgid programs.
    
    The following files are being installed with setuid and/or setgid
    permissions:
      /usr/local/jive/httpd/bin/suexec <setuid root>
    
    Do you want to install these as setuid/setgid files [y,n,?,q] y
    
    This package contains scripts which will be executed with super-user
    permission during the process of installing this package.
    
    Do you want to continue with the installation of <JiveSBS> [y,n,?] y
    Installing JiveSBS for SunOS 5.10 sparcv9 as <JiveSBS>
    
    ## Executing preinstall script.
    Preparing clean installation.
    ## Installing part 1 of 1.
    /etc/jive/jiverc
    /usr/local/jive/.bash_profile
    /usr/local/jive/applications/template/README
    /usr/local/jive/applications/template/application/404.jsp
    /usr/local/jive/applications/template/application/500.jsp
    /usr/local/jive/applications/template/application/META-INF/MANIFEST.MF
    ... (ommitted for brevity)
    ## Executing postinstall script.
    Executing Jive post-install configuration.
    Marking all upgrades as complete.
    Sun Microsystems Inc.   SunOS 5.10      Generic January 2005
    Initializing database for first use.
    Sun Microsystems Inc.   SunOS 5.10      Generic January 2005
    Starting Jive System Database.
    Staging Jive Application.
    Sun Microsystems Inc.   SunOS 5.10      Generic January 2005
    Validating configuration.
    Staging application from template: /usr/local/jive/applications/template
    Linking application to master binary at '/usr/local/jive/applications/template/application'.
    System memory requirements invalid. Application will likely run out of memory during normal usage.
    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.
    Jive post-install configuration complete.
    
    Installation of <JiveSBS> was successful.

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

  7. 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.
  8. 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 package 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 on Solaris

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

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.

System memory requirements invalid. Application will likely run out of memory during normal usage.
Despite this warning, the package does install correctly. However, be sure to see the log file at '/usr/local/jive/var/logs/sbs.out'." Upon further examination, the contents of this log file might indicate:
bash-3.00# 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 package file name, as you did when installing. Instead, you give the logical name by which the package manager now knows the application: JiveSBS. Here's an example using the pkgrm command:

pkgrm JiveSBS

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

rm -rf /usr/local/jive