Install and Configure SAS Interactively

Installing and configuring SAS interactively with the SAS Deployment Wizard consists of two main phases:

Providing installation information such as the following:
- installation type (planned or unplanned)
- 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:
- prompting level (express, typical, custom)
- SAS components to be configured on the machine
- configuration directory name
- single sign-on preference (Windows only)
- required user account credentials
- server port numbers

This topic describes some of the more important configuration pages that you will encounter during the installation and configuration phases of a SAS 9.3 deployment. The type and number of configuration-related pages that you will see depend on the prompt level that you choose, the SAS tier that you are currently deploying, and the contents of your SAS 9.3 custom order. Configuration Options by Prompt Level lists which configuration options are available for each prompt level. For information about all SAS Deployment Wizard prompts, see the online Help for the wizard page in question.

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

To install and configure SAS interactively, complete these steps:

Make sure that you have reviewed all of the documents listed in Step 1: Review Additional Documentation.
Verify that you have performed the earlier required steps outlined in Overview of Installing and Configuring Your SAS Software.

Note: A few pages into the SAS installation, the SAS Deployment Wizard prompts you for paths to the requested third-party software. You must have the necessary third-party software installed on the current machine, or the SAS Deployment Wizard will not let you continue with the installation. In this situation, you will have to end the SAS Deployment Wizard session and install the required third-party software before you can continue.
If you use any garbage collection scripts, temporarily suspend these scripts during SAS Deployment Wizard execution. 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 Content Repository Considerations.
Review information about SAS Deployment Wizard configuration prompting levels described in Overview of Configuration Options by Prompt Level.
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.
If you are deploying the SAS middle tier and intend on having the SAS Deployment Wizard automatically configure your Web application server, make sure that the server is installed, but not running.
If any machines on which you are deploying SAS 9.3 use IPv6, then a different deployment procedure is required. For more information, see IPv6 Windows Machines That Communicate with SAS Foundation Servers.
Log on to the machine with a user ID that meets the requirements for the appropriate operating system:
- Windows:
  
  Use an account that is available for the long term (for future SAS maintenance) and is a member of the Administrators group.
- UNIX:
  
  Use the same account on all machines on which you are deploying SAS. Do not use root.
- z/OS:
  
  Use the same account on all machines on which you are deploying SAS.

Start the SAS Deployment Wizard from the highest-level directory in your SAS Software Depot using the command appropriate for your operating system:

Start Up Commands for the SAS Deployment Wizard
Operating System	Command
Windows	`setup.exe -record -deploy`
UNIX	`setup.sh -record -deploy`
z/OS	First invocation of the deployment wizard to install the metadata server as a 64-bit application: `setup.rexx -z64 -record -deploy` Second invocation of the deployment wizard to install the remainder of your SAS 9.3 order as a 31-bit application: `setup.rexx -record -deploy` To use a temporary directory other than `/tmp`, specify `-templocation` new-temp-dir.

Note: Using the

-record
                              -deploy

options causes the wizard to create a response file that records the inputs that you supplied. This can be helpful when you want to repeat the deployment on other machines or when troubleshooting a deployment issue.

By default, the deployment wizard writes the response file in the following location:

Windows:

C:\Documents and Settings\current-user\sdwresponse.properties
UNIX and z/OS:

~/sdwresponse.properties

You should see a welcome page similar to the following:

Select the language that you want the SAS Deployment Wizard to use when it displays text.

For more information, see Locale and Encoding Considerations.
Select Install SAS Software.
If you have more than one SAS software order in your depot, the wizard prompts you to select the order that you want to deploy.
Select Perform a Planned Deployment, and make sure that Install SAS Software and Configure SAS Software are both selected.

Note: If any machines on which you are deploying SAS 9.3 use IPv6, then a different deployment procedure is required. For more information, see IPv6 Windows Machines That Communicate with SAS Foundation Servers.
Specify the location (SAS Home) where you want to install SAS. For more information, see SAS Installation Directory (SAS Home) Considerations.

Note: The deployment wizard prompts you for SAS Home the first time you run the wizard. On any subsequent sessions on this machine, the wizard uses the previously specified location for SAS Home.

Note: SAS Home should not be a directory within your SAS Software Depot.

Note: On z/OS, the length of the SAS Home path cannot exceed 54 characters.
Specify the type of deployment plan that you are using:
- customized deployment plan
  
  Choose Specify the full path to a customized deployment plan, and then click Browse to navigate to the plan file (plan.xml).
- standard deployment plan
  
  Choose Select a standard deployment plan, and then choose the appropriate plan in the drop-down list.
  
  For more information, see About Deployment Plans.
