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

• About Deployment Plans

• Content Repository Considerations

• Installation Order Rules for Multiple Machine Deployments

• IPv6 Windows Machines that Communicate with SAS Foundation Servers

• Interactive Prompting Levels

• Installing SAS OnlineDoc for the Web

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:

• interactively

  a standard method of providing input via fields on wizard pages with a Back and Next button navigation method. You can choose from three levels of configuration prompting: Express (minimum set of prompts), Typical (basic set of prompts), and Custom (all prompts). For more information, see Install and Configure SAS Interactively.

• non-interactively

  a record and playback feature that enables you to automate a SAS installation for use on multiple machines. This feature is designed for large-scale enterprise deployments to prevent users from having to manually provide input on every page each time the SAS Deployment Wizard is run on a machine. For more information, see Automating the SAS Installation on Multiple Machines.

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.

• If a SAS representative created a custom plan for you, an XML file (or a ZIP file containing an XML file) will have been e-mailed to you.

• If your SAS representative recommended that you use a standard plan, you just need the name of the plan that you will use; you will download the actual plan with your SAS custom order (or included in your custom media that is shipped to you.) During the installation, the standard plan will be available from a drop-down list in the SAS installation program.

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:

• SAS Table Server

  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. Setting the table server content directory path is possible only on the SAS Deployment Wizard custom configuration prompting level. For more information, see Interactive Prompting Levels.

• SAS Metadata Server

  We recommend that your metadata repositories reside either on a local file system or a high-performance, high-availability network file system. For more information about metadata repositories, see About SAS Metadata Repositories in the SAS Intelligence Platform: System Administration Guide.

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:

• Always install SAS software on the metadata server machine first.

• Install the SAS application servers (such as workspace or stored process servers) on machines other than the metadata server machine.

• Install the middle tier with SAS Foundation Services (that is, Remote Services).

• Install the middle tier with SAS Web Infrastructure Platform

• Install the middle tier with other Web applications (such as SAS BI Dashboard, SAS Web OLAP Viewer, SAS Web Report Studio, and so on).

• Install software on machines that will host only clients last.

IPv6 Windows Machines that Communicate with SAS Foundation Servers

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

• uses IPv6 (Internet Protocol version 6)

  Note:   For more information, see Designating Ports and Multicast Addresses.  

• runs Windows

• communicates with the SAS Foundation Server tier

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.

   

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.

   

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.  

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.  

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 name	X	X	X
Unrestricted administrator account credentials*	X	X	X
Trusted user account credentials*	X	X	X
E-mail server information*	X	X	X
Anonymous Web user account credentials*	X	X	X
Web application server administration server name, port, and secured port	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 Shared 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 Web OLAP Viewer dependencies	X	X	X
SAS Shared Services 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
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 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
Metadata utility SAS DATA step batch server deployed jobs information*		X	X
Deployment Tester port and JUnit JAR file		X	X
Web application server automatic configuration*		X	X
WebLogic Web application server node manager host name and port		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
Web application server administrator*		X	X
WebSphere application server node SOAP port and RMI port		X	X
Web application server: managed server name and ports*		X	X
Web application server automatic deployment*		X	X
Shared themes for SAS Web applications host name, protocol, and port		X	X
IP multicast address, UDP port, TTL, authentication token option2*		X	X
SAS Remote Services application host name and port		X	X
Event broker HTTP port and admin port		X	X
Enable SAS Web Report Studio scheduling*		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
DataFlux Integration server name and host name		X	X
DataFlux Integration server: server component name		X	X
Select products to configure1			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 invocation options			X
Metadata server foundation repository			X
Metadata server Windows service information			X
SAS BI Web Services authentication method			X
SAS products folder path*			X
SAS BI Web Services authentication method*			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
Metadata utility SAS DATA step batch server name, logical name, and invocation options*			X
Deployment Tester host name			X
Query cache library directory and libref*			X
Output management library information*			X
Web application server administration server host name (WebLogic only)			X
Web application server administration server protocol and additional JVM options			X
WebSphere application server protocol for deployment manager - node agent			X
Secure JMS resources (WebLogic 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			X
BI Web Services for Java completion code values, dynamic prompt validation, and execution time-out			X
SAS Remote Services Windows service information			X
SAS Remote Services JVM settings*			X
SAS Web Report Studio deployment instance name			X
SAS Web Report Studio description, display name, and 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 and temporary directory			X
SAS Web OLAP Viewer deployment instance name			X
SAS Web OLAP Viewer description, display name, and context root			X
SAS Information Delivery Portal banner title			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 displays during express prompting whenever the middle tier is deployed. 2 Option displays during express and typical prompting when the configuration directory and level pre-exists.

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

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

For more information, see Manual Deployment of SAS OnlineDoc for the Web in the SAS Intelligence Platform: Web Application Administration Guide.

Previous Page

|

Next Page

|

Top of Page

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