Installing the software

Having obtained the software (via one of the previous steps) you are now ready to install it on your network.

SUGGESTION: Before you dive right in, be sure to read the RELEASE_NOTES for important information. This file contains updates, corrections, suggestions, and/or product changes that are not contained in the manuals.

General guidelines

If you are loading Razor onto your system for a simple evaluation of the product, you may install the release right under your home directory. Everything will work just fine, and it (perhaps) postpones the need to involve your local sys-admin department. We do ask you to consider our words of wisdom previously mentioned in "Before you get started..." on page 21.

For the sake of our discussion and examples, we'll assume that you'll be putting the product under a globally accessible area called /home/razoradm, and that this directory is writable by you. You will need to make substitutions as necessary in the following instructions.

Un-tarring the release

Uncompress and un-tar the Razor.tar.Z file into the Razor directory.

# cd /home/razoradm
# zcat Razor.tar.Z | tar xf -

A directory listing at this point would show you that a new directory has been created and populated with the full Razor release. The version number of the release will be imbedded in the directory name.

Running rz_install

The next step is to run the installation script¹. It will perform a variety of system checks and prepare the release for general use.

1. Invoke the rz_install shell script. You will need to substitute the full release directory name for what is shown below.

# /home/razoradm/Razor_<version>2/scripts/rz_install

2. This script is used for new installations and upgrades. The script will ask you a series of questions and provide informational messages along the way. Follow the instructions provided by the script. The first question asked will be whether this is a new installation or an upgrade. For new installations, you will be asked if you want to create a symbolic link to the Razor tools. We recommend you answer `y', (the default). This will help make product updates go more smoothly for you later on because users can always point to the Razor executables in the `Razor' directory.

The script is fairly self explanatory. Unless you have specific reasons to do otherwise, accept the default answers as supplied to the questions.

3. One key question that you will be asked is where the Razor license directory (Razor_lm) is to exist. We suggest that it appear parallel to where the release itself now exists: In this example, /home/razoradm. (Please... do not put the Razor_lm directory within the Razor release area itself; this will only complicate things later.)

Please enter the fullpath to the directory where the
Razor_lm directory should be created: /home/razoradm

Make note of this directory. It will be used to install the license keys and to set the environment variable RAZOR_LICENSE_DIR a little later. Remember, you will need to have write permission in the named directory as you run the installation script.

4. Another key question will be whether you want to use RCS instead of SCCS for the underlying archival mechanism. Razor will work fine with either (provided that you are running RCS version 5 or better). If you aren't sure, answer `n' to the question and SCCS will be used.

5. All of the text from running the rz_install script is stored in the file razor_install.info for your review. The directory tree under the /home/razoradm installation area should now look something like that shown below.

                /-- Razor  - - - -> /home/razoradm/Razor_<ver>
                | 
                |                 /-- Razor_iw_lib
                |                 |-- bin
                |                 |-- doc
                |                 |
                |                 |-- examples -------- small_glyphs
                |                 |
/home/razoradm -+-- Razor_<ver> --+-- glyphs
                |                 |-- help
                |                 |-- lib-------------- nls
                |                 |-- scripts
                |                 |
                |                 |                /-- Issues_tables_templates
                |                 \-- templates ---+-- Threads_tables_templates
                |                                  \-- Versions_tables_templates
                | 
                \-- Razor_lm

You'll notice that the rz_install script created a symbolic link called Razor which points to where the true installation resides. This makes product upgrades much easier to install.

Sample installation

Here is a sample Razor installation so that you can see that it is really quite straightforward. This sample installation³ assumes the following:

• first-time installation
• symbolic link install (recommended)
• installation target directory /home/razoradm/Razor
• release has been untarred

# cd /home/razoradm/Razor
# ./scripts/rz_install

Checking your configuration...


Welcome to the Razor product installation.


If at any point during this process you have questions
please contact us at:
                support@tower.com
                (315) 363-8000



Is this a product upgrade (y/n)? [n] 

A new installation.... Welcome aboard!


We recommend that you use a symbolic link to point to the current
Razor executables.  This will prevent your users from having to
change database specific setup files (rz_prep AND rz_prep.sh)
due to future product upgrades.

Would you like to be configured this way (y/n)? [y] 

When referring to the Razor release directory, the Razor tools
will use the directory:
         /home/razoradm

Is this correct (y/n)? [y] 