Select the machine on which you are installing software, and select the SAS products that you want to install, by doing the following:
1. Select the machine on which you are installing software from the Deployment Step drop-down list.
  
  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.
  
  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.
2. By default, all products displayed will be installed. Deselect any products that you do not want to install.
If SAS Enterprise Guide is in your deployment plan, and you are deploying on a 64-bit machine, the wizard prompts you whether to install SAS Enterprise Guide in 32-bit or 64-bit mode.

If you want to take full advantage of your 64-bit machine, select 64-bit Native Mode. If you are concerned about compatibility with 32-bit software that you have installed or may eventually install, select 32-bit Compatibility Mode. Note that some products have a dependency on 32-bit SAS Enterprise Guide. If one of those products is in the list of products to be installed and you choose to install the 64-bit version of SAS Enterprise Guide, the 32-bit version will be installed also.

Note: In the 64-bit version of SAS Enterprise Guide, you cannot open Microsoft Exchange or Microsoft Access data or send files by using e-mail applications that support the Messaging Application Programming Interface (MAPI). If you need these features, install the 32-bit version of SAS Enterprise Guide.
If SAS Add-In for Microsoft Office is in your deployment plan, and you are deploying on a 64-bit machine, the wizard prompts you whether to install SAS Add-In for Microsoft Office in 32-bit or 64-bit mode.

If you want to take full advantage of your 64-bit machine, select 64-bit Native Mode. If you are concerned about compatibility with 32-bit software that you have installed or may eventually install, select 32-bit Compatibility Mode.
Specify the location of the SAS installation data file that contains information about the software that you have licensed for the current machine.

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 installation failure for SAS add-on products or other errors later when attempting to run SAS.
Deselect any languages that you do not want SAS to support. By default, SAS attempts to support all languages that your machine’s operating system is configured for.
Specify the URL for the SAS environment file.

The SAS environment file defines the available set of SAS environments for SAS client applications, and is generated during the configuration of the SAS Web Infrastructure Platform. The file sas-environment.xml is located in the SAS-config-dir\Lev1\Web\Common directory.

An entry for a SAS system using a JBoss application server might resemble the following:

http://mySASWebserver.com:8080/SASLogon/sas-environment.xml

For more information, see Configuring the SAS Environment File in SAS Intelligence Platform: Middle-Tier Administration Guide.
Select the locale that affects how SAS displays text, numbers, currencies, dates, times, and sorts data. If you want to configure SAS as a Unicode server, do that here.

For more information, see Locale and Encoding Considerations.
The deployment wizard prompts you to do one of the following:

(z/OS only) No Java Runtime Environment

Select to have the deployment wizard install your software on z/OS without a Java Runtime Environment (JRE).

(UNIX and Windows only) Use the recommended Java Runtime Environment

(Recommended) select to have the deployment wizard install the required JRE on this machine.

On UNIX, specify in the text field where you want the deployment wizard to extract the JRE.

Select an existing Java Runtime Environment

Select to specify the path to a JRE that you have already installed on this machine.

For more information, see http://support.sas.com/resources/thirdpartysupport/v93/jres.html.
On Windows, on the Select Microsoft Office Applications page, choose the Microsoft Office applications for which you want the SAS Add-In for Microsoft Office activated.

When the Office application is launched, the activated SAS add-in automatically loads, and users see either a SAS tab on the Ribbon (Microsoft Office 2010 and 2007) or a SAS menu and toolbars (Microsoft Office 2003). To activate the SAS Add-In for Microsoft Office in Microsoft Excel, Word, PowerPoint, or Outlook after the installation, you can run SwitcherUtility.exe. For more information, see the Help for the SAS Add-In for Microsoft Office.
The deployment wizard scans your machine to determine whether any pre-existing SAS files are locked or do not have Write permission. 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.
(z/OS only) Provide input for the following prompts:

Note: For more information, see the SAS Deployment Wizard and SAS Deployment Manager User's Guide available at: http://support.sas.com/documentation/installcenter/en/ikdeploywizug/64204/PDF/default/user.pdf.
- FTP Batch Generation
  
  Specify the fully qualified host name or IP address of the z/OS mainframe machine on which you are deploying SAS. Also supply a valid user ID and password with which the SAS Deployment Wizard will FTP deployment information to the mainframe machine.
- Specify Jobcard Information
  
  Specify the job account, programmer-name, message class, message level, time, and region values. For more information, consult your z/OS documentation.
- Select Installation Action
  
  Choose A - Install a new SAS system.
- Specify New Installation Qualifier
  
  Specify the path where you want to install SAS. You can also choose to require Storage Management Subsystem (SMS) parameters. For more information, consult your z/OS documentation.
- Specify IBM’s SMS Parameters
  
  If you chose to require Storage Management Subsystem (SMS) parameters on the previous page, enter them here. For more information, consult your z/OS documentation.
- Specify Parameters
  
  These are all parameters that are used in various DD statements throughout the installation. For more information, consult your IBM JCL documentation.
- Specify Entry Point
  
  Specify the parameters for various ways that SAS can be run with different performance implications. Choose SAS (default ENTRY point) to run the unbundled configuration. Choose SASB to run the bundled configuration. Choose SASLPA to run the bundled configuration with some modules installed in the Link Pack Area (LPA).
- Specify Parameters
  
  Specify additional parameters for DD statements. VOLDISK designates the VOLSER that the installed data sets will go to. For more information, consult your IBM JCL documentation.
- Specify Parameters
  
  Specify parameters used for reblocking the SAS load modules to a library with an optimum block size.
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 deployment 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 the SAS Install Center at http://support.sas.com/documentation/installcenter/93, and use the operating system and SAS version to locate the appropriate SAS Foundation Configuration Guide.
(UNIX only) If your system uses Pluggable Authentication Modules (PAM), select Use PAM Authentication. In addition, you might also need to update your PAM configuration files in order for SAS 9.3 to use PAM authentication. For more information, see the Configuration Guide for SAS 9.3 Foundation for UNIX Environments.

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

Note: Do not select the PAM option if you know that your system uses /etc/password or /etc/shadow authentication.
Review the list of third-party software that is required for the SAS software that you are installing on the current machine. (The list of third-party software depends on the SAS software that you are installing on the current machine.) In the pages that immediately follow, be prepared to provide paths to these third-party applications. For more information about the third-party software versions that SAS 9.3 supports, see Pre-installation Checklists for Third-Party Products. (The number of wizard pages varies depending on the SAS software that you are deploying on the current machine.)

Note: You must provide valid paths to the requested third-party software, or the SAS Deployment Wizard will not let you continue with the installation.
Specify the amount of information to provide the SAS Deployment Wizard for configuring the SAS software that you are installing on the current machine. Choose one of the three prompting levels:

Note: When deploying the SAS 9.3 middle-tier, by default, the SAS Deployment Wizard automatically configures your Web application server. To disable this feature, run the wizard using either the Typical or Custom prompting levels.

Express

display the minimum number of wizard pages needed to complete the SAS configuration.

Typical

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

Custom

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

Refer to Overview of Configuration Options by Prompt Level 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 will encounter during the configuration phase of a SAS 9.3 deployment. The options for which the SAS Deployment Wizard prompts you depends on which SAS products are identified in your deployment plan and, in multiple machine deployments, which machine you are currently deploying. Configuration Options by Prompt Level lists which configuration options are available for each prompt level. For information about all SAS Deployment Wizard prompts, see the online Help for the wizard dialog box in question.
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 (for example, Lev1 = production).

In UNIX 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.

Note: The last digit of the default port number reflects the configuration level that you select in the SAS Deployment Wizard. For example, when you select Lev1, the default port for the metadata server is 8561. If you choose 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 Home and SAS configuration directories can share the same parent directory, one directory should not reside inside another. Defining the configuration directory under the SAS Home directory, or vice versa, can lead to file permission issues arising from the need to manage installed files differently than site-specific configurations.

On z/OS, the mount point must exist. The SAS Deployment Wizard will create the necessary subdirectories.

If you are deploying the SAS Framework Data Server, then SAS configuration path should be a path local to the machine. The configuration path should not be on an NFS shared disk. If you want to put your configuration path on a shared disk, then you must make sure that you specify a local path for the Framework Data Server content directory. You can set the content directory on the Framework Data Server Invocation Options page. This page is available only on the custom configuration prompting level.

Local Machine Name

Enter the complete name of the local host in Fully-qualified Local Host Name. The fully qualified local host name typically takes the form of the local host name plus the domain name server (for example, myserver.example.com). Enter a short host name in Short Local Host Name. The short local host name is the abbreviated, more common method of referring to the host, usually only a single word.

Migration Information

Ignore this page and click Next.

If you need to migrate SAS 9.1.3 content to SAS 9.3, see Introduction in SAS Intelligence Platform: Migration Guide.

