TutorialInstallation: Preparation




Prev | Up | Next | Back | Forward | Online Documentation Home Page
This chapter outlines the preparation necessary to install Ada-ASSURED. Ada-ASSURED is distributed on CD-ROM or by download. Installation consists of running the setup program for Ada-ASSURED, enabling the appropriate license management software, and setting certain environment variables.


Materials Needed

Installing Ada-ASSURED. To do the installation, which takes approximately ten minutes, you will need: In addition, several of the installation steps may require Administrator privileges. Except where otherwise stated, Administrator privileges are not required.

Running Ada-ASSURED. To run Ada-ASSURED you will need a valid license key. Depending on the type of installation, you may need to request a key from GrammaTech using the form titled ``Ada-ASSURED Software Registration and Installation Key Request.'' All new license keys are contained on the form titled ``Licensing Information for Ada-ASSURED.'' If you are already using Ada-ASSURED, see the Release Notes for more information regarding license keys for this release.


Definition of Terms

Refer to the following terms when using this installation guide.


Planning Your Installation

When planning an installation, you should determine:

System Requirements

Disk Space.
 
To install Ada-ASSURED you will need approximately 30 Megabytes of free disk space. Some of the disk space may be recovered after installation. See Disk Conservation for details.

Memory.
 
Because Ada-ASSURED can edit more than one file at a time in different buffers and windows, its effective performance depends on the size of physical memory and swap space available. The more memory and swap space, the more files that can be edited simultaneously. The following is recommended as a minimum for running Ada-ASSURED:


Planning an Upgrade Installation

Recommended Procedure

GrammaTech recommends the following procedure for preserving customizations from a previous installation of Ada-ASSURED.

  1. Merge your current versions of the enforcement parameters with the newly installed ones. Edit the aahome\files\ aa-default-options.stk or the existing aahome\User\ username\aa-options.stk files to reflect the previous settings (either translated from a X Windows resource file or merged from a previous version of a native Microsoft Windows Ada-ASSURED installation). See below for instructions on how to merge these files.

  2. Confirm that the merged parameters files are correct.

  3. Inform all users of Ada-ASSURED of the new version.

  4. After all users of Ada-ASSURED are using the new version, delete the previous version to reclaim the disk space.

Merging Files

Before attempting to merge your current enforcement parameter file or resource files, complete the installation of the new version and confirm that it works.

Enforcement parameters.
 
The enforcement parameter file is stored in a non-ASCII format and can be updated only by Ada-ASSURED. Use the following instructions for this process.
  1. Save a copy of the new enforcement parameter file, aahome\ files\ .aa_enforcement_params:
    cd aahome\files
    rename .aa_enforcement_params .aa_enforcement_params.orig
  2. Copy the old version of the enforcement parameters file into the new location:
    cd aahome\files
    copy old-aahome\ files\.aa_enforcement_params .
  3. Invoke Ada-ASSURED by entering the command below. It is displayed across two lines because of its length, but you should enter it all on one line.
    aa -command "(define sg:user0 \"aahome\\\
    Ada-ASSURED\\\ files\\\ .aa_enforcement_params\")"
  4. Update the enforcement settings by choosing the Set command from the Options/Enforcement Preferences menu.
  5. While editing the enforcement parameters file, choose the convert-to-new transformation.
  6. Save the updated settings by selecting the Save command from the Options/Enforcement Preferences menu.
  7. Exit Ada-ASSURED by choosing Exit from the File menu.

Resources.
 
Any changes to the Ada-ASSURED resources must be merged by hand using a text editor. See the reference manual on how X resource names are associated with scheme resource variables.


Before Beginning an Installation

Read through the entire installation procedure before starting an installation.

 
STOP!

Have you done the following:


Forward