Preparing to Install and to Configure

Overview of Preparing to Install and to Configure

The following topics are contained in this section:

SAS Deployment Wizard Options

The SAS Deployment Wizard is a cross-platform utility that installs and configures many SAS products. Using a SAS installation data file and a deployment plan for its initial input, the wizard is designed to prompt the customer for all the remaining input at the start of the session so that the customer does not have to monitor an entire deployment.
There are two major ways that you can run the SAS Deployment Wizard:
  • interactively
    This is a standard method of providing input via fields on wizard pages with a back and next button navigation method. You can choose from three levels of configuration prompting: Custom (all prompts), Typical (basic set of prompts), and Express (minimum set of prompts). For more information, see Install and Migrate SAS Interactively.
  • non-interactively
    A record and playback feature enables you to automate a SAS installation for use on multiple machines. This feature is designed for large-scale enterprise deployments to prevent users from having to manually provide input on every page each time the SAS Deployment Wizard is run on a machine. For more information, see Automating SAS 9.3 Client Installation across Multiple Machines.

About Deployment Plans

A deployment plan describes what software should be installed and configured on each machine in a SAS deployment. A deployment plan is an XML file that is used as input to the SAS Deployment Wizard. There are two types of deployment plans: standard and custom. A standard deployment plan describes a common configuration. Standard deployment plans are stored by default in the SAS Software Depot. A custom deployment plan is created by a SAS representative specifically for a site.
  • If a SAS representative created a custom deployment plan for you, an XML file (or a ZIP file containing an XML file) will have been e-mailed to you.
  • If your SAS representative recommended that you use a standard deployment plan, you just need the name of the deployment plan that you will use; you will download the actual deployment plan with your SAS custom order (or included in your custom media that is shipped to you.) During the installation, the standard deployment plan will be available from a drop-down list in the SAS installation program.
  • Your deployment plan must be a valid SAS 9.3 plan. The SAS Deployment Wizard does not accept plans from earlier SAS releases.
At the end of the SAS deployment, the SAS Deployment Wizard makes a copy of the deployment plan it used. The deployment plan can be helpful when you want to add another SAS product or change your SAS configuration. The wizard stores a copy of the deployment plan in the SAS configuration directory in the utilities directory, and inserts a date and time stamp to the deployment plan filename. For example:
C:\SAS\Config\Lev1\Utilities\plan.2009-02-17-11.04.xml
To download the latest SAS 9.3 standard deployment plans, go to http://support.sas.com/installcenter/plans.
If you do not have the deployment plans from your previous SAS deployments, the migration utility analysis report can help you determine what SAS products are configured in your current SAS deployment. For more information, see List of Configured Products in Your Current SAS Deployment.

Changes After SAS 9.1.3 that Affect the Deployment Plan

