Chapter 1

This chapter details how to install the Apex and Summit releases from the distribution media.

The following topics are covered in this section:

• "Installation Prerequisites"
• "Installation Steps"

Before starting the installation, you need:

• Installation instructions including this manual and the current release note
• The distribution media, which contains the software and on-line help for the current release
• A general understanding of your UNIX operating system and the X Window System environment
• UNIX system administration ability to log in as root for some of the installation steps

Note: Additional hardware and software requirements are discussed in "Prerequisites".

If you want to integrate Rational licensing with an existing license manager, you need to know the name of the license server and the location of the license file.

You will also need to provide a TCP port number for the license server. The default port number is 1706. Use it unless you have already assigned that port number to another application.

Check for conflicts by searching the /etc/services file or, if you are running the Network Information Service (NIS), by entering this command:

% ypcat services | grep 1706

Note: The license feature names for Apex changed as of the 2.2.2 release. Refer to "Managing Apex/Summit Licenses".

1. Log into any workstation that:

• Gives you access to the CD-ROM drive or tape drive
• Mounts the file system(s) into which you will load the Apex or Summit release

Do not log in as root. Use a regular login account.

2. Create the Rational root directory, which is referred to as rational_dir throughout this guide:

% mkdir rational_dir
% cd rational_dir

For rational_dir, supply a pathname such as: /vendor/rational. The rational_dir directory needs to be visible on all machines you wish to run this product. The NFS name for rational_dir must be the same on all machines.

---

Caution: On HP-UX, if the file system on which the HP executables are installed is NFS mounted, that filesystem must be mounted with the -nointr option on any HP machine. If this filesystem isn't mounted with the -nointr option, debuggers will core dump due to an HP ptrace requirement.

This option should not be placed in the global NIS maps, since it can cause problems for other OS's. One solution in a heterogeneous networked UNIX environment is to install a local auto.accts on the HP-UX machines to override the global NIS map for those file systems which require the -nointr option.

3. Apex and Summit are delivered on CD-ROM by default and on magnetic tape (by special request and additional cost). For tape installs, skip to step 6. For CD-ROM installs, do steps 4 and 5 and then skip to step 7.

When cdinstall completes, skip to step 7.

4. As root, make a directory (if one does not already exist) to be the mount point for the CD-ROM drive. The following examples for each platform uses the directory /cdrom. Make sure you know the device name of the CD-ROM drive. If you do not know the device name for the CD-ROM drive, consult your system administrator. Mounting commands for different operating systems are as follows:

• Sparc/Solaris

  Solaris 2.x with volume management mounts to the /cdrom directory. This happens automatically when you load the CD-ROM drive. You have volume management if the vold daemon is running on your system.

• Sparc/Solaris (Solaris 2.x) without volume management
  # mkdir /cdrom
  # mount -r -F hsfs /dev/dsk/c0t6d0s0 /cdrom

• HP (HP-UX 10.x)
  # mkdir /cdrom
  # mount -r -F cdfs /dev/dsk/c0t2d0 /cdrom

• IBM (AIX 4.1.x and 4.2.x)
  # mkdir /cdrom
  # mount -r -v cdrfs /dev/cd0 /cdrom

• Dec/Alpha Digital Unix (OSF1 4.x)
  # mkdir /cdrom
  # mount -r -t cdfs -o rrip /dev/rz4c /cdrom

Note: If the following error occurs when attempting to read the CD-ROM on your DEC Alpha machine:

/dev/rz4c on /cdrom: No such device.

Verify that /dev/rz4c is the correct device name. If so, it may be necessary to have your system administrator include "options CDFS" in the system configuration file. Once this has been done, it will be necessary to rebuild the kernel. Refer to "man cdfs(4)" for additional information.

• SGI (IRIX 6.x)

  IRIX 6.x with volume management mounts /CDROM automatically after loading the CD into the CD-ROM drive. You have volume management if the mediad daemon is running on your system.

• SGI/IRIX 6.x without volume management
  # mkdir /cdrom
  # mount -r -t iso9660 /dev/scsi/sc0d6l0 /cdrom

  (requires eoe2.sw.cdrom package)

5. Exit root and go to the /cdrom directory and run the cdinstall command. For Solaris with volume management, go to /cdrom/cdrom0. For SGI/IRIX with volume management, go to /CDROM

# exit
% cd /cdrom # (or /cdrom/cdrom0 or /CDROM)
% ./cdinstall

From the cdinstall menu, enter the "rd" key to set the rational_dir directory where you are going to be installing each product. Enter the "sp" key to select a product. Enter the "go" key to begin the install. When cdinstall completes, skip to step 7.

6. For tape installs, you must rewind the tape and load the install scripts using tar. The exact command for reading the tape depends on your tape drive's device name and whether your tape drive is local or remote.

• If your tape drive is local, that is, attached directly to the workstation to which you are logged in, enter:
  % tar xvpf /dev/tape_device

  Or, for HP-UX, enter:

  % tar xvf /dev/rmt/tape_device

• If your tape drive is remote, enter:
  % rsh tape_server -n dd if=/dev/tape_device \
  bs=20b | tar xvBpf -

  Or, for HP-UX, enter:

  % remsh tape_server -n dd \
  if=/dev/rmt/tape_device bs=20b |
  tar xvf -

  For tape_server, supply the hostname of the workstation to which your tape drive is attached.

  • If you get an I/O error, you need to rewind the tape. See step 3.

    If this command results in a tar error, check your .cshrc file for statements that issue messages to the standard output. One way to test this is to issue this command:

    % rsh tape_server uname -a

  • If this command returns anything more than the hostname, the above rsh will fail.

