TYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
Untitled
Installing Rational Rose 3.0 on UNIX
Copyright (c) 1996 Rational Software Corporation.
All rights reserved.
Part Number 507-004226
April 1996 (Software Release 3.0)
This document is subject to change without notice.
Note the Reader's Comments form at the end of this book, which request your
evaluation to assist Rational in preparing future documentation.
RESTRICTED RIGHTS LEGEND:
Use, duplication, or disclosure by the U.S. Government is subject to restrictions
set forth in subparagraphs (a) through (d) of the Commercial Computer Restricted
Rights clause at FAR 52.227-19 when applicable, or in subparagraph (c)(1)(ii) of
the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013,
and in similar clauses in the NASA FAR Supplement.
You may copy this manual for use internal to your company provided you include
Rational's copyright notice and mark the copies "made by customer."
Trademark acknowledgements:
The word "Rational" and Rational's products are trademarks of Rational Software
Corporation. References to other companies and their products use trademarks
owned by the respective companies and are for reference purposes only.
The following copyright notice applies to the software that accompanies this
documentation:
Rational Rose/C++ Release 3.0
Copyright (c) 1991-1996 Rational Software Corporation. All rights reserved.
Rational Software Corporation
2800 San Tomas Expressway, Santa Clara, CA 95051-0951
Contents
Preface i
Before You Start iii
How to Use This Guide iii
Conventions iv
Installation Guide iv
Installation Scripts v
Chapter 1
Overview 1
Installation Checklist 1
Hardware Configurations 2
Directory Structure 3
Chapter 2
Prerequisites 5
Configuration Checklist 5
Hardware Requirements 7
X11/NeWS Patch 9
Chapter 3
Loading Rose 9
Background 9
Installation Steps 9
Reading tape media 10
Installing More Than One Architecture 12
Chapter 4
Configuring Rose 13
Background 13
Preparation 14
Installation Steps 15
Setting Up Your Printer 16
Setting Up User Files 18
Using Rose 18
Appendix A
Managing Rose Licenses 19
How Licenses Work 19
The License Manager 21
License Manager Commands 21
The License File 21
Format 22
Feature Name 23
Options 24
Obtaining Licenses 24
Appendix B
Contacting Technical Support 27
Preface
This guide explains how to install Rational Rose (r) hereafter Rose,
on UNIX platforms.
Before You Start
Before starting the installation, you need:
* This guide, which is your primary source of installation
instructions
* A current Rose release note, which you have read in case it
contains any updates to the instructions in this guide
* The Rose distribution media, which contains the software
and online help for the current Rose release
* A general understanding of the UNIX operating system
and X Window System environment on the platform which
you will install Rose
* Help from your system administrator, or experience in
UNIX system administration, and the ability to log in
as root to do some of the installation steps
How to Use This Guide
Proceed straight through all the chapters in this guide,
following instructions in the order given.
Conventions
This section summarizes conventions that are followed
by this guide and by the scripts you run to install Rose.
Installation Guide
This guide uses the following text conventions:
Example Meaning
rational_dir Indicates a variable element for which you must
supply a value. For example, you might enter
/someplace/rational instead of rational_dir.
./install Specifies literal text that you enter exactly as
shown.
csh Identifies UNIX utilities, pathnames, or filenames.
File:New Specifies the menu and the menu button for an
operation. It means: From the File menu, select
the New menu item.
Return Represents a key that must be pressed to initiate
or complete an action.
Control-C Represents keys that must be pressed along with
one or more modifier keys. For example, while
holding down Control, press C.
% Represents your shell prompt when you are a
regular user. (Do not type the % as part of the
command.)
# Represents your shell prompt when you are the
super user (root). (Do not type the # as part
of the command.)
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,
1.0 or 2.5.1 - wherever you see I.J.K.
Installation Scripts
Rose installation scripts can be run on any type of character
terminal or in an xterm window on a workstation that is running
the X Window System. The scripts assume only that the terminal
can print characters and new lines. All output is sent to the
shell's standard output or standard error.
The script first prints the Rose version and a copyright notice.
Then the script prompts you for any information that it needs.
You are allowed to step through the prompts as many times as
you wish. Once you are sure that you have provided the proper
responses to each prompt, the script proceeds with its
installation steps.
Many prompts give you a limited number of choices - for example:
yes or no. In such cases, the scripts provide the following
interface:
If you enter: The installation script will:
Anything starting with y or Y Assume that you mean yes
Anything starting with n or N Assume that you mean no
Just Return Use the default value displayed
in brackets in the prompt message
An Interrupt
(usually Control-C) Exit without doing remaining
installation steps
Anything else Ask you to please type Yes or No
and repeat the prompt
Chapter 1
Overview
This chapter presents an overview of the Rose installation to
provide context for the installation procedures that follow.
Installation Checklist
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.
1. Read the release note in case it contains updates to the
instructions in this guide.
2. Read the preface and this chapter in this guide to better
understand the procedures that follow.
3. Make sure that your workstations satisfy the requirements
described in Chapter 2, "Prerequisites." You might need
your system administrator's help with some of the requirements.
4. Load the release media as described in Chapter 3,
"Loading Rose."
5. Complete the installation as described in Chapter 4,
"Configuring Rose."
Hardware Configurations
You can install Rose on a:
* Stand-alone workstation
* Client-server network that includes many workstations
You can have different workstations performing each of these roles:
* Clients, which display X windows and accept input
from Rose users
* File servers, which store the Rose installation and
user data such as Rose models. When a file server is
distinct from other Rose workstations, its file systems
must be:
* Visible via the Network File System (NFS)
* Mounted on all Rose workstations with the same pathnames
* Compute servers, which run Rose processes. When a
compute server is distinct from a client, the compute server
is accessed via remote login (rlogin) or remote shell
(rsh) from the client.
* License server, which runs daemons that control
access to Rose.
More commonly, a file server doubles as the license server,
and workstations 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,
observe that you must enter specific commands on specific workstations. For
example, daemons that run on the Rose license server must be started on that
license server, not on some other workstation.
Directory Structure
Plan to structure your rational_dir as follows, where
rose.i.j.k is the current release and rose.l.m.n
and rose.o.p.q are imagined future releases:
rational_dir/
releases/
rose.i.j.k/
rose.l.m.n/
rose.o.p.q/
rose
Chapter 2
Prerequisites
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.
Configuration Checklist
The following table lists 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 Item Recommendation For(b)
Memory(1) 24 + (16 * N) MB of RAM R
Disk space 30 MB for loading release I, R
+ 20 MB during installation
+ 1-3 MB for each Rose model
Tape drive 4mm tapedrive (HP-UX) I
8mm tape drive (SunOS, Solaris and AIX)
CD ROM reader If you are installing from
CD ROM I
(1) This is a suggested minimum amount; additional memory
may improve performance. Your requirements will be
larger if you are constructing large models.
Software Item Requirementa For(b)
Operating system SunOS 4.1.3 R
AIX 4.1 or 3.2.5
Solaris 2.4 or 2.5
HP-UX 9.05 or 10.01
TCP/IP Must be running I, R
Host names Must be configured I, R
Swap space(2) 100 + (32 * N) MB R
X Window System MIT X11R5 R
Sun OpenWindows x.x on
SunOS or Solaris
Window Manager OSF/Motif(tm) 1.2 R
window manager (mwm)
or Sun olwm.
aN = Number of users running Rose simultaneously on a given
workstation
bI = Installing Rose
R = Running Rose
(2) This is a suggested amount. Your requirements may be
larger if you expect to be constructing very large models.
If all of your models are small, you may need less than the
amount shown here.
Automated Requirements Checking
A script named check_rose_reqs is included in the
rose.i.j.k/bin directory that is loaded from the
Rose release disks. 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.
Before using Rose, you (or each Rose user) can use
check_rose_reqs to verify TCP/IP, the portmap daemon,
host names, memory swap space, pseudo terminals,
resource limits, the X Window System, and the Motif window
manager. The check_reqs script cannot check the available
physical memory on some platforms.
Hardware Requirements
Your hardware can be configured in various ways. For example:
* A powerful, stand-alone, desktop workstation
* Moderately powerful desktop workstations with a
central file server
* Less powerful desktop workstations with a
central file server
* X-terminals with a powerful central file and
compute server
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 c
ompute 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.
X11/NeWS Patch
If you are using Sun's X11/NeWS server, you may notice a
problem that will affect Rose. When you select a pop-up menu,
your X server hangs.
To avoid this problem, you can install the following patch
from Sun:
Patch-ID# 100444-55
Keywords Synopsis X11/NeWS, server, patch, xnews,
3.0OpenWindows 3.0: OpenWindows
Server Patch for X11/NeWs server
Date Mar/24/94
SunOS release 4.1, 4.1.1, 4.1.2, 4.1.3
Unbundled Product OpenWindows
Unbundled Release 3.0
To get the patch, contact your local Sun technical support
or download it from your local Sun FTP site.
Chapter 3
Loading Rose
This chapter tells you how to load the Rose release from the
Rose release media.
Background
The Rose release media contain installation scripts and
the Rose components. You use the UNIX tar command to
read the installation scripts, and then use one of the
scripts to load the Rose components.
Installation Steps
1. Log into any workstation that:
Gives you access to the device you will use to read the
Rose media
Mounts the file system(s) into which you will load the
Rose release
Do not log in as root. Use a regular login.
2. If Rational Apex (and/or other Rational products) have already
been installed, the Rational root directory -referred to as
rational_dir throughout this guide-will already exist.
If so, use it for Rose, too. If it does not already exist,
create it:
% mkdir rational_dir
% cd rational_dir
For rational_dir, supply a pathname such as:
/someplace/rational
Note that on a client-server network, rational_dir must be
visible (by NFS mounting) to all Rose workstations. Then:
% cd rational_dir
Reading tape media
1. If Rose is delivered on tape, insert the tape into the tape
drive. Some kinds of machines allow you to read a tape using
a drive on another machine on the network.
Note: Your tape drive should be compatible with your system.
For example, you may have problems loading the tape across
the network from a tape drive that is attached to a different
type of system.
2. If the tape needs to be rewound, enter one of the
following commands depending on whether your tape drive
is local or remote.
* If your tape drive is local - that is, attached directly
to the workstation on which you are logged in - enter:
% mt -f /dev/tape_device rewind
Or, for HP-UX enter:
% mt -t /dev/rmt/tape_device rew
* If your tape drive is remote, enter (on HP-UX rewind the tape locally):
% rsh tape_server -n \
mt -f /dev/tape_device rewind
For tape_server, supply the hostname of the workstation
which your tape drive is attached.
3. The exact command for reading the tape also depends on
your tape device'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 on which you are logged in - enter:
% tar xvpf /dev/tape_device
Or, on 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.
The tar command reads in some of the subdirectories
and installation scripts, including the install script that
you will run in the next step.
4. Load the Rose components from the tape:
% cd releases/rose.I.J.K/install
% ./install
The install script will prompt you for the device, host, and so on,
and then it will read the Rose components from the tape.
When the install script is finished, you are done with
the release tape. Store it in a safe place in case you
ever need to reinstall Rose.
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 different
sets of media.
The media contains the following kinds of components:
Platform Independent Component. This component must
always be installed. However, if you are installing
from more than one media set, it must only be installed once.
Shared Binary Component for each platform. This
component must be installed for each platform
on which you will execute any variant of Rose.
Rose/C++ and Analyzer Component for each platform.
This component must be installed for each platform on
which you will execute Rose/C++.
FLEXlm Component for each architecture. 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 architecture
can serve Rose running on any other architecture.
Converter component for each architecture. This
component must be installed for each platform on
which you need to convert models from other OO tools
to Rose models. The available conversion tools are
accessible via our World Wide Web page, www.rational.com.
Chapter 4
Configuring Rose
This chapter tells you how to configure Rose after loading it
from disks. You must complete these steps before using Rose.
Background
To complete the installation, you must run four scripts:
* get_license_info, add_license_info, and start_lm,
which help you configure your Rose licensing.
For more details about licensing, see Appendix A,
"Managing Rose Licenses."
* post_install, which completes the installation by
customizing the configuration (startup) files such
as config.csh, config.sh, app-defaults, rose.ini,
and a Rose executable shell.
Preparation
Rose uses the FLEXlm license manager to manage access to the
product. FLEXlm manages Rose floating and node-locked licenses.
Rose 3.0 uses FLEXlm version 4.1. If upgrading from a version
of Rose prior to Rose 2.7, you must install FLEXlm 4.1.
You do not need to reinstall FLEXlm if you are upgrading
from Rose 2.7.
If you want to integrate Rose 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.
You can check for conflicts by searching the
/etc/services file or by entering this command if you are
running the Network Information Service (NIS).
% ypcat services | grep 1706
Note: 1706 is the default port number for other Rational
products. If you are installing Rose, and if you want
to use the same license server, specify the same port number.
Installation Steps
1. Log into any workstation that mounts the file system(s)
into which you loaded the Rose release. Do not log in as root.
Use the regular login.
2. Go to Rose's install subdirectory
% cd rational_dir/releases/rose.i.j.k/install
3. Enter:
% ./get_license_info
This script will help you gather the information you need for
configuring your Rose license. This information is stored as a
part of the rational_dir/releases /rose.i.j.k/install/install.log file.
4. Contact Rational to request an encryption code (also known
as a license key) and its expiration date, using one of the
following methods:
* Send LICENSE_INFORMATION file via e-mail to
support@rational.com.
* Telephone Rational using phone numbers in
LICENSE_INFORMATION file.
5. Enter:
% ./add_license_info
This script will help you add your licensing information
to your license file - for example: license.dat.
6. Having updated your license file, enter:
% su # become root
#./start_lm
#exit # leave root
This script will help you:
* Update the system file to start the license manager
each time the license server boots. (Note: The script
will allow you to update this file manually if you prefer.
You will likely need root permissions and perhaps help
from your system administrator.)
* Start - or if it is already running, restart - your
license manager.
Note: If you will be using a multiserver configuration,
you must log into one of the servers and run the start_lm
script on it. When the script is finished, go back to
the machine on which you installed the software to run
the remaining steps.
7. Enter:
% ./post_install
This script customizes the Rose configuration files. The
post_install script also instructs you to verify the
installation before proceeding.
Setting Up Your Printer
1. Go to Rose's xprinter subdirectory
% cd rational_dir/releases/rose.i.j.k/xprinter
The xprinter directory contains several subdirectories
whose names end in PPDS. Each file in a PPDS directory
contains the description for a single print device.
Most printer descriptions begin with manufacturer and
model for the printer the file describes. For example,
the printer description xprinter/PCLPPDS/HP3SI.PPD begins:
*Product: " (HP LaserJet IIISi) "
*ModelName: "HP LaserJet IIISi PCL Cartridge"
*NickName: "HP LaserJet IIISi PCL Cartridge"
2. Search through the PPDS directories until you find the
description file for your printer.
3. Go to the Rose directory.
% cd ..
4. Give yourself write permission to the WindU file.
% chmod 644 WindU
5. Open the WindU file for editing.
6. Make sure that your printer is listed in the [Devices]
section of the file. Device listing take the form:
SymbolicName=PPDSPrefix Type, VariableName:
Where:
* SymbolicName is any name you want to assign
to the printer. This name appears in the list of
printers in Rose's Printer Setup dialog box.
* PPDSPrefix is the name of the description file
for your printer, without the suffix.
* Type is either PCL5 or PostScript.
* VariableName is any string that matches the
name of a print instruction in the [Ports] section.
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 -Plaser1
7. Save and close the WindU file.
8. Remove write permission from the WindU file.
% 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.
Setting Up User Files
1. For each user, edit the ~username/.login or the
~username/.profile file to source the applicable config file
for the UNIX shell in which the user works:
* For csh or tcsh shell, enter the following line
in the .login file:
source rational_dir/releases/rose.i.j.k/config.csh
* For sh or ksh shell, enter the following line in the
.profile file:
rational_dir/releases/rose.i.j.k/config.sh
2. Verify that the config.csh and config.sh files have read
permission for the Rose users.
3. Verify that the Rose directories have execute permission
for Rose users.
Using Rose
You have completed the Rose installation. Use the following commands
to start Rational Rose products:
Product Command
Rose rose
Rose/C++ rose_cpp
Analyzer analyzer
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.
Appendix A
Managing Rose Licenses
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
SoDA simultaneously.
For example, if you purchased five licenses and three users
are currently using Rose, then two more users can use Rose.
How Licenses Work
Licenses are controlled by a license manager (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
the license is returned by another user.
The License Manager
Rose uses the Flexible License Manager, FLEXlm, from
Globetrotter Software, Inc. The license manager includes
the following components:
* A vendor daemon named rational that dispenses
Rose licenses. The rational daemon is used for all
of Rational's licensed products. If you have other
products from other vendors that also use FLEXlm,
they will include their own vendor daemons.
* A license daemon named lmgrd. The same license
daemon is used by all licensed products from all
vendors that use FLEXlm. The lmgrd daemon does
not process requests on its own, but forwards
requests to the appropriate vendor daemon.
* A license file that you maintain. It specifies your
license servers, vendor daemons, and product restrictions.
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:
AIX, HP-UX /etc/inittab
SunOS /etc/rc.local
Solaris /etc/rc2.d/SlmRational.sh
Rose provides installation scripts to guide you through this
setup. They are described in Chapter 4, "Configuring Rose."
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.
License Manager Commands
To verify that your license manager is operational, you can
enter these commands on your license server to see if its
daemons are running (on HP-UX and Solaris 2, use ps -ef
instead of ps axww):
% ps axww | grep lmgrd
% ps axww | grep rational
Their output should include lines similar to the following
(your pathnames will vary):
1719 - S 0:00 /someplace/rational/rose/ROSEARCH/license/lmgrd
-c /someplace/rational/rose/license.dat
10424 - S 0:13 rational -T garcon 4
-c /someplace/rational/config/license.dat
The license manager supports several system-administration commands.
Command Description
lmdown Shuts down license and vendor daemons
lmhostid Reports license manager host ID of workstation
lmremove Returns specific licenses to license pool (for
example, after a workstation crashes)
lmreread Rereads license file, starts new vendor daemons
lmstat Reports status on daemons and feature usage
The License File
The default Rose license file is rational_dir/config/license.dat.
As you install Rose, you can merge the Rose license data into
another license file that you have already set up for another
product.
When users start Rose, the start up script automatically
defines the environment variable LM_LICENSE_FILE for them.
FLEXlm uses this variable to locate the license file.
Format
The 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
/someplace/rational/rose/ROSEARCH/license
FEATURE rose.model.sun4 rational 3.000
30-oct-98 6 FBE669014E142A4CF37 " "
In general, one or more server lines are followed by one or more
vendor daemon lines, which are followed by one or more feature
lines. Rose requires only one of each, but your license file may
include data for other products, too.
Each server line contains, in order, the:
* Keyword SERVER
* Host name of the license server, from hostname
* License manager host ID of the license server,
from lmhostid
* TCP port number to use
Each vendor daemon line contains, in order, the:
* Keyword DAEMON
* Name of the vendor daemon (always rational for Rose)
* Pathname to the directory that contains the executable
code for this daemon (which defaults to
rational_dir/base/cots/flexlm.4.1/rose/ROSEARCH
* Pathname to your options files for this daemon
(optional - see the "Options" section below)
Each feature line contains, in order, the:
* Keyword FEATURE
* Name of the feature
* Name of the vendor daemon, previously defined on a
DAEMON line, that serves this feature (always rational
for Rose)
* Latest (highest numbered) version of this feature
that is supported (3.000) for this release of Rose)
* Expiration date (obtained from Rational for Rose)
* Number of licenses
* Encryption code (obtained from Rational for Rose)
* Vendor string, enclosed in double quotes, contains
node-locked info when licensing Rose as node-locked
* License manager host ID, supplied only when this
feature is bound to a specific host, that is, node-locked
Note: You cannot combine floating and node-locked licenses for
the same product in a single license file.
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:
* Host names on SERVER lines
* TCP port numbers on SERVER lines
* Pathnames to vendor daemons on DAEMON lines
All other tokens are included as input to the encryption algorithm
that produces the encryption codes on the FEATURE lines.
Feature Name
The feature names for Rose have changed from those used in
previous releases. Feature names are now of the form
rose.product.architecture. The product is either model
for Rose or cpp for Rose/C++. The architecture is sun4 for
Sun (both SunOS and Solaris), hppa for HP-UX, and rs6k for IBM AIX.
Note that a single floating license cannot be used to run Rose
on more than one architecture. In past Rose releases, while
this was not enforced, it was in violation of Rational's
license agreement.
If you desire to have one or more floating licenses that may
be used across machine architectures, you may obtain such a license
(with the architecture set to "any" instead of "sun4, hppa or rsk6" )
for an additional charge.
Options
You can customize Rose access by:
1. Creating an options file for the rational daemon.
2. Adding the pathname of the options file as the
fourth field on the DAEMON line for the rational daemon.
An options file allows you to:
* Reserve licenses for specified users or groups of users
* Allow or disallow licenses for certain users
For Rose, lines in the options file have this format:
GROUP name list_of_users
RESERVE number rose.product.architecture
{USER | HOST | DISPLAY | GROUP} name
INCLUDE rose.product.architecture
{USER | HOST | DISPLAY | GROUP} name
EXCLUDE rose.product.architecture
{USER | HOST | DISPLAY | GROUP} name
TIMEOUT rose seconds
Obtaining Licenses
Contact Rational Software Corporation to obtain the encryption
code 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 them. It creates a file
called LICENSE_INFORMATION that can be e-mailed to
support@rational.com.
Rational Software Corporation will provide your encryption code
and its expiration date. The code will be a 20-digit
hexadecimal string - for example: 4B868981DB6D7295573E.
The date will be in a dd-mmm-yy format - for example: 30-oct-94.
The day must be expressed as two digits - for example: 01-oct-98,
not 1-oct-98. If your encryption code never expires, the year
(yy) in your expiration date will be 00.