SAS 7.4 Distributed LASR Visual Analytics Installation and Configuration Guide

3. (Optional) Deploy the SAS High-Performance Analytics infrastructure.

4. Create operating system users and groups and designate ports.

For more information, see Chapter 2, “Pre-Installation: Creating a SAS Software

The following sections provide a brief description of each of these steps.

Subsequent chapters in the guide provide step-by-step instructions.

Step 1: Create a SAS Software Depot

Create a SAS Software Depot, which enables you to install SAS software over your site’s network rather than from the installation media.

Note:

If you chose to receive SAS through Electronic Software Delivery, a SAS

Software Depot is automatically created for you.

Depot,” on page 13 .

Step 2: Check for Documentation Updates

It is very important to check for late-breaking installation information in SAS

Notes and to review the system requirements for your SAS software.

Samples & SAS Notes n n

System Requirements--SAS Visual Analytics 7.4 (Distributed or Nondistributed LASR)

System Requirements--SAS Visual Analytics 7.4 and SAS Visual Statistics

7.4

Step 3: Deploy the SAS High-Performance

Analytics Infrastructure

Note:

SAS Visual Analytics 7.2 requires that you use SAS High-Performance

Analytics environment 2.9 or higher.

The SAS High-Performance Analytics infrastructure consists of the following: n

SAS High-Performance Analytics environment

Deploying SAS Visual Analytics

11 n is the foundation for SAS LASR Analytic Server. A root node is deployed on the grid host and worker nodes are deployed on each remaining machine in the Hadoop cluster.

SAS High-Performance Computing Management Console (optional) is a web application tool that eases the administrative burden on multiple machines in a distributed computing environment.

SAS Plug-ins for Hadoop (optional) n is a group of JAR files and executables that enable SAS LASR Analytic

Server to work with SASHDAT files in a co-located HDFS.

For information about deploying the SAS High-Performance Analytics infrastructure, see the SAS High-Performance Analytics Infrastructure documentation website.

Step 4: Create Operating System Users and

Groups and Designate Ports

Create a set of operating system users and groups that are required during the installation and configuration of your system. Designate a set of ports to use.

SAS Visual Analytics users must have an operating system account. For distributed environments, users must have passwordless SSH on all machines in the cluster or on blades across the appliance. SAS High-Performance

Computing Management Console enables you to perform these two tasks from one location.

For more information, see Chapter 3, “Pre-Installation: Setting Up Users,

Groups, and Ports,” on page 51 .

Step 5: Deploy Required Third-Party Software

Install any required third-party products, such as Python. These products are identified in your

deployment plan .

For more information, see Chapter 4, “Installing Third-Party Software,” on page

Step 6: Deploy the Servers and Middle Tier

Install and configure your SAS LASR Analytic Server, SAS Visual Analytics server, and SAS Visual Analytics middle-tier software using the SAS

Deployment Wizard. The wizard is an installation and configuration tool that is supplied by SAS.

For more information, see Chapter 5, “Deploying the SAS Visual Analytics

Server and Middle Tier,” on page 71

Chapter 1 / Introduction to Deploying SAS Visual Analytics

Pre-Installation: Creating a SAS

Software Depot

Deployment Process Overview: Step One

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

About SAS Software Depots

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Benefits of a SAS Software Depot

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Best Practices for SAS Software Depots

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating SAS Software Depots

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of Creating SAS Software Depots

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Prerequisites for Creating a SAS Software Depot

. . . . . . . . . . . . . . . . . . . . . . . . . . .

Create a Depot By Using the SAS Download Manager

. . . . . . . . . . . . . . . . . . . . . .

Create a Depot By Using the SAS Deployment Wizard

. . . . . . . . . . . . . . . . . . . . . .

Subsetting SAS Software Orders

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of Subsetting SAS Software Orders

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Subset an Order

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List Contents of Subsetted Orders

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Managing SAS Orders

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of Managing SAS Orders

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Change Order Information

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Delete an Order

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Create a Disc Image of Your Order

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Checking Your SAS Software Depot

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of Checking Your SAS Software Depot

. . . . . . . . . . . . . . . . . . . . . . . . . . .

Check Your SAS Software Depot

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Deployment Process Overview: Step One

One prerequisite for deploying SAS is to create a special file system of SAS product and order data—a SAS Software Depot—that the SAS Deployment

Wizard then uses to install and configure SAS.

Creating a SAS Software Depot is the first of six steps required to install and configure SAS Visual Analytics.



1. Create a SAS Software Depot.

3. (Optional) Deploy the SAS High-Performance Analytics infrastructure.

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

4. Create operating system users and groups and designate ports.

“Prerequisites for Creating a SAS Software Depot” on page 18 .

About SAS Software Depots

A SAS Software Depot is a file system that consists of SAS installation files that represent one or more orders. The depot is organized in a specific format that is meaningful to the SAS Deployment Wizard, which is the tool installs and initially configures SAS. The depot contains the SAS Deployment Wizard executable, one or more deployment plans, a SAS installation data file per order, order data, and product data.

Figure 2.1 SAS Software Depot File Structure

Before you can install SAS, you must have a SAS Software Depot to install from.

During a SAS software download, the SAS Download Manager downloads your order, verifies it, and automatically creates a SAS Software Depot. If you receive your SAS Software Order in the form of physical media, then you must create a depot using the SAS Deployment Wizard.

Benefits of a SAS Software Depot

Figure 2.2 Methods for SAS Software Depot Creation

Benefits of a SAS Software Depot

The main advantage of a SAS Software Depot is realized when it resides on the network at a location that you can share access to. When it is shared, a depot provides a faster and more reliable means of installation compared to traditional removable media (cartridges, CDs, DVDs, and so on).

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

Figure 2.3 Shared SAS Software Depot Model

If you have remote sites running SAS without access to the network on which your depot resides, you can use the SAS Deployment Wizard to create your own

SAS media image to write to the removable media of your choice.

Here are some other benefits of using a SAS Software Depot: n centralizes SAS orders n n

The depot enables you to place multiple SAS orders in one location to simplify initial SAS deployment and future maintenance.

makes applying maintenance and upgrades easier

You need only to download the changed depot files instead of having to download an entire SAS order.

saves disk space

Storing multiple SAS orders in a single depot saves disk space because any content shared between SAS orders is not duplicated, but rather shared, in the depot.

A single depot in SAS 9.4 can store SAS installation data files for more than one operating system, making the single, multi-system SAS 9.4 depot cumulatively smaller than the multiple, single-system depots in older versions of SAS.

n n saves download time

Because there is a shared copy of common files, the single, multi-system

SAS depot requires smaller amounts to download.

organizes license keys (also known as SAS installation data files)

The depot enables you to place SAS installation data files in a standard location to better associate license keys with their corresponding SAS orders.

(These SAS installation data files are stored in the

sid_files

directory, directly under the depot’s root.)

Best Practices for SAS Software Depots

17 n identifies multiple SAS orders

The depot supports the SAS Deployment Wizard’s feature that enables you to customize order descriptions and enter notes to better identify multiple

SAS orders residing in a single depot.

Because depots contain your personal SAS order, it is important to use the following best practices for securing and backing up your depot.

Best Practices for SAS Software Depots

For customers who download SAS, their SAS Software Depot is the only copy of their SAS order. The depot contains the files from which SAS is initially installed.

For this reason, it is important to use these best practices when managing your depot: n

Keep your depot.

n n

When you keep your SAS 9.4 depot, applying maintenance and upgrades becomes easier because you have to download only the changed depot files instead of downloading an entire SAS order.

Locate in an empty directory.

Create or download your depot into an empty directory that will not be the future location of the SAS installation directory (SASHOME).

Perform routine backups.

As with your SAS production system, it is important to routinely back up your

SAS Software Depot and to verify the integrity of these backups.

Note:

Another important reason for securing and backing up your SAS

Software Depot is that there are limits on the number of times that you can download your SAS order.

n n n

Secure the depot location.

Problems such as data loss, virus infection, and file corruption can compromise your investment in SAS. It is imperative that you have a comprehensive security policy in place to protect your depot.

Store SAS installation data files with your depot.

The SAS installation data file for your order contains information that is integral to successfully deploying SAS. As you get renewal installation data files from SAS—such as the file that contains your permanent SAS license key—it is important that you store them with your depot in the

sid_files

directory.

CAUTION! Be careful to use the correct installation data file that contains

the SAS products that you are planning to install. Using an incorrect file can cause failure when installing SAS add-on products or other errors later when attempting to run SAS.

Create a SAS Software Depot administrator.

Consider designating one or more users to serve as SAS Software Depot administrators. Users needing to deploy SAS software or to apply maintenance require depot Read and Execute privileges. Depot administration tasks such as initially creating the depot, storing SAS

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

installation data files, and updating order details require depot Write privileges. Separating depot administration from routine depot usage is a best practice that further protects your SAS Software Depot.

Creating SAS Software Depots

Overview of Creating SAS Software Depots

There are two ways that you can create a SAS Software Depot.

Download SAS software.

When you download a SAS order, the SAS Download Manager automatically creates a SAS Software Depot on your system.

Run the SAS Deployment Wizard.

Creating a SAS Software Depot is an option on one of the wizard pages.

Before creating a depot, make sure that you have met the necessary requirements described in the following section.

Prerequisites for Creating a SAS Software Depot

Before you start creating a SAS Software Depot, make sure that you have met the following prerequisites: n

Choose a machine that has the following: o

Internet access n o o

If you are downloading your SAS order, you need a machine that can access the SAS download website. Ideally, this machine should be networked so that you can perform deployments directly from the machine without having to physically relocate the depot to another machine.

Windowing environment

If you want to run the SAS Download Manager and the SAS Deployment

Wizard using a traditional graphical user interface, then on Linux, make sure that a windowing environment such as the Common Desktop

Environment or X11 is installed.

To run the deployment wizard on operating systems that do not have windowing systems, see the SAS Deployment Wizard and SAS

Deployment Manager User's Guide .

certain Linux packages and libraries n

The SAS Download Manager on some 64-bit distributions of Linux might require the compat-libstdc++ RPM.

The SAS Download Manager on Red Hat Enterprise Linux 5 or later requires both the 32-bit and 64-bit versions of the library, libXp.so, to be installed.

For more information, see the SAS Download Manager readme file.

Designate a target directory.

Creating SAS Software Depots

19 n

Decide where you will create the SAS Software Depot. It is helpful if this directory can be shared on a network and accessible to all of the machines on which you will be installing software from the depot.

Note:

SAS recommends that you do not copy a depot from one location to another. Choose a permanent location before you create the depot.

Grant required access permissions.

The SAS installer user must have Write access on the depot target directory.

Windows requires that you run the SAS Download Manager installation program using administrator privileges.

Check disk space requirements.

Make sure you have enough free disk space available on the target directory.

Just before creating a depot, the SAS Deployment Wizard and the SAS

Download Manager both present you with an estimate for required disk space.

Create a Depot By Using the SAS Download

Manager

A SAS Software Depot contains one or more deployment plans, a SAS installation data file, order data, and product data. The depot also contains the

SAS Deployment Wizard executable—the tool required to install and initially configure SAS.

Note:

There is no expiration date for downloading your SAS order. However, if the time period for your initial SAS installation data file has expired, you will have to obtain a current SAS installation data file before you can run the SAS

Deployment Wizard.

Before you can create a depot by using the SAS Download Manager, you must first download it. So, there are two steps involved.

Download and run the SAS Download Manager.

Download a SAS order and automatically create a depot using the SAS

Download Manager

Although these steps flow one after the other, at the end of each step, you can stop and resume the process later.

Follow these steps to download a SAS order and automatically create a depot using the SAS Download Manager:

Locate your software order email sent by SAS. In this email, find the URL for the SAS download website from where you will download the SAS Download

Manager.

Note:

It is very important that you locate your original software order email to get the correct order and SAS installation key to download the software. You

cannot use the renewal order number. The renewal order is a license update and it cannot be used to download software. If you cannot locate your original software order email, contact your SAS Installation Representative or

SAS Contracts at the following URLs: n n http://support.sas.com/adminservices/contact.html

http://support.sas.com/techsup/license

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

Make sure that you have met the necessary requirements described in

Log on to the machine as a SAS Software Depot administrator or a user with depot Read, Write, and Execute privileges.

Note:

Consider designating one or more users to serve as SAS Software

Depot administrators. Users needing to deploy SAS software or to apply maintenance require depot Read and Execute privileges. Depot administration tasks such as initially creating the depot, storing SAS installation data files, and updating order details require depot Write privileges. Windows Vista and later requires that you run the SAS Download

Manager installation program using administrator privileges.

Launch a web browser and navigate to the URL specified in your software order email.

In the prompt in the dialog box, select the option that enables you to save the file to disk.

Choose a path accessible to the machine to download the SAS Download

Manager.

Your download begins.

When your browser has finished downloading the SAS Download Manager, run it. Select the language in which the SAS Download Manager displays messages and prompts.

At some sites, you might see a page that prompts for proxy information. If so, provide proxy server settings for the SAS Download Manager to access the

Internet. If needed, contact your site's system administrator for help with these settings.

9 When prompted, enter your order number and SAS installation key.

Creating SAS Software Depots

Verify the list of SAS products in your order.

We recommend that you add a description for your SAS order (for example,

“TS1M3, Rev. 940_15w29”) to distinguish this from other SAS orders. The

SAS Deployment Wizard will display this order information during the SAS installation.

Note:

At any time after the download, you can run the SAS Deployment

Wizard to add or modify SAS order information. For more information, see

“Change Order Information” on page 39

Select Include complete order contents if you do not want to subset your order.

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

This selection causes the SAS Download Manager to include all the software

in the order. For more information, see “Subsetting SAS Software Orders” on page 32

Specify a depot location and whether you want to remove duplicate files.

Click Next.

The depot location is where you want to download SAS and build the SAS

Software Depot.

We recommend that this directory be empty of any content. The exception is if this directory also contains other SAS Software Depots for the same SAS major release as this order. For more information, see

“Prerequisites for

Creating a SAS Software Depot” on page 18

CAUTION! Make sure that your SAS Software Depot directory is not

nested within another depot directory (for example, C:\Depot1\Depot2).

Launching your SAS installation from a depot that resides within another depot causes your installation to fail.

Select Remove duplicate files and save space for the download manager to evaluate and optimize your depot after downloading your order. This optimization is being performed on the entire depot after the latest download has been added. Therefore, all software in the depot—not just the software being downloaded—is optimized.

Note:

The SAS Deployment Wizard cannot create media from a SAS

Software Depot that has been optimized. However, depots that have been optimized can be copied with the SAS Software Copy Utility.

Depots that have been optimized can be added to later, and the optimization tool can be run on depots to which orders have been added. Optimization can also be performed on depots that have been optimized in the past.

Creating SAS Software Depots

If the directory that you specify does not exist, the wizard prompts you. If you want it to create the directory for you, click Yes.

The SAS Download Manager has finished collecting order input. This is your last opportunity to change any information before downloading the SAS order and writing files to the target directory.

Make one of the following choices: n

Click Download to begin downloading the SAS order and writing files to the target directory.

n n

Click Back to navigate to earlier pages to change order information previously entered.

Click Cancel to terminate the SAS Download Manager session. Note that you will lose order the information previously entered.

Note:

SAS tracks downloads and counts only a complete download toward your download limit.

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

Note:

The Disk space required value that is displayed on the Final Review page will actually be smaller if you have selected the Remove duplicate

files and save space on the earlier page, Specify SAS Software Depot

Options. For more information, see

Step 12 on page 22 .

The SAS Download Manager begins downloading, uncompressing, and creating a SAS Software Depot for your SAS order.

When you see a page similar to the following with the progress indicator at

100%, the SAS Download Manager is finished. Click Next to go to the final page, which describes post-download instructions.

Creating SAS Software Depots

Click Finish to close the SAS Download Manager.

To continue with the software installation, proceed to

Chapter 4, “Installing

Third-Party Software,” on page 65 .

After you finish your SAS 9.4 deployment, be sure to keep your SAS

Software Depot, because it will make applying maintenance and future upgrades easier.

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

Create a Depot By Using the SAS Deployment

Wizard

You can use the SAS Deployment Wizard to create a copy (or subset) of your

SAS Software Depot in another directory. If the new depot location is a remote directory on another machine, the directory must be on a shared network drive accessible from the machine running the wizard.

To create a depot on a machine that does not have shared network storage, you must use another mechanism such as SFTP or SCP to copy the depot. (For more information about these programs, see your operating system documentation.)

To create a SAS Software Depot by using the SAS Deployment Wizard, follow these steps:

Make sure that you have met fulfilled the requirements described in

“Prerequisites for Creating a SAS Software Depot” on page 18 .

Log on to the machine that will contain the depot as a SAS Software Depot administrator or a user with depot Read, Write, and Execute privileges.

Note:

Consider designating one or more users to serve as SAS Software

Manager installation program using administrator privileges.

Start the SAS Deployment Wizard using one of two methods: n

If you are starting the wizard from physical media, proceed as follows, depending on your operating system: o

Windows: o

The

setup.exe

program starts automatically when the media is inserted into the drive.

Note:

If the SAS Deployment Wizard does not start automatically, open Windows Explorer, navigate to the media’s root directory, and double-click

setup.exe

Linux:

Navigate to the media's root directory, and enter

./setup.sh

at a command prompt.

If you are starting the wizard from an existing SAS Software Depot, proceed as follows, depending on your operating system:

Navigate to the depot’s root directory, and do one of the following: o

Windows: o

Double-click

setup.exe

Linux:

Enter

./setup.sh

at a command prompt.

Creating SAS Software Depots

Select the language in which the SAS Deployment Wizard displays messages and prompts.

Select Create or Add to a SAS Software Depot. Do not select Install SAS

software.

Verify the list of SAS products in your order.

We recommend that you update the description for your SAS order to distinguish this order from other SAS orders. The SAS Deployment Wizard will display this order information during the SAS installation.

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

Note:

At any time after the download, you can rerun the SAS Deployment

Wizard to add or modify SAS order information. For more information, see

“Change Order Information” on page 39

If you have multiple orders in your depot, you must select the order for which you want to create a depot. (Creating unique order descriptions helps you select the correct order.)

Select Include complete order contents if you do not want to subset your order. This selection causes the SAS Deployment Wizard to include all the

software in the order. For more information, see “Subsetting SAS Software

Orders” on page 32

Specify a location where you want to download SAS and build the SAS

Software Depot. (This location can be shared storage that physically resides on another machine.)

We recommend that this directory be empty of any content. The exception is if this directory also contains other SAS Software Depots for the same SAS major release as this order.

CAUTION! Make sure that your SAS Software Depot directory is not

nested within another depot directory (for example, C:\Depot1\Depot2).

Launching your SAS installation from a depot that resides within another depot causes your installation to fail.

For more information, see

“Prerequisites for Creating a SAS Software Depot” on page 18

Creating SAS Software Depots

If the directory that you specify does not exist, the wizard prompts you. If you want it to create the directory for you, click Yes.

11 The SAS Deployment Wizard has finished collecting order input. This is your last opportunity to change any information before writing files to the target directory.

Make one of the following choices: n

Click Start to begin creating the depot in the target directory.

n n

Click Back to navigate to earlier pages to change order information previously entered.

Click Cancel to terminate the SAS Deployment Wizard session. Note that you will lose the order information previously entered.

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

If you are running the SAS Deployment Wizard from physical media, the SAS

Deployment Wizard prompts you for media. Continue to provide media as prompted.

Note:

If you are working on a Linux system without an automounter, mount the device. For information about the privileges required to mount a device and the syntax of the

mount

command for your system, see the SAS

Deployment Wizard and SAS Deployment Manager User's Guide .

The SAS Deployment Wizard begins creating a SAS Software Depot of your

SAS order.

When you see a page similar to the following with the progress indicator at

100%, the SAS Download Manager is finished. Click Next to go to the final page, which describes post-download instructions.

Creating SAS Software Depots

Click the

depotsummary.html

link on the page to review the SAS

QuickStart Guide.

Click Finish to close the SAS Deployment Wizard.

If you are using physical media on a Linux system with an automounter, use the

eject

command to remove the media. On a Linux system without an automounter, you must unmount the drive using the

umount

command, and then manually open the drive. For information about the

umount

command to unmount a device on your system, see the SAS Deployment Wizard and

SAS Deployment Manager User's Guide .

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

To continue with the software installation, proceed to

Chapter 4, “Installing

Third-Party Software,” on page 65 .

After you finish your SAS 9.4 deployment, be sure to keep your SAS

Software Depot, because it will make applying maintenance and future upgrades easier.

Subsetting SAS Software Orders

Overview of Subsetting SAS Software Orders

The SAS Deployment Wizard enables you to break up—or subset—your SAS software order. Subsetting your order makes it easier to provision individual SAS clients and conserves download time and disk space.

When you subset your depot, you are creating a copy of your original depot with only those products that you designate based on criteria such as operating system, product type, and language.

Figure 2.4 Specify Subset Options Page

The SAS Deployment Wizard also enables you to create a list of the contents of

your order subset. For more information, see “List Contents of Subsetted

Orders” on page 37 .

Subset an Order

The SAS Deployment Wizard enables you to subset your SAS order based on operating system, product type, and language.

Subsetting SAS Software Orders

Note:

Because of its large size, the

utilities

subdirectory is not included in a subsetted depot.

To subset an order, follow these steps:

Log on to the depot machine as a SAS Software Depot administrator or a user with depot Read, Write, and Execute privileges.

Note:

Consider designating one or more users to serve as SAS Software

Manager installation program using administrator privileges.

Start the SAS Deployment Wizard by navigating to the depot’s root directory and running one of the following commands, depending on your operating system: n

Windows:

Double-click

setup.exe

Linux:

Enter

./setup.sh

at a command prompt.

Select the language in which the SAS Deployment Wizard displays messages and prompts.

4 Select Create or Add to a SAS Software Depot.

5 If you have more than one order, select the order that you want to subset, and then click Next.

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

We recommend that you update the description for your SAS order to distinguish this order from other SAS orders. The SAS Deployment Wizard displays this order information during the SAS installation.

When you are finished adding order information, click Next.

Select Subset order contents, and click Next.

On the Specify Subset Options page, select one or more of the following options, and click Next.

Select By product platform/operating system to choose SAS products based on the operating systems on which the products run. n n

Select By product languages to choose SAS products by the language with which they will be installed.

Select By products to choose SAS products that you want to include in the SAS Software Depot by name.

If you select By products, the drop-down list is activated, enabling you to further refine the products to subset: o

Select SAS Foundation products to include products (and their prerequisites) that are installed only with Base SAS.

o o

Select Client products to include products that are not SAS

Foundation and are intended to be installed on client machines.

Select SAS Foundation and client products to include both kinds of products (and their prerequisites). One example is a depot with Base

SAS and SAS Enterprise Guide.

Note:

If you select By products, you cannot deploy the subsetted products using a deployment plan file. Typically, client products do not require a deployment plan file, so this restriction should not affect deploying them. Also, if you select By products, the SAS Migration

Utility is not included in the subsetted software depot.

Subsetting SAS Software Orders