Note: Depending on the way your network security is configured, you might need a .rhosts file in your home directory on the tape server. That .rhosts file, which allows you to specify host and login names that are equivalent and trusted, would need to include the name of the workstation to which you are logged in. As a trusted user, you will be able to access the tape server via rlogin, rsh, or rcp without supplying a password.

The tar command reads in some subdirectories and installation scripts, including the install script that you will run in step 7.

7. Load the Apex/Summit components from the media:

% cd releases/apex./install
% ./install

---

Caution: For tape installs, do not change the default tape drive unless you are sure it is incorrect.

Note: For patch releases, your user community does not need to upgrade their existing subsystems.

The install program allows you to quickly and easily load the default product from the release media with very little user input. If you want to install something other than the default product, you must tailor the installation

The install program has 5 menus. When you run it, you start from the General Menu. You must traverse to the Product-Configuration Menu or the Group Menu and tailor the install. Option `t' will traverse you to one of these 2 menus. From there, you can use option `t' to traverse to the next menu or use option `r' to return to the previous menu. The menus are:

General Menu
 ==> Product-Configuration Menu](optional)
 ==> Group Menu
 ==> Component Menu
 ==> Storage-Location Menu

At each menu, you can select option `h' to get help.

The Product-Configuration Menu allows you to select one, and only one, product configuration. If there is only one product on the release media, this menu is skipped.

The Group Menu allows you to select or deselect a group of components to install. Each group is numbered for you to easily specify a particular one. You may select one or more group numbers at a time.

The Component Menu allows you to select or deselect a component to install. You may enter one or more component numbers at a time.

FLEXlm license code is included for all platforms. However, FLEXlm will only be installed by default for the platform you are running the install on. To install a copy of FLEXlm for another platform, you must tailor the install in the Component Menu.

When the install script finishes, you are done with the release media. Store the CD-ROM (or tape) in a safe place in case you ever need to reinstall the product.

Note: If you have problems installing Rational products run the rreport script located in the install directory. It will help you gather the information needed by Rational support. With this script you can e-mail or FTP the information directly to Rational.

8. If you are installing Apex or Summit and you do not have the licenses listed in "Managing Apex/Summit Licenses", you will need to run the next three scripts.

a. Enter:

% ./get_license_info

This script will help you gather the information you need for configuring your licenses.

After running this script, contact Rational and provide us with the information saved in the LICENSE_INFORMATION file. The phone numbers for Rational are also in this file.

b. After contacting Rational and receiving your license key(s), use your favorite text editor to add them to your license file. This file should have been specified by you when you ran get_license_info.

% <edit> <license_file>

For example, run vi to edit this license file:

% vi /vendor/rational/config/license.dat.

Take the FEATURE, UPGRADE or INCREMENT lines and include them in the file. You can only have one FEATURE line for each license feature. Duplicates will be ignored. The first one in the file takes precedence.

c. Having updated your license file, enter:

%./start_lm

If the license server is already running you can run the lmreread command instead.

This script will start the license daemon if it is not running. If it is running, it will tell the license daemon to reread the license file. You can use it to restart the server. To have the license server restart automatically when the license server machine reboots, you will need root privileges to update the system startup file.

Host O/S:	APEX_ARCH:	System startup file:
Digital Unix	alpha_osf1	/etc/rc2.d/SlmRational.sh
HP-UX	hppa_hpux	/sbin/init.d/SlmRational.sh
IRIX 6.x	mips_irix_n32	/etc/init.d/SlmRational.sh
IRIX 5.x	mips_irix5	/etc/init.d/SlmRational.sh
AIX	rs6k	/etc/inittab
Solaris	sun4_solaris2	/etc/rc2.d/SlmRational.sh

This file needs to be updated so that the system will start the license manager each time the license server boots. A file called install/APEX_ARCH/start_lmgrd is created by the get_license_info script. This script can be copied to the appropriate start file listed in the table above.

You will be instructed by start_lm on how to set the system startup file.

9. Enter:

% ./post_install

This script will prompt you for configuring parts of Apex or Summit that you have installed. You may need to refer to other chapters in this guide or the release note if you are not sure how to respond.

If the license manager is not running, or if it is not installed correctly, post_install will display an error message. If necessary, check that your license file is correct and restart the license server. If post_install still does not work, contact Rational Customer Support.

The post_install script will perform step 10. It prompts you, asking if you want it to do this.

If you are running any Apex or Summit layered products such as TestMate, answer yes when asked to update the Apex or Summit startup file.

10. Create a symbolic link to the current release:

% cd rational_dir
% ln -s releases/apex. apex

This allows Apex and Summit users to reference rational_dir/apex, thereby minimizing the impact of new installations on their personal startup files.

If the symbolic link rational_dir/apex already exists and is pointing to a previous release of Apex or Summit, switch it to point to the new release when you are ready to make the new release the default release for your user community:

% cd rational_dir
% rm apex
% ln -s releases/apex. apex

Then users will get the new release next time they start Apex or Summit

11. For CD-ROM installs, unmount the CD-ROM drive.

• Solaris with volume management (vold is running):

  % eject cd
  

• SGI/IRIX with volume management (mediad is running):

  % eject /CDROM
  

All others must unmount the CD as root.

% su
# umount /cdrom

---

[Prev] [Next]       [TOC] [Index]