When you work with your SAS representative to develop a custom deployment plan, or if you are choosing among the standard deployment plans available to you in your SAS 9.3 Software Depot, remember that there have been some deployment plan changes between SAS 9.1.3 and SAS 9.3. The following table enumerates these changes:
Changes After SAS 9.1.3 That Affect the Deployment Plan
Prior to SAS 9.3
In SAS 9.3
Standard deployment plans are not shipped with the SAS Software Depot.
Standard deployment plans are shipped with the SAS Software Depot (and also available at http://support.sas.com/installcenter/plans).
No architectural diagrams and pre-installation checklists that match the standard deployment plans are supplied by SAS.
Architectural diagrams and pre-installation checklists that match the standard deployment plans are supplied by SAS (available at http://support.sas.com/installcenter/plans).
The deployment plan used to deploy SAS is not stored in the SAS configuration directory.
The deployment plan used to deploy SAS is stored in the SAS configuration directory (under SAS-config-dir/Levn/Utilities).
SAS Web Infrastructure Kit is included.
The SAS Web Infrastructure Kit has been replaced by the SAS Web Infrastructure Platform.
Xythos and Apache HTTP WebDAV servers are included.
Xythos and Apache servers are replaced with the SAS Content Server.
Apache Tomcat is included.
Apache Tomcat is replaced with the JBoss Application Server.
A separate deployment plan entry is required for SAS Foundation Services Manager.
No separate entry is required for SAS Foundation Services Manager (part of SAS Management Console).
SAS Query and Reporting Services and SAS Reporting Services are included.
These components are replaced with SAS BI Reporting Services.
SAS Web Report Studio scheduling requires Platform Process Manager.
SAS In-Process Scheduler can be used for SAS Web Report Studio scheduling.
By default, certain deployment plans contain both SAS Web Report Studio and SAS Web Report Viewer.
By default, certain deployment plans contain SAS Web Report Studio only.
The Java Runtime Environment (JRE) is required in deployment plans.
The JRE is no longer included in deployment plans.
SAS Add-In for Microsoft Office is optional in deployment plans (when part of the order).
SAS Add-In for Microsoft Office is required in deployment plans (when part of the order).
Note: In the SAS Deployment Wizard, you can deselect SAS Add-In for Microsoft Office to avoid errors when deploying on machines without Microsoft Office.
SAS Deployment Tester is optional in deployment plans.
SAS Deployment Tester is required in deployment plans.
SAS Pooled Workspace Server is not available.
SAS Pooled Workspace Server is new after SAS 9.1.3.
SAS Framework Data Server is not available.
SAS Framework Data Server is new in SAS 9.3.
SAS 9.2 Table Server is included.
SAS Table Server is replaced by SAS Framework Data Server in SAS 9.3.
SAS 9.2 Web OLAP Viewer for Java is included.
This functionality is added to SAS Web Report Studio.
SAS In-Process Scheduler is not available.
SAS In-Process Scheduler is new in SAS 9.2 and later.
SAS Distributed In-Process Scheduler is not available.
SAS Distributed In-Process Scheduler is new in SAS 9.3.
SAS Shared Services is included.
SAS Shared Services is a part of the SAS Web Infrastructure Platform in SAS 9.3.
SAS Online Doc for the Web is included.
SAS Online Doc for the Web is canceled in SAS 9.3.
Windows 32-bit SAS middle tier is included.
The SAS middle-tier is supported on 64-bit systems only for SAS 9.3.

Installation Order Rules for Multiple Machine Deployments

Be aware that if you are deploying SAS on a multiple-machine, distributed system, you must install software on your computers in a particular order:
  • Always install SAS software on the metadata server machine first.
  • Install SAS Application Servers (such as workspace or stored process servers) on machines other than the metadata server machine.
  • Install the middle tier with SAS Foundation Services (that is, Remote Services).
  • Install the middle tier with SAS Web Infrastructure Platform.
  • Install the middle tier with other Web applications (such as SAS BI Dashboard, SAS Web Report Studio, and so on).
  • Install software on machines that will host only clients last.

SAS Installation Directory (SAS Home) Considerations

Although your SAS Home and SAS configuration directories can share the same parent directory, one directory should not reside inside another. Defining the configuration directory under the SAS Home directory, or vice versa, can lead to file permission issues arising from the need to manage installed files differently than site-specific configurations.
CAUTION:
Users running SAS on 64-bit Linux machines, must keep any 32-bit SAS Foundation products in a separate installation directory (SAS Home). Intermixing 32-bit SAS Foundation products with 64-bit SAS products in the same SAS Home location is not supported and might cause SAS to run improperly.
Note: SAS Home should not be a directory within your SAS Software Depot.
Note: On z/OS, the length of the SAS Home path cannot exceed 54 characters.

Content Repository Considerations

Before deploying SAS 9.3, consider where certain content repositories will reside:
  • SAS Web Infrastructure Platform database
    By default, SAS Framework Data Server is an internal data server format used as the default storage for SAS Web Infrastructure Platform Services. You have the option of using other third-party databases if you choose. For more information, see Database type for SAS Web Infrastructure Platform.
    The SAS Framework Data Server requires that its configuration path be local to the machine. The configuration path should not be on an NFS shared disk. If you want to put your configuration path on a shared disk, then you must make sure that you specify a local path for the data framework server content directory. Setting the data framework server content directory path is possible only on the SAS Deployment Wizard custom configuration prompting level. For more information, see Overview of Configuration Options by Prompt Level.
  • SAS Content Server repository
    In SAS 9.3, you can choose to move to your SAS Content Server repository to the new SAS Web Infrastructure Platform database, or use the machine file system. The SAS Framework Data Server replaces the SAS Table Server, and is the default data store for the SAS Web Infrastructure Platform database. You also have an option to use several third-party databases for the SAS Web Infrastructure Platform database. For more information, see Database type for SAS Web Infrastructure Platform.
    If you want to use the SAS Web Infrastructure Platform database as your SAS Content Server repository, be sure to run the SAS Deployment Wizard using either the typical or custom prompting levels. For more information, see Overview of Configuration Options by Prompt Level.
  • SAS Metadata Server
    We recommend that your metadata repositories reside either on a local file system or a high-performance, high-availability network file system. For more information about metadata repositories, see About SAS Metadata Repositories in SAS Intelligence Platform: System Administration Guide.

Installer Write Permission to the Content Server Migration Package on UNIX

The user ID under which the SAS Deployment Wizard runs must have Write permission for the SAS Content Server directories in the migration package on UNIX. Before running the deployment wizard, change the SCS directory and its child directories from 750 (rwxr-----) to 755 (rwxr--r--).
As a best practice, after running the deployment wizard, be sure to reset the permission for these two directories to their previous values.
Copyright © SAS Institute Inc. All rights reserved.