10 (This page appears if you chose By Products in

Step 9

Select one or more SAS products to add to your new depot, and click Next.

Note:

The page that appears is based on which type of product you chose:

SAS Foundation products, client products, or SAS Foundation and client products. (The page shown here is for SAS Foundation products.)

(This page appears if you chose By product platform/operating system in

Step 9

Select SAS products to add to your new depot based on the operating systems on which they run, and click Next.

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

(This page appears if you chose By product languages in Step 9 .)

Select SAS products to add to your new depot by the language in which they are installed, and click Next.

Specify a directory where the deployment wizard creates your depot, and click Next.

CAUTION! Make sure that your SAS Software Depot directory is not

nested within another depot directory (for example, C:\Depot1\Depot2).

Launching your SAS installation from a depot that resides within another depot causes your installation to fail.

Subsetting SAS Software Orders

Review the Final Review page. If you are satisfied, click Start. Otherwise, click Back, and make changes.

15 After the depot has been created, click Finish to close the SAS Deployment

Wizard.

List Contents of Subsetted Orders

It is helpful to know exactly which SAS products are in an order that has been subsetted. The SAS Deployment Wizard enables you to create a list of the

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

contents of your order subset. You generate this list by using submitting a command when you invoke the wizard: n

Windows n

setup.exe -listdepot output-pathname

Linux:

setup.sh -listdepot output-pathname

For example, a command on Linux might resemble the following:

./setup.sh —listdepot /mydata/order_contents.txt

The deployment wizard executable resides in your depot’s root directory.

The list resembles the following:

Date: 2013 Dec 12 10:02:56

Depot: /nfs/mymachine/vol/vol7/sas_software_depot

Order: 099SPS

+ Base SAS [base__94ts1m0__mvs__ne__sp0__1]

+ Base SAS [base__94ts1m0__mvs__w0__sp0__1]

+ Base SAS Help and Documentation [basedoc__94110__prt__xx__sp0__1]

+ Base SAS JAR Files [basejars__94110__prt__xx__sp0__1]

<...>

Order: 099SQ2_2011-12-01-12.27.01

+ Advanced Analytics Common Components [aacomp__94110__wx6__en__sp0__1]

+ DATA Step to DS2 Translator [accelmva__94160__wx6__en__sp0__1]

+ Microsoft Office Access Database Engine 2010 [ace__94112__prt__xx__sp0__1]

- SAS/GRAPH ActiveX Control [activexgraph__94230__win__de__sp0__1]

+ SAS/GRAPH ActiveX Control [activexgraph__94230__win__en__sp0__1]

- SAS/GRAPH ActiveX Control [activexgraph__94230__win__es__sp0__1]

The character at the beginning of a line indicates how to interpret the output.

A line beginning with a: n n

The line with the order number has

Order:

at the beginning.

plus sign (+) indicates that the product is in the order.

n minus sign (-) indicates that the product is in the depot, but it is not in the specified order.

For more information, see the SAS Deployment Wizard and SAS Deployment

Manager User's Guide .

Managing SAS Orders

Overview of Managing SAS Orders

Using the SAS Deployment Wizard, you can do the following with your SAS order: n n

“Change Order Information” on page 39

“Delete an Order” on page 41

Managing SAS Orders

39 n

“Create a Disc Image of Your Order” on page 43

Change Order Information

Being able to identify a SAS order is important, especially when your SAS

Software Depot contains multiple orders. To change the information about a SAS order, follow these steps:

Log on to the depot machine as a SAS Software Depot administrator or a user with depot Read, Write, and Execute privileges.

Note:

Consider designating one or more users to serve as SAS Software

Manager installation program using administrator privileges.

Start the SAS Deployment Wizard. Navigate to the SAS Software Depot's root directory, and do one of the following, depending on your operating system: n

Windows:

Double-click

setup.exe

Linux:

Enter

./setup.sh

at a command prompt.

Select the language in which the SAS Deployment Wizard displays messages and prompts.

Select Manage this SAS Software Depot.

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

Select the order for which you want to change information, and then click

Change Details.

Update the description for your SAS order to distinguish this order from other

SAS orders. The SAS Deployment Wizard will display this order information during the SAS installation.

Managing SAS Orders

When you are finished adding order information, click OK.

Click Finish to close the SAS Deployment Wizard.

Delete an Order

CAUTION! It is a best practice to always make sure that you have backed up

the SAS Software Depot before deleting an order. Keep in mind that there are limits on the number of times that you can download an order from SAS.

To delete a SAS order, follow these steps:

1 Log on to the depot machine as a SAS Software Depot administrator or a user with depot Read, Write, and Execute privileges.

Note:

Consider designating one or more users to serve as SAS Software

Manager installation program using administrator privileges.

Start the SAS Deployment Wizard. Navigate to the depot’s root directory, and do one of the following, depending on your operating system: n

Windows:

Double-click

setup.exe

Linux:

Enter

./setup.sh

at a command prompt.

Select the language in which the SAS Deployment Wizard displays messages and prompts.

Select Manage this SAS Software Depot.

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

Select Manage this SAS Software Depot.

Select the order that you want to delete, and then click Delete Order.

Managing SAS Orders

Confirm that you want to delete the order by clicking Yes.

The SAS Deployment Wizard begins to delete your order. When all of the order’s files have been deleted, the Manage SAS Software Depot page appears again, without the deleted order listed.

Select Finish to close the SAS Deployment Wizard.

Create a Disc Image of Your Order

If you have SAS running on a remote site that does not have access to the network on which your SAS Software Depot resides, you can use the SAS

Deployment Wizard to create an ISO image of your order. Then, using a media creation tool of your choice you can write the ISO image to the physical media format that you specify: either CD or DVD.

You can create an ISO image on a per-order basis only. If your SAS Software

Depot has more than one order, then you have to make an ISO image of each order.

To create an ISO image of your SAS order, follow these steps:

Log on to the depot machine as a SAS Software Depot administrator or a user with depot Read, Write, and Execute privileges.

Note:

Consider designating one or more users to serve as SAS Software

Depot administrators. Users needing to deploy SAS software or to apply maintenance require depot Read and Execute privileges. Depot

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

administration tasks such as initially creating the depot, storing SAS installation data files, and updating order details require depot Write privileges. Windows Vista and later requires that you run the SAS Download

Manager installation program using administrator privileges.

Start the SAS Deployment Wizard. Navigate to the depot’s root directory, and do one of the following, depending on your operating system: n

Windows:

Double-click

setup.exe

Linux:

Enter

./setup.sh

at a command prompt.

Select the language in which the SAS Deployment Wizard displays messages and prompts.

Select Manage this SAS Software Depot.

Managing SAS Orders

Select the order for which you want to create an ISO image, and then click

Create Media-Ready Image.

Select the type of media (CD or DVD) for which you want to create an image of your order. Provide the target directory where you want the SAS

Deployment Wizard to write this image. When you are ready, click Start.

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

The SAS Deployment Wizard begins writing SAS order files to the target directory.

When the progress indicator displays 100%, the image is complete. Click

OK.

Click Finish to close the SAS Deployment Wizard.

The file system that the SAS Deployment Wizard creates is an ISO image of your SAS order that is logically arranged into directories that map to either

CD or DVD media. Each directory contains a summary to enable you to maintain media labels.

10 Using a media creation tool of your choice, you can now write the ISO image of your SAS order to physical media that you specified earlier: either CD or

DVD.

Checking Your SAS Software Depot

Overview of Checking Your SAS Software Depot

SAS provides a utility with which you can verify the integrity of your SAS

Software Depot. The SAS Software Depot Checker Utility scans your depot and

Checking Your SAS Software Depot

47 assembles a list of the files contained in the depot. The depot checker identifies any missing files. For each file that it finds, the depot checker attempts to validate its size, checksum, and date-and-time stamp.

The depot checker attempts to fix any problems that it encounters and lists the results of its various validation tests. You have the option of printing the results or viewing them in a web browser.

Figure 2.5 Depot Checker Results Displayed in a Web Browser

Check Your SAS Software Depot

To run the SAS Software Depot Check Utility, follow these steps:

Note:

It is recommended that you use the same user account with which the

SAS Software Depot was created to run the SAS Software Depot Check Utility.

In your SAS Software Depot, locate the

utilities/depotchecker

directory.

Depending on your operating system, do the following:

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

Table 2.1 Start Up Commands for the SAS Deployment Wizard

Operating

System

Windows

Linux z/OS

Command

SASDepotCheck.exe

SASDepotCheck.sh

SASDepotCheck.rexx

In the dialog box that appears, navigate to the top level directory of your depot.

The depot checker initializes.

4 From the drop-down list, select the language that you want the depot checker to use when it displays text, and click OK.

You should see a welcome page similar to the following:

Enter the path to your SAS Software Depot (for example,

C:\SAS Software

Depot

6 On the Final Review page, click Start.

Checking Your SAS Software Depot

The depot checker begins scanning your depot. The time required to complete the scan depends on the size of your depot.

When the scan is complete, you see a page similar to the following:

Select one of the following options and then click Finish: n

Save Report writes the results of the depot checker scan to a text file.

n n

View in Browser launches a web browser and displays the results of the depot checker scan.

Print Report prints the results of the depot checker scan.

Chapter 2 / Pre-Installation: Creating a SAS Software Depot

Click Finish.

Pre-Installation: Setting Up Users,

Groups, and Ports

Deployment Process Overview: Step Four

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Defining User Accounts

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of Defining User Accounts

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Controlling User Access to Hosts

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Internal User Accounts

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Required External User Accounts for SAS

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Rights Required by SAS External User Accounts

. . . . . . . . . . . . . . . . . . . . . . . . . . .

Password Policies

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Pre-installation Checklist for External User Accounts for

SAS Visual Analytics

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Defining Groups

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Define the sas Group

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Pre-installation Checklist for Groups for Third-Party Software

. . . . . . . . . . . . . . . .

Pre-installation Checklist for Groups for SAS Visual Analytics

. . . . . . . . . . . . . . . .

Configuring Machine Access

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Designating Ports and Multicast Addresses

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

About Ports and Multicast Addresses

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Multicast Address Considerations

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Pre-installation Checklist for Ports for SAS

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Deployment Process Overview: Step Four

Before you begin installing and configuring your software, you must create a set of required users and groups at the operating-system level, and you must designate a set of TCP/IP ports for the servers to use. This is the fourth of six tasks required to install and configure SAS Visual Analytics.

3. Deploy the SAS High-Performance Analytics infrastructure.



4. Create operating system users and groups and designate ports.

information, see “Create SAS Users and Groups” on page 142

Chapter 3 / Pre-Installation: Setting Up Users, Groups, and Ports

Defining User Accounts

Overview of Defining User Accounts

There are two types of user accounts to understand when deploying SAS: n

Internal user accounts are accounts known only to SAS and are created and authenticated internally in SAS metadata rather than externally.

External user accounts are accounts created outside of SAS metadata.

These accounts are local to a machine or are defined in a network directory service of which the machine is a member, such as LDAP.

The following sections describe the user accounts that SAS and third-party software require. They help you answer these questions: n

What are internal and external user accounts?

n n n

What user rights does each account have and to what groups must each account be assigned?

Should I create local or network directory service accounts?

What password policies should I enforce?

Controlling User Access to Hosts

SAS Visual Analytics uses passwordless secure shell (SSH) for access to the machines in the analytics cluster. The following list identifies some of the requirements for configuring passwordless SSH to enable access: n

Data administrators must configure their user accounts for passwordless

SSH to start and stop SAS LASR Analytic Server instances. Passwordless

SSH is also needed to load and unload tables to server instances. For more information, see the SAS High-Performance Analytics Infrastructure:

Installation and Configuration Guide .

User accounts that are used as shared logins for group access to data must be configured for passwordless SSH. For more information, see the SAS

High-Performance Analytics Infrastructure: Installation and Configuration

Guide .

To reduce the number of operating system (external user) accounts, use the

SAS Installer account for running SAS LASR Analytic Server monitor. Although not required, it is useful to create a SAS First User (sasdemo) account to do a simple validation of your deployment after installation and initial configuration.

Internal User Accounts

SAS identifies internal user accounts by appending a special string to the user

ID. This string begins with an at sign (@) and contains saspw (for example,

@saspw

). For two of the required user accounts, the SAS Administrator and the

SAS Trusted User, the SAS Deployment Wizard prompts you by default to create internal user accounts.

Defining User Accounts

The following table shows the default internal user accounts required by SAS.

(SAS internal user accounts are authenticated on the SAS Metadata Server.)

Table 3.1 SAS Internal User Accounts

Description User ID

SAS Administrator

The user account that has privileges associated with the SAS

Metadata Unrestricted Users role.

sasadm@saspw

SAS Trusted User

The user account that can impersonate other users on connections to the metadata server. Some SAS processes use this account to communicate with the metadata server on a client's behalf.

sastrust@saspw

Search Interface to SAS Content User

The user account that permits access to SAS content that is supplied to SAS Information Retrieval Studio for indexing.

sassearch@saspw

SAS Environment Manager Service

The user account that the SAS Environment Manager Server and its agent uses to communicate while monitoring the processes in your SAS deployment. This internal user account has unrestricted administrative access rights to the metadata server. For more information, see SAS Environment Manager:

User’s Guide.

sasevs@saspw

SAS Anonymous Web User

An optional user account that is used to grant web clients access to applicable SAS Web Infrastructure Platform components. When web clients request access to web services, they are not prompted for credentials. Instead, they are granted access under this user account.

webanon@saspw

In the following table are additional internal user accounts:

Table 3.2 Additional SAS Internal User Accounts

Description dbmsowner

User ID and password for accessing the SAS Web

Infrastructure Platform Data Server. This is the owner of all databases.

SharedServices

User ID and password for accessing the SharedServices database used by the SAS Web Infrastructure Platform.

adminowner

User ID and password for accessing the Administration database used by the SAS Environment Manager.

User ID dbmsowner

SharedServices adminowner

Chapter 3 / Pre-Installation: Setting Up Users, Groups, and Ports

sasevdb

User ID and password for the Environment Manager

Enablement Kit Database.

sasevdb

EVManager

User ID and password for accessing the EVManager database used by the SAS Environment Manager.

EVManager vatadm vatadm

User ID and password for accessing the database used with

SAS Visual Analytics Services.

vdbadm

User ID and password for accessing the database used with

SAS Visual Data Builder.

vdbadm

For more information about SAS internal user accounts and their purposes, see

“Understanding the State of Your System” in SAS Intelligence Platform: System

Administration Guide

Here are some benefits of internal user accounts: n less maintenance n n n n

The account is defined only once in SAS. You do not define this account externally using the authentication provider.

isolation from the host machine security policy

The SAS Administrator and the SAS Trusted User credentials are referenced in many locations within SAS. For example, forcing a recurring password change (a common security policy) might make unnecessary work for the person administering SAS.

independence from IT

You can create additional SAS unrestricted user and administrative user accounts for metadata management without involvement from your IT department.

reduced “headless” external user accounts

The SAS Trusted User is an account used for SAS inter-process communication. It will not be mistaken for a human user.

minimal security exposure to your enterprise

The SAS Administrator and the SAS Trusted User are highly privileged accounts and only provide access to SAS—not to operating system resources.

Required External User Accounts for SAS

SAS requires certain external user accounts for two purposes: installing and running certain SAS server processes.

During installation and configuration, the SAS Deployment Wizard must run under an external user account with the necessary privileges on the target machine to write SAS program and log files. To run servers such as the SAS

Defining User Accounts

Stored Process Server and the SAS Pooled Workspace Server, SAS requires an external user account to be the server process owner. For more information about SAS external user accounts and their purposes, see “About the Initial

User Accounts” in SAS Intelligence Platform: System Administration Guide .

Although it is not required, you might find it useful to create a SAS First User account. You can use this account to test a typical user’s ability to access various SAS applications and to validate your deployment. (A SAS First User account is sometimes referred to as the sasdemo account.) The SAS

Deployment Wizard asks you if you want to create a SAS First User account in

SAS metadata, and you must have an external operating system account available for this purpose. After the wizard finishes, remember that you must add this SAS user to the Visual Analytics Data Administrators Group. For more

As you set up external user accounts, remember to use different external accounts for the SAS First User and the SAS Spawned Servers accounts.

Otherwise, your configuration will generate errors and the SAS Pooled

Workspace Server will not be functional.

As you create these external user accounts, record information about them in the

“Pre-installation Checklist for External User Accounts for SAS Visual

Analytics” on page 56 . You will need this information when you run the SAS

Deployment Wizard later.

The following table shows the external user accounts required by SAS, the recommended user ID, and the machines on which they are authenticated.

Table 3.3 Required SAS External User Accounts

Description

SAS Installer

This user account installs SAS and starts the

SAS LASR Analytic Server monitor.

Recommende d User ID

sas

Machine Where

Authenticated

Every machine

SAS Hadoop User

This user account starts Hadoop on the machines in the cluster. (This user account is created by the SAS Visual Analytics Hadoop configuration script—the hdpsetup command.) hadoop

SAS Spawned Servers

This user account is the process owner for

SAS Stored Process Servers and SAS Pooled

Workspace Servers.

sassrv SAS Stored

Process Server

SAS Pooled

Workspace Server

Note:

For information about the user rights that each external account requires, see

“Rights Required by SAS External User Accounts” on page 56 .

n n

The SAS Installer generally overrides the default configuration directory with the site’s preferred location (for example,

/opt/sas/config

). The SAS

Installer must have Write permission on this path.

Do not use root for the SAS Installer user ID.

Chapter 3 / Pre-Installation: Setting Up Users, Groups, and Ports

TIP

To understand the user accounts required by the SAS analytics cluster, see “Preparing Your System to Deploy the SAS High-Performance Analytics

Infrastructure” in the SAS High-Performance Analytics Infrastructure:

Installation and Configuration Guide .

Rights Required by SAS External User Accounts

Operating systems require that you assign certain rights to the external user accounts used to deploy and to run SAS.

The following table describes the user rights required:

Table 3.4 Rights Required by External User Accounts for SAS

External User

Account

SAS Installer

SAS Spawned

Servers

User Rights Needed

The group that you designate as the primary group for the SAS

Installer must contain the SAS Spawned Servers account.

Member of a group that is the primary group for the SAS

Installer.

(This group does not have to be the primary group for the SAS

Spawned Servers account.)

Password Policies

Note:

This section addresses the passwords for the external user accounts that

SAS requires, not the passwords for regular users of the system.

When you set up passwords for your SAS external user accounts, we highly

recommend that these passwords do not have to be reset when a user first logs on. If, for some reason, it is required that you create passwords that have to be reset, you will have to log on using each account and change the password before you install and configure your software. And, of course, you will need to know the changed password for each account.

By default, passwords for internal user accounts are set not to expire. When passwords for user accounts change, you must use SAS Deployment Manager to update a set of configuration files and some metadata objects. SAS provides instructions for updating these files and metadata objects.

For more information, see “Update a Managed Password” in SAS Intelligence

Platform: Security Administration Guide

Pre-installation Checklist for External User

Accounts for SAS Visual Analytics

Use the following pre-installation checklist to create the necessary external user accounts to deploy and run SAS Visual Analytics.

Note:

Defining Groups

Table 3.5 Pre-installation Checklist for External User Accounts for SAS Visual Analytics

Account Recommended User ID

SAS Installer sas

SAS Spawned

Servers sassrv

Actual User ID You Are Using

CAUTION! Do not use root as the installer account.

Note these important items: n n

During deployment, the SAS Installer user must have Write permission to

/etc/opt/vmware

in order to configure VMware license files on all SAS middle tier machines.

For information about the user rights that each external account requires, see

“Rights Required by SAS External User Accounts” on page 56 .

n n n

The SAS Deployment Wizard prompts you for SAS Installer account and

SAS Spawned Servers account information. You cannot complete the installation without providing it.

Prior to configuration, the SAS Deployment Wizard prompts you for the root

(or sudo) password. Certain SAS products and features use functionality that requires SAS to check user ID authentication and file access authorization.

This, in turn, necessitates that certain files within your SAS installation have setuid permissions and be owned by root.

If your system uses an authentication method other than

/etc/passwd

/etc/shadow

, then you must configure authentication before you begin your SAS software deployment or SAS Visual Analytics will not function properly. For more information, see the Configuration Guide for SAS 9.4

Foundation for UNIX Environments .

Defining Groups

Define the sas Group

To deploy SAS Visual Analytics, you should create an operating system group called sas and make it the primary group for the SAS Installer user. The SAS

Spawned Servers account should be made a member of the sas group.

(Members of the sas group are given access to certain directories and files created by the SAS Deployment Wizard.)

For information about creating groups and adding user accounts, see your Linux documentation.

Pre-installation Checklist for Groups for SAS

Visual Analytics

Use the following pre-installation checklist to make sure that you have created the necessary groups to deploy and run SAS Visual Analytics.

Chapter 3 / Pre-Installation: Setting Up Users, Groups, and Ports

Note:

Table 3.6 Pre-installation Checklist for Groups for SAS Visual Analytics

Recommended

Group Name

sas

Group Members

SAS Installer

SAS Spawned

Servers

Purpose

Primary group for the SAS Installer user. Enables the SAS Deployment

Wizard to create the necessary SAS log and configuration directories.

Through group membership, grants

Write permission to the SAS Spawned

Servers account for modifying specific

SAS log and configuration directories.

Actual Group Name

You Are Using

Data Admin user

SAS First User

Any other users

Owner of the LASRMonitor process.

Enables Data Admin user to load data

(or, create server signature files in

/opt/VADP/var

Limit membership because this privileged group has operating system access to certain configuration files.

Pre-installation Checklist for Groups for Third-

Party Software

Use the following pre-installation checklist to create the necessary groups to deploy and run third-party software.

Note:

Table 3.7 Pre-installation Checklist for Groups for Third-Party Software

Recommended

Group Name

sas

Group Members

SAS Installer (sas)

Operating System and Purpose

Suggested method for assigning required permissions to write to certain installation directories.

Actual Group Name

You Are Using

Configuring Machine Access

For the SAS LASR Analytic Server Monitor process to be able to show the tables that are in-memory on a server instance, network name resolution might need to be modified on the machine that runs the SAS Visual Analytics middletier machine.

Designating Ports and Multicast Addresses

For deployments that use SAS High-Performance Deployment of Hadoop as a co-located data provider, the middle-tier machine typically has network name resolution without additional modification. However, if the machines in the cluster use multiple network interfaces, then make sure that network name resolution works. For

/etc/hosts

on the SAS middle-tier machine, make sure that your machine names resolve. For example:

255.255.255.255 gridhost01 gridhost01.example.com hdfs0

# hdfs0 is not normally public

Designating Ports and Multicast Addresses

About Ports and Multicast Addresses

While you are creating operating system user accounts and groups, you need to review the set of ports that the SAS servers, third-party servers, and spawners in your system will use by default. If any of these ports are unavailable, select an alternate port and record the new port on the following ports pre-installation

checklist “Pre-installation Checklist for Ports for SAS” on page 61

You need to plan for designating IP multicast addresses for all of the machines in your SAS deployment. Multicasting simplifies the ongoing management and deployment of SAS web applications by providing the flexibility to customize the

SAS middle tier and to distribute SAS web components to implement load balancing.

Multicast Address Considerations

Note:

By default, multicasting is not used in the typical SAS deployment, and

SAS Remote Services is turned off. If you created a custom application that uses SAS Remote Services, you can use multicasting and enable SAS Remote

Services.

The SAS Deployment Wizard prompts you to supply a multicast address for inter-machine communication. The wizard provides you with a default multicast address that it generates based on the machine's IP address and the adminlocal scope that is recommended in RFC 3171 (IPv4) or RFC 4291 (IPv6).

A multicast group communication protocol is used to communicate among middle-tier SAS applications in a single SAS deployment (the SAS applications connected to the same SAS Metadata Server). The combination of multicast IP address and multicast UDP port should be different for each SAS deployment and different from those used by other multicast applications at your site.

The IP multicast address must be valid for IP multicasting and should be in the range 224.0.0.0 to 239.255.255.255 for IPv4 or have the prefix ff00::/8 for IPv6.

Typically, the chosen IP multicast address is in the admin-local scope block, which corresponds to 239/8 for IPv4 and ff14::/8 for IPv6. The sample address provided during configuration by the SAS Deployment Wizard conforms to these standards. The address should be unique to SAS applications for the subnet that they are installed on.

The IP multicast UDP port should be open and usable on any machine on which a middle-tier application is to be installed. This is a UDP port and does not conflict with any previous TCP port definitions such as the SAS Metadata

Chapter 3 / Pre-Installation: Setting Up Users, Groups, and Ports

Server. The multicast group communication is intended to be used only within your data center environment. Many sites keep their data center network separated from users via a firewall that will automatically isolate the multicast protocol. Alternatively, the time to live (TTL) parameter can be used to restrict the scope of multicast communication. Your network administrator can suggest a

TTL setting to limit the scope of multicast. The TTL option and the authentication token option both have security implications.

The multicast TTL parameter (default = 1, range = 0–255) affects the number of network hops a multicast packet can take before being dropped. This TTL value must be greater than or equal to the highest number of hops between any two servers containing SAS products. In addition, some network router documentation recommends that multicast datagrams with initial TTL=0 are restricted to the same host, multicast datagrams with initial TTL=1 are restricted to the same subnet, and multicast datagrams with initial TTL=32 are restricted to the same site. Consult your network router documentation or your network administrator to determine the correct values for your environment.

Note:

Make sure that all of the machines in your SAS 9.4 deployment are members of the same subnet or be sure to set the default TTL value to a number higher than 1. The deployment wizard lets you set the TTL value during

SAS 9.4 deployment. For information about how to change this option after deployment, see “Administering Multicast Options” in SAS Intelligence Platform:

Middle-Tier Administration Guide

Because the multicast protocol conveys credentials, it is protected via encryption. By default, the multicast group communication is protected only with a fixed encryption key that is built into the software. If your middle tier is running in an environment that is not well-isolated from user access, then you might want better protection against eavesdroppers and unauthorized group participants. In this case, choose an authentication token known only to your

SAS middle-tier administrative users. The authentication token is a passwordlike string needed to connect to the multicast group and create a site-specific encryption key.

The deployment wizard default simplifies configuration by using the authentication token that is built into the software. This option is best used in development and other low-security environments. It might also be appropriate in higher-security environments where the multicast group communication is isolated from the user community, either via a firewall or TTL option, and where all data center administrative users and operational users have sufficient security approval.

If your multicast group communication is not within a well-isolated data center environment, or if the security procedures at your site require protection for administrative users and operational users in various roles, you should specify an authentication token that is known only to the administrators of the SAS environment. The same token string must be supplied on each tier in the configuration.

By default, there is a code-level authentication token shared between all SAS middle-tier applications to prevent access to the multicast group from unauthorized listeners. If you choose to use a customized authentication token, use the deployment wizard to enter an authentication token value that meets your organization's security guidelines. The authentication token can be any password-like string. In a multi-tier configuration, a prompt appears on each tier that has an application participating in the SAS multicast group. You must

Designating Ports and Multicast Addresses

61 provide the same authentication token string to each tier in the same SAS deployment (that is, each tier associated with the same SAS Metadata Server).

Pre-installation Checklist for Ports for SAS

Use the following pre-installation checklist to see what ports are used for SAS by default and to record the port numbers that you are actually using.

Note:

The SAS Deployment Wizard prompts you for this information. You cannot complete the installation without providing it.

The last digit of the default port number reflects the configuration level that you select in the SAS Deployment Wizard. For example, if you select Lev1, the default port for the SAS Metadata Server is 8561. If you select another level, such as Lev2, the wizard changes the default port to 8562.

Note:

This checklist is superseded by a more complete and up-to-date checklist that can be found at http://support.sas.com/installcenter/plans . This website also contains a corresponding deployment plan and an architectural diagram. Consult the pre-installation checklist provided by your SAS representative for a complete list of ports that you must designate.

Table 3.8 Pre-installation Checklist for Ports

Server or Spawner

E-mail server

HTTP server

HTTP server (secure port)

SAS Remote Services

SAS OLAP Server

SAS Deployment Agent

Event Broker administration

SAS Web Application Server JMX

Port

SAS Environment Manager

Default Port

Data

Direction

Outbound

80 (Windows)

7980 (UNIX)

Inbound and outbound

Actual Port

You Are

Using

443

(Windows)

8343 (UNIX)

Inbound and outbound

5091

5451

5660

6051

6969

Inbound

Inbound and outbound

Inbound

7080

SAS Environment Manager (secured) 7443

Inbound and outbound

Chapter 3 / Pre-Installation: Setting Up Users, Groups, and Ports

Server or Spawner Default Port

SAS/CONNECT server and spawner 7551

SAS Web Report Studio In-Process

Scheduling UDP Port 1

7570

Data

Direction

Inbound and outbound

Actual Port

You Are

Using

Inbound and outbound

7571 SAS Web Report Studio In-Process

Scheduling UDP Port 2

SAS Web Report Studio In-Process

Scheduling UDP Port 3

7572

Inbound and outbound

Event Broker HTTP 8111

Operating System Services scheduler 8451

SAS/SHARE server

Multicast (UDP port)

8551

8561

Inbound

Inbound and outbound

SAS Metadata Server

SAS Object Spawner: operator port

SAS Workspace Server

SAS Stored Process Server: bridge connection

SAS Stored Process Server: load balancing connection 1 (MultiBridge)

SAS Stored Process Server: load balancing connection 2 (MultiBridge)

8561

8581

8591

8601

8611

8621

Inbound and outbound

Inbound

SAS Stored Process Server: load balancing connection 3 (MultiBridge)

SAS Pooled Workspace Server

SAS Object Spawner: SAS Pooled

Workspace Server port bank 1

SAS Object Spawner: SAS Pooled

Workspace Server port bank 2

SAS Object Spawner: SAS Pooled

Workspace Server port bank 3

SAS Stored Process Server: load balancing connection 3 (MultiBridge)

8631

8701

8801

8811

8821

8631

Inbound

Designating Ports and Multicast Addresses

Server or Spawner

SAS Web Infrastructure Platform

Database Server

SAS LASR Analytic Server Monitor

RMI port

SAS High-Performance Analytics environment port

SAS High-Performance Computing

Management Console server

SAS Deployment Tester server

SAS Visual Analytics (Autoload)

Default Port

9432

9971

Data

Direction

Inbound and outbound

Actual Port

You Are

Using

Inbound and outbound

10010 Inbound

10020

10021

10031

Inbound

SAS Information Retrieval Studio

SAS Information Retrieval Studio proxy server

SAS Information Retrieval Studio proxy server admin

SAS Information Retrieval Studio proxy server web admin

SAS Information Retrieval Studio pipeline server

SAS Information Retrieval Studio pipeline server admin

SAS Information Retrieval Studio pipeline server web admin

SAS Information Retrieval Studio index builder

SAS Information Retrieval Studio query server

SAS Information Retrieval Studio query statistics server

SAS Information Retrieval Studio query statistics server UDP

10651

10661

10671

10681

10691

10701

10711

10721

10731

10741

Inbound

Chapter 3 / Pre-Installation: Setting Up Users, Groups, and Ports

Server or Spawner

SAS Information Retrieval Studio crawler admin

SAS Information Retrieval Studio web query server

Default Port

10751

10761

Data

Direction

Inbound

TCP port for middle-tier cache communications

Hadoop Service on the Name Node

Hadoop Service on the Data Node

Cache Locator port

0–65535

Cache Locator membership port range

(TCP/UDP port range)

Hadoop Data Node address

Hadoop Data Node IPC address

Hadoop TaskTracker

Hadoop Name Node web interface

50010

50020

50060

50070

Hadoop Data Node HTTP address

Hadoop secondary Name Node

50075

50090

Hadoop Name Node backup address 50100

Hadoop Name Node backup HTTP address

50105

Inbound and outbound

15452

15453

41415

Inbound

Inbound and outbound

1024–65535 Inbound and outbound

Inbound

Actual Port

You Are

Using

Hadoop Name Node HTTPS address 50470

Hadoop Data Node HTTPS address 50475

Inbound

SAS High-Performance Deployment of Hadoop

JMS Server Port

54310

61616

Inbound

Inbound and outbound

If the default port is set to zero, the operating system selects an available port. Each process on a machine must have its own TCP port. Some operating systems restrict the range of ports usable by non-privileged users, and using restricted port numbers can cause run-time errors in GemFire start-up.

The range of ephemeral ports available for unicast UDP messaging and for TCP failure detection in the peer-to-peer distributed system. These ephemeral ports are created from available ports in a system.

Installing Third-Party Software

Deployment Process Overview: Step Five

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

About Installing Third-Party Products

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Obtaining Third-Party Software

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of Obtaining Third-Party Software

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SAS Software Depot: third_party Directory

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SAS Third-Party Software Website

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

About the Java Runtime Environment

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Pre-installation Checklists for Third-Party Products

. . . . . . . . . . . . . . . . . . . . . . . . .

Overview of Pre-installation Checklists for Third-Party Products

. . . . . . . . . . . . . .

PowerShell

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Python

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

JUnit

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Java Access Bridge

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Platform Suite for SAS

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Deployment Process Overview: Step Five

Installing third-party software is the fifth of six tasks required to install and configure SAS Visual Analytics.

3. Deploy the SAS High-Performance Analytics infrastructure.

4. Create operating system users and groups and designate ports.



5. Deploy required third-party software.

software checklists found in “Pre-installation Checklists for Third-Party Products” on page 67 .

About Installing Third-Party Products

SAS Visual Analytics requires the following third-party products: n

JUnit

Chapter 4 / Installing Third-Party Software

n n

PowerShell

Python

As you install third-party products, print and fill out the appropriate third-party

Note:

You must have the necessary third-party software installed on the current machine, or the utility that you use to deploy SAS, the SAS Deployment Wizard, will not let you complete your SAS deployment.

For more information, see System Requirements--SAS Visual Analytics 7.4

(Distributed or Non-distributed LASR) or System Requirements--SAS Visual

Analytics 7.4 and SAS Visual Statistics 7.4

Obtaining Third-Party Software

Overview of Obtaining Third-Party Software

SAS provides you with two ways to obtain required third-party software: n

SAS Software Depot

SAS third-party software website

SAS Software Depot: third_party Directory

Some third-party products are shipped with SAS 9.4. These products’ installation files and documentation are located in the SAS Software Depot under the

third_party

directory.

Figure 4.1 The third_party Subdirectory in the SAS Software Depot

Platform Suite for SAS is an example of one third-party application that you install in this way. To determine whether any of your third-party software is

Pre-installation Checklists for Third-Party Products

67 distributed with your order, refer to your SAS Software Summary that resides in your SAS Software Depot in your order_number directory under

install_doc

For example:

C:\SAS Software Depot\install_doc\

order_number

\ordersummary.html

Some third-party software can be obtained from the website that SAS maintains.

For more information, see “SAS Third-Party Software Website”

SAS Third-Party Software Website

SAS maintains a third-party software website to help you do the following: n determine what version of the product to install n n obtain the product, if you do not already have it find installation instructions n learn about any patches required

The SAS third-party website is located at http://support.sas.com/resources/ thirdpartysupport/ .

About the Java Runtime Environment

SAS Java applications require the Java Runtime Environment (JRE), which includes a Java Virtual Machine (JVM) that executes the application and a set of standard Java class libraries. On Windows, UNIX, and Linux, the SAS

Deployment Wizard installs the default version of the 32-bit JRE with which SAS has been tested.

If a different supported version of the JRE is required, it can be obtained from the appropriate vendor’s website. Links to the appropriate JRE vendor's website can be found on the SAS 9.4 third-party support site located at http:// support.sas.com/resources/thirdpartysupport/v94 .

Pre-installation Checklists for Third-Party

Products

Overview of Pre-installation Checklists for Third-

Party Products

As you install third-party products, print and fill out the appropriate third-party software checklists.

Note:

You must have the necessary third-party software installed on the current machine, or the utility that you use to deploy SAS, the SAS Deployment Wizard, will not let you complete your SAS deployment.

This section contains checklists for the following third-party products: n

PowerShell

Chapter 4 / Installing Third-Party Software

n n n n

Python

JUnit

Java Access Bridge (optional)

Platform Suite for SAS (optional)

PowerShell

Microsoft Windows PowerShell is a .NET-based configuration management framework that is required to deploy the SAS middle tier on Windows. The SAS

Deployment Wizard uses PowerShell to run configuration scripts that modify path information. During installation, the deployment wizard prompts you to specify the PowerShell installation location.

For more information about PowerShell version requirements and a download link, go to http://support.sas.com/resources/thirdpartysupport/v94/othersw.html

Table 4.1 PowerShell

Description

PowerShell location

Product version

Default Values

\Windows

\System32\WindowsPower

Shell\v1.0

2.2

Actual Values

Python

Python is an open-source, high-level general purpose programming language required for SAS Information Retrieval Studio on the Visual Analytics middle tier.

During installation, the deployment wizard prompts you to specify the Python installation location.

For more information about Python version requirements and a download link, go to http://support.sas.com/resources/thirdpartysupport/v94/othersw.html

Table 4.2 Python

Actual Values Description

Python location

Product version

Default Values

/Python26

2.6

JUnit

JUnit is an open-source software testing framework for Java, and the de facto standard for writing unit and regression tests. Some of the validation tests shipped with SAS products run under the SAS Deployment Tester framework

Pre-installation Checklists for Third-Party Products

69 and require JUnit. During SAS installation, the SAS Deployment Wizard prompts you to specify the location of the JUnit JAR file.

For more information about JUnit version requirements and a download link, go to http://support.sas.com/resources/thirdpartysupport/v94/othersw.html

Table 4.3 JUnit

Description

JUnit jar file location

Product version

Default Values

\Program Files\Junit

/usr/local/junit

4.8.1

Actual Values

Java Access Bridge

The Java Access Bridge (JAB) is a prerequisite for JAWS, the Windows accessibility solution. JAB is shipped with SAS 9.4. For more information, see http://support.sas.com/resources/thirdpartysupport/v94/othersw.html

Platform Suite for SAS

If you will use products from Platform Computing Incorporated either for scheduling or for grid computing, you must install several of the products from the Platform Suite for SAS offering. Platform Suite for SAS includes three products: n

Platform Process Manager n provides scheduling capabilities. Process Manager submits jobs to Platform

LSF and manages dependencies between jobs. (When you install Platform

Process Manager, Platform LSF is also installed.)

Platform LSF (Load Sharing Facility) manages resource requirements and provides for load balancing.

Platform Grid Management Service includes a monitoring daemon that enables administrators to monitor the load on machines running Platform LSF.

If you are using the Platform Suite for SAS for grid computing, you must install Platform LSF and the Platform Grid Management Service. If you want to schedule jobs to run on the grid, you must also install Platform Process

Manager.

For more information about where to install each of these products, see “SAS

Grid Topology” in Grid Computing in SAS .

Platform Suite for SAS is distributed with SAS in the depot

third_party

directory, where you will find the installation programs and instructions.

You can also find the Platform Suite for SAS installation instructions on the SAS

Scalability and Performance focus area on the web at http:// support.sas.com/rnd/scalability/platform/index.html

Chapter 4 / Installing Third-Party Software

Table 4.4 Platform Suite for SAS

Description Default Values

Platform Process Manager port

1966 (inbound)

Product version 8.1

Platform LSF ports

Product version

6878, 6881, 6882, 7869,

7870, 7871, 7872

(inbound)

7.06

Platform Grid

Management Service port

1976 (inbound)

Product version 7.11

Actual Values

Deploying the SAS Visual Analytics

Server and Middle Tier

Deployment Process Overview: Step Six

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Components of SAS Visual Analytics

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to Deploy SAS Visual Analytics

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Which SAS LASR Analytic Server Mode?

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Deploy the SAS High-Performance Analytics Environment

. . . . . . . . . . . . . . . . . . .

SAS Deployment Wizard Options

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

About Deployment Plans

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Reducing the Number of Password Prompts

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Re-entry Feature of the Deployment Wizard

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SAS Visual Analytics Configuration Options

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SAS Deployment Agents

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SAS Metadata Server Clustering

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Server and Middle Tier Topology Constraint Removed in Release 7.1

. . . . . . . .

SAS Web Application Servers

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SAS Web Application Server Clustering

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installation Rules for Multiple-Machine Deployments

. . . . . . . . . . . . . . . . . . . . . . . .

SAS Metadata Server Recommendation

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SAS Metadata Repository Considerations

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Locale and Encoding Considerations

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A Note about Host Names

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How the SAS Deployment Wizard Names SAS Web Application Servers

. . . . .

Reviewing Third-Party Database Requirements

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Deploying the SAS Visual Analytics Hub on a Separate Machine

. . . . . . . . . . . . .

SAS Visual Analytics Sample Data

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Deploying SAS Visual Analytics Interactively

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Post-Deployment Tasks for Horizontal Clusters

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

135

Post-Deployment Tasks for SAS Information Retrieval Studio

. . . . . . . . . . . . . .

135

Adding SAS LASR Analytic Server Monitor as a Windows Service

. . . . . . . . .

136

Validating Your SAS Visual Analytics Deployment

. . . . . . . . . . . . . . . . . . . . . . . . .

137

Validating Your SAS LASR Analytic Server Monitor Deployment

. . . . . . . . . . .

139

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

Deployment Process Overview: Step Six

Deploying SAS Visual Analytics is the sixth and final task required to install and configure SAS Visual Analytics.

3. Deploy the SAS High-Performance Analytics infrastructure.

4. Create operating system users and groups and designate ports.

password check box on the SAS Internal Account: Unrestricted Administrator page , the SAS Deployment Wizard reuses this password for the following



6. Deploy the servers and middle tier.

Components of SAS Visual Analytics

Deploying the SAS Visual Analytics server tier consists of installing and configuring the following components on the server-tier machine: n n

SAS LASR Analytic Server Monitor

SAS Workspace Servers n n

SAS Pooled Workspace Servers

SAS Stored Process Servers

Deploying the SAS Visual Analytics middle tier consists of installing and configuring the following components on the middle-tier machine: n n n n n n n n n n n

SAS Visual Analytics Home Page

SAS Visual Analytics Explorer

SAS Visual Statistics

SAS Visual Analytics Designer

SAS Visual Data Builder

SAS Visual Analytics Viewer

SAS Visual Analytics Administrator

SAS LASR Authorization Service

Visual Analytics Transport Service

Search Interface to SAS Content

SAS Remote Services

Preparing to Deploy SAS Visual Analytics

Preparing to Deploy SAS Visual Analytics

Which SAS LASR Analytic Server Mode?

SAS LASR Analytic Server was originally developed to operate in a distributed computing environment and to perform analytic tasks on data that is loaded in memory. This is referred to as running the server in distributed mode.

The server can also run on a single machine or in non-distributed mode.

SAS enables you to license SAS LASR Analytic Server to run in distributed mode, non-distributed mode, or both modes. The mode that you deploy and run is driven by the license that accompanies your order. For more information, consult with your SAS representative.

Deploy the SAS High-Performance Analytics

Environment

SAS Visual Analytics that uses SAS LASR Analytic Server running in distributed mode is dependent on the SAS High-Performance Analytics environment.

Before you proceed, make sure that you have consulted the SAS High-

Performance Analytics Infrastructure: Installation and Configuration Guide .

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 user for the remaining input at the start of the session so that the user does not have to monitor the entire deployment.

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. A deployment plan for SAS Visual

Analytics is created by a SAS representative specifically for a site. Each deployment plan also contains a corresponding architectural diagram and a preinstallation checklist.

n n

A SAS representative has created a custom deployment plan for you (an

XML file or a ZIP file containing an XML file). It has been e-mailed to your site.

Your deployment plan must be a valid SAS 9.4 deployment 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 that it used. The deployment plan can be helpful when you want to add a SAS product or change your SAS configuration. The wizard stores a copy of the deployment plan in the SAS configuration directory in the

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

Utilities directory, and it appends a date and time stamp to the deployment plan filename. Here is an example:

/opt/SAS/config/Lev1/Utilities/plan.2015-04-23-13.10.xml

Reducing the Number of Password Prompts

In the third maintenance release for SAS 9.4, the SAS Deployment Wizard enables you to reduce the number of password prompts for the required, SAS internal, metadata-based server accounts and SAS Web Infrastructure Platform

Data Server accounts.

When you select the Set passwords using the Unrestricted Administrator

accounts: n n

SAS Internal Account: Trusted User (sastrust@saspw)

SAS Internal Account: Anonymous Web User (webanon@saspw) n n n n

SAS Web Infrastructure Platform Data Server (dbmsowner)

SAS Environment Manager: Administration Database Configuration

(adminowner)

SAS Internal Account: SAS Environment Manager Service Account

(sasevs@saspw)

SAS Environment Manager: Database Configuration (EVManager) n n

SAS Environment Manager Enablement Kit Database Credentials User

(sasevdb)

SAS Visual Analytics Services Database User (vatadm)

When you select the Express prompting level for the SAS Deployment Wizard, you are not prompted for the required, SAS internal, metadata-based server

Preparing to Deploy SAS Visual Analytics

75 accounts and SAS Web Infrastructure Platform Data Server accounts. When you select the Typical or Custom prompting levels, you do see password prompts for these accounts. However, their password fields are pre-populated with the SAS

Internal Account: Unrestricted Administrator password.

Re-entry Feature of the Deployment Wizard

In the third maintenance release for SAS 9.4, a re-entry feature has been added to the SAS Deployment Wizard.

If, for any reason, the SAS Deployment Wizard is interrupted during the installation phase, when the wizard is restarted, it installs only those SAS products that it has not already installed successfully.

The SAS Deployment Wizard works in a similar way if it is interrupted during the configuration phase. However, the wizard does not retry any skipped configuration steps (in other words, steps that failed and then the user intentionally directed the wizard to continue anyway).

In the past, if the SAS Deployment Wizard was interrupted, it would attempt to install and configure all of the products in a SAS order when it was restarted.

(The wizard behaved in this manner because it kept no record of which products had errors during the installation or configuration or of the point in the installation or configuration chain at which the user terminated the wizard.)

Note:

When you restart the SAS Deployment Wizard in re-entry mode, the wizard assumes that you want to deploy SAS. Therefore, the wizard ignores any non-deployment arguments that you might supply, such as

-record

SAS Visual Analytics Configuration Options

To provide values specific to installing and configuring SAS Visual Analytics, choose the wizard’s Typical or Custom prompting level.

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

Figure 5.1 Select Configuration Prompting Level Page

The following table lists SAS Deployment Wizard pages that are specific to SAS

Visual Analytics and the prompting level under which you can find them. For a list of the other configuration options associated with the SAS Intelligence

Platform, see “Configuration Options by Prompt Level” on page 164

In addition, there are JVM settings that are recommended for SAS Web

Application Server and SAS Remote Services. For more information, see “SAS

Remote Services Application: JVM” on page 110

Table 5.1 Configuration Options By Prompting Level

Prompting Level That Displays the Option

Express Typical Custom

X X X

Configuration Option in the SAS

Deployment Wizard

SAS Visual Analytics Data Provider on page 120

SAS Visual Analytics High-Performance

Configuration Information on page 120

Hadoop on page 121

Greenplum on page 122

SAS Visual Analytics: Allow Guest

Teradata on page 123

Access on page 107

Distributed

Server Only

Configuration Option in the SAS

Deployment Wizard

Greenplum (Schema) on page 122

Library: Hadoop on page 123

Library: Greenplum on page 123

Library: Teradata on page 124

SAS LASR Analytic Server Monitor

Provider on page 124

Configuration Information on page 124

Library Information on page 125

SAS Visual Analytics AutoLoad

Location on page 125

SAS Visual Analytics Administrator:

SAS LASR Analytic Server Library on page 125

SAS Visual Analytics Administrator:

Public LASR Libraries on page 125

SAS Visual Analytics Services

Database Credentials on page 125

SAS Visual Analytics Transport

Service: Whitelist Mobile Devices on page 126

SAS Visual Analytics: Protocol for

OpenStreetMap Server on page 126

SAS Visual Analytics Sample Reports

SAS Visual Analytics: Configure ArcGIS

Server on page 126

SAS Visual Analytics: ArcGIS Server

Details on page 126

SAS Visual Analytics: Access to Geo

Map Server URLs on page 127

SAS Visual Data Builder Database

Credentials on page 129

SAS Information Retrieval Studio on page 129

Distributed

Server Only

Preparing to Deploy SAS Visual Analytics

Prompting Level That Displays the Option

Express Typical

Custom

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

Configuration Option in the SAS

Deployment Wizard

Search Interface to SAS Content

Feeder Configuration on page 129

SAS Internal Account: Search Interface to SAS Content User on page 129

SAS Visual Analytics High-Performance

Configuration Properties on page 120

SAS Visual Analytics Hyperlink Service:

Hadoop Ports on page 124

Context Root on page 127

SAS Visual Analytics Designer: Context

Root on page 127

SAS Visual Analytics Hub: Context

Root on page 127

SAS Visual Analytics Report Viewer:

Context Root on page 128

SAS Visual Analytics Admin: Context

Root on page 128

SAS Visual Analytics Graph Builder:

Context Root on page 128

SAS Visual Analytics Explorer: Context

Root on page 128

SAS Visual Data Builder: Context Root on page 129

SAS Information Retrieval Studio Port

Numbers

Distributed

Server Only

Prompting Level That Displays the Option

Express Typical

Custom

X X

SAS Deployment Agents

The SAS Deployment Agent and its remote clients are required for deployments that run remote processes. SAS uses the SAS Deployment Agent to copy content and to perform configuration management operations associated with creating new servers and clustering. It is also used for server administration tasks such as deployment backups.

SAS Metadata Server Clustering

A metadata server cluster is a group of three or more host machines (nodes) that have been configured as identical metadata servers. Each node runs its own server process and has its own server configuration information, journal file, and copy of the repository data sets. In addition, each node maintains a

Preparing to Deploy SAS Visual Analytics

79 complete in-memory copy of the Metadata Repository. The nodes work together as if they were a single metadata server.

Note:

If you are configuring metadata server clustering, and if your server tier or middle tier includes one or more Windows hosts, then the SAS Deployment

Wizard should prompt you for the SAS Deployment Backup and Recovery Tool:

User Account. This external account, also referred to as the backup user, will be used to run the Deployment Backup and Recovery tool. The account must meet the requirements that are specified in “What Is a Backup User?” in SAS

Intelligence Platform: System Administration Guide

. If this prompt does not appear, then you must configure the user manually after the deployment process is complete. For instructions, see “Specifying a Backup User Manually” in SAS

Intelligence Platform: System Administration Guide

Clustering provides redundancy and high availability of the metadata server.

Client applications and users interact with the cluster in the same way that they would interact with a metadata server that is not clustered. A load-balancing process automatically distributes work among the nodes. If a node ceases to operate, the metadata server continues to be available using the remaining nodes.

On Windows you need an external, Windows domain-based user account that will start all of the nodes. The suggested user ID for this service login is

myWindowsDomain\sassvlgn. On Linux, the nodes are started by the SAS

Installer account. For more information, see For more information, see

“Configuring a Metadata Server Cluster” in SAS Intelligence Platform: System

Administration Guide

All of the nodes in the cluster must have the same operating system.

You deploy your metadata cluster by installing an initial metadata server, and then moving to another machine and running the deployment wizard to deploy a metadata server node. You indicate which type of metadata server you want to deploy by choosing the appropriate step on the deployment wizard’s Select

Deployment Step and Products to Install page.

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

Figure 5.2 Select Deployment Step and Products to Install Page

For more information, see “Using Metadata Server Clustering” in SAS

Intelligence Platform: System Administration Guide

Server and Middle Tier Topology Constraint

Removed in Release 7.1

Starting with SAS Visual Analytics 7.1, if the server tier and middle tier are deployed on separate machines, these machines no longer must use operating systems in the same operating system family. (For example, Red Hat Enterprise

Linux 6.1, x86, 64-bit, and SUSE Linux Enterprise 11 Service Pack 1, x86, 64bit, are both in the same operating system family.) The SAS Visual Analytics 7.1 server tier and middle tier—like the SAS Metadata Server and SAS Web

Infrastructure Platform—can be deployed on machines that use different operating system families.

For example, the SAS Visual Analytics server tier can reside on a Windows machine and the SAS Visual Analytics middle tier can reside on a Linux x86 machine.

SAS Web Application Servers

SAS supports multiple SAS Web Application Servers on the middle-tier machine.

SAS Web Application Server Clustering

Server clustering provides redundancy and high availability and enhances performance. In SAS 9.4, the deployment model has been enhanced to better support clustering of SAS Web Application Servers. You can easily configure vertical cluster members (additional server instances on the same machine) and

Preparing to Deploy SAS Visual Analytics

81 horizontal cluster members (servers on additional machines). Combining vertical and horizontal clustering is also supported and can be configured easily.

For more information, see the

SAS Intelligence Platform: Middle-Tier

Administration Guide

Installation 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 machines in a particular order.

Always install SAS software on the metadata server machine first.

If you are implementing metadata server clusters, install the metadata server nodes next.

Install the SAS application servers (such as the SAS Workspace Server or

SAS Stored Process Server) on machines other than the metadata server machine.

If your deployment plan separates SAS Web Server from SAS Web

Application Server, install SAS Web Server first.

Install the middle tier.

For SAS deployments where the metadata server and middle tier reside on the same machine, remember that the SAS server tier (the compute tier) must be configured after the metadata server and before the middle tier.

If you are implementing SAS Web Application Server clusters, install the SAS

Web Application Server nodes next.

Install software on machines that will host only clients last.

SAS Metadata Server Recommendation

You should deploy the metadata server on a dedicated server machine. A machine running only the metadata server greatly simplifies tuning, management, and diagnostics.

For more recommendations, see information about the SAS Metadata Server in the system requirements for your SAS product.

SAS Metadata Repository Considerations

Your SAS Metadata Repositories should reside either on a local file system or on 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 .

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

Locale and Encoding Considerations

Locale and Encoding Preparation

Before you invoke the deployment wizard, your operating system must match the locale and encoding that you plan to select on the Select Regional Settings page of the deployment wizard.

Figure 5.3 Select Regional Settings Page

On Windows, the Windows system locale must match your selection on the

Select Regional Settings page. For more information, see your Windows documentation.

On UNIX and Linux, the LANG environment variable setting must match the locale and encoding you plan to select for SAS Foundation and SAS Metadata

Server.

Additionally, if you plan to select Configure as a Unicode server, you must use

UTF-8 as your operating system encoding.

For example, on Linux, if you plan to choose the locale Japanese (Japan) and the default encoding, you would enter the following command:

$ LANG=ja_JP.eucjp; export LANG

On UNIX and Linux, there are differences in the spelling and case of languageencoding pairs. For this reason, we suggest that you run the

locale

command to check the current locale and to verify the spelling of locale values. A misspelling causes the LANG environment variable to be improperly set and interferes with propagation to other locale-related environment variables. For example, consider the case and spelling differences across Linux and UNIX for

US English, UTF8:

Preparing to Deploy SAS Visual Analytics

83 n n n

On Linux and Solaris:

en_US.UTF-8

On AIX:

EN_US.UTF-8

On HP-UX:

en_US.utf8

Locale and Encoding Settings in the SAS Deployment

Wizard

The deployment wizard enables you to select the default locale and languages for the deployment wizard and for SAS 9.4. (A separate tool, the SAS

Deployment Manager, enables you to configure the locale of SAS Java clients.

For more information, see “Change Locale for SAS” in SAS Intelligence

Platform: Installation and Configuration Guide

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

Figure 5.4 Choose Language Dialog Box

The language that you select in the Choose Language dialog box specifies the language that the deployment wizard uses to display text.

You can also set the languages that your SAS 9.4 products use.

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

Figure 5.5 Select Language Support Page

The deployment wizard also prompts you for your locale setting.

Figure 5.6 Select Regional Settings Page

The locale setting controls how SAS 9.4 displays the following: n text

Preparing to Deploy SAS Visual Analytics

85 n n n numbers currencies dates times n n data (sorting)

The locale setting specifies the language that the SAS Metadata Server uses to store objects in its repository.

On Windows and Linux machines, you can choose to configure SAS 9.4 as a

Unicode server. Unicode can be particularly useful when your SAS deployment supports multiple languages. Choosing to configure SAS 9.4 as a Unicode server means that SAS reads and writes all of its data sets, catalogs, and text files in UTF-8 encoding. UTF-8 encoding supports characters from all of the world’s languages, including characters found in both single- and double-byte character sets. However, UTF-8 can make data sharing with SAS sites that use default encodings problematic.

If configuring SAS as a Unicode server is not a viable option for your deployment, you can implement a more advanced deployment that requires adding an additional server configuration to support a separate encoding. This separate configuration can be used by the SAS Customer Intelligence system only. For more information, see Adding Additional SAS Workspace Servers to

Support Multiple Encodings .

CAUTION! The SAS automated deployment tools do not support changing

locale after SAS is initially deployed. For example, you cannot initially deploy

SAS as English (US), and then reconfigure SAS with the SAS Deployment

Manager and change the locale to French.

For single-byte character set languages, the chosen locale is set in the configuration file that matches the default language. It is also set in the English configuration file. For example, if you choose fr_FR as your locale, 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. 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 how SAS supports locales and encodings, see the

SAS National Language Support (NLS): Reference Guide

A Note about Host Names

The SAS Deployment Wizard follows the Internet Host Table Specification and does not allow the underscore character (_) in host names. For more information about what constitutes a valid host name, see RFC 952 at http://www.rfcbase.org/txt/rfc-952.txt

How the SAS Deployment Wizard Names SAS Web

Application Servers

The deployment wizard creates multiple SAS Web Application Servers as needed based on the products in your SAS order. By default, each SAS Web

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

Application Server 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 names for the SAS Web

Application Servers might not be sequential.

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

Reviewing Third-Party Database Requirements

The SAS 9.4 middle-tier software and certain SAS solution software use the

SAS Web Infrastructure Platform Data Server to store transactions. The data server relies on PostgreSQL 9.1.9 and is configured specifically to support SAS

9.4 software.

Make sure that you follow these general hardware requirements for Postgres: n

In postgresql.conf, make sure that fsync=on

n n

(The storage device hosting Postgres must support its operating system fysnc() call.)

The storage device should use ECC (error correcting) physical memory

(RAM).

As specified by Postgres, do not use regular shared storage that is mapped to a network drive (Windows) or mounted as an NFS drive (Linux).

For more information, see your PostgreSQL documentation available at http://www.postgresql.org/docs/9.1/static/creating-cluster.html

Note:

The database used by SAS Environment Manager, the SAS Deployment

Backup and Recovery Tool, and certain SAS solutions, such as SAS Visual

Analytics, will be PostgreSQL regardless of the database you choose for the

SAS Web Infrastructure Platform.

SAS enables you to use a database management system other than the SAS

Web Infrastructure Platform Data Server for storing transactional data for the

SAS middle tier and certain SAS solution software. (The deployment wizard gives you this option when you choose the Custom prompting level.) In SAS 9.4, the following third-party databases are supported: n n n n

DB2

MySQL

Oracle

PostgreSQL n

SQL Server

Third-party databases often have requirements that you need to know about, such as database name limits, minimum tablespace sizes, and so on. If you have not already done so, make sure that you review “Configuring an Alternate

Database for SAS Web Infrastructure Platform Services ” in SAS Intelligence

Platform: Installation and Configuration Guide

Preparing to Deploy SAS Visual Analytics

If you want to use a third-party database, you must deselect Use SAS Web

Infrastructure Platform Data Server on the SAS Web Infrastructure Platform

Database: Data Server page during SAS installation and configuration.

Figure 5.7 SAS Web Infrastructure Platform Database: Data Server

On the SAS Web Infrastructure Platform: Database Type page, select the database management system type for the database that you plan to use.

Figure 5.8 SAS Web Infrastructure Platform: Database Type

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

The deployment wizard prompts you for additional information about your database, including a database user ID and password. The user ID that you specify must have the ability to insert, update, and delete database records.

Note:

If your site uses network attached storage (NAS) or storage area network

(SAN) systems that have been verified for use with database systems (such as

Oracle and DB2), follow your storage provider’s instructions for configuration.

For more information, see “SAS Web Infrastructure Platform Database: JDBC

Properties” on page 116

Deploying the SAS Visual Analytics Hub on a

Separate Machine

Starting with release 7.2, the SAS Visual Analytics Hub can be deployed in SAS solutions that do not include SAS Visual Analytics or SAS Visual Analytics

Administration and Reporting. In addition, you can deploy the SAS Visual

Analytics Hub on a machine that does not contain the SAS Visual Analytics middle tier.

If you are deploying the SAS Visual Analytics Hub on a machine that does not contain the SAS Visual Analytics middle tier, note the following: n n

The hub must be configured before the other SAS Visual Analytics applications can be configured.

The search function is no longer required for the hub.

For more information, see “The SAS Visual Analytics Home Page ” in SAS

Intelligence Platform: Web Application Administration Guide

SAS Visual Analytics Sample Data

Starting with release 7.3, SAS Visual Analytics provides sample objects. During installation, the SAS Deployment Wizard prompts you to include sample reports by default:

Deploying SAS Visual Analytics Interactively

Figure 5.9 SAS Deployment Wizard Prompt for Sample Reports

After a successful initial configuration of SAS Visual Analytics Administrator, you should see SAS Visual Analytics Sample in the Visual Analytics Samples section of SAS Home. After a successful initial configuration of SAS Visual

Analytics Explorer, you should see SAS Visual Analytics Sample Includes

Exploration Content in the Visual Analytics Samples section of SAS Home.

When you load the SAS data set containing the samples, full reports are available and visible. When neither the administrator nor the explorer are configured, no sample data is available.

For more information, see “Sample Objects” in SAS Visual Analytics:

Administration Guide

Deploying SAS Visual Analytics

Interactively

Installing and configuring SAS Visual Analytics interactively with the deployment wizard consists of two main phases: n

Providing installation information such as the following: o deployment type (planned or unplanned) n o o o o deployment plan location (if planned) machine type (single machine, server machine, and so on)

SAS components to be installed on the machine valid paths to any required, pre-installed, third-party software

Providing configuration information such as the following:

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

o o o o prompting level (Express, Typical, or Custom)

SAS components to be configured on the machine configuration directory name single sign-on preference (Windows only) o o required user account credentials server port numbers

This section describes the installation pages and some of the more important configuration pages that you encounter during the configuration phase of a SAS

Visual Analytics deployment. The type and number of configuration pages that you get depend on the prompting level and the contents of your SAS Visual

Analytics custom order.

“Configuration Options by Prompt Level” on page 164

lists which configuration options are available for each prompting level. For information about all deployment wizard prompts, see the online Help.

To install and configure SAS Visual Analytics interactively, complete these steps:

If you are using HTTPS self-signed or site-signed certificates, you must deploy SAS Visual Analytics in the following way: a

Install SAS Visual Analytics and the trusted CA bundle.

Run the SAS Deployment Wizard in install mode.

Add your self-signed and site-signed certificates to the trusted CA bundle.

Use the trusted CA bundle tasks in the SAS Deployment Manager.

Configure SAS Visual Analytics.

Run the SAS Deployment Wizard in configure mode.

For more information, see “Add Your Certificates to the Trusted CA Bundle” in Encryption in SAS .

Make sure that you have reviewed all of the documents listed in “Step 2:

Check for Documentation Updates” on page 10 .

Verify that you have performed the previous required steps outlined in

“Preparing to Deploy SAS Visual Analytics” on page 73 .

Note:

A few pages into the SAS installation, the deployment wizard prompts you for paths to the required third-party software. The required third-party software must be installed on the current machine or the deployment wizard will not let you continue with the installation. In this situation, you need to end the deployment wizard session and install the required third-party software before you can continue.

If you are adding on SAS Visual Analytics or SAS Visual Analytics

Administration and Reporting to an existing SAS 9.4 deployment, make sure

that you first review “Add on SAS Visual Analytics Administration and

Reporting” on page 179 .

If you are deploying SAS LASR Analytic Server in non-distributed mode, you get fewer configuration prompts. You do not see any prompts about data providers and SAS High-Performance Computing Management Console. For

a list of the prompts that you get, see Table 5.1 on page 76

Deploying SAS Visual Analytics Interactively

If you use any garbage execution scripts, temporarily suspend these scripts during deployment wizard. If any wizard temporary files are deleted during wizard execution, configuration failures can occur.

Review information about where to source certain SAS content repositories

described in “SAS Metadata Repository Considerations” on page 81

Review information about deployment wizard configuration prompting levels

described in Appendix 3, “Configuration Options by Prompt Level,” on page

163

Log on to the machine on which you plan to install the SAS Visual Analytics server tier and middle tier (blade 0). Do not use

root

Start the SAS Deployment Wizard from the highest-level directory in your

SAS Software Depot and use the command appropriate for your operating system:

Table 5.2 Start-Up Commands for the SAS Deployment Wizard

Operating

System

Windows

Linux

Command setup.exe

setup.sh

Note:

In SAS Visual Analytics 7.2 and later, the SAS Deployment Wizard automatically records your responses, regardless of whether you run the wizard with the

-record

option. This record of your wizard input is written to a file named ResponseRecord_yyyy-mm-dd-hh.mm.ss.log in one of the following locations:

C:\Users\SAS-Installer\AppData\Local\SAS

\SASDeploymentWizard

(Windows) or

home-directory/.SASAppData/

SASDeploymentWizard

(Linux).

You should see a welcome page similar to the following:

Choose Language

Select the language for the deployment wizard, and click OK.

From the drop-down list, select the language that you want the SAS

Deployment Wizard to use when it displays text.

For more information, see “Locale and Encoding Considerations” on page

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

If you have more than one SAS software order in your depot, the wizard prompts you to select the order in which you want to deploy. When you are finished, click Next.

Select Deployment Task

Select the deployment task that you want to perform, and click Next.

Select Install SAS Software.

Specify SAS Home

Specify the location where you want to install SAS, and click Next.

If you want to specify a different location where SAS is installed other than the default, enter this path in SAS Home.

CAUTION! The directory path for SAS Home cannot contain parentheses.

Using parentheses cause SAS Environment Manager scripts to fail.

Although your SAS installation directory (which the wizard refers to as

SAS Home) and SAS configuration directories can share the same parent directory, one directory cannot reside inside another. Also, the SAS installation directory should not be a directory within your SAS Software

Depot.

CAUTION! There should be one SAS installation directory (SAS Home) per

SAS deployment. Therefore, when deploying multiple tiers on the same host, the SAS installation directory location should always be shared. By contrast, when deploying different versions of SAS on the same machine, there should be a unique SAS installation directory for each SAS version.

Note:

On Windows, the deployment wizard prompts you for the SAS installation directory the first time you run the wizard. On any subsequent wizard sessions on this machine, the wizard uses the previously specified location for the SAS installation directory.

Select Deployment Type

Specify the type of deployment that you want to perform, and click Next.

Confirm that Perform a Planned Deployment, Install SAS Software, and Configure SAS Software are all selected, unless you are providing your own Transport Layer Security (TLS) certificates.

Deploying SAS Visual Analytics Interactively

Specify Deployment Plan

Specify the type of deployment plan that you are using, and click Next.

n customized deployment plan n

Choose Specify the full path to a customized deployment plan, and click Browse to navigate to the plan file (plan.xml).

standard deployment plan

Select Select a standard deployment plan, and the appropriate plan in the drop-down list.

For more information, see “About Deployment Plans” on page 73 .

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

Select Deployment Step and Products to Install

Select the machine on which you are installing software, and select the SAS products that you want to install. When you are finished, click Next.

In the Deployment Step drop-down list, select the machine on which you are installing software.

Note:

If you are deploying SAS on multiple machines, make sure that you are following the process described in “Installation Order Rules for

Multiple Machine Deployments” in SAS Intelligence Platform: Installation

and Configuration Guide

Note:

When a machine has multiple deployment steps, the deployment wizard attempts to default to the correct step. However, in some cases, this can be difficult for the wizard to determine. Therefore, always be careful to choose the correct step and avoid merely choosing the default step.

For information about SAS Web Parts for Microsoft SharePoint, see

“Deploying SAS Web Parts for Microsoft SharePoint” in SAS Intelligence

Platform: Installation and Configuration Guide

Note:

Starting with SAS Visual Analytics 7.1, if the server tier and middle tier are deployed on separate machines, these machines are no longer required to use operating systems in the same operating system family

(for example, Red Hat Enterprise Linux 6.1, x86, 64-bit, and SUSE Linux

Enterprise System 11 SP1, x86, 64-bit are both in the same family). The

SAS Visual Analytics 7.1. server and middle tiers—like the SAS Metadata

Server and the SAS Web Infrastructure Platform—can be located on machines that use a different operating system family. For example, the

SAS Visual Analytics server tier could reside on a Windows machine, and the SAS Visual Analytics middle tier could reside on a Linux x86 machine.

Deploying SAS Visual Analytics Interactively

95 n

In the table, by default, all products that are displayed will be installed.

Deselect any products that you do not want to install. When you are finished, click Next.

Note:

If you are deploying a middle-tier node machine, make sure that

SAS Web Application Server Node Configuration is selected.

Note:

If you are deploying a SAS Data Management product, you should select a SAS Quality Knowledge Base product.

Specify SAS Installation Data File

Specify the path to your SAS installation data file, and click Next.

Click Browse and locate your SAS installation data file.

The SAS installation data file contains information about the software that you have licensed for the current machine.

CAUTION! Be careful to use the correct SAS installation data file that

contains the SAS products that you are planning to install. Using an incorrect file can cause installation failure for SAS add-on products or other errors later when attempting to run SAS. For multi-machine deployments, during the clients step, choose the SAS installation data file for the server machine that is associated with the clients being installed.

19 Select Language Support

Select the languages for your SAS software to support, and click Next.

Click Clear All. (English remains selected as the default language.) n

Add any additional languages that you want SAS software to support.

By default, SAS attempts to support all languages for which your machine’s operating system is configured.

Select Regional Settings

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

Select the language, region, and locale setting that affect how SAS displays text, numbers, currencies, dates, and times and how SAS sorts data. Then, click Next.

n n

Accept the default value of English (United States), or select a different language, region, and locale in Language (Region) [Locale].

Select Configure as a Unicode server if you want to configure SAS as a

Unicode server.

For more information, see “Locale and Encoding Considerations” on page

Select Authentication Type

(Linux only) Specify the type of authentication for this machine, and click

Next.

Select Use PAM Authentication if your system uses Pluggable

Authentication Modules (PAM).

In addition, you might need to update your PAM configuration files for

SAS 9.4 to use PAM authentication. For more information, see the

Configuration Guide for SAS Foundation for UNIX Environments .

If you are uncertain whether your system uses PAM for authentication, contact your system administrator.

Note:

Do not select PAM authentication if you know that your system uses

/etc/password

/etc/shadow

authentication.

Specify Remote Communication Configuration

Specify the configuration for communication with the SAS Deployment Agent, and click Next.

If you want to change the default port (5660) for communication with the

SAS Deployment Agent, enter the new port in Port.

For more information, see “SAS Deployment Agents” on page 78 .

In Specify how to secure the remote connection, make one of the following selections: o

Select Generate credentials to secure the connection if you want the deployment wizard to create a self-signed certificate, generate a keystore, and import the certificate into the keystore.

o o

Select Specify existing credentials to secure the connection if you have already implemented CA-signed, site-signed, or self-signed certificates. On the next page, the wizard prompts you for the keystore location and password.

Select Do not secure the connection if you do not want to secure

SAS Deployment Agent communication or have not yet implemented certificates.

You can set up certificates later on your own or by using the SAS

Deployment Manager. Do not start the SAS Deployment Agent until you have completed the manual security configuration.

For more information, see

SAS Intelligence Platform: Middle-Tier

Administration Guide

Specify SAS Deployment Agent Keystore Credentials

Deploying SAS Visual Analytics Interactively

Specify the location and credentials for the keystore used to verify credentials for outgoing communications from your SAS Deployment Agent machine, and click Next.

n n n

In Agent Keystore Location, enter your SAS Deployment Agent keystore file location (path and filename).

In Agent Keystore Password, enter the password that you used when you created the keystore using the Java keytool

command.

In Confirm Agent Keystore Password, re-enter the password.

For more information, see

SAS Intelligence Platform: Middle-Tier

Administration Guide

Specify SAS Deployment Agent Truststore Credentials

Specify the location of and credentials for the truststore used to verify credentials for incoming communications to your SAS Deployment Agent machine, and click Next.

n n n

In Agent Truststore Location, enter your SAS Deployment Agent truststore file location (path and filename).

In Agent Truststore Password, enter the password that you used when you created the truststore using the Java keytool

command.

In Confirm Agent Keystore Password, re-enter the password.

For more information, see

SAS Intelligence Platform: Middle-Tier

Administration Guide

Specify SAS Remote Deployment Agent Client Keystore Credentials

Specify the location and credentials for the keystore used to verify credentials for outgoing communications from your remote SAS Deployment

Agent client machine, and click Next.

n n n

In Remote Client Keystore Location, enter your remote SAS

Deployment Agent client keystore file location (path and filename).

In Remote Client Keystore Password, enter the password that you used when you created the keystore using the Java keytool

command.

In Confirm Remote Client Keystore Password, re-enter the password.

For more information, see

SAS Intelligence Platform: Middle-Tier

Administration Guide

Specify SAS Remote Deployment Agent Client Truststore Credentials

Specify the location and credentials for the truststore used to verify credentials for incoming communications to your remote SAS Deployment

Agent client machine, and click Next.

n n n

In Remote Client Truststore Location, enter your remote SAS

Deployment Agent client truststore file location (path and filename).

In Remote Client Truststore Password, enter the password that you used when you created the truststore using the Java keytool

command.

In Confirm Remote Client Truststore Password, re-enter the password.

For more information, see

SAS Intelligence Platform: Middle-Tier

Administration Guide

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

The deployment wizard scans your machine to determine whether any preexisting SAS files are locked or do not have Write permission. If no action is required, click Next.

If the wizard lists any files in the text box, then while the wizard is running, quit SAS and add Write permission to the files listed. When you are finished, click Next.

If you use a third-party database, and SAS/ACCESS is a part of your order, select the software version for the third-party database.

The wizard uses your selection to configure SAS/ACCESS for the correct version of the third-party database.

Make sure that you perform any additional configuration on your system, such as installing the third-party database client and configuring the system environment for access to the native client libraries. For more information about the correct environment variables, go to SAS Install Center

Documentation . Select an operating system and SAS version to locate the appropriate SAS Foundation configuration guide.

Review Required Software

Review the list of third-party software that is required for the SAS software that you are installing on the current machine, and click Next. (The list of third-party software depends on the SAS software that you are installing on the current machine.) n

On the pages that immediately follow, be prepared to provide paths to these third-party applications. The number of wizard pages varies depending on the SAS software that you are installing on the current machine.

Note:

You must provide valid paths to the third-party applications or the

SAS Deployment Wizard will not let you continue with the installation.

For more information, see the following resources:

Deploying SAS Visual Analytics Interactively

“Pre-installation Checklists for Third-Party Products” on page 67 .

System Requirements--SAS Visual Analytics 7.4 (Distributed or Nondistributed LASR) or System Requirements--SAS Visual Analytics 7.4 and

SAS Visual Statistics 7.4

Third-Party Software for SAS 9.4

Specify Software Location

Specify the installation directory for the required software, and click Next.

In the field, enter the installation directory for the required third-party software.

Select Configuration Prompting Level

Specify the amount of information to provide to the SAS Deployment Wizard for configuring the SAS software that you are installing on the current machine. Select one of the three prompting levels, and click Next: n

Express

Displays the minimum number of wizard pages needed to complete the

SAS configuration.

Note:

When deploying the SAS middle tier, by default the SAS

Deployment Wizard automatically configures your SAS Web Application

Server. To disable this feature, run the wizard using either the Typical or

Custom prompting level. Manually configuring your SAS middle tier is an advanced procedure and requires using other documents such as your

Instructions.html file.

n n

Typical

Displays the basic set of wizard pages needed to complete the SAS configuration.

Custom

Displays all the wizard pages needed to complete the SAS configuration.

Refer to Appendix 3, “Configuration Options by Prompt Level,” on page

163 for more information about the SAS Deployment Wizard prompting

levels.

Provide the remaining configuration information as the wizard prompts you for it.

Note:

This topic describes some of the more important pages that you encounter during the configuration phase of a SAS Visual Analytics deployment. The options for which the deployment wizard prompts you depend on which SAS products are identified in your deployment plan. In addition, in multiple-machine deployments, the options depend on which

machine you are currently deploying. “Configuration Options by Prompt

Level” on page 164

lists which configuration options are available for each prompting level. For information about all deployment wizard prompts, see the online Help.

100

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

Specify Configuration Information

Select the path where the SAS Deployment Wizard will write SAS configuration files and logs and the level that you want to deploy. Then, click

Next.

In Configuration Directory, enter the path for SAS configuration files and logs.

In Linux environments, the SAS Installer generally overrides the default configuration directory with the site’s preferred location (for example,

/opt/sas/config

). The installer must have Write permission on this path.

In Configuration Level, enter the level that you want to deploy (for example, Lev1 = production).

Note:

The last digit of the default port number reflects the configuration level that you select in the deployment wizard. For example, when you select Lev1, the default port for the metadata server is 8561. If you select another level, such as Lev2, the wizard changes the default port to 8562.

For more information, see “Overview of the Configuration Directory

Structure” in SAS Intelligence Platform: System Administration Guide .

Note:

Although your SAS installation directory and SAS configuration directories can share the same parent directory, one directory should not reside inside another. Defining the configuration directory under the SAS installation directory or vice versa can lead to file permission issues because of the need to manage installed files differently from site-specific configurations.

Local Machine Name

Identify the local machine in various ways, and click Next.

In Fully-qualified Local Host Name, enter the complete name of the local host.

The fully qualified local host name typically takes the form of the local host name plus the domain name server (for example,

MyMachine.example.com).

TIP

If you do not know the domain name server used at your site, check with your system administrator.

In Short Local Host Name, enter a short host name.

The short local host name is the abbreviated, more common method of referring to the host, usually only a single word (for example,

MyMachine).

Migration Information

Specify the path to the migration package, and click Next.

Select Perform Migration if you are migrating to SAS 9.4.

Note:

Ignore this page unless you are migrating.

See the instructions in

“Overview of Migrating SAS Visual Analytics” on page 151

Deploying SAS Visual Analytics Interactively

101

Authentication Domain

Specify the authentication domain SAS uses to authenticate logins to servers, and click Next.

Accept the default value (DefaultAuth) unless you are planning to use a different SAS authentication domain for servers on this machine. For example, if the SAS Metadata Server is on Windows and the SAS

Workspace Server is on Linux, the workspace server might be assigned to a SAS authentication domain named LinuxAuth.

For more information, see “Manage Authentication Domains” in SAS

Management Console: Guide to Users and Permissions

Windows Options (run as server management scripts or Windows services)

Select Windows options available for the Windows operating system, and click Next.

In Server Operation Type, select how to run your SAS servers. They can be run using management scripts or they can be run as Windows services.

If you select the management script option, then the user account that runs the SAS Object Spawner must be the administrator or a member of the Windows Administrators group. Or, it must have the following

Windows local user rights on the SAS Object Spawner machine: o

Adjust memory quotas for a process

o n

Replace a process level token

Select Create Windows Shortcuts to create shortcuts to start and stop your SAS servers.

These shortcuts function whether the servers are running as Windows services or by using management scripts.

Integrated Windows Authentication

Indicate whether you are using Integrated Windows authentication (IWA) for

SAS client/server connections, and click Next.

Select Use Integrated Windows authentication (single sign-on) to configure SAS Workspace Servers running on Windows or Linux to use IWA.

IWA uses a single sign-on feature that allows a user’s identity, obtained from authentication to the user’s desktop, to be securely passed from the desktop to other processes such as the SAS

Metadata Server and the SAS Workspace Server running on either

Windows or Linux. The mechanism used is typically Kerberos, but on

Windows, NTLM can be used.

Note:

If you choose to use IWA, you cannot also implement token-based authentication.

You also encounter this page when deploying SAS Enterprise Guide and SAS Add-In for Microsoft Office. If you have not chosen IWA for the SAS Workspace Server, then choosing IWA for these clients has no effect.

For more information, see “Integrated Windows Authentication” in SAS

Intelligence Platform: Security Administration Guide

. Also, see

“Configuring Integrated Windows Authentication,” in the Configuration

Guide for SAS Foundation for UNIX Environments .

102

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

A metadata server running on Windows has IWA turned on by default.

For more information, see “SSPI System Option” in SAS Intelligence

Platform: Application Server Administration Guide

Token-based authentication

Indicate whether you are using token-based authentication for SAS client/ server connections, and click Next.

Select Use SAS Token authentication to cause clients of the workspace server to request a token from the metadata server.

SAS client applications obtain a connection to the metadata server and request a SAS token to connect to the workspace server. For the workspace server to be launched, a launch credential will be defined for the workspace server by the SAS Spawned Servers account.

If token authentication is not selected, SAS uses host authentication.

Clients provide either an IWA token or a user name and password to authenticate to the workspace server.

For more information, see “SAS Token Authentication” in SAS

Intelligence Platform: Security Administration Guide

and see “Host

Authentication” in SAS Intelligence Platform: Security Administration

Guide

Note:

If you choose to use token-based authentication, you cannot also implement IWA.

SAS Metadata Server

Specify connection information for the metadata server, and click Next.

In SAS Metadata Server Logical Name, enter the logical name of the metadata server. The maximum number of characters in the name is

60. Do not use special characters (for example, dashes, underscores, hyphens, and so on). Use only characters appropriate for an operating system subdirectory name. On Linux, avoid shell characters that might cause unintended side effects.

By default, SAS prefixes the logical server name with the application server name (SASMeta). A logical server is a container for definitions of physical servers. A logical server can have one server component for each SAS server type.

n n n

In SAS Metadata Server Name, enter the name of the metadata server. The maximum number of characters in the name is 60. Do not use special characters (for example, dashes, underscores, hyphens, and so on). Use only characters appropriate for an operating system subdirectory name. On Linux, avoid shell characters that might cause unintended side effects.

By default, SAS prefixes the logical server name with the application server name (SASMeta). A server name is the definition for a physical server. Servers are contained within a logical server (server component) that matches its server type (for example, a metadata server definition is contained in a logical metadata server).

In Host Name, enter the name of the machine on which the metadata server runs.

In Port, enter the metadata server listening port. If you choose to not accept the default value, refer to your completed Pre-Installation

Checklist for the value that you should enter.

Deploying SAS Visual Analytics Interactively

103

For more information, see “Overview of the SAS Metadata Server and

Its Initial Configuration” in SAS Intelligence Platform: System

Administration Guide

SAS Metadata Server: Override Backup Location

Indicate a different location for the metadata server backup directory if necessary. When you are finished, click Next.

If you want to change the location of the metadata server backup directory, select Override the default SAS Metadata Server backup

directory.

When configuring a metadata server cluster, you must specify a network file system path accessible to all nodes in the cluster.

For more information, see “Backing Up and Recovering the SAS

Metadata Server” in SAS Intelligence Platform: System Administration

Guide

SAS Metadata Server: Repository Configuration

Specify the name and location of the metadata and foundation repositories, and click Next.

SAS Metadata Server Configuration Directory is read-only. It identifies the parent directory under which the metadata and foundation repositories reside.

After deployment, you should apply appropriate operating system security on this directory. For more information, see “First-Priority

Setup Tasks” in SAS Intelligence Platform: Installation and

Configuration Guide

n n

In Metadata Repository Root Directory, enter the location of the metadata repositories. This location must be specified as a path relative to the metadata server configuration directory above. All metadata repositories created during configuration are created as subdirectories in this location. Do not use special characters (for example, dashes, underscores, hyphens, and so on). Use only characters appropriate for an operating system subdirectory name. On

Linux, avoid shell characters that might cause unintended side effects.

In Foundation Repository Name, enter the name of the foundation repository and the name of the subdirectory (relative to the Metadata

Repository Root Directory) in which the foundation repository is located. The maximum number of characters in the name is 60. Do not use special characters (for example, dashes, underscores, hyphens, and so on). Use only characters appropriate for an operating system subdirectory name. On Linux, avoid shell characters that might cause unintended side effects.

SAS Metadata Server: Override Service Login Account

Indicate a different default service login user account for the metadata server.

When you are finished, click Next.

If you want to change the service login user account for the metadata server, select Specify the service login account for the SAS

Metadata Server. The local system account is the default Windows service login user account for the metadata server.

When configuring a metadata server cluster on Windows, you must specify the external user account that is used to start the server. This user account must be the same account that you specify to start the

104

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

other nodes. The deployment wizard automatically grants the Log on

as a service Windows user right if the user account does not already have it.

For more information, see “Backing Up and Recovering the SAS

Metadata Server” in SAS Intelligence Platform: System Administration

Guide

Deployment Accounts: Type of Accounts

Select which type of user accounts to use for initial deployment SAS identities, and click Next.

Select Use SAS internal accounts when appropriate for SAS to use accounts known only to SAS.

SAS creates and authenticates internal accounts in metadata rather than using an operating system account.

Note:

On Windows, whenever the deployment wizard prompts you for an external account, always enter a domain-qualified user account (for example, myDomain\myAccount).

For more information, see

“Internal User Accounts” on page 52 .

External Account: Installer

Specify the operating system account (external account) used to initialize the metadata server, and click Next.

In External User ID, enter the user ID for the external account that you are using to install and configure SAS.

Depending on the operating system, this account should meet the following requirements:

Windows:

Use a domain-qualified account that is available in the long term (for future SAS maintenance) and is a member of the Windows

Administrators group.

Linux:

Use the same account on all machines on which you are deploying

SAS. Do not use

root

In External Password, enter the password for the user ID.

For more information, see

Automatic Script Execution

(UNIX only) Specify your preference for automatic script execution, and click

Next.

Select Run setuid.sh with my ID and password for the deployment wizard to attempt to run the script with the credentials that you provide.

You see this page on Linux for SAS products that require that you run the setuid.sh script with sudo privileges. If you select this option, you are asked on a subsequent page for the sudo password (if you are deploying a metadata server, you have already provided this information). As it installs your software, the deployment wizard attempts to run the script with the credentials that you provided.

Deploying SAS Visual Analytics Interactively

105

If you do not select this option, you have to run setuid.sh manually during installation (and configuration if you have chosen to configure).

Note that setuid.sh must be run as root in order to complete successfully. If you have any concerns about the deployment wizard running as root or you do not know the sudo information for the machine that you are installing on, you should not select this option.

Password for Current ID

Enter the password for the current user ID, and click Next.

In Password for Current ID, enter the password for the current user

ID.

On Linux, this page appears if you have indicated on the previous page that you want the SAS Deployment Wizard to run the setuid.sh script via sudo. If you have any concerns about the SAS Deployment

Wizard running as root or you do not know the sudo information for the machine on which you are installing, you should go back and change your previous selection.

In Confirm Password, re-enter the password.

SAS Internal Account: Unrestricted Administrator

Enter the metadata password for the first unrestricted administrator identity, and click Next.

n n

In New Internal Password, enter a password for the internal account

(sasadm@saspw) that the wizard will create to serve as an unrestricted administrator for configuring the metadata server.

Note:

Remember and record this password as you will need it in the future.

In Confirm New Internal Password, re-enter the password. Click

Next.

For more information, see

“Reducing the Number of Password

Select Set passwords using the Unrestricted Administrator

password if you want to reuse this password for the internal metadata server accounts and SAS Web Infrastructure Data Server accounts during this deployment. Selecting this option when running the deployment wizard with the Express prompting level reduces the number of configuration prompts.

For more information, see

Prompts” on page 74

SAS Internal Account: Trusted User

Specify the metadata password for the Trusted User identity, and click Next.

In New Internal Password, enter a password for an internal account

(sastrust@saspw) that the wizard will create to enable SAS server and spawner components to communicate securely with each other.

Note:

Remember this password as you will need it in the future.

In Confirm New Internal Password, re-enter the password.

For more information, see

106

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

SAS BI Web Services: Authentication Method

Select the method by which users of SAS BI Web Services are authenticated, and click Next.

n o

In Authentication Method, make one of the following selections and click Next:

SAS Authentication is managed by the metadata server.

Web Authentication is managed by the SAS Web Application Server using container-based authentication or a third-party product.

Selecting Web Authentication has these effects: n n n

Partially configures web authentication BI Web Services for Java.

For more information, see “Securing SAS BI Web Services for

Java ” in SAS Intelligence Platform: Middle-Tier Administration

Guide

Has no effect on the BI web applications (such as SAS Web

Report Studio, SAS Information Delivery Portal, and so on). You have to configure web authentication for these BI web applications.

Prevents you from setting up an anonymous web user (as this is incompatible with web authentication).

Anonymous Web Access

When using SAS authentication, you can select this option to set up a SAS identity for anonymous access to certain web services and web applications that support this feature. When you are finished, click Next.

Select Enable anonymous web access to set up a SAS identity for anonymous access to certain web services and web applications that support this feature.

SAS BI Web Services for Java and .NET, the SAS Stored Process

Web Application, and SAS Visual Analytics Guest Access are the only components that support this feature.

For more information, see “PUBLIC Access and Anonymous Access” in SAS Intelligence Platform: Security Administration Guide .

SAS Internal Account: Anonymous Web User

Enter the metadata password for the anonymous web access identity, and click Next.

In New Internal Password, enter a password for the internal SAS account that the wizard will create to be used to grant clients access to applicable SAS Web Infrastructure Platform applications such as

SAS BI Web Services and the SAS Stored Process Web Application.

When SAS authentication is being used and the user has not preemptively specified credentials, the client is given access to these applications under the anonymous web access identity.

For more information, see “Using the SAS Anonymous Web User with

SAS Authentication” in SAS Intelligence Platform: Middle-Tier

Administration Guide

Note:

Remember this password because you will need it in the future.

In Confirm New Internal Password, re-enter the password, and click

Next.

Deploying SAS Visual Analytics Interactively

107

SAS Visual Analytics: Allow Guest Access

Specify whether to allow anonymous access to a subset of SAS Visual

Analytics resources and functionality, and click Next.

Select Guest Access Permitted to allow guest access for participating SAS Visual Analytics applications.

Guest access is an optional feature. All users who connect to a guest access URL are authenticated as the same service account (the SAS

Anonymous Web User), which functions as the single surrogate identity for all connecting users. Guest access is not compatible with web authentication.

TIP

If you are unsure about whether to allow guest access in SAS

Visual Analytics, you can create the SAS Anonymous Web User, and then easily add guest access after installation.

For more information, see “Supporting Guest Access” SAS Visual

Analytics: Administration Guide .

External Account: SAS Spawned Servers Account

Specify the credentials used to launch the back-end SAS Stored Process

Server and SAS Pooled Workspace Server, and click Next.

In External User ID, enter the user ID to start the SAS Pooled

Workspace Server and the SAS Stored Process Server.

Note:

On Windows, enter a domain-qualified user ID.

In External Password, enter the password for the external user ID.

Note:

Remember this password because you will need it in the future.

For more information, see

“Pre-installation Checklist for Ports for SAS” on page 61

Create Common Directories

Indicate the common directories that you want the deployment wizard to create. On Windows, you can specify a data directory, and click Next.

Select the appropriate check box to create common directories for server and spawner logs, user-specific files, data (SAS libraries for tables and cubes), and temporary work tables and files.

When you select this option, the deployment wizard creates the specified directory (

Logs

Users

Data

, and

Temp

) under the SAS configuration directory.

In Data Directory, enter a location to contain SAS libraries for tables and cubes.

This directory is required when configuring SAS BI Dashboard.

Enable FIPS-certified Encryption Algorithms

Indicate whether you want to use AES encryption, and click Next.

Select the check box to use the Advanced Encryption Standard (AES) algorithm to encrypt communications to and from a SAS Metadata

Server. A block cipher that encrypts 128-bit blocks by using a 256-bit key, AES complies with Federal Information Processing Standards

(FIPS).

For more information, see “FIPS 140-2 Standards Compliance” in

Encryption in SAS

108

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

Server Encryption

Select the encryption level and algorithm that SAS clients and servers use to connect to the SAS Metadata Server, and click Next.

In Server Encryption Level, select Credentials to encrypt only login credentials. Select Everything to encrypt all communication with the metadata server.

Selecting Everything can affect your SAS performance.

In Server Encryption Algorithm, you can specify an encryption algorithm other than SAS Proprietary. The other algorithms are RC2,

RC4, DES, Triple DES, and AES.

For more information, see “Encryption Model” in SAS Intelligence

Platform: Security Administration Guide

and “SAS Proprietary

Encryption” in Encryption in SAS .

Client-side Credentials Policy

Set the policy for client-side storage of credentials, and click Next.

Select Allow users to save credentials in client-side connection

profiles to allow users to save their user IDs and passwords in clientside connection profiles on the metadata server for desktop applications.

When set, SAS enables OMA_SASSEC_LOCAL_PW_SAVE in omaconfig.xml.

For more information, see “Reference Information for omaconfig.xml” in SAS Intelligence Platform: System Administration Guide .

Estimated System Size

Size your system configuration based on user number, system size, and workload size. Then, click Next.

In Size Estimate, select Large System, and click Next.

After you have finished deploying SAS Visual Analytics, you can change JVM settings and any other necessary parameters in the following file:

Linux: o

SAS-configuration-directory/Web/WebAppServer/

SASServer1_1/bin/setenv.sh

Windows: n

SAS-configuration-directory\Web\WebAppServer

\SASServer1_1\bin

For more information, see “Initial Sizing and Tuning Configuration

Options for Deployments” in SAS Web Applications: Tuning for

Performance and Scalability

E-mail Server

Specify e-mail server configuration information, and click Next.

In Host Name, enter the host name for an SMTP e-mail server at your site. SAS uses this server to send alerts for system-related issues to an administrator (for example, the SAS Metadata Server detects a journaling issue).

Deploying SAS Visual Analytics Interactively

109

The deployment wizard uses this e-mail server as the default for the

SAS Application Server to provide e-mail services to various SAS clients. For example, with SAS Data Integration Studio, you can use a

Publish to Email transformation to alert users about various data changes. For the SAS BI Dashboard to send alerts by e-mail to dashboard users and administrators, the port and host name must be configured for the e-mail server.

For more information, see

and “Managing Alert E-mail Options for the SAS Metadata

Server” in SAS Intelligence Platform: System Administration Guide .

In Port, enter the port that the SMTP e-mail server uses.

For more information, see

“Pre-installation Checklist for Ports for SAS” on page 61

and “Managing Alert E-mail Options for the SAS Metadata

Server” in SAS Intelligence Platform: System Administration Guide .

SAS Application Server: Server Context

Enter the name of the SAS Application Server context, and click Next.

In SAS Application Server Context Name, accept the default

(SASApp) or enter a different name of the SAS Application Server context for that the wizard will create in metadata.

A server context is a SAS IOM server concept that describes how

SAS Application Servers manage client requests. A SAS Application

Server has an awareness (or context) of how it is being used and makes decisions based on that awareness. The server context name is prepended to all server names defined in the server context.

Note:

The server context name must be unique and cannot contain spaces.

For more information, see “Overview of SAS Application Servers” in

SAS Intelligence Platform: Application Server Administration Guide

SAS Pooled Workspace Server

Specify SAS Pooled Workspace Server information, and click Next.

In Logical SAS Pooled Workspace Server Name, enter the name of the logical pooled workspace server to be stored in SAS metadata.

n n n

In SAS Pooled Workspace Server Name, enter the name of the pooled workspace server to be stored in SAS metadata.

In Host Name, enter the name of the machine on which the pooled workspace server runs. The machine name should match the name specified to the SAS Object Spawner.

In Port, enter the port on which the object spawner will listen for client requests to launch pooled workspace servers.

For more information, see “Overview of Workspace Servers and

Stored Process Servers” in SAS Intelligence Platform: Application

Server Administration Guide

SAS Web Infrastructure Platform Data Server

Specify information for the SAS Web Infrastructure Platform Data Server, and click Next.

In Host Name, enter the fully qualified host name of the SAS Web

Infrastructure Platform Data Server or accept the default value.

110

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

n n

The default value is the host name where the deployment wizard is currently running. In most cases the default is correct. However, a machine can have more than one network interface card (NIC) or host name alias. If so, to determine whether the default is correct, see your

Pre-Installation Checklist.

In Port, enter the TCP/IP port number on which SAS Web

Infrastructure Platform Data Server listens or accept the default value.

In Data Server Administrator, enter the user ID for administering

SAS Web Infrastructure Platform Data Server.

In Data Server Administrator Password, enter the password for the user ID associated with the SAS Web Infrastructure Platform Data

Server administrator.

Note:

Remember this password because you will need it in the future.

In Confirm Password, re-enter the password and click Next.

For more information, see

“Reviewing Third-Party Database

Requirements” on page 86 .

SAS Remote Services Application: JVM

Specify the appropriate heap sizes for the SAS Remote Services application using the JVM option format, and click Next.

In Initial JVM Heap Size, enter the appropriate initial heap size for the

SAS Remote Services Application using the JVM option format.

Note:

SAS 9.4 no longer requires SAS Remote Services. However, some custom SAS applications still require SAS Remote Services. The deployment wizard deploys SAS Remote Services, but it is not automatically started by default.

In Max JVM Heap Size, enter the appropriate maximum heap size for the remote services application using the JVM option format.

In Additional JVM Options, enter any additional Java options that you want the SAS Remote Services JVM to use. For example, you might want to add

-Dmulticast_udp_ip_ttl=1

to restrict multicast traffic to a single subnet based on your network topology.

For more information, see SAS Web Applications: Tuning for

Performance and Scalability .

SAS Web Server: Automated or Manual Configuration Option

Indicate whether you want the deployment wizard to configure the SAS Web

Server automatically, and click Next.

If you want to configure the SAS Web Server manually, clear

Configure SAS Web Server automatically.

Select this option for the deployment wizard to automatically build and configure the SAS web applications and configure a sample web application server for use with SAS 9.4. (To use this wizard feature, make sure that your web application server is not running before proceeding.)

It is strongly recommended that you choose to automatically configure the SAS Web Server. If you need to make changes to the SAS Web

Server after the automatic configuration, there are tools to help you reconfigure it.

Deploying SAS Visual Analytics Interactively

111

For more information, see “Scripting Tool for SAS Web Application

Server” in SAS Intelligence Platform: Middle-Tier Administration

Guide

If you choose not to automatically configure your web application server, you are still prompted for web application server information, and deployment stages such as Configure Products, Deploy Web

Applications, and Start Web Application Servers will execute to create instructions for manual deployment. When configuration is complete, follow manual instructions on how to configure your server and deploy your web applications available at: http://support.sas.com/resources/ thirdpartysupport/v94/appservers/index.html

. (Select the product name of your web application server.)

Note:

Manually configuring your SAS middle tier is an advanced procedure and requires using other documents such as your

Instructions.html file.

SAS Web Server: Configuration

Specify SAS Web Server configuration options, and click Next.

The standard port for HTTP traffic is 80. If you want to change this for

SAS Web Server, then specify a new port number in HTTP Port.

Note:

On Linux systems that you must start servers as root if you want servers to listen on ports lower than 1024. We recommend that you install and configure as a less-privileged user, and then start SAS Web Server manually as root.

For more information, see

“Pre-installation Checklist for Ports for SAS” on page 61

and “Managing Alert E-mail Options for the SAS Metadata

Server” in SAS Intelligence Platform: System Administration Guide .

n n n

The standard port for Transport Layer Security (TLS) traffic is 443. If you want to change this for SAS Web Server, then specify a new port number in HTTPS Port. (See earlier note.)

In Configured Protocol, select the communication protocol for SAS

Web Server. There are two choices, HTTP (unsecured) and HTTPS

(secured).

If you select HTTPS, an X.509 certificate and RSA private key are required. The deployment wizard prompts you for the paths to these items on a later page. You can enter locations for these items or provide information to create them. For more information, see

SAS

Intelligence Platform: Middle-Tier Administration Guide

In Administrator Mail Address, enter an e-mail address for e-mail to be sent to the SAS Web Server administrator.

SAS Web Server: Server Process for Handling Responses

Specify the user name and group name for the HTTPD response processes, and click Next.

In User Name, enter the host system user name for the HTTPD response processes. Do not use the numeric user ID.

On Linux, when the HTTPD listener process is run as root, it forks a set of child processes that handle the requests and respond to the client. For security reasons, these child processes must run with a more limited user ID and group ID.

112

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

In Group Name, enter the host system group name for the HTTPD response processes. Do not use the numeric group ID.

SAS Web Server: Location of X509 Certificate and RSA Private Key

If you already have an X.509 certificate, enter their locations. When you are finished, click Next.

n n

In X509 Certificate, enter the path to the valid X.509 certificate with the DNS name of this machine as the Common Name (CN).

In RSA private key, enter the path to the RSA private key that is not protected by a passphrase.

For more information, see

SAS Intelligence Platform: Middle-Tier

Administration Guide

Web Application Server: Configure Internet Proxy Server

Indicate whether to configure an Internet proxy server and specify proxy information, and click Next.

n n

In Proxy Host, enter the fully qualified host name for the proxy server.

If you are using SAS Information Delivery Portal RSS feeds, then you have to provide proxy server information.

In Proxy Port, enter the port that your site uses to access the Internet.

In NonProxy Hosts, enter the DNS names of all the machines that should not be accessed through the proxy server. Separate each machine name with a vertical line character (|). Use an asterisk (*) as a wildcard for an entire subnet. For example, *.subnet.com excludes all machines with a DNS name that ends with .subnet.com.

If your site does not allow Internet access on production systems, see the configuration information available at this SAS website: http:// support.sas.com/resources/thirdpartysupport/v94 , and select your

SAS Web Application Server.

Web Application Server: Multiple Servers

Indicate whether to configure multiple SAS Web Application Servers on which to deploy SAS web applications, and click Next.

Select Configure multiple servers to have the deployment wizard automatically configure multiple managed servers for you. The deployment wizard uses SAS best practices for choosing the server to deploy each application to.

In some situations, it might be preferable to split the SAS web applications across multiple managed servers. This is usually done for performance reasons.

If you choose to manually configure your SAS Web Application

Servers, you are provided with recommended configuration settings in a generated instructions file (Instructions.html) when the deployment wizard completes.

More advanced performance configuration considerations are documented in the

SAS Intelligence Platform: Middle-Tier

Administration Guide

Deploying SAS Visual Analytics Interactively

113

Web Application Server: Server Configuration

Specify SAS Web Application Server information, and click Next.

In Server Name, enter a logical name for your server. A suffix is automatically added to the name to distinguish cluster members.

For example, if the name SASServer1 is entered, the actual name is

SASServer1_1. If the multiplier provided on the next page is greater than one, additional servers are created with unique suffixes. For example, if the multiplier is 2, then servers named SASServer1_1 and

SASServer1_2 are created.

In Additional JVM Options, enter any additional Java options that you want the server JVM to use. These JVM options are tagged onto the end of the server's command line. Options that are hardcoded into the deployment wizard default set can be overridden in this way.

Web Applications: Automatic Deployment

Indicate whether you want the wizard to automatically deploy SAS web applications to the SAS Web Application Server, and click Next.

Select Deploy web applications automatically for the deployment wizard to automatically deploy SAS web applications to the SAS Web

Application Server.

If you do not choose to deploy web applications automatically, manual deployment instructions are written to the Instructions.html file during the web application deployment stage.

Note:

Manually deploying your SAS web applications is an advanced procedure and requires using other documents such as your

Instructions.html file.

Regardless of whether you choose to automatically deploy your SAS web applications, when building web applications, the wizard automatically explodes web application archive files (EAR files).

For more information, see “Deploying Content Manually to the SAS

Content Server” in SAS Intelligence Platform: Middle-Tier

Administration Guide

Web Applications: White List of Sites Allowed to Link to This SAS Installation

Enter a comma-delimited list of additional known hosts and domains to trust, and click Next.

In URLs White List, enter a comma-delimited list of additional known hosts and domains to trust in the following form:

http|https://host[:port]|domain/, ...

The valid URLs whitelist can include just a list of host names to trust.

The valid URLs whitelist can also include wildcards such as '*' for host name and domain.

Note:

The port number must be specified if the whitelisted site uses port numbers other than the standard 80 for HTTP or 443 for HTTPS.

For example:

https://myserver:443/,http://example.com

For security reasons, you must list any host name URLs for any site that could redirect browsers to your solution. This might include

114

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

n corporate sites linking to your solution for reporting purposes or single sign-on servers.

For example, if https://corporatePortal.company.com/ links to your server, then enter

https://corporatePortal.company.com/

as one entry. This field enables you to add additional known hosts and domains to a preset list automatically created by the SAS configuration process.

For more information, see “Configuring the Cross Domain Proxy

Servlet through a Whitelist” in SAS Intelligence Platform: Middle-Tier

Administration Guide

Select Enter advanced options for URL white list handling to display an additional page in which you can specify advanced options for the filter.

Web Applications: Advanced Options for Allowed URLs White List

Enter a comma-separated list of HTTP methods to exclude from filtering, and click Next.

Select Enable restrictions to use the URLs white list. Deselecting

Enable restrictions causes SAS to ignore all white list restrictions.

n n

For more information, see “Whitelist of Websites and Methods Allowed to Link to SAS Web Applications” in SAS Intelligence Platform: Middle-

Tier Administration Guide

In Disable restrictions for a comma-separated list of HTTP

methods, enter a comma-separated list of HTTP methods to exclude from filtering (for example,

GET,OPTIONS,TRACE

In URL Overrides, enter a comma-separated list of specific URLs to override if you are using wildcards in the URLs white list.

For example, suppose that you have added http://example.*.com to your URLs white list, but you want to block one URL from the domain.

Therefore, you would enter the following exception in URL Overrides:

http://example.sales.com

IP Multicast Version

(UNIX only) Specify the IP version to use for the IP multicast address, and click Next.

In IP Version, select the IP version appropriate for your system.

The deployment wizard detects that the machine has an IPv4 address and an IPv6 address. If you select IPv6, you are confirming that all servers running SAS products are connected to an IPv6-enabled network and have IPv6-enabled network interfaces.

For more information, see

“Multicast Address Considerations” on page

59 .

IP Multicast

Specify IP multicast information between SAS applications. Accept the IP multicast settings or enter new settings. If you choose to use an authentication token, you must enter token information. When you are finished, click Next n

In IP Multicast Address, enter a new multicast address.

A multicast group communications protocol is used to communicate among middle-tier SAS applications in a single SAS deployment (the

Deploying SAS Visual Analytics Interactively

115 n set of applications connected to the same metadata server). The combination of IP multicast address and multicast UDP port should be different for each SAS deployment and different from those used by other multicast applications at your site. The default values are most appropriate for deployments in a firewall-isolated data center environment.

For more information, see

“Multicast Address Considerations” on page

59 .

In IP Multicast UDP Port, enter a valid UDP port for use on all the machines where a SAS middle-tier application is installed.

n n

In IP Multicast UDP TTL, enter a valid multicast TTL property (default

= 1, range = 0–255). This property affects the number of network hops a multicast packet takes before being dropped. This TTL value must be greater than or equal to the largest number of hops between any two servers running SAS products.

Choose Use an authentication token to connect to prevent access to the multicast group from unauthorized listeners. The authentication token can be any password-like string. You must provide the same authentication token string to each tier in the same SAS deployment

(each tier associated with the same metadata server).

SAS Content Server: Repository Directory

Specify SAS Content Server repository options, and click Next.

n n

In Repository Directory, enter the location on the disk for the SAS

Content Server indexes and repository configuration file. You can click

Browse to search for this location.

For more information, see “Administering the SAS Content Server” in

SAS Intelligence Platform: Middle-Tier Administration Guide

Select Start initial node as clustered when this machine is (or might be) part of a clustered deployment.

CAUTION! If you enable this option, you must also establish a central

backup vault for the SAS Deployment Backup and Recovery Tool.

Starting in the second maintenance release for SAS 9.4, a vault is no longer required for clustered SAS Content Servers.

Deselect Start initial node as clustered when you are not deploying the SAS middle tier on a machine cluster. (This setting enables journaling and the necessary cluster synchronization processes.)

If you redeploy the middle tier on a machine cluster in the future, you can manually set the Java system property

-Dcom.sas.server.isclustered=true

and restart the initial application server node. For more information, see “Adding a

Horizontal Cluster Member” in SAS Intelligence Platform: Middle-Tier

Administration Guide

SAS Web Infrastructure Platform Database: Data Server

Specify whether to use a third-party database for the SAS Web Infrastructure

Platform database, and click Next.

Clear Use SAS Web Infrastructure Platform Data Server to use a different database to store SAS Web Infrastructure Platform data.

In SAS 9.4, the following third-party database management systems are supported: DB2, MySQL, Oracle, PostgreSQL, and SQL Server.

116

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

SAS Web Infrastructure Platform: Database Type

Specify the alternate database that you want to use for the SAS Web

Infrastructure Platform Database, and click Next.

In Database Type, select one of the following supported databases:

DB2, MySQL, Oracle, PostgreSQL, or SQL Server.

Note:

The database used by SAS Environment Manager, the SAS

Deployment Backup and Recovery Tool, and certain SAS solutions, such as SAS Visual Analytics, will be PostgreSQL regardless of the database that you choose for the SAS Web Infrastructure Platform.

For more information, see

“Reviewing Third-Party Database

Requirements” on page 86 .

SAS Web Infrastructure Platform Database: Database Connection Properties

Specify connection information for the SAS Web Infrastructure Platform Data

Server database, and click Next.

Select Automatically create tables and load data to have the SAS

Deployment Wizard automatically create tables and load the selected pre-existing database with initial data.

n n

If you are using MySQL, the SAS Web Application Server configuration process also creates a new MySQL database named according to the value specified in Database SID or Service Name on the

SAS Web Infrastructure Platform Database: JDBC Properties page

In Host Name, enter the host name where the database server is installed.

In Port, enter the port number to which the database server is listening.

n n

Select Use Catalog to indicate that the database catalog needs to be specified to uniquely locate a table in the database.

Select Use catalog if you are using MySQL or SQL Server.

Select Use schema pattern to indicate that the database schema needs to be specified to uniquely locate a table in the database.

Select Use schema pattern if you are using Oracle or DB2.

n n

In Directory containing JDBC driver JAR files, identify the appropriate JDBC driver JAR files and your selected RDBMS and version. Inappropriate or additional JAR files cause configuration failures, so copy the minimum required JDBC driver JAR files to this directory.

SAS Web Infrastructure Platform Database: JDBC Properties

If you selected a database server other than the SAS Web Infrastructure

Platform Data Server, then the following fields are editable. If you are using the SAS Web Infrastructure database server, the database name and user ID are Read-Only. When you are finished, click Next.

In Database Name, enter the name of the database that contains the

SAS Web Infrastructure Platform Database tables.

In User ID, enter the user ID for accessing the database used with your SAS Web Infrastructure Platform Database tables. This user ID must have the ability to insert, update, and delete records.

Deploying SAS Visual Analytics Interactively

117 n

In Password, enter a valid password for the user ID associated with the SAS Web Infrastructure Platform Database Server account. The deployment wizard uses this password to create the database server account.

Note:

Remember this password because you will need it in the future.

In Confirm Password, re-enter the password.

SAS Web Infrastructure Platform Database: Metadata Properties

Specify the metadata information for the SAS Web Infrastructure Platform

Data Server database, and click Next n o

The field on this page changes depending on the database type that you chose earlier.

In Catalog, enter the name of the database catalog to use to uniquely locate a table in the database.

In Schema Pattern, enter the name of the schema pattern to use to uniquely locate a table in the database.

SAS Web Infrastructure Platform Database: JDBC Driver Validation

Decide whether to enable dynamic validation of the JDBC driver’s connection to the database, and click Next.

Select Validate the JDBC driver's connection to database to enable dynamic validation of the JDBC driver’s connection to the database.

SAS Environment Manager: Administration Database Configuration

Specify administrator credentials for the SAS Environment Manager database, and click Next.

In User ID, specify the user ID for accessing the database used with your SAS Web Infrastructure Platform Database tables. This user ID must have the ability to insert, update, and delete records.

By default, the SAS Environment Manager uses the Administration database on the SAS Web Infrastructure Platform Data Server. If you are using the SAS Web Infrastructure Platform Database Server, the user ID is Read-Only.

For more information, see “SAS Web Infrastructure Platform Data

Server” in SAS Intelligence Platform: Middle-Tier Administration

Guide

In Password, enter a valid password for the user ID.

Note:

Remember this password because you will need it in the future.

In Confirm Password, re-enter the password.

SAS Internal Account: SAS Environment Manager Service Account

Specify the metadata password for the SAS Environment Manager service, and click Next.

In SAS Environment Manager Service Account Password, enter a password for the SAS Environment Manager service account

(sasevs@saspw).

The password must contain at least six characters. Make sure that you enter the same password that was specified in any previous SAS

Environment Manager configuration prompts.

118

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

Note:

Remember this password because you will need it in the future.

This service account is required for the SAS Environment Manager and its agent to communicate while monitoring the processes in your

SAS deployment. This internal SAS account has unrestricted administrative access rights to the metadata server.

For more information, see SAS Environment Manager: User’s Guide.

In Confirm Password, re-enter the password.

Choose SAS Environment Manager: Keystore

Indicate whether to use the built-in or customized keystore, and click Next.

By default, the SAS Environment Manager uses the trusted CA list supplied by SAS.

If you want to use a different keystore, in the SSL Keystore list, select

Use a customer-supplied JKS format keystore.

For more information, see

SAS Intelligence Platform: Middle-Tier

Administration Guide

SAS Environment Manager: Keystore Configuration

Provide a keystore path, filename, and password, and click Next.

In Keystore Path and Filename, enter a valid path and filename of the keystore that you are using when communicating with the SAS

Environment Manager.

For more information, see

SAS Intelligence Platform: Middle-Tier

Administration Guide

In Keystore Password, enter a password for the keystore.

Note:

SAS Environment Manager requires that the keystore password and private key password be identical. For more information, see http:// pubs.vmware.com/vfabric5/index.jsp?topic=/com.vmware.vfabric.hyperic.

4.6/Configure_SSL_Options.html

In Confirm Password, re-enter the password.

SAS Environment Manager: Database Configuration

Specify SAS Environment Manager database credentials. EVManager is a default Postgres database supplied by SAS that is used to store collected server metrics. When you are finished, click Next.

n n

In Database User, enter a user ID used for accessing the EVManager database.

In Database User Password, enter a valid password for the user ID associated with the database server account.

Note:

Remember this password because you will need it in the future.

In Confirm Password, re-enter the password.

In Database Encryption Passphrase, enter a valid passphrase key used for encrypting and decrypting the SAS Environment Manager database user password.

The key must be at least eight characters long and can contain letters and numbers only.

Note:

Remember this passphrase because you will need it in the future.

Deploying SAS Visual Analytics Interactively

119 n

In Confirm Database Encryption Passphrase, re-enter the passphrase key. Click Next.

SAS Environment Manager Agent Communication

Specify SAS Environment Manager agent information, and click Next.

Select Establish secure communication to enable secure communication using Transport Layer Security (TLS) between the

SAS Environment Manager and its agents.

For more information, see

SAS Intelligence Platform: Middle-Tier

Administration Guide

Choose SAS Environment Manager Agent: Keystore

Indicate whether to use the built-in or customized keystore, and click Next.

By default, the SAS Environment Manager Agent uses the trusted CA list supplied by SAS.

If you want to use a different keystore, in the SAS Environment

Manager SSL Keystore list, select Use a customer-supplied JKS

format keystore.

For more information, see

SAS Intelligence Platform: Middle-Tier

Administration Guide

SAS Environment Manager Agent

Provide a keystore path, filename, and password, and click Next.

In Keystore Alias, enter a valid alias for your keystore.

Note:

SAS Environment Manager requires that the keystore alias and its password be identical.

In Keystore Path and Filename, enter a valid path and filename of the keystore that you are using when communicating with the SAS

Environment Manager.

For more information, see

SAS Intelligence Platform: Middle-Tier

Administration Guide

In Keystore Password, enter a password for the keystore.

Note:

4.6/Configure_SSL_Options.html

In Confirm Password, re-enter the password.

SAS Environment Manager Enablement Kit Database Credentials

Specify database connection information, and click Next.

n n

In User ID, enter the user ID for accessing the database used with

SAS Environment Manager Enablement Kit.

In Password, enter the password for the user ID.

Note:

Remember this password because you will need it in the future.

In Confirm Password, re-enter the password.

120

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

SAS Visual Analytics High-Performance Configuration Properties

Specify properties to create a libref to reference the directory that contains uploaded and extracted SAS data sets, and click Next.

In Uploaded SAS Dataset Libref Name, enter the libref name to reference the directory that contains uploaded and extracted SAS data sets. The maximum number of characters for a libref name is eight.

SAS Visual Analytics Data Provider

Select the data provider to be used with SAS Visual Analytics, and click

Next.

n n

In SAS Visual Analytics High-Performance Data Provider, select

Non-distributed LASR, and click Next.

In SAS Visual Analytics High-Performance Data Provider, select the data provider to be used with SAS Visual Analytics.

The supported values are co-located Hadoop; Hadoop, Greenplum, or

Teradata with the SAS Embedded Process; and MapR Hadoop that is mounted on a shared NFS drive.

TIP

If you are planning to use SAS Visual Analytics with co-located

Hadoop now or in the near future, select Hadoop (co-located HDFS).

If you are not planning to use SAS Visual Analytics with co-located

Hadoop, then select Hadoop (with SAS Embedded Process).

For more information, see “Configuring Existing Hadoop Clusters” in the SAS High-Performance Analytics Infrastructure: Installation and

Configuration Guide .

Note:

If you are using HANA or Oracle, make sure that you choose

Greenplum (with SAS Embedded Process) and configure your provider after running the wizard, manually. For more information, see SAS 9.4 In-

Database Products: Administrator’s Guide .

This configuration page appears only when your SAS order also contains a license for the distributed SAS LASR Analytic Server. If your SAS order also contains a license for the non-distributed SAS

LASR Analytic Server, you can select Non-distributed LASR.

SAS Visual Analytics High-Performance Configuration Information

Specify configuration information for the SAS High-Performance Analytics environment, and click Next.

n n n

In SAS High-Performance Analytics Environment Host, enter the fully qualified machine name in the cluster to which the SAS clients connect.

In SAS High-Performance Analytics Environment Port, enter the port number in the environment through which the SAS clients connect. (By default, the port is 10010.)

For more information, refer to “Pre-installation Checklist for Ports for

SAS” on page 61

In Signature files location, specify the absolute path where the SAS

LASR Analytic Server writes signature files.

If you are using SAS LASR Analytic Server in distributed mode, specify a path located on the SAS High-Performance Analytics

Deploying SAS Visual Analytics Interactively

121 n environment root node. If you are using a non-distributed SAS LASR

Analytic Server, specify a path located on the local machine.

It is important to carefully manage access to the signature files directory. User IDs under which certain activities are performed (for example, starting a server or loading data) must have Write access to the signature files directory. Access to a signature files directory can provide access to loaded data, so that the signature files directory should be protected against unauthorized access. For more information, see “Signature Files” in the SAS Visual Analytics:

Administration Guide .

In Location of the TKGrid or TKGrid_REP Installation on the SAS

High-Performance Analytics Environment, specify the absolute path to the TKGrid directory or the TKGrid_REP directory on the root node host (for example,

/opt/TKGrid

Specify the TKGrid_REP directory when you are feeding your SAS

High-Performance Analytics environment with parallel loads from a remote (not co-located) data provider.

TIP

Be sure not to leave any whitespace characters at the end of the path because whitespace characters can cause problems when you attempt to submit SAS LASR Analytic Server jobs later.

n n

For more information, see “Install the Analytics Environment” or

“Configure for Access to a Data Store with a SAS Embedded Process” in the SAS High-Performance Analytics Infrastructure: Installation and

Configuration Guide .

In SAS High-Performance Computing Management Console URL, enter the URL used to access SAS High-Performance Computing

Management Console. (By default, the URL is http://local_host_name:

10020.)

For more information, see the SAS High-Performance Computing

Management Console: User’s Guide .

n n

In Location for the SAS linguistic distributed binaries, specify the directory on disk that stores the SAS linguistic binary files. These binary files are required to perform text analysis on the SAS LASR

Analytic Server with SAS Visual Analytics and to run PROC HPTMINE and PROC HPTMSCORE with SAS Text Miner.

SAS Visual Analytics Data Provider: Hadoop

Specify Hadoop configuration information, and click Next.

In Hadoop NameNode Host, specify the machine in the HDFS cluster that is the Hadoop NameNode.

In Hadoop NameNode Port, enter a port number for the HDFS

NameNode service, which runs only on the NameNode in the HDFS cluster. This value maps to the Hadoop property com.sas.lasr.hadoop.service.namenode.port

For more information, see the Configuration Guide for SAS 9.4

Foundation for UNIX Environments .

In Hadoop NameNode Authentication Domain, enter the domain to use for identifying logins that access the Hadoop NameNode machine.

122

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

The authentication domain is a metadata construct that pairs each login with the servers for which that login is valid. The authentication domain provides logical groupings for resources and logins in a metadata repository. This ensures that resources use the same authentication process.

For example, when an application needs to locate credentials that enable a particular user to access a particular server, the application searches the metadata for logins that are associated with the authentication domain in which the particular server is registered.

In Library Name, enter the library name for the Hadoop library.

In Libref, enter the libref for the Hadoop library.

n n

In Hadoop Path, enter the path to the database for the Hadoop data server.

SAS Visual Analytics Data Provider: Greenplum

Specify the requested Greenplum information to create a remote parallel connection with the SAS High-Performance Analytics environment, and click

Next.

n n n n n

In Greenplum Database Host, enter the name of the Greenplum

Data Computing Appliance. Host name, fully qualified host name, or an IP address are valid values.

In Greenplum Database Port, enter the port for the database.

In Greenplum Database Authentication Domain, enter the domain associated with metadata identities that can access the Greenplum

Data Computing Appliance.

The authentication domain is a metadata construct that pairs each login with the servers for which that login is valid. The authentication domain provides logical groupings for resources and logins in a metadata repository to ensure that resources use the same authentication process.

In Library Name, enter the library name for the Greenplum library.

In Libref, enter the SAS libref that points to the Greenplum library.

n n

In Greenplum Database, enter the database name of the Greenplum database.

For more information, see “Configuring the Analytics Environment for a Remote Parallel Connection” in the SAS High-Performance

Analytics Infrastructure: Installation and Configuration Guide .

SAS Visual Analytics Data Provider: Greenplum (Schema)

Specify the requested Greenplum information to create a remote parallel connection with the SAS High-Performance Analytics environment, and click

Next.

In Greenplum Database Schema, enter the database schema name for the Greenplum database, and click Next.

Deploying SAS Visual Analytics Interactively

123 n

For more information, see “Configuring the Analytics Environment for a Remote Parallel Connection” in the SAS High-Performance

Analytics Infrastructure: Installation and Configuration Guide .

SAS Visual Analytics Data Provider: Teradata

Specify the requested Teradata information to create a remote parallel connection with the SAS High-Performance Analytics environment, and click

Next.

n n

In Teradata Data Server Host, enter the name of the Teradata

Managed Server Cabinet. Host name, fully qualified host name, or an

IP address are valid values.

In Teradata Data Server Authentication Domain, enter the domain associated with metadata identities that can access the Teradata

Managed Server Cabinet.

n n

The authentication domain is a metadata construct that pairs each login with the servers for which that login is valid. The authentication domain provides logical groupings for resources and logins in a metadata repository to ensure that resources use the same authentication process.

In Library Name, enter the library name for the Teradata library.

In Libref, enter the SAS libref that points to the Teradata library.

n n

In Teradata Database, enter the database name of the Teradata Data

Server.

For more information, see “Configuring the Analytics Environment for a Remote Parallel Connection” in the SAS High-Performance

Analytics Infrastructure: Installation and Configuration Guide .

SAS Visual Analytics Public Data Library: Hadoop

Specify public data library configuration information for Hadoop, and click

Next.

n n n

In Library Name, enter the library name for the public Hadoop library.

In Hadoop Path, enter the path to the database for the public Hadoop data server.

In Libref, enter the SAS libref that points to the public Hadoop library.

For more information, see “Configuring the Analytics Environment for a Remote Parallel Connection” in the SAS High-Performance

Analytics Infrastructure: Installation and Configuration Guide .

SAS Visual Analytics Public Data Library: Greenplum

Specify public data library configuration information for Greenplum, and click

Next.

n n

In Library Name, enter the library name for the public Greenplum library.

In Libref, enter the SAS libref that points to the public Greenplum library.

124

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

n n n n

In Greenplum Database, enter the database for the public

Greenplum data server.

In Greenplum Database Schema, enter the database schema for the public Greenplum data server.

For more information, see “Configuring the Analytics Environment for a Remote Parallel Connection” in the SAS High-Performance

Analytics Infrastructure: Installation and Configuration Guide .

SAS Visual Analytics Public Data Library: Teradata

Specify public data library configuration information for Teradata, and click

Next.

In Library Name, enter the library name for the public Teradata library.

In Libref, enter the SAS libref that points to the public Teradata library.

n n

In Teradata Database, enter the database for the public Teradata data server.

For more information, see “Configuring the Analytics Environment for a Remote Parallel Connection” in the SAS High-Performance

Analytics Infrastructure: Installation and Configuration Guide .

SAS Visual Analytics Data Provider: Hadoop Ports

Confirm the various ports used for Hadoop, and click Next.

In File System Default Port, enter the port used to access the

NameNode default file system.

n n n n

In MapReduce Job Tracker Port, enter the port used to access the

MapReduce server JobTracker process. This value maps to the

Hadoop property mapred.job.tracker

In Primary NameNode HTTP Port, enter the port on which the

NameNode primary web user interface listens. This value maps to the

Hadoop property dfs.namenode.http-address

In Secondary NameNode HTTP Port, enter the port on which the

NameNode backup web user interface listens. This value maps to the

Hadoop property dfs.secondary.http-address

In Job Tracker HTTP Port, enter the port on which the JobTracker web user interface listens. This value maps to the Hadoop property mapred.job.tracker.http.address

SAS Visual Analytics Public Data Provider

Specify a library definition for a public, non-distributed SAS LASR Analytic

Server data provider, and click Next.

n n

In Data Reload Library Name, enter the name for the Reload library.

In Data Reload Libref, enter the libref for the Reload library.

n n

In SAS Visual Analytics Reload Path, enter the absolute path to the

Reload library.

SAS LASR Analytic Server Monitor Configuration Information

Specify SAS LASR Analytic Server Monitor configuration information, and click Next.

In SAS LASR Analytic Server Monitor Host, enter the SAS LASR

Analytic Server Monitor host name.

Deploying SAS Visual Analytics Interactively

125 n

In SAS LASR Analytic Server Monitor RMI Registry Port, enter the

Remote Method Invocation (RMI) port that the SAS LASR Analytic

Server Monitor listens on for activity.

For more information, see

“Pre-installation Checklist for Ports for SAS” on page 61

SAS Visual Analytics Public Data Library Information

Confirm the port for the SAS High-Performance Analytics environment to which the SAS clients connect, and click Next.

In SAS Visual Analytics Public Data Library Port, enter the port number for the SAS High-Performance Analytics environment to which the SAS clients connect.

For more information, see

“Pre-installation Checklist for Ports for SAS” on page 61

SAS Visual Analytics AutoLoad Location

Specify the path to the SAS Visual Analytics AutoLoad location, and click

Next.

In SAS Visual Analytics AutoLoad Location, enter the absolute path of the host directory in which users place tables for loading to memory.

SAS Visual Analytics: SAS LASR Analytic Server Library

Specify the SAS LASR Analytic Server library name and libref, and click

Next. You can modify both of these properties after installation by using SAS

Management Console.

In Library Name, enter the library name for the SAS LASR Analytic

Server library.

In Libref, enter the libref for the SAS LASR Analytic Server library.

SAS Visual Analytics: Public LASR Libraries

Specify the public LASR library name and libref, and click Next. You can modify both of these properties after installation by using SAS Management

Console.

In Public LASR Library Name, enter the name for the library that is pre-populated for users when they import data files and create data queries. (This public LASR library provides ease of use rather than data security.)

In Public LASR Libref, enter the libref for the public LASR library.

SAS Visual Analytics Services Database Credentials

Specify JDBC connection information for the SAS Visual Analytics Services database, and click Next.

n n

In User ID, enter the user account that SAS uses to create a JDBC connection to the SAS Visual Analytics Services database. (The default is vatadm.) n

In Password, enter a password for the user account (vatadm).

Note:

Remember this password because you will need it in the future.

In Confirm Password, re-enter the password.

126

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

SAS Visual Analytics Transport Service: Whitelist Mobile Devices

Specify whether to enforce a whitelist for SAS Mobile BI, and click Next.

Select Enforce whitelist for mobile devices to use a whitelist to control access to SAS Mobile BI.

A deployment enforces either the blacklist or the whitelist. If the whitelist is not selected to be enforced, the blacklist is enforced by default. If the whitelist is enforced, only devices that are on the whitelist can use SAS Mobile BI. If the blacklist is enforced, any device that is not on the blacklist can use SAS Mobile BI. Although only one list is enforced, you can make changes to both lists.

For more information, see “Access to SAS Mobile BI” in SAS Visual

Analytics: Administration Guide

SAS Visual Analytics: Protocol for OpenStreetMap Server

Specify the protocol for how SAS Visual Analytics Explorer communicates with the OpenStreetMap server hosted by SAS, and click Next.

In SAS-hosted OpenStreetMap Server Communication Protocol, select a protocol to use for standard web browser communication.

Your options are HTTP Protocol (default) and HTTPS Protocol

(secure).

Using HTTPS can result in performance degradation because of additional communication and encryption.

For more information, see “OpenStreetMap Server” in SAS Visual

Analytics: Administration Guide

SAS Visual Analytics Sample Reports

Decide whether to include nearly 13 GB (or more) of data and reports to help you get started, and click Next.

Select Include Visual Analytics Sample Reports to install sample

SAS Visual Analytics reports with your configuration.

Quick links to these reports are available on the SAS Visual Analytics home page. The sample data is loaded when the associated server

(Public LASR Analytic Server) starts. For more information, see

“Sample Objects” in SAS Visual Analytics: Administration Guide .

SAS Visual Analytics: Configure ArcGIS Server

Specify whether to configure an Esri ArcGIS server, and click Next.

Select Configure ArcGIS Server to configure an ArcGIS server. If this option is not selected, then the wizard skips ArcGIS server configuration.

For more information, see “Esri Server” in SAS Visual Analytics:

Administration Guide

SAS Visual Analytics: ArcGIS Server Details

Specify the URL of the ArcGIS REST Services directory, and click Next.

In ArcGIS REST Services Directory, enter the URL used to connect to the ArcGIS REST Services directory.

Use the format

protocol://hostname:port/instance/ services/folder

Deploying SAS Visual Analytics Interactively

127

SAS Visual Analytics: Access to Geo Map Server URLs

Select the check box to provide outbound access from SAS Visual Analytics applications to necessary geo map server URLs by adding them to the cross domain proxy servlet whitelist, and click Next.

Select Add the necessary geo map URLs to the whitelist to add

OpenStreetMap servers (hosted by SAS) and your specified ArcGIS server (optional) to the cross domain proxy servlet whitelist.

If you do not select the check box, geo map functionality might be incomplete.

After installation is completed, you can review and modify the whitelist in the Configuration Manager in SAS Management Console (on the

SAS Application Infrastructure node via the sas.web.cdps.knownHosts property).

For more information, see “Configuring the Cross Domain Proxy

Servlet through a Whitelist” in SAS Intelligence Platform: Middle-Tier

Administration Guide

SAS Visual Analytics Hyperlink Service: Context Root

Specify the context root, and click Next.

In Context Root for SAS Visual Analytics Hyperlink Service, enter the context root that ties the user to the EAR file that is specified in the

Display Name field.

The form of the URL for SAS Visual Analytics Service Hyperlink

Service is http://machine:port/SASVisualAnalytics. Although the machine and port are configured elsewhere and typically apply to the web container as a whole, the SASVisualAnalytics portion is the

context root, and you can change it (within the constraints of URL rules).

SAS Visual Analytics Designer: Context Root

Specify the context root, and click Next.

In Context Root for SAS Visual Analytics Designer, enter the context root that ties the user to the EAR file that is specified in the

Display Name field.

The form of the URL for SAS Visual Analytics Designer is http://

machine:port/SASVisualAnalyticsDesigner. Although the machine and port are configured elsewhere and they typically apply to the web container as a whole, the SASVisualAnalyticsDesigner portion is the

context root, and you can change it (within the constraints of URL rules).

SAS Visual Analytics Hub: Context Root

Specify the context root, and click Next.

In Context Root for SAS Visual Analytics Hub, enter the context root that ties the user to the EAR file that is specified in the Display

Name field.

The form of the URL for SAS Visual Analytics Hub is http://

machine:port/SASVisualAnalyticsHub. Although the machine and port are configured elsewhere and they typically apply to the web container as a whole, the SASVisualAnalyticsHub portion is the context root, and you can change it (within the constraints of URL rules).

128

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

SAS Visual Analytics Report Viewer: Context Root

Specify the context root, and click Next.

In Context Root for SAS Visual Analytics Report Viewer, enter the context root that ties the user to the EAR file that is specified in the

Display Name field.

The form of the URL for SAS Visual Analytics Report Viewer is http://

machine:port/SASVisualAnalyticsReportViewer. Although the machine and port are configured elsewhere and they typically apply to the web container as a whole, the SASVisualAnalyticsReportViewer portion is the context root, and you can change it (within the constraints of

URL rules).

SAS Visual Analytics Admin: Context Root

Specify the context root, and click Next.

In Context Root for SAS Visual Analytics Admin, enter the context root that ties the user to the EAR file that is specified in the Display

Name field.

The form of the URL for SAS Visual Analytics Administrator is http://

machine:port/SASVisualAnalyticsAdministrator. Although the machine and port are configured elsewhere and they typically apply to the web container as a whole, the SASVisualAnalyticsAdministrator portion is the context root, and you can change it (within the constraints of

URL rules).

SAS Visual Analytics Graph Builder: Context Root

Specify the context root, and click Next.

In Context Root for SAS Visual Analytics Graph Builder, enter the context root that ties the user to the EAR file that is specified in the

Display Name field.

The form of the URL for SAS Visual Analytics Graph Builder is http://

machine:port/SASVisualAnalyticsGraphBuilder. Although the machine and port are configured elsewhere and they typically apply to the web container as a whole, the SASVisualAnalyticsGraphBuilder portion is the context root, and you can change it (within the constraints of

URL rules).

SAS Visual Analytics Explorer: Context Root

Specify the context root, and click Next.

In Context Root for SAS Visual Analytics Explorer, enter the context root that ties the user to the EAR file that is specified in the

Display Name field.

The form of the URL for SAS Visual Analytics Explorer is http://

machine:port/SASVisualAnalyticsExplorer. Although the machine and port are configured elsewhere and they typically apply to the web container as a whole, the SASVisualAnalyticsExplorer portion is the

context root, and you can change it (within the constraints of URL rules).

For more information, see

SAS Studio: Administrator’s Guide

Deploying SAS Visual Analytics Interactively

129

SAS Visual Data Builder: Context Root

Specify the context root, and click Next.

In Context Root for SAS Visual Analytics Data Builder, enter the context root that ties the user to the EAR file that is specified in the

Display Name field.

The form of the URL for SAS Visual Analytics Data Builder is http://

machine:port/SASVisualAnalyticsDataBuilder. Although the machine and port are configured elsewhere and typically apply to the web container as a whole, the SASVisualAnalyticsDataBuilder portion is the context root, and you can change it (within the constraints of URL rules).

SAS Visual Data Builder Database Credentials

Specify JDBC connection information for the SAS Visual Data Builder database, and click Next.

In User ID, enter the user account that SAS uses to create a JDBC connection to the SAS Visual Data Builder database. (The default is vdbadm.) n

In Password, enter a password for the user account (vdbadm).

Note:

Remember this password as you will need it in the future.

In Confirm Password, re-enter the password.

SAS Information Retrieval Studio

On this page and the next page, confirm the ports used for SAS Information

Retrieval Studio, and click Next.

Review the SAS Information Retrieval Studio ports.

For more information, see

“Pre-installation Checklist for Ports for SAS” on page 61

Search Interface to SAS Content Feeder Configuration

Specify feeder information for Search Interface to SAS Content, and click

Next.

In Index Loader Interval In Minutes, enter the interval to provide

SAS content to the server for search indexing.

SAS Internal Account: Search Interface to SAS Content User

Specify a metadata password for the internal user account that permits access to SAS content that is provided to SAS Information Retrieval Studio for indexing. Click Next.

n n

Display Name contains the SAS Content User display name that is stored in SAS metadata.

Name contains the SAS Content User account name that is stored in

SAS metadata.

n n

Internal User ID contains the SAS Content User user ID

(sassearch@saspw) that is stored in SAS metadata.

In New Internal Password, enter a password for the SAS Content

User. SAS stores this password in SAS metadata. The password must contain at least six characters.

Note:

Remember this password as you will need it in the future.

In Confirm New Internal Password, re-enter the password.

130

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

SAS Deployment Backup and Recovery Tool: Enable Central Vault

Indicate whether to use a central backup vault for the SAS Deployment

Backup and Recovery Tool, and click Next.

Select Enable central vault storage of backup files, to enable central storage of backup files by specifying a network-accessible vault directory.

CAUTION! If your SAS deployment is not current with the second

maintenance release for SAS 9.4, then a central vault location is required if your middle-tier environment includes a clustered SAS

Content Server.

o o o

The default value for the shared centralized vault location is kept blank. The feature of storing backup at a centralized location is disabled as default.

To enable this feature, in the two pages that follow, provide a directory shared across all the tiers. The default retention period for a backup is

30 days. If the configuration that you are performing requires a backup at a centralized shared location and you want to change retention period, select this option.

(On Windows only.) Finally, provide a valid operating system (external) user account and password to be used to execute commands using the SAS Deployment Agent. This user account must: be an external account that has access to and sufficient privileges for each host machine to be included in the backup.

be known to the host machine that contains the central vault.

have Read and Write access to the following directories: n the central vault directory n

SAS-configuration-directory/SASMeta/MetadataServer

For more information, see “Using the Deployment Backup and

Recovery Tool” in SAS Intelligence Platform: System Administration

Guide

SAS Studio Mid-Tier: Context Root

Specify the context root, and click Next.

In Context Root for SAS Studio Mid-Tier, enter the context root that ties the user to the EAR file that is specified in the Display Name field.

The form of the URL for SAS Studio Mid-Tier is http://machine:port/

SASStudio. Although the machine and port are configured elsewhere and typically apply to the web container as a whole, the SASStudio portion is the context root, and you can change it (within the constraints of URL rules).

For more information, see

SAS Studio: Administrator’s Guide

Deployment Summary

Review the summary of software that the deployment wizard will install and configure.

When you see the Deployment Summary page, the deployment wizard has finished collecting installation and configuration input. This is the last opportunity to go back and change any information that you have

Deploying SAS Visual Analytics Interactively

131 provided in previous pages before the wizard begins writing to your system.

Make one of the following choices: o

Click Start to begin installing SAS files and writing the configuration to the current machine.

The deployment wizard launches the installation and configuration process and provides an ongoing status update.

o o

Click Back to navigate to earlier wizard pages to change installation and configuration information previously entered.

Click Cancel to terminate the wizard session. Note that you will lose installation and configuration information previously entered.

CAUTION! If you encounter a situation in which the deployment wizard

reports a configuration failure, leave the error message displayed and do not continue. Consult additional documentation and, if necessary, contact

SAS Technical Support. Moving past an error most often results in having to delete your deployment and start over.

On Linux, when you are installing the server tier, you will be instructed to run a script as root. As the message in the installation program explains, certain SAS products and features use functionality that requires SAS to check user ID authentication and file access authorizations. This, in turn, necessitates that certain files within your SAS installation have setuid permissions and be owned by root.

Your credentials are temporarily stored in your Windows registry using the

Windows automatic logon functionality. In rare circumstances, it is possible those values will remain in your Windows registry after their use, thus posing a potential security risk.

For more information about this functionality, including any risks, see

Microsoft documentation about security and automatic logons. You should weigh the risks of convenience for automatic logon after restart against the security policies in place at your site.

132

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

Deployment Complete

The Deployment Complete page displays the configuration results for each

SAS product.

Green check marks next to every item on this page indicate that your deployment completed successfully. Click Next.

If you received errors during your deployment, then contact SAS

Technical Support at mailto:[email protected]. Attach to your e-mail the files listed in “Review SAS Deployment Tool Documents, Reports, and

Logs” in SAS Intelligence Platform: Installation and Configuration Guide .

Deploying SAS Visual Analytics Interactively

133

Additional Resources

Use the links displayed to review more information about your SAS deployment.

Click Finish to close the SAS Deployment Wizard.

Configuration Guidelines and Details

134

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

Review Configuration Guidelines and Details for post-deployment steps, and click Next.

To complete your SAS deployment, review Configuration Guidelines and

Details and perform the steps listed.

Configuration Guidelines and Details (Instructions.html) is automatically generated by the deployment wizard and has post-installation steps specific to your SAS order that you must perform.

The SAS Deployment Wizard writes the Configuration Guidelines and

Details (Instructions.html) file to the

Documents

directory under the SAS configuration path. For example: o

Linux: o

/opt/SAS/Lev1/Documents/Instructions.html

Windows:

C:\SAS\Config\Lev1\Documents\Instructions.html

Back up your metadata repository and your SAS configuration directory.

n n n

Make a backup copy of your SAS Visual Analytics configuration directories by using your site-approved method. Your SAS configuration directories are all of the child directories under the path that you specified previously on the Specify Configuration Information wizard page.

Back up your SAS Web Application Server directories.

Back up your metadata repository and repository manager. For more information, see “Best Practices for Backing Up and Restoring Your SAS

Content” in SAS Intelligence Platform: System Administration Guide .

If you opted not to automatically deploy your SAS web applications, then you must manually deploy them. For more information, see SAS Support for Web

Application Servers and HTTP Servers .

Be sure to restart any servers that you stopped when creating the backup.

Post-Deployment Tasks for SAS Information Retrieval Studio

135

If you are deploying SAS Visual Analytics on Windows, proceed to “Adding

SAS LASR Analytic Server Monitor as a Windows Service” on page 136 .

Otherwise, proceed to

“Validating Your SAS Visual Analytics Deployment” on page 137 .

Post-Deployment Tasks for Horizontal

Clusters

On a SAS Visual Analytics horizontal cluster, perform the following steps after deploying SAS Visual Analytics:

Sign on to SAS Management Console with administrative privileges.

On the Plug-ins tab, navigate to Application Management



Configuration Manager



SAS Application Infrastructure.

Expand SAS Application Infrastructure, right-click Visual Analytics

version-number, and select Properties.

On the Advanced tab of the Visual Analytics Properties dialog box, for

va.lastActionLogPath, enter the path to a network share that is available to all machines in the cluster.

Administrators should grant Read and Write access to this path for the SAS

Web Application Server process owner and users of the SAS Visual

Analytics Administrator (or for the launch credential account if SAS Token

Authentication is being used).

Save your changes.

To make the changes take effect, restart the SAS Web Application Server on each machine in the cluster.

One approach is to restart all instances of the SAS Web Application Server from your equivalent of

SAS-configuration-directory/Web/Scripts/

AppServer/

UNIX

appsrvconfig.sh restart

Windows

appsrvconfig.cmd restart

Post-Deployment Tasks for SAS

Information Retrieval Studio

After running SAS Deployment Wizard to install and configure SAS Visual

Analytics, you must add the path to SAS Foundation for SAS Information

Retrieval Studio. On Linux, in addition to the path to SAS Foundation, you must add the path to the trusted CA bundle provided by the SAS Security Framework.

136

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

To add the SAS Foundation path to SAS Information Retrieval Studio, perform these steps:

Sign on to the SAS Visual Analytics server machine as the SAS Installer user.

Using a text editor, open

SAS-configuration-directory/

Applications/SASInformationRetrievalStudioforSAS/work/ information-retrieval-studio.conf

Add the following paths to the information-retrieval-studio.conf file based on your operating system: n

Linux

Add tkpath and auth-server-certificates-path

: o

In the second maintenance release for SAS 9.4 and earlier: tkpath=/SAS-installation-directory/SASFoundation/9.4/sasexe:

/SAS-installation-directory/SASFoundation/9.4/utilities/bin/ auth-server-certificates-path=certificate-file.pem

In the third maintenance release for SAS 9.4 and later: tkpath=/SAS-installation-directory/SASFoundation/9.4/sasexe:

/SAS-installation-directory/SASFoundation/9.4/utilities/bin/ auth-server-certificates-path=SAS-installation-directory/

SASSecurityCertificateFramework/1.1/cacerts/trustedcerts.pem

Windows

Add tkpath

: tkpath=\SAS-installation-directory\SASFoundation\9.4\core\sasext

After you make your changes to the information-retrieval-studio.conf file, restart SAS Information Retrieval Studio.

Sign on to SAS Home and clear the browser cache, including favorites. Enter an asterisk (*) in Search to verify that the search feature is working.

Adding SAS LASR Analytic Server Monitor as a Windows Service

To add the SAS LASR Analytic Server Monitor as a Windows Service, follow these steps:

Log on to the SAS LASR Analytic Server Monitor machine as a user who is a member of the Windows Administrators group.

In the Windows taskbar, click Start, in Search programs and files, type

services.msc

, and then press Enter.

In the Services window, right-click SAS [configuration-name] LASR

Analytic Server Monitor, and select Properties.

On the Log On tab, select This account, and enter the domain and user name (for example, DOMAIN\user_name). Click Apply.

Validating Your SAS Visual Analytics Deployment

137

Windows automatically grants the Log On As A Service right. Click OK.

Click OK.

Copy the SSH keys from the SAS High-Performance Analytics environment host to the SAS LASR Analytic Server Monitor machine under

disk:\Users

\current-user-ID\.ssh

Open LASRMonitor.conf, located at

SAS-configuration-directory\Applications\SASVisualAnalytics

\HighPerformanceConfiguration\wrapper

Update the set.USERNAME=

property with the SAS High-Performance

Analytics environment host user ID whose SSH keys match the SSH keys that you copied earlier.

Save and close LASRMonitor.conf.

Start the SAS LASR Analytic Server Monitor in the Services window or by running the following script from the command line:

SAS-configuration-directory\Applications\SASVisualAnalytics

\HighPerformanceConfiguration\LASRMonitor.bat -start

Validating Your SAS Visual Analytics

Deployment

Here are suggestions of how you can validate your distributed SAS Visual

Analytics deployment using SAS Home (the modern appearance). The SAS

Visual Analytics documentation is available at http://support.sas.com/ documentation/onlinedoc/va/ .

Remember that a large part of SAS Visual Analytics is shipped with SAS solutions. Therefore, you can use this section to validate any part of SAS Visual

Analytics that your SAS solution contains (usually every part except SAS Visual

Analytics Explorer).

You might want to wait to validate your deployment after you have deployed both the server tier and middle tier. If you have deployed only the server tier, then some of the validation steps cannot be completed until you have deployed the middle tier.

138

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

Table 5.3 Suggestions for SAS Visual Analytics Validation (Modern Home Page)

Purpose Actions

Create an account for use later in the validation.

1. Use the SAS LASR Analytic Server installer account

(sas) or create a new administrator account (such as saslasradm).

2. In SAS High-Performance Computing Management

Console, create SSH keys. (SSH keys have already been created for the installer account.)

3. Assign the Windows user permission Log on as a

batch job to the account.

Create a SAS identity for use later in the validation.

In SAS Management Console:

Define a SAS Visual Analytics Administrator (use the account previously created (saslasradm)).

Assign the administrator to the Visual Analytics Data

Administrators group and the Visual Data Builder

Administrators group.

Give this user the necessary operating system permissions to write to the signature files location.

More Information

Operating system documentation.

“Managing Users and Groups” in the

SAS High-

Performance

Computing

Management

Console: User’s

Guide .

“Add Users” in SAS

Management

Console: Guide to

Users and

Permissions

“Adjust Group or

Role Membership” in SAS

Management

Console: Guide to

Users and

Permissions

Operating system documentation

Validate that SAS Home is running and valid logins are accepted.

Sign on to SAS Home as saslasradm (for example,http:// myHost.example.com/SASVisualAnalyticsHub).

“Accessing SAS

Visual Analytics” in

SAS Visual

Analytics: User’s

Guide

Start the Public LASR

Analytic Server (to save a data query later in this topic)

On SAS Home:

1. Click the side menu icon (next to SAS Home)

2. Click Administrator.

3. Select the check box next to the Public LASR Analytic

Server.

4. Click the start button icon

“Operating Your

Servers” in SAS

Intelligence

Platform: System

Administration

Guide

Demonstrate that SAS

Visual Analytics

Administrator is functional and able to communicate with the SAS LASR

Analytic Server.

In Visual Analytics Administrator:

1. Right-click Public LASR Analytic Server, and select

Load a Table from the pop-up menu.

“Load a Table” in

SAS Visual

Analytics:

Administration

Guide

Demonstrate that SAS

Visual Analytics Explorer is functional.

On SAS Home:

1. Click Data Explorer.

2. On the SAS Visual Analytics Explorer window, click

Select a Data Source.

3. On the Open Data Source window, select a data source in the list and click Open.

“Create a New

Exploration” in SAS

Visual Analytics:

User’s Guide

Validating Your SAS LASR Analytic Server Monitor Deployment

139

Purpose

Demonstrate that SAS

Visual Data Builder is functional.

Actions

On SAS Home:

1. Click Data Preparation.

2. In the SAS Visual Data Builder window, click New 

Data Query.

Demonstrate that SAS

Visual Analytics Designer is functional.

On SAS Home:

1. Click Report Designer.

2. Click the Data tab.

3. Click the in the Select a data source field.

The Add Data Source window is displayed.

4. Select one or more data sources that begin with

VA_SAMPLE, and click Add.

More Information

“Creating Data

Queries” in SAS

Visual Analytics:

User’s Guide

“Create a New

Report” in SAS

Visual Analytics:

User’s Guide

Demonstrate that the

SAS Visual Analytics

Graph Builder is functional.

On SAS Home:

1. Click Report Designer.

2. On the Objects tab, click , and then select Show or

Hide Objects.

3. In the Show or Hide Objects window, verify that

Schedule Chart, Vector Plot, and Numeric Series Plot are displayed in the list. (These custom report objects are available only with the graph builder.)

Deploy SAS Mobile BI.

View a SAS Visual Analytics report on a mobile device.

“Build a Custom

Graph Object” in

SAS Visual

Analytics: User’s

Guide

Demonstrate that SAS

Mobile BI is operable.

“Viewing Reports on a Mobile Device” in

SAS Visual

Analytics: User’s

Guide

SAS Visual Data Builder requires that a SAS identity be a member of the Visual Data Builder Administrators group. Members of the

Visual Analytics Data Administrators group do not have access to SAS Visual Data Builder.

Some SAS orders do not contain SAS Visual Analytics Explorer.

Validating Your SAS LASR Analytic Server

Monitor Deployment

On distributed server deployments only, certain features in the SAS Visual

Analytics Administrator rely on the SAS LASR Analytic Server Monitor.

To validate the SAS LASR Analytic Server Monitor deployment, follow these steps:

Log on to the SAS LASR Analytic Server Monitor machine (blade 0) using the SAS installer account.

2 Change to the SAS LASR Analytic Server Monitor configuration directory.

By default, this directory is located at

SAS-configuration-directory/

Applications/SASVisualAnalytics/

HighPerformanceConfiguration

140

Chapter 5 / Deploying the SAS Visual Analytics Server and Middle Tier

Run the LASRMonitor.sh script with a user account that normally starts the

SAS LASR Analytic Server or with a user account that has Read permission on the lasrmonitor.pid file. (The lasrmonitor.pid file is in the same folder as the LASRMonitor.sh script.)

Enter the following command to confirm that SAS LASR Analytic Server

Monitor is running:

LASRMonitor.sh status

If the SAS LASR Analytic Server Monitor is not running, enter the following command:

LASRMonitor.sh start

For more information, see the

SAS Visual Analytics: User’s Guide

141

What to Do Next: Administration

Tasks

Overview of Required Administration Tasks

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

141

Review Post-deployment Documentation

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

141

Review SAS Intelligence Platform Post-deployment Documentation

. . . . . . .

142

Check Status for SAS Visual Analytics Servers

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

142

Create SAS Users and Groups

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

142

Set ulimits for SAS Web Applications

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

143

Overview of Required Administration Tasks

After installing and configuring SAS Visual Analytics using the SAS Deployment

Wizard, you must perform certain administration tasks. These tasks are organized into the following topics: n n

“Review Post-deployment Documentation” on page 141

“Check Status for SAS Visual Analytics Servers” on page 142

n n

“Create SAS Users and Groups” on page 142

“Set ulimits for SAS Web Applications” on page 143

Review Post-deployment Documentation

Review the Instructions.html file that is generated by the SAS Deployment

Wizard. This file provides an overview of the configuration guidelines and details. Any warnings that were generated during the deployment process are described in this file. The file is in the following location:

SAS-config-dir/Levn/Documents/Instructions.html

142

Chapter 6 / What to Do Next: Administration Tasks

Review SAS Intelligence Platform Postdeployment Documentation

Review the chapter, “What to Do Next: Administration Tasks” in SAS Intelligence

Platform: Installation and Configuration Guide

Check Status for SAS Visual Analytics

Servers

Ensure that the SAS Visual Analytics servers are running: n

The status of SAS High-Performance Computing Management Console on the server tier is checked with the following command: n n service sashpcmc status

The status of the server-tier SAS servers is checked with the following command:

SAS-config-dir/Levn/sas.servers status

For more information, see “Checking the Status of Servers” in SAS

Intelligence Platform: System Administration Guide

The status of SAS LASR Analytic Server Monitor is checked with the following command: n

SAS-config-dir/Levn/Applications/SASVisualAnalytics/

HighPerformanceConfiguration/LASRMonitor.sh status

For more information, see “Managing the Monitoring Server” in SAS Visual

Analytics: Administration Guide

The status of SAS Information Retrieval Studio server is checked with the following command:

SAS-config-dir/Levn/Applications/

SASInformationRetrievalStudioforSAS/IRStudio.sh status

For more information, see “Administering the Search Facility” in SAS

Intelligence Platform: Middle-Tier Administration Guide

Create SAS Users and Groups

The following tasks related to SAS users and groups need to be performed. For more information, see the

SAS Visual Analytics: Administration Guide

Create operating system groups and user accounts for data administrators on the machines in the cluster.

Set ulimits for SAS Web Applications

143 n

Create SAS metadata users for the operating system accounts for data administrators and add these users to the Visual Analytics Data

Administrators group.

(Membership in the Visual Analytics Data Administrators group grants metadata users explicit permission to use a default library for the distributed database.) n

Create groups and users in SAS metadata for SAS Visual Analytics Explorer,

SAS Visual Analytics Designer, and the mobile viewers.

For more information, see “Roles and Capabilities” in SAS Visual Analytics:

Administration Guide

Set ulimits for SAS Web Applications

On the SAS middle tier system, set ulimit settings in

/etc/security/ limits.conf

for the Installer user account that runs the SAS Web Application

Server processes.

For example, here are ulimit settings added to

/etc/security/limits.conf

for the Installer user account, sas

: sas - nofile 150000 sas - nproc 100000 sas - stack 10240

The NPROC (max number of processes) changes do not take effect unless

/etc/security/limits.d/90-nproc.conf

(Red Hat Enterprise Linux

6) or

/etc/security/limits.d/20-nproc.conf

(Red Hat Enterprise Linux

7) is also changed.

For example, to allow 100,000 processes on Red Hat Enterprise Linux 6, make the following change to

/etc/security/limits.d/90-nproc.conf

: sas soft nproc 100000

144

Chapter 6 / What to Do Next: Administration Tasks

145

Appendix 1 Deploying SAS LASR Analytic Server in a Different Mode

Overview of Deploying SAS LASR Analytic Server in a Different Mode

. . . . .

145

Deploy Visual Analytics with SAS LASR Analytic Server in

Non-distributed Mode

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

146

Add a SAS LASR Analytic Server to Run in Non-distributed Mode

. . . . . . . . .

146

Convert a Non-distributed SAS LASR Analytic Server to Distributed Mode

146

Overview of Deploying SAS LASR Analytic

Server in a Different Mode

SAS LASR Analytic Server has two modes of operation: n n

Distributed mode runs in a distributed computing environment and performs analytic tasks on data that is loaded in memory.

Non-distributed mode runs on a single machine.

For documentation about deploying SAS Visual Analytics for a nondistributed SAS LASR Analytic Server, see the

SAS Visual Analytics:

Installation and Configuration Guide (Non-distributed SAS LASR)

SAS enables you to license SAS LASR Analytic Server to run in distributed mode, non-distributed mode, or both modes. The server mode that you deploy and run is driven by the contents of your order and the license that accompanies it. For more information, see your SAS representative.

Using the SAS Deployment Wizard and the SAS Deployment Manager, you can do the following: n

Deploy the server in non-distributed mode.

For more information, see

“Deploy Visual Analytics with SAS LASR Analytic

Server in Non-distributed Mode” on page 146

Deploy the server in distributed mode.

For more information, see

“Deploying SAS Visual Analytics Interactively” on page 89

Add a server to run in non-distributed mode.

146

Appendix 1 / Deploying SAS LASR Analytic Server in a Different Mode

For sites that are licensed for both server modes, you can add and run a server in non-distributed mode. For more information, see

“Add a SAS LASR

Analytic Server to Run in Non-distributed Mode” on page 146

Convert a non-distributed server to a distributed server.

Your non-distributed servers are upgraded, and you can run the server in distributed mode only.

Also, during conversion, the SAS Deployment Wizard automatically configures the SAS LASR Analytic Server monitor.

For more information, see

“Convert a Non-distributed SAS LASR Analytic

Server to Distributed Mode” on page 146 .

Deploy Visual Analytics with SAS LASR

Analytic Server in Non-distributed Mode

For documentation about deploying SAS Visual Analytics for a non-distributed

SAS LASR Analytic Server, see the

SAS Visual Analytics: Installation and

Configuration Guide (Non-distributed SAS LASR)

Add a SAS LASR Analytic Server to Run in

Non-distributed Mode

For sites that are licensed to run both server modes, the SAS Deployment

Wizard prompts you during installation to deploy SAS LASR Analytic Server in distributed mode only. (Actually, the non-distributed mode is deployed silently.)

When sites are licensed for both server modes, to create a non-distributed SAS

LASR Analytic Server, you use SAS Management Console.

For more information, see “Add a SAS LASR Analytic Server” in SAS Visual

Analytics: Administration Guide

Convert a Non-distributed SAS LASR

Analytic Server to Distributed Mode

When converting to distributed mode, your non-distributed servers are upgraded, and SAS retains their names. (We recommend that you rename these new distributed servers.)

Also, during conversion, the SAS Deployment Wizard automatically configures the SAS LASR Analytic Server monitor.

To convert your SAS LASR Analytic Server to run in distributed mode, follow these steps:

Shut down your SAS server and middle tiers.

Convert a Non-distributed SAS LASR Analytic Server to Distributed Mode

147

For more information, see “Operating Your Servers” in SAS Intelligence

Platform: System Administration Guide

Deploy the SAS High-Performance Analytics environment on your data appliance or machine cluster.

For more information, see “Deploying the SAS High-Performance Analytics

Environment” in the SAS High-Performance Analytics Infrastructure:

Installation and Configuration Guide .

Run the SAS Deployment Wizard with it set to install only.

Follow the directions in the topic,

“Deploying SAS Visual Analytics

Interactively” on page 89

. When the Select Deployment Type page appears, make sure that you choose Install SAS Software. Make sure that Configure

SAS Software is deselected.

Figure A1.1 SAS Deployment Wizard Install Mode

When the wizard is finished, restart your SAS server tier.

For more information, see “Operating Your Servers” in SAS Intelligence

Platform: System Administration Guide

Rerun the SAS Deployment Wizard with it set to configure only.

Follow the directions in the topic, “Deploy SAS Visual Analytics Interactively.”

When the Select Deployment Type page appears, make sure that you choose Configure SAS Software. Make sure that Install SAS Software is deselected.

148

Appendix 1 / Deploying SAS LASR Analytic Server in a Different Mode

Figure A1.2 SAS Deployment Wizard Configure Mode

Note:

When prompted for the SAS configuration directory, make sure that you specify the directory that contains your pre-existing SAS Visual Analytics configuration.

When the wizard displays the Select Products to Configure page, it is important that you choose SAS Visual Analytics High-Performance

Configuration.

Figure A1.3 SAS Visual Analytics High-Performance Configuration

Convert a Non-distributed SAS LASR Analytic Server to Distributed Mode

149

Using SAS Management Console, change the Single machine server property to No for the newly converted SAS LASR Analytic Server.

For more information, see “Add a SAS LASR Analytic Server” in SAS Visual

Analytics: Administration Guide

The deployment wizard retains a server’s text analytics binary paths. To update these paths, use SAS Management Console and navigate to the server’s Extended Attributes tab. Update the

VA.TextAnalyticsBinaryLocation attribute.

For more information, see “Supporting Text Analytics” in SAS Visual

Analytics: Administration Guide

Restart your SAS server and middle tiers.

For more information, see “Operating Your Servers” in SAS Intelligence

Platform: System Administration Guide

Make sure that the signature file path for SAS LASR Analytic Server exists on the root node machine.

Regenerate all pre-existing code maintained by SAS applications (SAS

Visual Analytics, SAS Enterprise Guide, SAS Data Integration Studio, and so on) that contain LIBNAME statements that reference SAS LASR Analytic

Server tables. (You must also redeploy any scheduled jobs for this code.)

150

Appendix 1 / Deploying SAS LASR Analytic Server in a Different Mode

151

Appendix 2 Migrating SAS Visual Analytics

Overview of Migrating SAS Visual Analytics

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How to Use This Document

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

What Is Migration and What Is Supported?

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

151

151

A High-Level View of Migration

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 1: Review Additional Documentation

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 2: Design Your Migration

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 3: Perform Pre-migration Tasks

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .