SAS(R) Intelligence Platform: 9.1.3 to 9.2 Migration Guide

Product	Release
SAS Enterprise Data Integration Server	9.1.3
4.2
SAS Enterprise BI Server	9.1.3
4.2
SAS Migration Utility	9.1.3.14
9.1.3.13
9.1.3.12
9.1.3.11
9.1.3.10
SAS Data Integration Server	9.1.3
4.2
SAS BI Server	9.1.3
4.2
SAS Metadata Server	9.2
SAS Deployment Wizard	9.2
SAS Management Console	9.2

Installing SAS 9.2 and Migrating Your SAS Content

Preparing to Install and to Configure

The topics contained in this section are:

The SAS Deployment Wizard is a cross-platform utility that installs and configures many SAS products. Using a SAS installation data file and a deployment plan for its initial input, the wizard is designed to prompt the customer for all 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: Custom (all prompts), Typical (basic set of prompts), and Express (minimum set of prompts). For more information, see Install and Migrate 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 SAS 9.2 Client Installation Across 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, go to http://support.sas.com/installcenter/plans.

SAS 9.2 Changes that Affect the Deployment Plan

When you work with your SAS representative to develop a custom deployment plan, or if you are choosing among the standard deployment plans available to you in your SAS 9.2 Software Depot, remember that there have been some deployment plan changes between SAS 9.1.3 and SAS 9.2. The following table enumerates these changes:

SAS 9.2 Changes That Affect the Deployment Plan
SAS 9.1.3 Deployment	Change in SAS 9.2 Deployment
Standard deployment plans are not shipped with the SAS Software Depot.	Standard deployment plans are shipped with the SAS Software Depot (and also available at http://support.sas.com/installcenter/plans).
No architectural diagrams and pre-installation checklists that match the standard deployment plans are supplied by SAS.	Architectural diagrams and pre-installation checklists that match the standard deployment plans are supplied by SAS (available in the SAS Software Depot and at http://support.sas.com/installcenter/plans).
The deployment plan used to deploy SAS is not stored in the SAS configuration directory.	The deployment plan used to deploy SAS is stored in the SAS configuration directory (under SAS-config-dir/Levn/Utilities).
SAS Web Infrastructure Kit (WIK) is included.	WIK is now referred to as SAS Web Information Portal (WIP).
Xythos and Apache HTTP WebDAV servers are included.	Xythos and Apache servers are replaced with the SAS Content Server.
Apache Tomcat is included.	Apache Tomcat is replaced with the JBoss Application Server.
A separate deployment plan entry is required for SAS Foundation Services Manager.	No separate entry is required for SAS Foundation Services Manager (part of SAS Management Console).
SAS Query and Reporting Services and SAS Reporting Services are included.	These components are replaced with SAS BI Reporting Services.
SAS Web Report Studio scheduling requires Platform Process Manager.	SAS In-Process Scheduler can be used for SAS Web Report Studio scheduling.
By default, certain deployment plans contain both SAS Web Report Studio and SAS Web Report Viewer.	By default, certain deployment plans contain SAS Web Report Studio only.
The Java Runtime Environment (JRE) is required in deployment plans.	The JRE is no longer included in deployment plans.
SAS Add-In for Microsoft Office is optional in deployment plans (when part of the order).	SAS Add-In for Microsoft Office is required in deployment plans (when part of the order). Note: In the SAS Deployment Wizard, you can deselect SAS Add-In for Microsoft Office to avoid errors when deploying on machines without Microsoft Office.
SAS Configuration Troubleshooter is included.	SAS Configuration Troubleshooter is not yet available in SAS 9.2.
SAS Deployment Tester is optional in deployment plans.	SAS Deployment Tester is required in deployment plans.
SAS Pooled Workspace Server is not available.	SAS Pooled Workspace Server is new in SAS 9.2.
SAS Table Server is not available.	SAS Table Server is new in SAS 9.2.

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. You can set the table server content directory 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 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.

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. These levels are as follows:

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 page is available only on the custom configuration prompting level. [cautionend]

The following table lists all the configuration options that the SAS Deployment Wizard prompts you for based on the wizard prompting level that you choose:

Note: The configuration 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. [cautionend]

Configuration Options By Prompt Level
Configuration Option in the SAS Deployment Wizard	Prompt Level That Displays the Option
Configuration Option in the SAS Deployment Wizard	Express	Typical	Custom
Configuration prompting level^*	X	X	X
Configuration directory and level^*	X	X	X
Migration^*	X	X	X
Unrestricted administrator account credentials^*	X	X	X
Trusted user account credentials^*	X	X	X
SAS spawned server 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 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 bank ports		X	X
Pooled workspace server port^*		X	X
Pooled workspace server dependencies^*		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 option²^*		X	X
SAS Remote Services application host name and port		X	X
Event broker ports		X	X
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 configure¹^*			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 invocation options and log filename			X
SAS Application Server librefs			X
Pooled workspace server name, logical name, and host name^*			X
Pooled workspace server invocation options and log filename			X
Stored process server log filename			X
OLAP server schema name			X
OLAP server invocation options and log filename			X
SAS/SHARE server invocation options, server short name, and log filename			X
SAS/CONNECT server invocation options and log filename			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.

Top of Page