Authentication Domain

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 metadata server is on Windows and the workspace server is on UNIX, the workspace server might be assigned to a SAS authentication domain named UnixAuth. For more information, see Manage Authentication Domains in SAS Management Console: Guide to Users and Permissions.
Windows Options (run as managed scripts or services)

On Windows, choose how to run your SAS servers, either by using management scripts or running them as Windows services. If you choose the script option, then the user account that runs the object spawner must meet the following requirements on the object spawner machine:

be the administrator or a member of the Windows Administrator’s group

have the following Windows local user rights:

Adjust memory quotas for a process

Replace a process level token
Integrated Windows Authentication

Select to configure workspace servers running on Windows or UNIX to use Integrated Windows authentication (IWA). IWA uses a single sign-on feature which 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 metadata server and the workspace server running on either Windows or UNIX. The mechanism used is typically Kerberos, but on Windows, NTLM may also be used.

You will also encounter this page when deploying SAS Enterprise Guide and SAS Add-In for Microsoft Office. If you have not chosen IWA for the 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 and the chapter “Configuring Integrated Windows Authentication” in Configuration Guide for SAS Foundation for UNIX Environments, available at: http://support.sas.com/documentation/installcenter/en/ikfdtnunxcg/64205/PDF/default/config.pdf.

A metadata server running on Windows or Unix has IWA enabled by default. For more information, see SSPI System Option in SAS Intelligence Platform: Application Server Administration Guide.

SAS Metadata Server

If you have any changes for the metadata server, enter them in this page.

The deployment wizard creates a separate server context (SASMeta) for the metadata server and the other servers required to perform metadata server utility functions, such as backup and promotion. 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. Therefore, we recommend that you not change the logical server or server prefix (SASMeta).

For more information, see Overview of the SAS Metadata Server and Its Initial Configuration in SAS Intelligence Platform: System Administration Guide.

Deployment Accounts: Type of Accounts

Select whether to use internal accounts when appropriate. Internal user accounts are accounts known only to SAS and are created and authenticated internally in metadata rather than externally.

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.
External Account: Installer

Enter the user ID and password for the external account to be used 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 Administrators group.

UNIX:

Use the same account on all machines on which you are deploying SAS. Do not use root.

z/OS:

Use the same account on all machines on which you are deploying SAS.

For more information, see Defining User Accounts.
SAS Internal Account: Unrestricted Administrator

Enter a password for the internal account (sasadm@saspw) that the wizard will create to serve as an unrestricted administrator for the purpose of configuring the SAS metadata server.

For more information, see Defining User Accounts.

SAS Internal Account: Trusted User

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.

For more information, see Defining User Accounts.
SAS BI Web Services: Authentication Method

Select the method by which users of SAS BI Web Services are authenticated:

SAS Authentication is managed by the metadata server.

Web Authentication is managed by the Web application server using container-based authentication or a third-party product. Selecting Web Authentication has these effects:

partially configures Web authentication for Java BI Web Services. 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 Web Information Portal, and so on). You will have to configure Web authentication for these BI Web applications.

prevents you from being offered a chance to set 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. Currently, SAS BI Web Services for Java and .NET and the SAS Stored Process Web Application are the only components that support this feature.

For more information, see Using the SAS Anonymous Web User with SAS Authentication in SAS Intelligence Platform: Middle-Tier Administration Guide.

SAS Internal Account: Anonymous Web User

(Optional) Enter the user ID and password for the internal SAS account to be used to grant clients access to applicable SAS Web Infrastructure Platform applications such as SAS BI Web Services and the Stored Process Web Application. When SAS authentication is being used and the user has not preemptively specified credentials, the client will be given access to these Web applications under the anonymous user account.

For more information, see Using the SAS Anonymous Web User with SAS Authentication in SAS Intelligence Platform: Middle-Tier Administration Guide.

External account: SAS Spawned Servers Account

Enter the user ID and password for the external account to be used to start the pooled workspace server and the stored process server. On Windows, enter a domain-qualified user ID.

For more information, see Defining User Accounts.

Create Common Directories

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

Server Encryption

Select the encryption level and algorithm that SAS clients and servers use to connect to the metadata server.

Choose Credentials to encrypt only login credentials. Choose Everything to encrypt all communication with the metadata server. (Choosing Everything can affect your SAS performance.)

To specify an encryption algorithm other than SASPROPRIETARY, you must have a license for SAS/SECURE software. The other algorithms are: RC2, RC4, DES, TripleDES, and AES.

For more information, see Encryption Model in SAS Intelligence Platform: Security Administration Guide.

Client-side Credentials Policy

Select this option to set the policy to allow users to save their user IDs and passwords in client-side connection profiles on the metadata server for desktop applications. This input sets the value for OMA_SASSEC_LOCAL_PW_SAVE in omaconfig.xml.

For more information, see Reference Information for omaconfig.xml in SAS Intelligence Platform: System Administration Guide.

E-mail Server

Enter the port and host name for an SMTP e-mail server that the SAS Metadata Server uses to send e-mail alerts to an administrator if journaling issues arise. The SAS Deployment Wizard also 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. In order 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 Adding or Modifying E-Mail Settings for SAS Application Servers in SAS Intelligence Platform: Application Server Administration Guide 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 server context for the SAS Application Server definition. 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.

For more information, see Overview of SAS Application Servers in SAS Intelligence Platform: Application Server Administration Guide.

Metadata Utility Workspace Server

Enter the name of the logical workspace server and the workspace in metadata. You also need to enter the name of the machine on which the workspace server runs and the port on which the object spawner will listen for client requests to launch workspace servers. The machine name should match the name specified to the object spawner.

Unlike a regular workspace server, access to this server is limited to members of the SAS Administrators group, and its use is limited to metadata server administration tasks such as promotion and backup.

In SAS 9.3, two or more workspace servers can share the same port even if they are running at the same time.

For more information about ports, see Designating Ports and Multicast Addresses.

SAS Pooled Workspace Server

Enter the name of the logical pooled workspace server and the pooled workspace in metadata. You also need to enter the name of the machine on which the pooled workspace server runs and the port on which the object spawner will listen for client requests to launch pooled workspace servers. The machine name should match the name specified to the object spawner.

For more information, see Overview of Workspace Servers and Stored Process Servers in SAS Intelligence Platform: Application Server Administration Guide.

SAS Framework Data Server

Enter the name of the logical Framework Data Server in metadata. You also need to enter the name of the machine on which the Framework Data Server runs and the TCP/IP port on which the Framework Data Server will listen to. For more information, see the SAS Intelligence Platform: Middle-Tier Administration Guide.

Metadata Utility SAS DATA Step Batch Server

Enter the various values required to configure a SAS DATA step batch server. The directory fields identify where the deployed SAS program is stored and the name of the deployed SAS DATA step program job. Access to this server is limited to members of the SAS Administrators group, and its use is limited to metadata server backup.

For more information, see Contents of the Metadata Server Subdirectory (SASMeta) in SAS Intelligence Platform: System Administration Guide.

Query Cache Library

Enter the physical location on the file system where the SAS library will exist for temporary files used when creating optimized tables for query look up.

In Query Cache Libref, enter the SAS library reference which SAS will use to refer to the query optimizer SAS library. The name must be eight characters or shorter and should be unique from other librefs used within this repository. Librefs must start with a letter or underscore and contain only letters, numerals, or underscores. The typical installation libref name is wrstemp. The libref will be used in conjunction with the server context name to form the SAS library name for the optimizer library.

Select Enable Query Cache to allow the query optimizer to run. If this selection is not made, then the query optimizer will not attempt to optimize queries and will not create temporary data sets for improving performance during rendering. A typical installation will have this selection turned on. The temporary files created within the query cache library will be visible to anyone with Read permission on the Renderer Optimizer directory, so if you have security concerns with the authorization on this folder, you might want to leave the optimizer off.

For more information, see Using the Query Cache in SAS Intelligence Platform: Web Application Administration Guide.

Output Management Library

Enter the physical location on the file system where the SAS library will exist for burst set definition tables for reports which will be distributed by e-mail. A burst definition table will contain e-mail addresses, channels, and possibly by group information.

In Output Management Library Libref, enter the SAS library reference that SAS will use to refer to the output management SAS library. The name must be eight characters or shorter and should be unique from other librefs used within this Repository. Librefs must start with a letter or underscore and contain only letters, numerals, or underscores. The typical installation libref name is wrsdist. The libref will be used in conjunction with the server context name to form the SAS library name for the distribution library.

For more information, see Verifying Permissions for the Distribution Library in SAS Intelligence Platform: Web Application Administration Guide.

Web Application Server: Automatic Configuration

Select this option for the deployment wizard to automatically build and configure the SAS Web applications as well as configuring a sample Web application server for use with SAS 9.3. (To use this wizard feature, make sure that your Web application server is not running before proceeding. For WebSphere, it is necessary to stop all deployment manager servers, all node agent servers, and all application servers before continuing with your SAS 9.3 deployment. The one exception is on z/OS, where the WebShere web application server should be running.) For more information, see Choose Whether to Automatically Configure Your Web Application Server.

