Installation of Version 0.1


In order to install PREDATOR, you must be able to access a distribution. If you are at Cornell, the distribution is available at /usr/u/praveen/PREDATOR. (This is the value you should set for your PREDATOR_LAIR environment variable--see below for details.) Otherwise, you must first download and unpack a PREDATOR distribution. You can find instructions to do so here.

Instructions

  1. Make sure you are on a Sparc running Solaris 2.5. You can make sure of this by typing uname -a. In the cs.cornell.edu domain, try hosts like leo, taurus, or rigel.
  2. PREDATOR requires some environment variables to be set during runtime and compilation. A text file is available which defines these variables, some of which you will have to modify. Copy it into your .cshrc file and then source your .cshrc file before proceeding. Below is a table of the variables you may change and their meanings:

    Variable NameMeaning
    PREDATOR_LAIRA path to the directory in which the distribution was downloaded and unpacked. By convention, this directory is usually named PREDATOR. At Cornell, this directory is /usr/u/praveen/PREDATOR.
    XXX_INSTALLROOTA path to the root of the installation (not the distribution!). By convention, this should point to a directory called predator somewhere. Make sure that you create such a directory. The default value is $HOME/predator.
    XXXSHOREDEFDEVPATHThe desired location of your "default disk". This is the Unix file that is used by PREDATOR ADTs as a storage volume. For instance, images and audio files are stored in this file. The default value is $XXXROOT/defdisk. Try to place your "default disk" on a local file system.
    XXXSHOREDEFDEVSIZE The size of your defdisk, in kilobytes. A good starting size is 10000.
    XXXSHORERELDISKPATH The desired location of your relational data "disk". This is the Unix file that is used by the PREDATOR Relation-ADT for storage. A good starting value is $XXXROOT/reldisk. Try to place your "relational disk" on a local file system.
    XXXSHORERELDISKSIZEThe size of your reldisk, in kilobytes. A good starting size is 10000.
    XXXSHORELOGDIR The directory in which SHORE will store its log files. This directory MUST exist and be writeable. Try to place your log files on a local disk. You MUST define this variable.
    XXXTMPDATADIR The directory which will serve as the "buffer" between the PREDATOR and web servers. This directory MUST exist and be writeable. The database server will write out temporary files such as images and query processing information files to this directory, and the webserver will link to it to retrieve them. You MUST define this variable.
    XXXSHOREDISKRW The location of SHORE's diskrw program, which performs asynchronous disk accesses. By default, this has the value $PREDATOR_LAIR/shore/apr97/bin/diskrw. Change this only if you are using an independent installation of SHORE.
    XXX_SERVER_PORT A port number (preferably above 5000) where the regression tests can safely start a server. This is meaningful only for the regression tests, not for normal execution.
    PATH In order for the server to be able to use Java classes (such as the one it uses to fetch data through URLs), it must have access to your JDK installation. Add a path to your JDK bin directory to your PATH variable.

    Note: The string "XXX" in this document really means "XXX". Do not subsitute with other strings.

  3. If the installation directory ($XXX_INSTALLROOT) does not exist, you should create it. Then create a soft link in it to the $XXX_RCSROOT directory.
    mkdir $XXX_INSTALLROOT
    cd $XXX_INSTALLROOT
    ln -s $XXX_RCSROOT/RCS .
    
    Now if you type ls, you should see the link to the RCS directory.
  4. Run script to capture the screen output of your installation process. This will help us debug your installation in case something goes wrong.
  5. Now you will "check out" copies of the PREDATOR source files. Type
    co RCS/*
    
    This will check out a copy of the Makefile and copyright notices. The Makefile can be used to complete the installation of PREDATOR. Now type
    make code
    
    Compilation is a lengthy process (approximately 30 minutes on a SparcStation 20). You will receive an e-mail informing you if the compilation was successful.
When your installation is complete, you should run regression tests to make sure that the system is running as expected.

If you have trouble with the installation, it is probably because one of the necessary utilities was not available or was improperly specified. Try to fix the problem from the error message, and repeat "make code". Otherwise, send mail with the typescript file to predator-support@cs.cornell.edu.


Mail user support: predator-support@cs.cornell.edu .... Back to PREDATOR Home Page