Preparing to Install and to Configure

The topics contained in this section are:

The SAS Deployment Wizard is a cross-platform utility that installs and configures many SAS products. Using a SAS installation data file (SID file) and a deployment plan (plan.xml) for its initial input, the wizard is designed to prompt the customer for all of 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:

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 included in the SAS Software Depot. A custom deployment plan is created by a SAS representative specifically for a site. At the end of the SAS deployment, the SAS Deployment Wizard makes a copy of the deployment plan that 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:

To download the latest SAS 9.3 standard deployment plans that also contain a corresponding architectural diagram and pre-installation checklist, go to http://support.sas.com/installcenter/plans.

In the second maintenance release for SAS 9.3, the SAS Download Manager automatically downloads the necessary SAS hot fixes required by the SAS products in your initial order. This enhancement makes the following possible: For a list of the hot fixes that the deployment wizard installs, click the link on the wizard's Additional Resources page.

Installing the SAS Intelligence Platform on z/OS consists of two major steps:

For more information, see: http://support.sas.com/documentation/installcenter/93/mvs/index.html.

Starting with the March 2012 release of SAS 9.3, the deployment wizard can be run on operating systems that do not have windowing systems. For more information, see the SAS Deployment Wizard and SAS Deployment Manager User's Guide, available at: http://support.sas.com/documentation/installcenter/en/ikdeploywizug/64204/PDF/default/user.pdf.

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:

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.

We recommend that you deploy the SAS Metadata Server on a dedicated server machine. A machine running only the metadata server greatly simplifies tuning, management, and diagnostics.

For more recommendations, see the SAS Metadata Server section in the System Requirements document for your SAS product.

Before deploying SAS 9.3, consider where certain content repositories will reside:

The SAS Deployment Wizard enables you to select the default locale and languages for the SAS Deployment Wizard and for SAS 9.3. (A separate tool, the SAS Locale Setup Manager, enables you to configure the locale of SAS Java clients. For more information, see Locale Setup Manager.)

One of the first dialog boxes in the deployment wizard is the Choose Language dialog box.

The language that you select in the Choose Language dialog box causes two actions:

Further into the deployment wizard, you have an opportunity to set the language that your SAS 9.3 products support.

And finally, the deployment wizard prompts you for your locale settings.

The locale (or regional) setting controls how SAS 9.3 displays the following:

On Windows and UNIX machines, you can choose to configure SAS 9.3 as a Unicode server. Unicode can be particularly useful when your SAS deployment supports multiple languages. Choosing to make SAS a Unicode server means that SAS writes all of its data sets, catalogs, and text files in UTF-8 encoding. UTF-8 encoding supports both single- and double-byte character sets. However, UTF-8 can make data sharing with SAS sites that use default encodings problematic.

For single-byte character set languages, the chosen locale is set in the configuration file that matches the default language and also in the English configuration file. For example, if you choose fr_FR, this value is added to both the French and English configuration files.

For double-byte character set languages, the chosen locale is set in the configuration file that matches the default language and English (US) is set as the default locale for English (SBCS), with some exceptions.

When a locale is set, a default encoding is used for that locale and the operating system.

For more information about locales and encodings, see the SAS National Language Support (NLS): Reference Guide.

On Windows machines, you can use the SAS Locale Setup Manager (LSM), to configure the locale of SAS Java clients. With the LSM, you can do the following:

You run the LSM from the Windows Start menu (StartAll ProgramsSASSAS Locale Setup Manager 3.1). For more information about how to use the LSM, see its online Help.

For more information about locales, see Locale and Encoding Considerations.

The SAS Deployment Wizard creates multiple SAS Web application servers as needed, based on the products in your SAS order. By default, each SAS Web application is assigned to a specific server for deployment. This distribution helps balance the load on each server, and defines a recommended number of servers based on the products in each configuration.

Most of the time, the deployment wizard numbers these servers sequentially (for example, SASserver1, SASserver2, and SASserver3). However, depending on your particular SAS product order, the default application server names might not be named sequentially.

If you use the default names (for example, SASservern) in your configuration, then we recommend that you also maintain the default numbering scheme.

SAS enables you to use a database other than the SAS Framework Data Server to store SAS Web Infrastructure Platform data. (The SAS Deployment Wizard gives you this option when you choose the Typical or Custom prompting levels.) In SAS 9.3, the following third-party databases are supported:

Third-party databases often have particular requirements that you need to know about, such as database name limits, minimum tablespace sizes, and so on. If you have not already, make sure that you review “Configuring an Alternative Database for SAS Web Infrastructure Platform Services,” available at: http://support.sas.com/resources/thirdpartysupport/v93/appservers/SharedServicesAlternativeDatabase.pdf.

If the machine that you are deploying SAS on matches these characteristics:

then you must perform your SAS 9.3 deployment in the following manner:

The most common topology involving the Load Sharing Facility Scheduler (LSF Scheduler) is to locate it on the same machine as the SAS workspace server.

However, an alternative topology could consist of the following:

To achieve this configuration, you run the deployment wizard twice: first on machine 1 and then on machine 2.

To deploy the SAS BI Lineage Scheduling Server when the LSF Scheduler is installed on a separate machine from the SAS workspace server, follow these steps: