Previous Page | Next Page

Installing and Configuring Your SAS Software

Preparing to Install and to Configure

The topics contained in this section are:

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 (SID file) and a deployment plan (plan.xml) for its initial input, the wizard is designed to prompt the customer for all of the remaining input at the start of the session so that the customer does not have to monitor an entire deployment.

There are two major ways that you can run the SAS Deployment Wizard:

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. There are two types of deployment plans: standard and custom. A standard deployment plan describes a common configuration. Standard plans are stored by default in the SAS Software Depot. A custom deployment plan is created by a SAS representative specifically for a site.

At the end of the SAS deployment, the SAS Deployment Wizard makes a copy of the deployment plan it used. The deployment plan can be helpful when you want to add another SAS product or change your SAS configuration. The wizard stores a copy of the deployment plan in the SAS configuration directory in the utilities directory, and inserts a date and time stamp to the deployment plan filename. For example:

C:\SAS\Config\Lev1\Utilities\plan.2009-02-17-11.04.xml

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

Content Repository Considerations

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

Installation Order 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 computers in a particular order:

How the Deployment Wizard Names SAS Web Application Servers

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

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

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

IPv6 Windows Machines that Communicate with SAS Foundation Servers

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

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

  1. Run the SAS Deployment Wizard in install mode.

    Begin following the directions for running the wizard. Early in the process, when the Select Deployment Type page appears, make sure that the Configure SAS Software check box is not selected. For more information, see Install and Configure SAS Interactively.

    [Choosing to run the SAS Deployment Wizard in install only mode]

  2. After the installation phase has completed, copy the following JAR file from your SAS Software Depot to the machine's JRE ext directory:

    depot-install-dir\thirdparty\ipv6\sas.nioc.channels.jar

    For example:

    copy C:\SAS Software Depot\thirdparty\ipv6\sas.nioc.channels.jar C:\Program Files\Java\jre1.5.0_15\lib\ext

  3. Add the following JVM start-up options to your Web application server start-up script:

    -Djava.net.preferIPv4Stack=false

    -Djava.net.preferIPv6Addresses=true

    By default, the script is named SASServer1.bat and resides in your Web application server configuration directory. For information on how to manually configure your Web application server for SAS Web applications, go to the Third-Party Software Downloads site at http://support.sas.com/resources/thirdpartysupport/v92 and search for the product name of your Web application server.

  4. Rerun the SAS Deployment Wizard in configure mode to complete your SAS 9.2 deployment.

    Begin following the directions for running the wizard. Early in the process, when the Select Deployment Type page appears, make sure that the Install SAS Software check box is not selected. For more information, see Install and Configure SAS Interactively.

    [Choosing to run the SAS Deployment Wizard in config only mode]

Interactive Prompting Levels

Shortly after you begin running the SAS Deployment Wizard to interactively install and initially configure SAS, you will be asked to choose between three wizard prompting levels:

Express

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

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.

Note:   If you are deploying the SAS Table Server, then the 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 table server content directory. You can set the content directory on the Table Server Invocation Options page. This option is available only on the custom configuration prompting level.  [cautionend]

The following table lists the configuration options and the prompt level in which they display for the SAS Intelligence Platform only. Depending on your configuration, you might see differences for the prompt level in which a particular option displays. This is one example of a prompt level and configuration option mapping for a sample configuration.

Note:   The configuration options you encounter depend on which SAS products are identified in your deployment plan, and, in multiple machine deployments, the machine you are currently deploying.  [cautionend]

Configuration Options By Prompt Level
Configuration Option in the SAS Deployment Wizard Prompt Level That Displays the Option
Express Typical Custom
Configuration prompting level*
 X X X
Configuration directory and level*
 X X X
Migration*
 X X X
Type of deployment accounts*
 X X X
Installer account credentials*
 X X X
Metadata server port and host name1 X X X
Unrestricted administrator account credentials*
 X X X
Trusted user account credentials*
 X X X
Anonymous Web user account credentials*
 X X X
SAS spawned server account credentials*
 X X X
E-mail server information*
 X X X
Web application server: managed server name and ports*
 X X X
SAS Shared Services JDBC connection credentials*
 X X X
Web application server administrator* 2
 X X X
WebSphere application server node name, node agent name, and profile name*
 X X X
Web application server dependencies X X X
SAS Web Application Themes dependencies X X X
SAS Web Report Studio scheduling user (Platform LSF only) X X X
SAS Web Report Studio dependencies X X X
SAS BI Dashboard dependencies X X X
SAS Information Delivery Portal JPS extension dependencies X X X
SAS Help Viewer metadata configuration dependencies X X X
SAS Web Infrastructure Platform dependencies X X X
SAS Information Delivery Portal dependencies X X X
SAS Shared Services dependencies X X X
SAS BI Portlets dependencies X X X
SAS Flex Application Themes dependencies X X X
SAS BID to WIP Cross Pollination dependencies X X X
Local machine name*
X X
Windows options: create shortcuts option
X X
Windows shortcuts scope
X X
Integrated Windows authentication (IWA)*
X X
Anonymous Web access*
X X
First user display name and account credentials
X X
Object spawner port
X X
Object spawner port bank ports
X X
SAS Application Server: server context*
X X
Workspace server port
X X
Metadata utility workspace server port*
X X
Pooled workspace server port*
X X
Stored process server bridge port
X X
Stored process server MultiBridge connection ports
X X
OLAP server port
X X
SAS/SHARE server port
X X
SAS/CONNECT spawner port
X X
Table server port*
X X
SAS DATA step batch server deployed jobs information
X X
Metadata utility SAS DATA step batch server deployed jobs information*
X X
Operating System Services Scheduling Server port
X X
Deployment Tester port and JUnit JAR file
X X
Web application server automatic configuration*
X X
SAS Remote Services application host name and port
X X
Event broker HTTP port and admin port
X X
Web application server automatic deployment*
X X
SAS Web Application Themes host name, protocol, and port
X X
IP multicast address, UDP port, TTL, authentication token option3*
X X
SAS Web Report Studio enable clustering support
X X
Enable SAS Web Report Studio scheduling*
X X
SAS Web Report Studio in-process scheduling ports
X X
BI Web Services: new Web services deployment method
X X
SAS Content Server repository directory*
X X
SAS Information Delivery Portal samples
X X
Database type for SAS Shared Services
X X
SAS Shared Services database properties (not for SAS Table Server)*
X X
SAS Shared Services JDBC driver jars directory*
X X
WebLogic Web application server node manager host name and port
X X
Web application server administration server name, port, and secured port (WebLogic and WebSphere only)
X X
WebSphere application server deployment manager profile name, node name, and cell name
X X
WebSphere application server deployment manager SOAP port and RMI port
X X
Web application server enable administrative security
X X
WebSphere application server node SOAP port and RMI port
X X
SAS WebParts for Microsoft SharePoint automatic deployment
X X
SAS Flex Application Themes host name, port, and protocol
X X
SAS BI Portlets Portal server
X X
Select products to configure4

X
Authentication domain*

X
Windows options: run as managed scripts or services*

X
Metadata server: server librefs

X
Metadata server name and logical name*

X
Metadata server log file name and invocation options

X
Metadata server foundation repository

X
Metadata server Windows service information

X
SAS BI Web Services authentication method*

X
SAS Spawned Servers account: enable local security policy settings

X
SAS First User account: enable local security policy settings

X
SAS General Servers group

X
SAS Table Server Admins group

X
SAS BI Web Services Users group

X
Common directories for logs, users, and temporary space*

X
Metadata server encryption level and algorithm*

X
Client-side connection profile credentials policy*

X
Object spawner name and host name

X
Object spawner object name in metadata

X
Object spawner invocation options and log filename

X
Object spawner Windows service information

X
SAS Application Server librefs

X
Workspace server name, logical name, and host name

X
Workspace server invocation options and log filename

X
Metadata utility workspace server name, logical name, and host name*

X
Metadata utility workspace server invocation options and log filename

X
Pooled workspace server name, logical name, and host name*

X
Pooled workspace server invocation options and log filename

X
Stored process server name, logical name, and host name

X
Stored process server invocation options and log filename

X
OLAP server name, logical name, schema name, and host name

X
OLAP server invocation options and log filename

X
OLAP server Windows service information

X
SAS/SHARE server name and host name

X
SAS/SHARE server: server component name

X
SAS/SHARE server invocation options, server short name, and log filename

X
SAS/SHARE server Windows service information

X
SAS/CONNECT server name and logical server name

X
SAS/CONNECT server invocation options and log filename

X
SAS/CONNECT spawner name and host name

X
SAS/CONNECT spawner server component name

X
SAS/CONNECT spawner invocation options and log filename

X
SAS/CONNECT spawner Windows service information

X
Table server name and host name*

X
Table server content directory, invocation options and log filename

X
Table server Windows service information

X
SAS DATA step batch server name, logical name, invocation options, and deployed jobs information

X
Metadata utility SAS DATA step batch server name, logical name, invocation options, and deployed jobs information*

X
Operating System Services name and host name

X
Operating System Services Scheduling Server additional SAS invocation options, object server parameter, and log filename

X
Deployment Tester host name

X
Query cache library directory and libref*

X
Output management library information*

X
Web application server administration server protocol and additional JVM options

X
WebSphere application server protocol for deployment manager - node agent protocol and ports

X
Secure JMS resources (WebLogic and JBoss only)

X
Web application server: proxy information*

X
WebSphere application server node additional JVM options*

X
Web application server: configure multiple managed servers*

X
WebLogic Web application server domain path and home directory

X
Web application server: managed server protocol and additional JVM options*

X
Web application server restrictive policy files (WebSphere and JBoss only)

X
SAS Remote Services Windows service information

X
SAS Remote Services JVM settings*

X
SAS Web Report Studio upgrade reports

X
SAS Web Report Studio deployment instance name (WebLogic and WebSphere only)

X
SAS Web Report Studio description and context root

X
SAS BI Dashboard context root

X
SAS BI Dashboard content directory

X
SAS BI Web Services: completion code values, dynamic prompt validation, and execution time-out

X
BI Web Services: new Web services base namespace, temp directory, and delete temp files

X
SAS Information Delivery Portal banner title and menu display options

X
SAS Information Delivery Portal unchallenged access*

X
SAS Information Delivery Portal and SAS Package Viewer context root

X
SAS BI Portlets editing and viewing interfaces

X
SAS BI Portlets and SAS JSR 168 Remote Portlets context roots

X
SAS Flex Application Themes host name, port, and protocol

X
SAS Web Parts for Microsoft SharePoint name, port, directory, and application pool

X
SAS Web Parts for Microsoft SharePoint URLs, installation directory, and user ID*

X
* An asterisk (*) next to a configuration option indicates that more information is available later in this document. See the SAS Deployment Wizard online Help for information about all options.

1 Option available for the server tier on Typical and Custom prompt levels only.

2 Option displays during express for WebLogic dpeloyments only.

3 Option displays during express and typical prompting when the configuration directory and level pre-exists.

4 Option displays during express and typical prompting whenever the middle tier is deployed.

Installing SAS OnlineDoc for the Web

If you choose to install and deploy SAS OnlineDoc for the Web, you must be sure to select the option Create the Enterprise Archive for SAS OnlineDoc for the Web when you run the SAS Deployment Wizard. (This is not the default.)

[Creating the SAS OnlineDoc EAR file]

In the page that follows, you must specify the Web application server that you are using.

[Specifying options for the SAS OnlineDoc EAR file]

After the deployment wizard finishes, check the following logs in the SAS-Home/Documentation/9.2 directory:

Search the logs for the occurrence of "ERROR" (case-sensitive). Note that the logs might state "BUILD SUCCESSFUL" even when errors have occurred.

For more information, see Deploying SAS OnlineDoc Manually for the Web in the SAS Intelligence Platform: Web Application Administration Guide.

Deploy SAS BI Lineage When LSF Scheduler Is on a Separate Machine from the Workspace Server

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

However, an alternative topology could consist of the following:

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

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

  1. When running the SAS Deployment Wizard on machine 1, the metadata and workspace server machine, make sure that you deselect SAS BI Lineage Scheduling Server on the Select Product to Install page.

    For information about how to run the deployment wizard, see Install and Configure SAS Interactively.

    [Select Products to Install]

  2. On the Select Configuration Prompting Level page, select Custom for the prompting level.

    [Select Cofiguration Prompting Level]

  3. On the Select Products to Configure page, deselect the following:

    • Platform Process Manager

    • SAS BI Lineage Scheduling Server

    [Select Products to Configure]

  4. On the SAS Web Report Studio: Scheduling page, deselect Enable Scheduling.

    [SAS Web Report Studio: Scheduling]

  5. Answer the remaining deployment wizard prompts.

    The wizard will install and initially configure machine 1 based on the input that you have provided.

  6. After the wizard completes running on machine 1, 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.2 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 System in the SAS Intelligence Platform: System Administration Guide.

  7. Be sure to restart any servers that you stopped for purposes of creating a backup.

  8. When you are finished completing any manual configuration tasks called for in Instructions.html, and you have made the necessary backups, log on to machine 2 (the BI Lineage Scheduling and LSF Scheduler servers machine) and launch the wizard a second time.

    For information about how to run the deployment wizard, see Install and Configure SAS Interactively.

  9. Use the same deployment plan and again select the Server and Middle Tier machine when prompted for products to install.

    [Select Products to Install]

  10. Select only the following products to install:

    • SAS Management Console

    • SAS BI Lineage Plug-in for SAS Management Console

    • SAS BI Lineage Scheduling Server

    • SAS Intelligence Platform Object Framework (not pictured).

    [SAS Web Report Studio: Scheduling]

  11. On the Select Configuration Prompting Level page, select Custom for the prompting level.

    [Select Cofiguration Prompting Level]

  12. On the Select Products to Configure page, select only the following products:

    • SAS Management Console

    • Platform Process Manager

    • SAS BI Lineage Scheduling Server

    [Select Products to Configure]

  13. Answer the remaining deployment wizard prompts.

    The wizard will install and initially configure machine 2 based on the input that you have provided.

  14. 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/v92 and search for the product name of your Web application server.

  15. When you are finished installing and configuring SAS on each machine called for in your deployment plan, proceed to the section Validate the SAS 9.2 Servers.

Installing SAS Web Parts for Microsoft SharePoint

This section contains the following topics:


What Is SAS Web Parts for Microsoft SharePoint?

SAS Web Parts for Microsoft SharePoint enables you to display SAS BI Dashboard and SAS Analytics in SharePoint pages. SAS Web Parts for Microsoft SharePoint includes the following components:


SAS Web Parts for Microsoft SharePoint Architecture

SAS Web Parts for Microsoft SharePoint consists of the following components:


Automatically Deploy SAS Web Parts for Microsoft SharePoint

This topic provides an overview for how you use the SAS Deployment Wizard to automatically install and configure SAS Web Parts for Microsoft SharePoint. For more information on automatically deploying SAS Web Parts, see Install and Configure SAS Interactively.

Note:   If you want to avoid installing a Java Runtime Environment (JRE), a dependency for the deployment wizard, you can manually deploy SAS Web Parts on a machine that contains a JRE and move the SAS Web Parts deployment to another machine. For more information, see Manually Deploy SAS Web Parts for Microsoft SharePoint and Move It.  [cautionend]

  1. Install the SAS Web Parts and the SAS Web Parts Services.

    When running the SAS Deployment Wizard, select the deployment plan for the SharePoint machine.

    [Select Products to Install page]

    If your SharePoint installation is not in the default location (C:\inetpub\wwwroot\wss\VirtualDirectories\80), you have to select the Custom option for the prompting level in the deployment wizard:

    [Select Configuration Prompting Level page]

    You must also change the installation path in the SharePoint installation directory field:

    [Select Configuration Prompting Level page]

    If you choose the option Automatically Deploy SAS Web Parts for Microsoft SharePoint in the SAS Deployment Wizard, SAS Web Parts is deployed and configured automatically.

    [Automatic Deployment page]

    For more information on automatically deploying SAS Web Parts, see Install and Configure SAS Interactively.

  2. Secure SAS Web Parts for Microsoft SharePoint.

    For more information, see Configure HTTPS Connections for SAS Web Parts for Microsoft SharePoint.

  3. Enable SAS BI Dashboard to access the SharePoint server

    For more information, see the Enabling SAS BI Dashboard to Access the SharePoint Server in the SAS Intelligence Platform: Web Application Administration Guide.


Manually Deploy SAS Web Parts for Microsoft SharePoint and Move It

The SAS deployment and configuration tools rely on a Java Runtime Environment (JRE) that is not a dependency for SAS Web Parts. To avoid installing a JRE on your Microsoft SharePoint server, you can deploy SAS Web Parts on a machine which does contain a JRE and then move your deployment to your SharePoint server later.

To manually deploy SAS Web Parts for Microsoft and then move it to a different machine, follow these steps:

  1. Run the SAS Deployment Wizard on a machine that contains the required JRE.

    For more information, see Install and Configure SAS Interactively.

  2. On the Automatic Deployment page, be sure to deselect the option Automatically Deploy SAS Web Parts for Microsoft SharePoint.

    [Automatic Deployment page]

  3. After the deployment wizard has finished executing, on the machine where you deployed SAS Web Parts, navigate to the Applications sub-folder under the SAS configuration folder.

    For example: C:\SAS\Lev1\Applications.

  4. Under the Applications, copy the sub-folder SAS Web Parts for Microsoft SharePoint to the Microsoft SharePoint server where you want to deploy the SAS Web Parts software.

    An example target location on the SharePoint server is: C:\Program Files\SAS Web Parts for Microsoft SharePoint.

    Note:   Be sure to copy (not move) the sub-folder so that you can continue to apply updates or reconfigure your SAS Web Parts deployment in the future.  [cautionend]

  5. On the Microsoft SharePoint server, run the batch file WebPartsSetup.bat.

    WebPartsSetup.bat resides in the SAS Web Parts for Microsoft SharePoint sub-folder that you copied in the previous step.

    A Windows command prompt window displays that lists the progress and status of the SAS Web Parts installation and configuration.

  6. When prompted, press any key to close the command prompt window.

    The move of SAS Web Parts for Microsoft SharePoint to the new machine is now complete.

  7. The next steps are as follows:


Configure HTTPS Connections for SAS Web Parts for Microsoft SharePoint

The connection between SAS Web Parts and the SAS Web Parts Service requires Hypertext Transfer Protocol Secure (HTTPS) to encrypt the communication. HTTPS uses Secure Socket Layer (SSL) and public key cryptography, which is based on the implementation of a public and private key pair.

To enable HTTPS, an SSL server certificate must be attached to the SAS Web Parts Service. If your organization has a standard procedure for obtaining an SSL server certificate, follow those guidelines and attach that certificate to the service.

Another alternative is to use a self-signed SSL certificate for the SAS Web Parts Service. Because the secure communication occurs only between SAS Web Parts and SAS Web Parts Service, the self-signed certificate needs to be imported only into the Microsoft SharePoint machine's certificate store. Refer to your Microsoft Internet Information Server (IIS) documentation for instructions on how to create and install the self-signed certificate, and complete the following steps:

  1. On the machine hosting the SAS Web Parts Service, use the IIS Manager to create a self-signed certificate and associate it with the SASWebPartsService Web site.

  2. On the SharePoint Server host, import the self-signed certificate into Internet Explorer's Trusted Root Certification Authorities store.

For more information about how to create and install a self-signed certificate, see the following SAS Note:

http://support.sas.com/kb/39/912.html


Configure User Access for SAS Web Parts for Microsoft SharePoint

Users of SAS Web Parts for Microsoft SharePoint can access content in the SAS servers in one of two modes:

Actual identity controls user access to SAS Web Parts explicitly through a SAS metadata identity and the permissions associated with that identity. Users might have permissions in SharePoint to view a page, but they can be denied access to the Web part's content if they are not granted permission to access the dashboard or stored process in SAS metadata. For information about creating metadata identities and assigning permissions, see Users, Groups, and Roles and Getting Started With Permissions in the SAS Intelligence Platform: Security Administration Guide.

Shared identity controls user access to SAS Web Parts through a single identity defined in SAS metadata that all users share. Authentication of the individual user is managed by SharePoint.

CAUTION:
When using shared identity, it is important in SharePoint to grant access to only those users who are allowed to view SAS content.   [cautionend]

To enable shared identity, store the SAS metadata identity in the web.config file.

CAUTION:
In addition to storing a possible shared metadata identity, web.config also contains connection information to the SAS Web Parts service plus an encrypted form of the SAS Trusted User ID and password. As a best practice, we recommend that you limit access to web.config.

The default location for config.web in IIS 6 is: C:\Inetpub\wwwroot\wss\VirtualDirectories\80\web.config. For more information, see your Microsoft Internet Information Server documentation.  [cautionend]

Previous Page | Next Page | Top of Page

Copyright © 2011 by SAS Institute Inc., Cary, NC, USA. All rights reserved.