The SAS Intelligence Platform: Installation and Configuration Guide explains how to install and initially configure the SAS Intelligence Platform.
This document contains new material on the following enhancements and changes to the SAS Intelligence Platform:
|New SAS Deployment Tools|
SAS 9.2 has new deployment tools:
The SAS Download Manager enables you to download your SAS order by using an HTTP connection over the Internet.
The SAS Deployment Wizard combines SAS installation and initial configuration into one wizard, replacing the SAS Software Navigator and the SAS Configuration Wizard.
In the second maintenance release for SAS 9.2, the SAS Update File Cleanup Utility removes backup copies of SAS software that the deployment wizard automatically creates when in update mode.
SAS 9.2 has the following security enhancements:
Fewer operating system accounts are required to run SAS 9.2.
Internal accounts are new to SAS 9.2 and are used by default for some of the required users (such as sastrust and sasadm).
Integrated Windows authentication (IWA) provides single sign-on functionality for Windows desktop users.
You no longer have to manually grant the Windows user right Log on as a batch job to the sassrv user account. The SAS Deployment Wizard automatically does this for you.
On Windows platforms supported by SAS 9.2, the Windows permission Act as part of the operating system is no longer required for SAS server users or the Platform Suite for SAS administrator.
SAS 9.2 has the following deployment enhancements:
Automated, initial SAS configuration eliminates most post-installation manual configuration scripts.
Up-front user inputs enable you to avoid having to monitor the entire wizard session.
Installation includes an automated check for required third-party software.
An electronic product registration feature sends customer installation
data to SAS in order to better assist customers if they call SAS with problems
or questions. Electronic registration is optional and secure, and does not
impact the licensing or use of the software. For more information, see:
The initial SAS installation data file is contained within the SAS Software Depot.
Automated deployment is possible across multiple machines (capture-replay feature).
Space and time estimates are provided for SAS software depot creation.
You can create disc images of your SAS order, so that you can burn to CDs or DVDs at a later time.
On z/OS, you no longer need to define a SAS/C executable library to be program controlled.
In the October 2009 release, the ability to renew your software license for SAS solutions with the SAS Deployment Manager is new.
|SAS Port Changes|
The following SAS port changes have been made:
A SAS Pooled Workspace Server port has been added: 8701.
A SAS Table Server port has been added: 2171.
Three new SAS Object Spawner port banks have been added: 8801, 8811, and 8821.
The SAS Remote Services Application port has been changed from 5099 to 5091.
The SAS Object Spawner load balancing port has been removed.
A metadata utilities SAS Workspace Server port has been added: 8591.
A SAS Deployment Tester Server port has been added: 10021.
In the November 2010 release of SAS 9.2, the following SAS port changes have been made:
The RMI port for the BI Portlets registry has been removed: 9000.
Three UDP ports for SAS Web Report Studio IP Scheduling have been added: 7570, 7571, and 7572.
|Third-Party Software Port Changes|
RMI ports for managed servers have been added: 1099, 1199, (additional managed servers increment by 100).
Listen ports for managed servers have been added: 8080, 8180, (additional managed servers increment by 100).
Secure listen ports for managed servers have been added: 8443, 8543, (additional managed servers increment by 100).
A WebLogic Nodemanager port has been added: 5556.
Secure listen ports for managed servers have been added: 7002, 7102, (additional managed servers increment by 100).
A SOAP port for administrative console has been added: 8879.
SOAP ports for application servers have been added: 8880, 8881, (additional application servers increment by one).
Secure HTTPS port for administrative console has been added: 9043.
A non-secure HTTP port for administrative console has been added: 9060.
Secure HTTPS ports for application server administrative console have been added: 9044, 9045, (additional administrative consoles increment by one).
An RMI port for administrative console has been added: 9809.
RMI ports for application servers have been added: 9811, 9812, (additional application servers increment by one).
In the November 2009 release of SAS 9.2, the IBM WebSphere Portal Server listening port 10040 was added.
|Changes to Groups for Third-Party Software|
In the third maintenance release for SAS 9.2, for UNIX and z/OS it is recommended that the SAS Installer and the WebSphere Application Server installer be in the same operating system group in order to have the necessary permissions for writing to installation directories.
SAS deployment troubleshooting information is now contained in the SAS Intelligence Platform: Installation and Configuration Guide.
In the November 2010 release of SAS 9.2, the following major documentation enhancements were made:
Data direction was documented for SAS and required third-party software ports.
Instructions were added for how to install SAS Web Parts for Microsoft SharePoint.
Instructions were added for how to deploy SAS BI Lineage when LSF Scheduler is on a separate machine from the workspace server.