Note: When installing SAS Enterprise BI server to use a WebSphere Base Server, make sure that you choose not to have the SAS Deployment Wizard automatically configure your Web application server.

If you choose not to automatically configure your Web application server, you will still be 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 these manual instructions on how to configure your server and deploy your Web applications. If you manually configure WebLogic, a reference domain will be created in your SAS configuration area, but no servers will be started. If you manually configure JBoss, sample start scripts will be created, but not launched.

For more information, go to http://support.sas.com/resources/thirdpartysupport/v93/appservers/index.html and select the product name of your Web application server.

Web Application Server: Multiple Managed Servers

Select to have the deployment wizard automatically configure multiple managed servers for you using 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 chose to manually configure your application servers, you will be provided with recommended configuration settings in a generated instructions file (Instructions.html) when the SAS Deployment Wizard completes.

More advanced performance configuration considerations are documented in the SAS Intelligence Platform: Middle-Tier Administration Guide.
Web Application Server: Managed Server

Enter a logical name for your managed server. This name will be displayed in your application server administrative console and used in administrative scripting.

CAUTION:

The managed server name must be unique. Non-unique names will cause your Web configuration to fail.

In HTTP Port, enter the unsecured port on which the managed server will listen.

In HTTPS Port, enter the SSL port to be assigned to the managed server.

In SOAP Port, (WebSphere only) enter the SOAP port that the WebSphere administrative services will use to communicate with this managed server, if SOAP was selected. This port can also be used by the wsadmin utility.

In RMI Port, enter a port using these considerations:

WebSphere

This maps to the RMI BOOTSTRAP port. Each server contains an administrative services component and a separate and unique port is required for each application server.

JBoss

This maps to the default JNDI port. Clients connecting to applications running on JBoss, such as the JBoss shutdown command, would use this port.

WebLogic

No RMI port is required for WebLogic.

In RMI Timeout, Enter the RMI timeout value (in seconds) that will be used to determine when RMI requests between the WebSphere deployment manager and the nodeagent have timed out, if the RMI protocol was selected.

In IPC Timeout, enter the IPC timeout value (in seconds) that will be used to determine when IPC requests between the WebSphere deployment manager and the nodeagent have timed out, if the WebSphere deployment manager and the nodeagent are on the same host.

In Configured Protocol, select the communication protocol for the administration server: HTTP or HTTPS. Automated configuration through the SAS Deployment Wizard only supports the HTTP protocol. If you perform a manual configuration, you can set up HTTPS.

In enter any additional Java options that you want the managed server JVM (Java Virtual Machine) to use. These JVM options are tagged onto the end of the managed server’s command line. Options that are deployment wizard defaults can be overridden in this way.

For more information, go to http://support.sas.com/resources/thirdpartysupport/v93/appservers/index.html and select the product name of your Web application server.
Database type for SAS Web Infrastructure Platform

If you want to use a database other than the SAS Framework Data Server to store SAS Web Infrastructure Platform data, then choose the type of database here. In SAS 9.3, the following third-party databases are supported: DB2, MySQL, Oracle, PostgresSQL, and SQLServer.

SAS Web Infrastructure Platform database properties

Enter the host name, fully qualified host name, or IP address for the host where the database is installed. Specify the port that the database server is listening to and the name of the database that will contain the SAS Web Infrastructure Platform tables.

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

Choose Automatically create tables and load data to have the deployment wizard automatically create tables and load the selected pre-existing database with initial data.

Choose Use Catalog to indicate whether the database catalog needs to be specified in order to uniquely locate a table in the database. The database catalog should be specified if using one of the following databases: MySQL, SAS Framework Data Server, or SQL Server.

Choose Use Schema Pattern to indicate whether the database schema needs to be specified in order to uniquely locate a table in the database. The database schema should be specified if using either DB2 or Oracle.

In the case of MySQL, the SAS Web Infrastructure Platform configuration process will also create a new MySQL database in addition to creating tables and loading data. The new database is named according to the value specified in the Database Name field.

Note: If you are using MySQL, do not specify a pre-existing MySQL database or the configuration will fail. For more information, see “Configuring an Alternative Database for SAS Web Infrastructure Platform Services” available at: http://support.sas.com/resources/thirdpartysupport/v93/appservers/SharedServicesAlternativeDatabase.pdf.

For more information, see JDBC Data Sources in SAS Intelligence Platform: Middle-Tier Administration Guide.

SAS Web Infrastructure Platform JDBC Properties

Enter the user account and its password for accessing the database used with your SAS Web Infrastructure Platform tables.

