Step 3: Prepare Your Environment

Overview of Prepare Your Environment

Review Your Pre-Installation Checklist

A pre-installation checklist accompanies the deployment plan that was prepared for deploying SAS at your site. Be sure to refer to that checklist as you prepare your environment.

Set Up User Accounts

User accounts that are needed for your SAS deployment can be either local accounts on the machine on which you are deploying SAS, or domain accounts that have access to the machine. Although you can use your own account names, SAS recommends using the names that are listed in the following table. If you choose to use different account names, be sure to record the names (and passwords) for future reference.
Pre-installation Checklist for User Accounts
User Account
Operating System
Recommended User ID
User Rights Needed
SAS Installer
Both
my-domain\sas
or
my-machine\sas
Windows
Log on as a batch job
Linux
The group that you designate as the primary group for the SAS installer must contain the SAS Spawned Servers account.
SAS Spawned Servers1
Both
my-domain\sassrv
or
my-machine\sassrv
Windows
Log on as a batch job
Linux
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.)
SAS First User1
Both
my-domain\sasdemo
or
my-machine\sasdemo
Windows
Log on as a batch job
Linux
SAS LASR Administrator 2
Both
my-domain\saslasradm
or
my-machine\saslasradm
Windows
Log on as a batch job
Linux
1The SAS Deployment Wizard automatically assigns the Log on as a batch job right to the SAS Spawned Servers account and SAS First User account.
2Not required but recommended when validating your deployment.
The accounts that are listed in the preceding table are recommended and used for the following purposes:
  • SAS Installer is used to install SAS. After you create the account, log on to the machine with this account to perform the deployment. It is recommended that this account remain available for future SAS maintenance and updates.
  • SAS Spawned Servers is the process owner for SAS Stored Process Servers and SAS Pooled Workspace Servers on the machine. During the SAS deployment, the SAS Deployment Wizard prompts you to enter the account name and password for this account.
  • SAS First User is used for demonstration purposes. This account is often referred to as sasdemo. During the SAS deployment, the SAS Deployment Wizard prompts you to specify the account name for this account. The SAS First User account is not a required account. However, it is used for the purposes of this installation guide.

Set Up an Operating System Group

Set Up the SAS Server Users Group (Windows)

To run SAS on Windows, users must have the Log on as a batch job right on the machine that hosts the server. We recommend that you create a group on the server, add SAS users to the group, and then assign that group the Log on as a batch job right.
Note: The SAS Deployment Wizard automatically assigns the Log on as a batch job right for the SAS Spawned Servers account and SAS First User account.
To create the SAS Server Users group and assign the Log on as a batch job right, do the following:
  1. Click Start. In the Search programs and files field, enter Computer Management, and select it from the Start menu when it appears.
  2. Expand Local Users and Groups.
  3. Right-click Groups, and select New Group.
  4. Name the group “SAS Server Users,” and click Create.
  5. Assign the Log on as a batch job right to the new SAS Server Users group.
    Click Start. In the Search programs and files field, enter Local Security Policy, and select it from the Start menu when it appears.
  6. In the left pane of the Local Security Policy window, expand Local Policies, and click User Rights Assignment.
  7. In the right pane under the Policy column, double-click Log on as a batch job. This displays the Log on as a batch job Properties dialog box.
  8. On the Local Security Setting tab, click Add User or Group. In the Enter the object names to select field, enter SAS Server Users, and click Check Names to select the SAS Server Users group. Then, click OK to return to the Log on as a Batch Job Properties dialog box. Verify that the new group that you created appears in the text box on the Local Security Setting tab.
  9. Click OK to close the dialog box and return to the Local Security Policy window.
In the future, any new SAS users that you add to your SAS system can be granted the Log on as a batch job right by adding them to the SAS Server Users group in Windows. Because the SAS Server Users group was assigned the Log on as a batch job right, it is not necessary to explicitly assign this right to users in the Local Security Policy window.

Set Up the sas Group (Linux)

To run SAS on Linux, you should create an operating system group (sas) and make it the primary group for the Linux SAS installer user. The SAS Spawned Servers account should be made a member of the sas group. (Members of this 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.

Download and Install Required Third-Party Software

SAS Visual Analytics requires that your machine have the following third-party software installed:
  • Windows PowerShell
    Windows PowerShell is a configuration management and task automation framework from Microsoft that is required by SAS Visual Analytics.
    Later, you are prompted for the Windows PowerShell installation path here: Step 18.
  • Python
    Python is a general-purpose programming language required by SAS Information Retrieval Studio.
    Later, you are prompted for the Python installation path here: Step 17.
    Note: For more information about Python, see Installation Note 50147.
  • JUnit
    To run certain test suites, the SAS Deployment Tester requires JUnit, which is an open-source framework for writing and running tests in the Java programming language.
    Later, you are prompted for the JUnit installation path here: Step 56.
If you need any of this software, you can download it from SAS Support for Additional Software Products.
Note the location where this third-party software resides on your machine. (See the following table.)
Pre-installation Checklist for Third-Party Software
Third-Party Software
Default Installation Path
Actual Installation Path
Windows PowerShell
C:\Windows\System32\WindowsPowerShell\v1.0
Python
C:\Python27
JUnit
C:\junit\junit-4.8.1.jar
Last updated: September 19, 2017