The following topics are covered in this section:
"General Installation Information"
Installation Instructions Prerequisites
This release enforces floating licenses using FlexLm. The install process no longer requires a password.
The license server must be run on one of the NT machines in the network. It is best to first install Apex NT on the machine that will be used as the license server. This allows subsequent installations to correctly specify the license server machine so install process can verify that a license is available.
Configuration of the license server and obtaining of licenses is described in "How to Configure a License Server and Obtain Licenses" .
Installation StepsThis step is important as some of the running programs may be using DLL's installed by a previous release of Apex. This will prevent these DLL's from being removed and hence prevent complete uninstall of previous versions of Apex or successful installation of new versions.
If you have previously installed a version of Apex Ada NT, uninstall it by choosing uninstall from the Rational Apex Ada program group.
Insert the CD-ROM into the CD-ROM drive and execute setup. For example, if your CD-ROM drive is drive e, execute the following command:
e:setup
Installation from Rational's FTP server
Transfer all the files in the directory exchange/private/@@WINNT_Apex@@/apex.1.0.2 on Rational's ftp server to your local disk in binary format. You can use the following commands to do this:
% ftp ftp.rational.com
ftp> cd exchange/private/@@WINNT_Apex@@
ftp> cd apex.1.0.2
ftp> bin
ftp> get release_notes.txt
ftp> get apex_ada.exe
ftp> quit
The release_notes.txt file is this file in Ascii format.
Execute Apex_Ada.exe. This is a self extracting executable which will extract the required files and guide you through the rest of the installation process.
C:tmp. If C: does not have sufficient space to extract the temporary files, a dialog box with a warning message comes up. Click QYes' on this dialog box and extraction will continue in the current drive. About 100MB of space is needed for the temporary files. These files are automatically deleted after the installation is completed.
How to Configure a License Server and Obtain Licenses
Make sure that NetBEUI protocol and either the SNMP service or the NW link (IPX/SPX) is installed on your license server machine. This is required in order to obtain a unique host id for the license server. The NetBEUI protocol can be installed by double clicking on the Network icon from the control panel and selecting the Protocols tab. If the NetBEUI protocol is already installed, it will be present in the list of protocols displayed. If it is not displayed, it can be added by clicking on the Add... button, selecting NetBEUI from the list of protocols displayed, and clicking OK.
A Configure License Server dialog comes up during the Apex Ada NT install process. This dialog asks the user whether this machine should be the license server. If you respond `yes', the machine is configured as the license server. In this case, later in the installation, you will be prompted for the required license information by the Apex Get License Information dialog box. This dialog can also be invoked by double clicking on the Get License Information icon in the Rational Apex Ada folder.
You need to supply the Company Name, Sales order number and Number of Licenses. This information is stored in the licensing.information file in the %APEX_CONFIG_DIRECTORY% directory. This file also stores the hostname of the license server and an unique host identification number.
Send this license.information file to Rational in order to obtain licenses for your installation. Rational will supply you one or more `feature' lines. These lines should be added to a file of your choice and stored on the license server machine.
Once you have obtained the feature lines from Rational and added them to a file of your choice, run Add License Information by double clicking on its icon in the Rational Apex Ada folder. You will be prompted for the filename containing the feature lines. Supply this filename and click OK. The licensing information will be added to the license.dat file in the %APEX_CONFIG_DIRECTORY% directory.
The license server can be started by double clicking on the FLEXlm icon from the Rational Apex Ada folder. This brings up a dialog box that allows you to stop and start the license server and to query its status. This dialog box can also be used to configure the license server so it starts up automatically when the machine is restarted. This dialog box is automatically brought up from the Add License Information dialog.
Licensing -Related Environment Variables APEX_LICENSE_FILE
This variable points to the license server host name. For example, if the license server machine name is lic_server, this variable should have the value @lic_server. The variable is automatically updated during the install process. It can be modified by the user if he/she wishes to change the license server machine.
Checks the license server state by checking whether an Apex Ada license is available. This can be run from the shell to verify that a license is available on this machine.
BORROW_LICENSEThis tool can be used to borrow a license from the available pool of floating licenses for a specified time. The borrowed license becomes available on the client machine for the duration specified, even when the client machine is disconnected from the network. This is specially useful for laptops which may be disconnected from the network and carried around. If the user wishes to run Apex while disconnected from the network he/she must borrow a license before disconnecting. The borrowed license is automatically returned to the pool of floating license after the specified time has expired. This command can be run from a shell or by selecting the Tools:Borrow License... menu item from the Apex GUI. The command line syntax is
apex borrow_license <no of days>
General Installation Information
For both CD-ROM and FTP installations, the setup procedure has been enhanced to optionally allow local installations to use existing Apex installations from other machines on the network instead of re-installing all components locally. Local installations need to run setup to update the registry entries and the environment variables. The setup script will ask whether you want to do a full install locally or use some components from an existing Apex.1.0.2 installation elsewhere on the network. Installing locally gives faster access but will require disk space on the local machine.
After the installation is complete, the new environment becomes available immediately. However shells started before the installation is complete will not have the new environment.
The setup script can also be used to reinstall components of the release in additional locations. The current product has a limitation that all imported views, including Rational supplied views, must be on the same drive. Therefore, if you want to have source towers on more than one drive you will need to reinstall the base subsystems on each drive. This can be done by running setup again. When the installation script asks for "installation type", specify `Use Existing Installation' instead of the default `Full Apex Installation'. You will then be asked which components you would like to reinstall. Specify "Reinstall base subsystems" in this dialog and answer other questions about where to install the new components. The base subsystems will then be reinstalled in the additional location.
The ability to install only certain components of the release can also be used to install only the base subsystems on your local drive and use the rest of the components from a drive on the network.
Note: Due to problems with NT 4.0, copying large files sometimes causes the copied file to be different from the original. Installing Service Pack 3 reduces these problems. If you have problems with the installation, run the "verify_install" program from the CD. This program will verify that each component of the product has been correctly copied.
Rational Apex Ada 95/83 for Windows NT
Copyright © 1993-1998 Rational Software Corporation.
This document is subject to change without notice.
Note the Reader's Comments form at the end of this book, which requests your evaluation to assist Rational in preparing future documentation.
GOVERNMENT RIGHTS LEGEND: Use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in the applicable Rational Software Corporation license agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (Oct 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14, as applicable.
"Rational", the Rational logo, and Rational's products are trademarks or registered trademarks of Rational Software Corporation in the United Staes and in other countries. All other names are used for identification purposes only and are trademarks or registered trademarks of their respective companies. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. Microsoft, Windows, Windows NT, and MS-DOS are trademarks or registered trademarks of Microsoft Corporation.
All rights reserved.
Installation Guide Version 1.0.2b