If you have selected to automatically configure the SAS Web Infrastructure Platform database, this user account must have the ability to create tables and insert records. If you are not automatically configuring the SAS Web Infrastructure Platform database, this user account must have the ability to insert, update, and delete records. The default user account is the SAS Administrator account (sasadm@saspw). For more information, see JDBC Data Sources in SAS Intelligence Platform: Middle-Tier Administration Guide.

In the Directory containing JDBC driver jars fields, enter the appropriate JDBC driver jars and your selected RDBMS database and version. Inappropriate or additional jar files will cause configuration failures, so just copy the minimum required jars to the JDBC driver jars directory.

SAS Web Infrastructure Platform: Database Metadata

Specify the database catalog or schema if necessary to uniquely query table metadata from the SAS Web Infrastructure Platform database.

Web Application Server: Automatic Deployment

Select to automatically deploy SAS 9.3 Web applications to the Web application server. For more information, see Choose Whether to Automatically Deploy the SAS Web Applications.

Regardless of whether you choose to automatically deploy your SAS Web applications, when building Web applications, the wizard also automatically explodes Web application archive files (.EAR files).

If you choose not to automatically deploy SAS Web applications, the deployment wizard writes manual deployment instructions to Instructions.html during the Web application deployment stage, that you will need to complete after the wizard finishes executing. For more information, go to: http://support.sas.com/resources/thirdpartysupport/v93/appservers/index.html and select the product name of your Web application server.
External Account: Web Application Server Administrator

You are prompted for this information if your site uses the WebSphere or WebLogic Web application server. Enter the user ID and password for the administrator account for either the WebSphere Application Server or the WebLogic Server. On Windows, be sure to enter a domain-qualified user ID.

For WebSphere, the Web application server administrator user ID is the administrator account specified when WebSphere Admin Security was enabled.

For WebLogic, the Web application server administrator user ID is used to configure the WebLogic default security realm. When the deployment wizard automatically configures your Web application server, the wizard uses these credentials to create the administrator account and the WebLogic domain.

If you choose to manually configure your Web application server, you will need to create this administrator account (using the credentials that you define here) with the WebLogic administrative tools.

For more information about configuring Web application servers to support the SAS middle tier, go to: http://support.sas.com/resources/thirdpartysupport/v93and select “IBM WebSphere” or “Oracle WebLogic”.
Web Application Server: Proxy Information

If you are using SAS Information Delivery Portal RSS feeds, then you will have to provide proxy server information. Enter the fully qualified host name for the proxy server and its port that your site uses to access the Internet.

For NonProxy Hosts, enter the DNS names of all the machines that should not be accessed through the proxy server. Be sure to include other machines where application servers are configured as part of a common WebLogic Domain or are part of a WebSphere cell. 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, refer to configuration information available at this SAS Web site: http://support.sas.com/resources/thirdpartysupport/v93 and select your Web application server.

WebSphere Application Server: Node

In Profile Name, enter a profile name, or accept the default (SAShostname01). The profile name is used for the directory that contains the node agent and the SAS Web application server.

The node agent name is required, but cannot be configured using the deployment wizard.

In Node Name, enter a node name or accept the default (SAShostnameNode). The node name is the WebSphere node that contains one or more of the Web application servers.

In Additional JVM Options, enter any additional Java options that you want the Web application servers to use.

IP Multicast

Accept these IP multicast settings or enter new ones.

A multicast group communications protocol is used to communicate among middle-tier SAS applications in a single SAS deployment (the set of applications connected to the same metadata server). The combination of multicast IP address and multicast UDP port should be different for each SAS deployment and also different from those used by other multicast applications at your site. The defaults are most appropriate for deployments in a firewall-isolated data center environment.

For more information, see Designating Ports and Multicast Addresses.

SAS Remote Services Application: JVM

Enter the desired initial heap size for the remote services application using the JVM option format.

In Max JVM Heap Size, enter the desired 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 Remote Services VM 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 9.3 Web Applications: Tuning for Performance and Scalability available at: http://support.sas.com/resources/thirdpartysupport/v93/appservers/WebTierScalabilityAndPerformance.pdf.
SAS Information Delivery Portal unchallenged access

When unchallenged access is enabled, users can access the portal and interact with selected content without providing a user ID and password.

Enter a user ID that SAS will use to grant unchallenged access to portal users. On Windows, be sure to qualify the user ID as appropriate (for example, myDomain\sasguest).

Deselect Display Search Menu for Unchallenged Access if you want to suppress the search link from displaying in the main portal banner.

Specify what should appear in the portal banner for unchallenged users:

logoff

