Step 4: Install and Configure SAS

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.

If the path is incorrect, the wizard does not proceed. In this case, enter the correct path where the third-party software is installed that you recorded in Pre-installation Checklist for Third-Party Software. Click Next.

If the path is incorrect, the wizard does not proceed. In this case, enter the correct path where the third-party software is installed that you recorded in Pre-installation Checklist for Third-Party Software. Click Next.

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).

The short local host name is the abbreviated, more common method of referring to the host, usually only a single word (for example, MyMachine).

Prefix the user ID with either the domain or machine name (for example, domain\user-ID or machine-name\user-ID). Click Next.

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.

If you do not select this option, you will have to run setuid.sh manually during installation (and configuration if you have chosen to configure) is complete. Note that setuid.sh must be run as root in order to complete successfully. If you have any concerns with the SAS 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. For more information, see Step 100.

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.

For more information, see “Reducing the Number of Password Prompts” in the SAS Visual Analytics: Installation and Configuration Guide (Distributed SAS LASR).

Prefix the user ID with either the domain or machine name (for example, domain\user-ID or machine-name\user-ID). Click Next.

The SAS First User account, which is often referred to as sasdemo, is used for demonstration purposes. Although it is not required, the SAS First User account can be used to validate your deployment.

Prefix the user ID with either the domain or machine name (for example, domain\user-ID or machine-name\user-ID). Click Next.

For more information, see Initial Sizing and Tuning Configuration Options for Deployments in SAS Web Applications: Tuning for Performance and Scalability.

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.

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.

For example:

For security reasons, you must list any host name URLs for any site that could redirect browsers to your solution. This might include 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.

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.

The password must contain at least six characters.

The passphrase must be at least eight characters long and can contain letters and numbers only.

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.

On Windows, the deployment wizard checks to make sure that your machine contains the minimum system requirements necessary to run SAS 9.4. Sometimes it is necessary to reboot your machine after the wizard has installed certain system components. When this occurs, after you log back on to the machine, the wizard continues to the next configuration step in your SAS deployment process.

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.