The Razor license manager controls the allocation of license
tokens.  This installation will create a Razor_lm directory
in the location you specify.


Please enter the fullpath to the directory where the Razor_lm 
directory should be created: /home/razoradm

Checking for existing link...

None found.

Creating link...
A symbolic link to /home/razoradm/Razor_<release> has been 
created as /home/razoradm/Razor.

Your Razor License data is located in /home/razoradm/Razor_lm.
Please use this location when creating a new database.


Installation complete.


Please contact Tower Concepts to obtain a demo or node key for 
your site.

Please have the Razor identification string of the machine that 
will be hosting the license server when contacting Tower 
Concepts.  The Razor identification string is obtained by 
invoking the command:

`/home/razoradm/Razor/bin/razor id'

Until this key is obtained, Razor will not execute.



A Razor database must now be created for the Razor tools to 
access. This should be done by the user who will be the owner of 
the database. Database owners run the `rz_new_database' script to 
add a database.


If you have any problems or questions, please contact Tower 
Concepts. The support number is:  (315) 363-8000
Or via e-mail:          support@tower.com


The installation information just presented is contained in this 
directory in the file:

                razor_install.info

License keys

Obtaining license keys

In order for Razor to run, you must now obtain and install some license keys. Demo keys may be obtained automatically via Tower's Web site at http://www.tower.com/keys.html. Demo keys will permit you approximately three weeks to evaluate Razor. If you have problems or do not have access to the Internet, contact Tower Concepts either via e-mail at "licenses@tower.com" or by phone at (315) 363-8000.

Permanent keys are obtained directly from Tower Conepts. To get the keys, you will need to provide the Razor identification for the machine that will be hosting the Razor license manager (razor_lm). To obtain this identification string, log onto the machine that will be hosting the license manager and enter the following command...

# /home/razoradm/Razor/bin/razor id

If you obtained Razor from a software reseller or distributor, contact them for a set of license keys. If you are working directly with Tower Concepts, then contact them either via e-mail at "licenses@tower.com" or by phone at (315) 363-8000. Be sure to provide the entire output of the "razor id" command.

Installing keys

Razor provides a command line mechanism for entering the license keys.

1. The Razor command line program (appropriately named, razor) needs to know where the Licenses file resides via an environment variable. If it is not already set (i.e., you've never done this before), then you must set it by hand.

C shell:

# setenv RAZOR_LICENSE_DIR /home/razoradm/Razor_lm

Bourne/korn shell:

# RAZOR_LICENSE_DIR=/home/razoradm/Razor_lm

2. Invoke the razor program and enter the keys you have been provided.

# /home/razoradm/Razor/bin/razor license
Enter hostid [5300a282]: DEMO
Enter key 1: aa9e741b
Enter key 2: f4b70163
Enter key 3: f46cc463
Enter key 4: abcd69e5

If you have been supplied a DEMO license, then you need to actually enter the word "DEMO" as shown in the example above. When running a demo license, the tools will not allow operations on files/issues/threads beyond version 1.5 and will only allow 50 issues. This will allow you to get started, and once a purchased key is installed, pick up right where you left off. If you are upgrading to new license keys, then the existing keys will be provided to you as default settings within brackets.

TIP: Everything beyond the first two lines of the Licenses file is ignored by the Razor license manager, so feel free to put whatever you wish in there, such as expiration date and your customer ID.

Installing product upgrades

The mechanics for installing product upgrades mirrors that of doing a full, original installation - that is they both are initiated by running the script rz_install (refer to "Running rz_install" on page 25.) There are only a few points to keep in mind.

• Make sure that all database servers and the license manager are down. Nobody can be using the old release while upgrading to a new one.
• Install the new beside the old. In other words, if you put the old release in /home/razoradm, put the new release there as well. The installation script (rz_install) will move the symbolic link to point to the new release.
• If you wish to drop back to an older release of the product, all you need to do is re-link Razor to point to an earlier release.
• Once you are sure you do not need older releases, feel free to remove them from your system. The upgrade NEVER removes previous versions.
• Be sure and read the file RELEASE_NOTES that accompany every release of Razor. These contain a summary of the changes as well as important information regarding possible database updates, required script changes, etc.

¹ See "Sample installation" on page 27 for an example.
² Note that when the compressed file is expanded, it will contain a version identifier.
³ Your mileage will vary depending upon your configuration, whether you performed a previous Razor installation, etc.