Previous Page | Next Page

Managing Your SAS Deployment

Adding, Updating, and Upgrading SAS Software

The topics contained in this section are:

What Is Adding, Updating, and Upgrading?

This document uses the terms "adding," "updating," and "upgrading" in the following ways.

Summary of Adding, Updating, and Upgrading SAS Software

When you are adding, updating, or upgrading your SAS 9.2 deployment, the SAS Deployment Wizard is able to determine whether the order from which you are running the wizard contains SAS software with a newer, older, or identical release level than what is already deployed in the SAS installation directory (commonly referred to as SAS Home).

If the wizard determines that there is newer SAS software in the current order than what's already deployed, then the wizard automatically goes into update mode. Update mode forces you to install updates to your software before you can perform any other deployment task. For example, if you are adding new products or language support to an existing SAS deployment, you will install those in an additional SAS Deployment Wizard session, after the wizard (in update mode) has first updated the products on your machine to match the versions contained in your SAS order.

For more information, see the following:

How the SAS Deployment Wizard Adds, Updates, and Upgrades Software

This topic describes in greater detail how the SAS Deployment Wizard adds, updates, and upgrades SAS software.

The wizard compares the release version of the SAS software in the current order to the SAS software that is deployed on the machine. Three possibilities exist:

Upgrades and updates consist of a new version or an incremental delta update (also referred to as maintenance) to an installed product. If the deployment wizard detects that one or more products in the order have a newer release level than any products deployed in the specified SAS Home on the machine, the wizard goes into update mode. (SAS Home is shorthand for the SAS installation directory (for example, C:\Program Files\SAS). The wizard displays an updates page of all the products deployed on the machine for which there are updates in the current order.

[Review Required Updates page]

The deployment wizard updates page is broken into two sections that list new product versions and new product delta updates (or maintenance). In the example of the updates page shown earlier, SAS Web Application Themes represents a new product version (for example, 9.2 to 9.21). SAS BI Dashboard Help and Documentation represents a delta update (for example, 4.2 to 4.2_M1). If you choose to proceed with your deployment from this order, to the specified SAS Home, the wizard requires that you install these updates to bring your existing deployment to the release level from which your new order was mastered. When you click Next, the wizard automatically upgrades the products to the release levels that are shown on the updates page.

When running in update mode, the wizard displays no deployment plan, SAS installation data file, or language pages down this path. The wizard simply installs the newest versions and delta updates of the product set already deployed in the specified SAS Home. If the update contains updated language support for a specific product (such as, SAS, SAS Enterprise Guide, and SAS Add-In for Microsoft Office), the wizard installs only the update for the languages previously installed. If you are adding new products or language support to an existing SAS deployment, you will install those in an additional SAS Deployment Wizard session, after the update is installed and any customization or validation is performed.

If the deployment wizard detects that one or more products in the software order has an older release level than any products deployed in the specified SAS Home on the machine, the wizard does not go into update mode. Instead, the wizard presents you with an alert box listing those products in your order that are older than the ones deployed on your machine.

[Warning alert box]

SAS wants to make sure that you are always installing software from an order corresponding to a release level that is identical to or newer than the one used to originally deploy your SAS software. Your options are to use a different software order, designate a different SAS Home directory, or uninstall the products that are newer.

If the deployment wizard detects that all the products in the order have an identical release level to all products deployed in the specified SAS Home on the machine, the wizard does not go into update mode. Instead, the wizard presents pages that enable you to perform normal deployment tasks such as deploying products, installing additional software, and so on.

The following diagram summarizes how the SAS Deployment Wizard manages deploying products, installing additional software, and applying updates:

SAS Deployment Wizard Flowchart

[SAS Deployment Wizard Flowchart]

Remove Update Backup Files

Whenever the SAS Deployment Wizard upgrades or updates software on a machine, it creates a backup copy of the software being updated. After you apply the updates, you can use the SAS Update File Cleanup Utility to remove the backup copies to reclaim disk space. To remove update backup files, follow these steps:

  1. Log on as the SAS Installer user to the machine on which the SAS updates were applied.

  2. From an operating system prompt, change to the SASHome/InstallMisc/MIT subdirectory.

    For example, issue one of the following commands:

    • UNIX:

      cd /opt/sas_92/InstallMisc/MIT

    • Windows:

      cd \Program Files\SAS\InstallMisc\MIT

    • z/OS:

      cd /usr/lpp/SAS/SAS_92/InstallMisc/MIT

  3. Type the following command appropriate for your operating system:

    • UNIX and z/OS:

      ./cleanup.sh

    • Windows:

      cleanup.bat

    The SAS Update File Cleanup Utility window appears.

    [SAS Update File Cleanup Utility]

  4. Click Remove Backup Files.

    The utility sweeps through the SAS Home directory structure and deletes backup files.

    [SAS Update File Cleanup Utility in progress]

    When the deletion process is complete, the Complete alert box displays.

    [SAS Update File Cleanup Utility Complete alert box]

  5. Click OK.

    The cleanup utility logs which files and directories that it removes in the following location: SASHome/InstallMisc/InstallLogs/Maintenance/Cleanup_nnnnn.log.

Specify a Different JRE

During a first-time SAS 9.2 deployment, the SAS Deployment Wizard prompts you for the version of the Java Runtime Environment (JRE) that you want to use with the SAS Java applications. Your options are to have the deployment wizard install a JRE that SAS has certified to run with SAS 9.2, or to point to a JRE that you have already installed.

[Select Java Runtime Environment page]

In most situations where you are updating or adding a product to SAS 9.2, the deployment wizard does not prompt you for a JRE. However, you can override this behavior. To specify a different JRE with which to run SAS Java applications, follow these steps:

  1. Log on to the machine on which you run SAS Java applications using the SAS Installer user.

    For more information, see Required External User Accounts for SAS.

  2. Run the deployment wizard using its command line invocation and add the option -forcejreprompt (for example, setup.exe -forcejreprompt ).

    For more information, see this step in "Install and Configure SAS Interactively."

  3. During your deployment wizard session, you should see the Select Java Runtime Environment page that prompts you for a JRE path.

  4. After the deployment wizard has finished executing, change to the SAS installation directory (SAS Home) (for example, C:\Program Files\SAS).

  5. Open sassw.config in a text editor and update the JREHOME property with the path to the new JRE that you want to use.

    For example:

    JREHOME=C:\Program Files\Java\jre6\bin\java.exe

Previous Page | Next Page | Top of Page

Copyright © 2011 by SAS Institute Inc., Cary, NC, USA. All rights reserved.