[Next] [Prev] [TOC]
[Next] [Prev] [TOC]
This guide explains how to install Rational Rational Rose 98 for UNIX®, hereafter Rose, on Unix platforms.
Before starting the installation, you need:
Proceed straight through all the chapters in this guide, following instructions in the order given.
This section summarizes conventions that are followed by this guide and by the scripts you run to install Rose.
This guide uses the following text conventions:
Also, the variable element I.J.K is used to represent the current release number, where I is the major release number, J is the minor update number, and K is the micro release number. Please substitute the current release number - for example, 4.5 or 4.5.8134 - wherever you see I.J.K.
Rose installation scripts can be run on any type of character terminal or in an X-terminal window on a workstation that is running the X Window System. The scripts assume only that the terminal can print characters and newlines. All output is sent to the installer's screen and recorded in the install.log file.
A script first prints the Rose version and a copyright notice. It then prompts you for any information that is needed. You are allowed to step through the prompts as many times as you wish. Once assured that you have provided the proper responses to each prompt, the script proceeds with installation.
Many prompts give you a limited number of choices - for example: yes or no. In such cases, the scripts provide the following interface:
This chapter details how to install the Rose release from the distribution media.
The following topics are covered in this section:
Before starting the installation, you need:
root for some of the installation steps
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
The default port number for other Rational products is also 1706. Specify the same port number in all installations if you are using the same license server.
Note: The license feature names for Rose have changed for the 98.1 release. Refer to "Managing Rose Licenses" in Appendix A.
Do not log in as root. Use a regular login account.
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.
When cdinstall completes, skip to step 7.
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
Dec/Alpha Digital Unix (OSF1 4.x)
# mkdir /cdrom
# mount -r -t cdfs -o rrip /dev/rz4c /cdrom
Note: The following error can occur when attempting to read the CD-ROM on your DEC Alpha (Digital Unix 4.0B) 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 the following line in your system configuration file:
options CDFS
Once this has been done, it will be necessary to rebuild the kernel.
Refer to "man cdfs(4)" for additional information.
Contact Rational Technical Support if you continue to have problems.
# mkdir /cdrom
# mount -r -F cdfs /dev/dsk/c0t2d0 /cdrom
# mkdir /cdrom
# mount -r -v cdrfs /dev/cd0 /cdrom
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)
/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.
% tar xvpf /dev/tape_device
% tar xvf /dev/rmt/tape_device
% rsh tape_server -n dd if=/dev/tape_device \
bs=20b | tar xvBpf -
% 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 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
rsh will fail.
.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.
% cd releases/rose.I.J.K/install
% ./install
Caution: For tape installs, do not change the default tape drive unless you are sure it is incorrect.
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:
[==> Product-Configuration Menu](optional)
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.
Installing More Than One Architecture
The Rose installation is structured in such a way that executables for several architectures may be present on the same media. You may install executables for more than one platform into the same installation area without conflict, even if those executables come from the same or different sets of media.
The media contains the following kinds of components (for each platform):
A Platform Independent Component. This component must always be installed. However, if you are installing for more than one platform, it must only be installed once.
A Shared Binary Component for each platform. This component must be installed for each platform on which you will execute any variant of Rose.
* Java Add-In Binary Component
* Ada 83 and Ada 95 Add-In Binary Component
* These components must be installed for each platform on which you will execute the specific component.
** If you are installing for more than one platform, these components must only be installed once.
A FLEXlm Component for each platform. This component must be installed for each platform on which you will run a Rose license manager. Note that a license manager running on any platform can serve Rose running on any other platform.
Converter components, which must be installed for each platform on which you need to convert models from other OO tools to Rose models, are no longer included on the media. The conversion tools are now available on Rational's World Wide Web page; its URL is http://www.rational.com.
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.
% ./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.
% <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.
%./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.
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/ROSE_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.
This script will prompt you for configuring parts of Rose 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 Technical Support.
post_install, completes the installation by customizing the configuration (startup) files such as config.csh, config.sh, app-defaults, Rose.ini, and a Rose executable shell.
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
This chapter details Rose configuration, performed after installation. You must complete these steps before using Rose.
The following topics are covered in this section:
Refer to the README file, located in the rational_dir/releases/rose.I.J.K/addins/clearcase directory, which describes how to utilize the Rose/ClearCase integration. You need to know the location of the ClearCase root directory. This is typically in /usr/atria. The clearcase.sh script may be used to configure your Rose/ClearCase integration.
If you have Apex 3.0.0b or greater installed, Rose can be configured with Apex so the two products run in an integrated fashion. Rose will be configured as a layered product (add-on) of Rational Apex. This configuration may be performed during post-install. You will need to know the location of the APEX_HOME directory. Electing this configuration during post-install creates the startup entry in the standard startup file for Apex. Once Apex is started it is automatically configured with Rose.
% cd rational_dir/releases/rose.I.J.K/xprinter
The xprinter directory contains a "ppds" subdirectory. Each file in the "ppds" directory contains descriptions for print devices. Most printer descriptions begin with manufacturer and model for the printer the file describes. For example, the printer description xprinter/ppds/hp3si.pcl begins:
*Product: "(HP LaserJet IIISi)"
*ModelName: "HP LaserJet IIISi PCL Cartridge"
*NickName: "HP LaserJet IIISi PCL Cartridge"
% cd ..
% chmod 644 WindU
For example, the device listing for the HP LaserJet printer described in Step 1 is:
[devices]
HP LaserJet SI=HP3SI PCL5,mylaser:
Note that the device specification determines device-dependent characteristics of output generated by the Rose Print commands. It does not determine the actual printer or file to which the output is written.
In the [ports] section of the WindU file, assign the Unix print command you want used for printing to the VariableName that you defined in the [devices] section. The command should include any options needed for your printer to recognize a PostScript file. Continuing the example above, the following assignment causes output sent to the printer named HP LaserJet SI to be printed using the Unix lp command:
mylaser:=cat | lp
By default, the lp command sends output to the printer specified in your $LPDEST or $PRINTER environment variable. If you have not set either of these variables, you may want to supply a printer name as an option to the lp command in the port assignment:
mylaser:=cat | lp -d laser1
% chmod 444 WindU
When a user first starts Rose, Rose copies the $ROSE/WindU file into a file called .WindU in the user's home directory. The user then has access to the printers and print command you have to set up. If you make changes to the $ROSE/WindU file after users have begun using Rose, you should merge the new $ROSE/WindU file with each Rose user's .WindU file.
Executing rational_dir/releases/rose.I.J.K/bin/rose will run the Rose configuration file config,sh prior to bringing up Rose. The configuration file sets environment information such as the ROSE home directory and location of the license file.
Any user running a previous version of Rose, should do the following - prior to running Rose version 98.2.
It is only necessary to perform these steps once - prior to running Rose version 98.2.
Upon running this release, a new .rose.ini file will be created. Customizations may then be added to this file, as required.
To run Rose, see the following "Using Rose."
Use the following commands to start Rational Rose products:
| Product |
Command |
|---|---|
| Rose 98 |
rose |
| Analyzer |
analyzer |
| Visual Difference and Merge |
visdiff |
These commands are shell scripts contained in the rational_dir/releases/rose.I.J.K/bin directory. The same scripts can be used to run Rose on any architecture; the scripts automatically determine the architecture and run the appropriate executable for the architecture.
This chapter presents an overview of the Rose installation to provide context for the installation procedures from "Installation Quick Start" in Chapter 1.
The following topics are covered in this section:
The major steps in the Rose installation are listed below. The time required for each major step will vary with factors such as your experience level, your workstation load, and your network performance.
This installation guide refers to the Rose version numbers as I.J.K where I is the major release, J is the minor update, and K is the micro release number. Please substitute the current version number when you see I.J.K.
Rose can be installed on a stand-alone workstation or a client-server network that includes many workstations.
Conceptually, you can have different workstations performing each of these roles:
Clients
File Servers
Compute Servers
rlogin) or remote shell (rsh) from the client.
License Server
More commonly, a file server doubles as the license server, and clients double as their own compute servers. In the simplest configuration, a stand-alone workstation performs all roles.
If you are installing Rose on a client-server network, note that you must enter specific commands on specific workstations. For example, the license server daemon must be started on that license server, not on another workstation.
The Rose release is structured as follows:
If previous Rose releases or other Rational products have already been installed, directories such as rational_dir, rational_dir/base/cots, and rational_dir/releases will already exist. Since you will not be creating them yourself while installing this Rose release, make sure that you have write permission to them before starting the installation.
Recommendation: If you have Rose models that were created with a previous Rose release, do not delete your previous release until your models have been successfully converted to Rose 98.
The installation scripts log progress to the install/install.log file. In case you encounter a problem with the installation, this file may help you (or Rational Technical Support) diagnose it.
If you are upgrading from Rose 4.0 or earlier, individual users should read "Upgrading from Rose 4.0 or earlier versions" in the Release Notes.
Ensure that you have the required hardware and software before proceeding with the Rose installation.
Recommendation: Before installing Rose, you might find it helpful to get a copy of the system management guide from your platform vendor.
Note that there may be additional Operating System patch requirements. These are described in Appendix C, "Operating System Patch(es) Requirements Specification". Refer to this specification before proceeding.
The following sections list the recommended configuration to successfully install and use Rose.
You do not need to log in as root to verify that most of these requirements are satisfied. If all are satisfied, you can proceed with the installation. If any are not satisfied, however, you probably will need help from your system administrator. Changing most of these items requires knowledge of your network and workstation configurations as well as root permissions.
Recommendation: Check all the items listed, noting any requirements that are not satisfied. Give the list of needed changes to your system administrator, wait for the changes to be made, and then proceed with the installation.
Hardware Requirements and ConfigurationsThe following table contains the hardware requirements for installation and use of this product. Note that the recommended amount of memory is only the suggested minimum amount. Additional memory may improve performance. Your memory requirements will also be larger if you are constructing larger models.
Your hardware can be configured in various ways. For example:
This chapter describes the requirements for a single-user desktop workstation that you will use either stand-alone or with a file server that provides no support other than file service. The desktop workstation will run all Rose processes.
The alternative is to run all Rose processes on a remote compute server, redirecting the display to your local workstation or X-terminal. If the compute server is shared by several Rose users, it will need to be more powerful than a desktop workstation that supports only one Rose user.
The following table contains the software requirements for installation and use of this product. Note that this is also only a suggested amount of swap space. Your requirements may be larger if you expect to construct very large models. If all of your models are small, you may need less than the amount shown here.
Note that script named check_rose_reqs is included in the rose.I.J.K/install directory that is loaded from the Rose release media. This script can assist you in the verification of required configurations and the minimum recommended resource settings.
While you are installing Rose, the installation scripts automatically use check_reqs -install to verify TCP/IP, the portmap daemon, and host names. These are requirements for the workstation(s) on which you install Rose.
The check_reqs script is run by install and rose scripts to verify TCP/IP, the portmap daemon, host names, memory, page or swap space, pseudo terminals, resource limits, the X Window System, the Motif window manager, and required operating system patches. These are requirements and recommendations for the workstation(s) on which you run Rose.
The check_reqs script is not able to check:
The following topics are covered in this section:
When you buy Rose, you purchase some number of node-locked and/or floating licenses. A node-locked license allows you to use Rose on a specific workstation. Floating licenses allow anyone on your network to use Rose as long as a floating license is available. Thus, the number of licenses that you purchase determines the maximum number of users who can use Rose simultaneously.
For example, if you purchased five licenses and three users are currently using Rose, then two more users can use Rose.
Licenses are controlled by a license manager FLEXlm (software delivered as part of Rose) that runs on a license server (one of your workstations). The license manager monitors license access, simultaneous usage, idle time, and so on.
When you start Rose, you are initially unlicensed. If a license is available, the license manager gives you a license and you retain it as long as you keep using Rose. When you exit Rose, your license is returned to the license manager and becomes available for another user.
If no license is available, you are unable to use Rose until a license is returned by another user.
Rose uses the Flexible License Manager, FLEXlm, from Globetrotter Software, Inc. Rose requires FLEXlm 6.0i. The license manager includes the following components:
Once the daemons and license file are in place, all that remains is to start the license daemon, which in turn will start the vendor daemons.
For convenience, you will probably want to augment a system initialization script on your license server to automatically start the license daemon each time the license server boots.
The names, locations, organization, and contents of system initialization scripts varies from system to system. You might begin by looking at the following files:
Digital Unix: /sbin/init.d/SlmRational.sh
HP-UX: /sbin/init.d/SlmRational.sh
Rose provides installation scripts to guide you through this setup. They are described in Chapter 1, "Installation Quick Start".
Note: You cannot run two rational daemons on the same host, so even though FLEXlm allows you to run multiple lmgrd daemons, you cannot put Rational products under the control of multiple lmgrd daemons on the same host.
To verify that your license manager is operational, you can enter these commands on your license server to see if its daemons are running:
% ps axww | grep -v grep | egrep "lmgrd|rational"
% ps -e | grep -v grep | egrep "lmgrd|rational"
Their output should include lines similar to the following (your pathnames will vary):
1719 - S 0:00 rational_dir/base/cots/flexlm.6.0i/ROSEARCH/lmgrd -c rational_dir/config/license.dat
10424 - S 0:13 rational -T garcon 4 -c rational_dir/config/license.dat
The license manager supports several system-administration commands.
The default Rose license file is rational_dir/config/license.dat. As you install Rational products, you can merge the Rational license data into another license file that you have already set up for another product.
When users start Rose, the start up script (config.sh) automatically defines the environment variable ROSE_LICENSE_FILE for them. FLEXlm uses this variable to locate the license file.
FormatThe license file is a text file that you can edit with any text editor. Your license file will contain lines similar to:
SERVER garcon 1874350 1706
DAEMON rational rational_dir/base/cots/flexlm.6.0i/ROSEARCH
FEATURE rose.modeler.unix rational 5.000 01-jan-00 6 FBE669014E142A4CF378 " " FEATURE rose.ada.unix rational 5.000 01-jan-00 6 EC64C40C38382FEB61BF " " FEATURE rose.c++.unix rational 5.000 01-jan-00 6 FCC488AE261FC124B82A " " FEATURE rose.java.unix rational 5.000 01-jan-00 6 FDB4783E806AF37884A5 " "
In general, one or three server lines are followed by one or more vendor daemon lines, which are followed by one or more feature or increment lines. Rose requires only one server and vendor daemon lines and four feature or increment lines, but your license file may include data for other products, too.
Each server line contains, in order, the:
Each vendor daemon line contains, in order, the:
Each feature and increment line contains, in order, the:
The tokens on each line can be separated by any amount of white space (spaces or tabs). You can edit only four kinds of tokens in the license file:
All other tokens are included as input to the encryption algorithm that produces the encryption codes on the FEATURE lines.
Note: A DEMO FEATURE line (including "DEMO" at the end of the FEATURE line) is a special temporary license which does not require running lmgrd or start_lm. Licensing is activated when the DEMO FEATURE line is placed in the license file.
The feature names for Rose changed in the Rose 98.1 release. Feature names are now in the form rose.product.unix. The product is:
You can customize license access by:
An options file allows you to:
For Rose, lines in the options file have this format:
GROUP name list_of_users
RESERVE number rose.modeler.unix
{USER | HOST | DISPLAY | GROUP} name
INCLUDE rose.modeler.unix
{USER | HOST | DISPLAY | GROUP} name
EXCLUDE rose.modeler.unix
{USER | HOST | DISPLAY | GROUP} name
The following table shows several examples:
Contact Rational Software Corporation to obtain the encryption codes for your Rose installation.
Please be prepared to supply the host name and ID number of your Rose license server, the number of licensed users, and the licensing version of your Rose release. The get_license_info installation script will help you gather this information. The information gathered is put in the LICENSE_INFORMATION file.
Rational Software Corporation will provide your encryption codes and their expiration dates. The codes will be in a 20-digit hexadecimal string - for example: 4B868981DB6D7295573E. The dates will be in a dd-mmm-yyyy format - for example: 31-dec-2001. The day can be expressed as one or two digits, and the year can be expressed as two or four digits - for example: 01-jan-98, or 1-jan-1998. If you express the year as two digits (yy) instead of four digits (yyyy), it is interpreted as 19yy. If your encryption codes never expire, the year (yy) in your expiration dates will be 00.
This chapter describes procedures for interacting with Rational Software Corporation's Technical Support services.
Online support can be found on the World Wide Web at the following location:
http://www.rational.com/support/
This location includes any updates not available at the printing of this manual in relation to such documents as:
This website also includes such information as:
When Contacting Rational Technical Support, please be prepared to supply the following information:
If your site has a designated, on-site support person, please try to contact that person before contacting Rational Technical Support.
Rational Technical Support can provide information and assistance via:
Please refer to Rational's web site at http://www.rational.com/support for current technical support contact listings.
Telephone support is available Monday through Friday from 6:00 a.m. to 6:00 p.m. Pacific time. International telephone support hours span the normal local business hours.
You can obtain technical assistance by sending electronic mail to the appropriate email address indicated in the following table. Electronic mail is acknowledged immediately and is usually answered within one working day of its arrival at Rational. Please include a description of your problem when contacting Rational Technical Support. When sending email concerning a previously-reported problem, please include in the subject field: "re: Case ID XXXXX", substituting your assigned Case ID for XXXXX.
Telephone and email addresses for Rational Technical Support are located here.
You can exchange information with Rational through the Internet, using Rational's anonymous FTP site. The service is available 24 hours a day, 7 days a week. To access the site:
ftp ftp.rational.com
You can also correspond with Rational at the following mailing addresses. Please mark correspondence to expedite its routing once it reaches Rational - for example: "Attention: John Smith" or "Attention: Technical Support."
Rational Software Corporation
18880 Homestead Road
Cupertino, CA 95014
U.S.A.
Rational Software B.V.
Siriusdreef 41
2132 WT Hoofddorp
The Netherlands
Rational Software Pty. Ltd.
Level 13, Tower A, Zenith Centre
821 Pacific Highway
Chatswood NSW 2067
AUSTRALIA
The following describes Rose 98 for Unix operating system runtime and/or patch requirements.
The requirements listed below, are in relation to the following platforms (operating system versions):
Note: This release has been tested
with the following patch versions. While we encourage you to contact the
appropriate vendor to determine if a patch has been superseded we cannot
guarantee release compatibility with a patch version we have not yet tested.
For information regarding the latest patch versions tested with this release,
visit the Rational website at http://www.rational.com/support.
Please contact Rational Technical Support if you encounter any compatibility
difficulties after installing a patch which may have superseded any of
the patches listed below.
Rational Rose requires that the appropriate HP aC++ runtime be installed on your HP-UX 10.20 machine:
Rational recommends the following dynamic loader to enhance operation and to avoid erroneous "out of memory" error messages:
Rational Rose requires that the appropriate HP aC++ runtime be installed on your HP-UX 11.00 machine:
OS-Core.CORE-SHLIBS,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
ProgSupport.LANG-MIN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
OS-Core.CORE-64SLIB,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
To verify the versions installed on your system, run 'what' on each file (i.e.):
to determine exactly which patches have been installed.
Attempting to run Rose without the appropriate HP-UX runtime libraries will typically result in the following types of error messages:
If Necessary to Install HP-UX OS PatchesIf the appropriate aC++ runtime is not installed or the HP-UX 10.20 dynamic loader needs to be updated, you will need to install the necessary HP-UX OS patches. At the time this document was created, the latest patches available and tested with this release are included as follows:
HP-UX 10.x OS Patchesrational_dir/releases/rose.4.5.K/install/patches/
hppa_hpux/hpux_10x
rational_dir/releases/rose.4.5.K/install/patches/
hppa_hpux/hpux_11
HP-UX 10-20 OS Patch (*not* for HP-UX 11.00)
When you display an application running on the hp700mt platform to a different platform, the application does not exit properly if you are using a csh or tsh shell. When you exit the application, the xterm continues to receive carriage returns and you must kill your xterm session. If you are displaying on an HP workstation, the application exits properly. HP patch PHCO_13632 is a csh patch that fixes the problem for csh, but a patch for tsh is not available yet. This error typically only occurs with rlogin, so using telnet instead may be a temporary workaround. If this error affects your application, contact Rational Technical Support for the current status.
To Extract and Install the PatchesRead each HP-UX patch for specific installation instructions.
Note: **Prior to Installing HP-UX OS
Patches**
The OS patches included in this release may have been superseded with newer
patches. In order to obtain information in relation to the latest HP-UX
patch(es), contact either location below.
http://us-support.external.hp.com/
Rational Rose requires that the "libsvld.a" archive from the AIX Shared Library Hookable Symbols Runtime Environment (RTE) be installed on your system.
Attempting to run Rose without this archive, will typically generate the following types of error messages:
Release Location of "libsvld.a"The release location of libsvld.a is:
rational_dir/releases/rose.4.5.K/install/patches/rs6k
How To Install "libsvld.a"
Rational Rose requires that the SGI patches listed in this section be installed on your system.
The latest patches that were tested with this release when this document was created are included as follows.
Note: **Prior to Installing SGI OS
Patches**
Carefully, read the README* file associated with each patch to verify the
patch is correct for your specific machine and processor.
In addition, the OS patches included in this release may have been superseded
with newer patches. Obtain current patch information from the following
SGI website.
http://support.sgi.com/surfzone/patches
Rational Rose 98 for Unix requires that the version of the Solaris shared library for C++ ("/usr/lib/libC.so.5") on your system, include the following symbols:
These symbols may be missing if your system does not include a version of "libC.so.5" which supports the SUN Solaris 4.2 C++ runtime. If this is the case, you will need to install the appropriate Solaris shared library patch for C++, as described below.
Attempting to run the Visual Differencer without the correct version of "libC.so.5" will typically generate the following error messages:
ld.so.1: visdiff: fatal: relocation error: symbol not found:
The latest patches that were available and tested with this release when this document was created are included as follows
Sun Solaris 2.5 and 2.5.1 OS Patch Sun Solaris 2.6 OS PatchTo verify if the shared library patch for C++ is necessary run the following command:
If the symbol is not present, the patch is necessary.
Release Location of Sun Solaris Patches Sun Solaris 2.5 and 2.5.1 Sun Solaris 2.6
http://access1.sun.com/search.html
Rational provides product releases, update releases and patches on our FTP server (ftp.rational.com). This chapter describes how to use the FTP server to install products, updates, patches or make a product release tape.
The following topics are covered in this section:
To install a product release using Rational's FTP server, perform the following:
Select the rinstall URL and do a File:Save As...
(login as user ftp. Use your internet E-mail address as the password. E.g ace@company.com)
Using a web browser, you must do a File:Save As... from the menu bar after selecting rinstall.
The rinstall script automates the process of downloading product files from the FTP server. It is a menu-driven script. It lets you select the product you want to install from an up to date list of products that are currently available from the FTP server. The script has a number of settings to allow you to customize its operations.
Each of the menu items is set by entering an alphabetic key. Here is a sample of the rinstall menu:
Key FTP Install Options Current Settings --- --------------------- ---------------- f ) FTP command: ftp ftp.rational.com u ) FTP user: anonymous p ) FTP user password: NEED-TO-SPECIFY uf) user FTP command: none t ) FTP transfer mode: NEED-TO-SPECIFY d ) FTP storage directory: /vendor/rational/tmp n ) number of retries: 5 rd) Rational directory: NEED-TO-SPECIFY sp) Select a product to install bg) change to background. Run in foreground td) time delay: none r ) reset to factory defaults si) show tracking information q ) quit rinstall
You must select a transfer mode to be used by the install tools. The transfer modes control how and when the files are downloaded from the server. Here is an explanation of the transfer modes:
With this mode you get all of the product files before running the install script. All of the product install files will be downloaded. This is required to make a complete product tape. The rinstall program will retry any failed transfers on a file-by-file basis.
You should use bulk transfer if one of the following is true:
With this mode you get only the product files necessary to complete the install. The rinstall script will invoke the install script. You will tailor the install at this time. The install script will determine which files are needed. This information is passed back to rinstall to download the specific files needed to install the tailored product.
You should use efficient transfer if:
The rinstall program will need to run the install program on the local machine to allow you to tailor the install. If you are not going to install the product on the same machine you are running rinstall, you need to...
This mode is similar to efficient transfer mode. In this mode, the install script gets the component files as it needs them and deletes each component file after it has been used. This results in the minimum amount of disk space being used during the install process.
You should use very_efficient transfer if all of the following are true:
The install machine has access to the Internet. You can install a release using the FTP server. Think of the internet and the FTP server as the install device.
Run the rinstall script, like this:
Set the FTP user password to your E-mail address. Set the transfer mode to very_efficient. Set the Rational directory (e.g /vendor/rational). Select a product to install and follow the instructions given by rinstall to complete the install.
The install machine does not have access to the Internet. You have a Unix machine with a locally attached tape drive. In many cases, the machine you want to install products on does not have access to ftp.rational.com. You can use rinstall to get all of the product files, defer the install step, and write the files to a tape.
Set the FTP user password. Set the transfer mode to bulk or efficient. Set the Rational directory to the default. Select the product. Finally, select the st key to start the transfer, but defer the install.
If you used bulk transfer mode you can create a product install tape using duptape. The duptape script will be transferred over after the product is transferred.
# Recommended. Must use bulk transfer.
With this tape, you can install the product as described in Chapter 1.
As an alternate method, you can make a simple tar tape of the files and include the network_install script on the tape. This method takes more disk space on the installation machine. This method is required if you use efficient transfer mode.
Follow the instructions given by this script.
The install machine does not have access to the internet and you cannot run the rinstall script (e.g. you have a PC).
You need to get all of the files for a particular product copied over from the FTP server and dump the files to a tape. You need to include the network_install script on this tape.
Once you have established an FTP connection to ftp.rational.com, you have two ways to make a tape. This depends on whether there is a product directory for a tar.gz file.
ftp> cd /public/rose98unix/releases/SYS_TYPE
ftp> prompt
ftp> cd rose.4.5.K
ftp> get network_install
ftp> bin
ftp> mget file*
ftp> quit
Using tar, put all of the files (network_install and file*) on a tape. (First alternate):
% tar -cvf tape_device network_install file*
ftp> cd /public/rose98unix/releases/SYS_TYPE
ftp> get network_install
ftp> bin
ftp> get product.x.y.z.tar
ftp> quit
Using tar, put the two files (product.x.y.z.tar and network_install) on a tape. (Second alternate):
% tar -cvf tape_device network_install *tar
To install either kind of tape untar all the files into a directory and run network_install:
% tar -xvf tape_device
% sh network_install
The install machine has access to the Internet through a firewall. Assuming your machine gives you access via these steps, you can use rinstall:
The top part of the rinstall menu shows 4 different settings.:
Key FTP Install Options Current Settings
--- --------------------- ----------------
f ) FTP command: ftp ftp.rational.com
u ) FTP user: anonymous
p ) FTP user password: NEED-TO-SPECIFY
uf) user FTP command: none
The `f' key is used to set the FTP command:
Enter the FTP command to use: [ftp] ftp Enter the FTP server to use: [ftp.rational.com] gateway
The `u' key is used to set the FTP user at the gateway:
Enter the FTP user: [anonymous] ftp@ftp.rational.com
The `uf' key is used to set the user FTP command to login to Rational's FTP machine from your gateway machine. You must set this before setting the password:
Enter a user defined FTP command or 0 to clear: []
ftp@ftp.rational.com george@company.com
The `p' key is used to set the FTP user password at the gateway:
Enter your complete E-mail address: [] *****
Can this be used to send you information via E-mail? no
Enter an E-mail address that can: [] george@company.com
Now, the top part of the rinstall menu will look something like this:
Key FTP Install Options Current Settings
--- --------------------- ----------------
f ) FTP command: ftp gateway
u ) FTP user: george
p ) FTP user password: *****
uf) user FTP command: ftp@ftp.rational.com ...
All of this is subject to your network administrator. The specific way to use your gateway machine may be different.The rinstall program is trying to accommodate a wide range of needs.
You can visit the Rational FTP server to get information about available patches.
To view the current list of available patches, visit the ftp://ftp.rational.com/patch_info/index.html patch information page on our FTP server. From this page you can navigate to the patches you are interested in. There you will find instructions for installing each patch.