Display the Log Off link.

logon

Display the Log On link (which users can click to display the SAS Logon Manager).

hide

Hide the Log Off and Log On links.

For more information, see Enabling Unchallenged Portal Access in SAS Intelligence Platform: Web Application Administration Guide.
SAS Web Report Studio: Scheduling

Choose whether to enable scheduling for SAS Web Report Studio. If Platform Suite for SAS is in your deployment plan, then you have a choice between using Platform Process Manager, provided by Platform Computing, Inc., or SAS In-Process Services.

For more information, see Setting Up Scheduling Using Platform Suite for SAS in Scheduling in SAS or Setting Up Scheduling Using SAS In-Process Scheduling in Scheduling in SAS

SAS Content Server: Repository Directory

Enter the location on the disk for the actual contents of the content repository.

Select Use configured database for content storage if you want to store SAS Content Server content in the SAS Web Infrastructure Platform database instead of the file system. When this check box is selected, the path identified in the Repository Directory is used to store configuration files and indexes only. (Selecting the SAS Web Infrastructure Platform database type is discussed earlier.)

For more information, see Administering the SAS Content Server in SAS Intelligence Platform: Middle-Tier Administration Guide.

SAS Web Parts for Microsoft SharePoint: Details

We recommend that you accept the defaults.

The Web URL is the address of the Web application where the SAS Web Parts solution is deployed.

The Site URL is the site collection where the feature is activated. A Web application can have multiple site collections, and a site collection can contain multiple sites. In most instances the URLs are the same (a site collection at the root of the web application), but they can also be different.

For more information, contact your site’s SharePoint administrator.

The SAS User ID is the metadata identity that you use to implement shared identity mode. For more information, see Configure User Access for SAS Web Parts for Microsoft SharePoint.
DataFlux Data Management Server

In DataFlux Data Management Server Name enter the simple name of the DataFlux Data Management Server definition. (Do not use quotation marks.)

In Host Name enter the fully qualified host name for the machine that contains the DataFlux Management Server.

DataFlux Data Management Server: Server Component Name

In Server Component Name enter a name to uniquely identify this DataFlux Data Management Server in metadata. When the server starts, it searches for its definition in SAS metadata using this name.
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 provided in previous pages before the wizard begins writing to your system.
Make one of the following choices:
- Click Start to begin installing SAS files and writing the configuration to the current machine.
- 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.
On UNIX, 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.

CAUTION:

To avoid configuration failure, do not proceed until the script completes.

On Windows, the deployment wizard checks to make sure that your machine contains the minimum system requirements necessary to run SAS 9.3.

Sometimes, it is necessary to reboot your machine after the wizard has installed certain system components. When this occurs, the wizard prompts you to log back on to the machine, and continues to the next configuration step in your SAS deployment process.

Your credentials are temporarily stored in your Windows registry using the Windows auto 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, please refer to 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.

When you see a page similar to the following, the SAS Deployment Wizard is finished:

The deployment wizard has installed, configured, and started SAS processes on your machine.
Click Review Manual Configuration Instructions and complete any necessary manual configuration steps.
The SAS Deployment Wizard writes the Instructions.html file to the Documents directory under the SAS configuration path. For example:
- UNIX and z/OS:
  
  /opt/SAS/Lev1/Documents/Instructions.html
- Windows:
  
  C:\SAS\Config\Lev1\Documents\Instructions.html
Click Finish to close the deployment wizard.
For multi-machine deployments, back up your metadata repository and your SAS configuration directory before you run the SAS Deployment Wizard on the next machine called for by your deployment plan.
- Make a backup copy of your SAS 9.3 configuration directories by using your site-approved method. Your SAS configuration directories are all the child directories beneath the path that you specified earlier in this procedure on the Specify Configuration Information wizard page.
- Back up your Web application server directories.
- Back up your metadata repository and repository manager on the SAS Metadata Server machine. For more information, see Best Practices for Backing Up and Restoring Your SAS Content in SAS Intelligence Platform: System Administration Guide.
If you are deploying a middle-tier machine and opted not to automatically deploy your SAS Web applications, then you must manually deploy them. For more information, go to the Third-Party Software Downloads site at: http://support.sas.com/resources/thirdpartysupport/v93/appservers/index.html and select the product name of your Web application server.
When you have completed any manual configuration tasks, and you have made the necessary backups, repeat the steps listed in this topic on each machine defined in your deployment plan.
Be sure to restart any servers that you stopped for purposes of creating a backup.
When you are finished installing and configuring SAS on each machine called for in your deployment plan, proceed to the next section.