SAS - Checklist

SAS9 Pre-Installation ChecklistInstallation and Configuration Service

Customer Name TAP - CM+DMPlan File Created By Joel BarrosPlan File Created On(yyyy-MM-dd HH:mm:ss.SSS)

2011-12-05 10:33:00.298

Plan NamePlan DescriptionMachine Names Server

Middle TierClients

Offerings SAS Digital Marketing 5.4SAS Campaign Management 5.4

1INSTALLATION AND CONFIGURATION PRE-INSTALLATION CHECKLIST

CONFIDENTIAL - Copyright 2011 SAS Institute Inc. All Rights Reserved.

Pre-Installation ChecklistCopyright Copyright 2010, SAS Institute Inc., Cary, NC, USA. All

rights reserved. Produced in the United States of America.

Disclaimer No part of this publication may be reproduced, stored in aretrieval system, or transmitted, in any form or by any means,electronic, mechanical, photocopying, or otherwise, withoutthe prior written permission of the publisher, SAS Institute Inc.

U.S. GovernmentRestricted Rights Notice

Use, duplication, or disclosure of this software and relateddocumentation by the U.S. government is subject to theAgreement with SAS Institute and the restrictions set forth inFAR 52.227-19, Commercial Computer Software-RestrictedRights (June 1987).

Trademarks andPatents

SAS Institute Inc., SAS Campus Drive, Cary, North Carolina27513.

SAS and all other SAS Institute Inc. product or servicenames are registered trademarks or trademarks of SASInstitute Inc. in the USA and other countries.

indicates USA registration. Other brand and product namesare registered trademarks or trademarks of their respectivecompanies.

Confidentiality This document is provided for informational purposes. SAS'contractual commitments are contained solely in theagreement for professional services executed between SASand the Client. This document is the confidential andproprietary property of SAS Institute Inc. This document maycontain approaches, techniques and other informationproprietary to SAS. This document shall not be disclosed inwhole or in part to third parties without the prior writtenconsent of SAS.



1 Software Order Information

A Software Order E-mail was sent to your site's SAS Representative. The Software Order E-mailcontains important information about obtaining your software and instructions for preparing to installyour software. The SAS Installation Data file (SID file), which contains the license required to runyour SAS Software, is included with the software itself, not the e-mail.

The following information is also contained in the Software Order E-mail. Record the following:

SAS Intelligence Platform documentation is available at: http://support.sas.com/92administration

Electronic Software Delivery and SAS Software Depots

The preferred method for acquiring your SAS software is by using the SAS Electronic SoftwareDelivery (ESD) system. By downloading the software over the Internet, you are able to receive yoursoftware faster. In addition, this helps you and SAS to make changes to protect our environment byeliminating the need to expend resources on a physical shipment. Once the software is downloaded,you have the option of creating physical media on-site if needed. If ESD does not work for you, thenSAS can discuss alternative methods of delivering your software.

For instructions on acquiring your software via the SAS Electronic Software Delivery (ESD) system,see the QuickStart Guide to Your SAS Electronic Software Delivery Installation for PlanningInstallations on Install Center: http://support.sas.com/documentation/installcenter/en/ikqsgplanesd/62324/PDF/default/quickstart.pdf

To begin accessing the SAS Electronic Software Delivery (ESD) system, you will need to downloadthe SAS Download Manager. The SAS Download Manager can be found here: http://support.sas.com/demosdownloads/sysdep_t1.jsp?packageID=000738&jmpflag=N

Once downloaded, the SAS Software Depot will need to be made available to all machines in thearchitecture.See Chapter 3 of the SAS 9.2 Intelligence Platform Installation and Configuration Guidefor additional information about the SAS Software Depot. http://support.sas.com/documentation/cdl/en/biig/60946/HTML/default/abtdep.htm

2 Data Sources

Site Number:SAS Installation Key:Order Number:



Provide the information below for each database repository to which your SAS environment will beconnecting to using SAS/ACCESS products. Include all source repositories of data that reside oneach server separately. If the DBMS is not on a SAS server, then the DBMS client software must beinstalled on the SAS server.

3 Network Configuration

SAS/ACCESS Interface to PC Files Repository/PlatformDBMS Products Required:- Microsoft Office 2007 System Driver: Data Connectivity Components (ACE)- Microsoft Data Access Components (MDAC), Version 2.8 or higherSAS Foundation will automatically install Microsoft Data Access Components (MDAC) and MicrosoftOffice 2007 System Driver components (ACE) when you install SAS/ACCESS Interface to PC Filessoftware.

SAS/ACCESS Interface to PC Files works with the following types of data on Windows systems:- Microsoft Access- Microsoft Excel- Lotus 1-2-3- DBF- JMP- SPSS- Stata- Paradox

This data is made available to SAS on UNIX and Windows 64-bit through a software componentrunning on a Windows workstation or server called the "SAS PC Files Server." The Windows datacan be local to the Windows machine or on a network drive. Your license allows the PC Files Serversoftware to be installed on as many Windows machines as needed. PC Files Server software canrun as a Windows Service. For more information, consult the SAS/ACCESS Interface to PC FilesReference documentation on Install Center:http://support.sas.com/documentation/cdl/en/acpcref/61891/PDF/default/acpcref.pdf1 Files Location2 Versions3 Hostname of the PC File Server4 Port of the PC File Server Default=8621 (TCP port type, Incoming data direction)5 Test ID \ Password6 Availability of the tables - can these

tables be accessed at any time thatwe choose?

7 DBMS Location\Path\Home directory8 Who is it in the organization that

understands the technical aspects ofthis data?



4 Logistics and Security

Network Configuration1 Is the SAS Software Depot

accessible from each machine thatwill be used for the SAS installation?Or has media been created, anddoes each system have theappropriate media drive attached oraccessible (DVD, CD or mainframecartridge)?

2 Will the SAS installer have remoteaccess to the servers?

3 Do all the hardware componentsreside within the same domain?

4 What is the bandwidth betweenserver and client accessingremotely?

5 A workspace and a workstation isrequired for each installer. Describethe workstation, its method of accessto the server(s) (terminal emulators,etc.) and the location of theworkspace in which it resides.

6 Will the SAS installer have Internetaccess from the workstation? Arethere any restrictions for browsers orFTP usage that we should be awareof?

7 Will the SAS installer have atelephone available at thisworkstation? Or, is the use of cellphones and other portablecommunication devices allowed inthis area?

Logistics and Security(For use if SAS or a consulting organization will be performing this installation.)

1 What is the address where theinstallation will occur? Pleaseprovide the street address, city, etc.

2 Provide any directions needed tolocate the facility and access it.

3 Who will be the SAS installer'scontact to enter the facility?

4 Do you have an airportrecommendation?

5 Do you have a hotelrecommendation?

6 What is the dress code for yourfacility?

7 Please inform us of any specialtravel policies you may have that weneed to comply with.



--

-

-

-

-

-

-

-

-

5 SAS I/O, File and Disk Characteristics

Before you can start designing the file systems that will be used by the SAS application, a thoroughtechnical assessment is required to understand how SAS will be used. In light of doing a thoroughtechnical assessment, we will give you some general guidelines on how to configure the various filesystems.

5.1 General SAS I/O CharacteristicsSAS usually does large, blocked I/O, especially when doing analytical tasks.SAS I/O does not pre-allocate storage.SAS data files are standard operating system files that are block-based and must create extentsas the data file grows.SAS generates a large number of temporary files of different sizes.SAS does not read or write directly from/to disks, we ask the operating system to fetch the datavia the operating system's file cache. Note that this can cause some strain on the memory in thecomputer.

5.2 Guidelines for Setting up SAS File SystemsThe main concern when setting up a file system is to ensure that SAS gets the sustained I/Obandwidth needed to complete the SAS jobs in the timeframe required by the SAS users.

The I/O rate for SAS data varies by process.With the large, block I/O that SAS does, the I/O throughput rate is very important to SAS. The I/Othroughput rate for SAS depends on what SAS tasks are being done: For most Extract,Transform, and Load (ETL) processes, 50-75MB/second of I/O throughput for each file systemSAS is using is required per SAS session.

For end-user exploitation, 15-25MB/second per user per file system is required. However, forheavy SAS users, 50-75MB/second per user per file system is required.Disks allocated to SAS working files - including "SASWORK" - require 15-25MB/second peruser for most SAS processes with heavy SAS users requiring 50-75MB/second per user.Disks allocated for SAS utility files for SAS threaded procedures and OLAP processing -"UTILLOC" - require 50-75MB/second per user.

Make sure that you use the best file system for your operating system that follows the types of I/Oyour SAS tasks will be doing. If you are doing large sequential I/O, then the file systems listed beloware adequate.

Logistics and Security(For use if SAS or a consulting organization will be performing this installation.)

8 Please inform us of any specialsecurity clearance requirements theSAS installer needs to comply with inorder to gain access to your facility.



--

-

-

-

-

-

-

-

-

-

-

-

-

-

-

Solaris 9 or 10 - VxFSSolaris 10 - ZFSAIX - JFS2HP-UX - JFSLinux X64 - XFSWindows - NTFS *These guidelines are not applicable for z/OS.

Make sure that you turn on Read-Ahead and Write-Behinds/Write-Through on and enable dynamicmulti-pathing to spread I/O over multiple fiber channels. These are needed to help the operatingsystem's file cache fetch the data faster from disk.

The recommended RAID levels for the primary file systems required by SAS are listed below. Notethat you should use the one that best fits your company's IT standards, the availability requirementsof your data, and what is available on your external storage array device.

Root operating system - RAID1SAS executables - RAID1SAS data - RAID5, RAID10 or RAID0Disks allocated to SAS working files - "SASWORK" and "Web Report Studio Query Cache" -RAID5, RAID10, or RAID0Disks allocated for SAS utility files for SAS threaded procedures and OLAP processing -"UTILLOC" - RAID5, RAID10 or RAID0

A best practices paper regarding how SAS does I/O and general disk usage is available for yourreview at: http://support.sas.com/rnd/papers/sgf07/sgf2007-iosubsystem.pdf

6 Anti-Virus and/or Firewall Software

Before installing your SAS software, it is recommended that you close your anti-virus and firewallsoftware. Some anti-virus and/or firewall configurations can prevent an application from installingsuccessfully.

If you are unable to close the anti-virus or firewall software, make sure that your configuration allowsyou to install software and to update the registry. If your SAS installation fails and you havemandatory anti-virus or firewall software running, check with your system administrator.

Following the deployment on the servers, the antivirus configuration should be modified to excludethe SAS WORK location, as well as all files with the following extensions:

.lck

.sd2

.sc2

.SPDS

.sas*



- .utl

This would be performed by an administrator and can prevent performance issues and file lockingerrors.



Server: Pre-Installation Checklist

Server, Part 1: Architecture Details

SAS Application Server

The SAS Application Server is where the bulk of the SAS processing occurs. The SAS workspace,stored process, and OLAP servers typically run on this machine, although the OLAP server can beinstalled on a separate machine if desired. A SAS license file (SID file) is required for this server.

SAS Metadata Server

The SAS Metadata Server is one of the key technology applications delivered with the SAS9 platform.Its ability to surface metadata from one or more repositories and serve it to applications via the SASOpen Metadata Architecture provides the ability to gather and store data in multiple formats andlocations without losing the ability to derive consistent business intelligence. The metadata serverprovides a centralized and easily managed system for consistent enterprise data repositories so youwill always know where your data is located, what it consists of, and how it has been modified. Thisprovides an auditable, repeatable, and secure environment from which to derive businessintelligence. The metadata server provides a foundation for greater metadata sharing to support amore advanced and collaborative environment. Metadata usage is consistent and accurate foranalysis, resulting in reduced errors in decision making for your report consumers.

It should be noted that the metadata server is an "in-memory" process. That is, all queried andupdated metadata will be held in memory by the server. Many factors determine the volume ofresources that the metadata server will require to operate efficiently and effectively. Although themetadata server can reside on a separate machine or it may operate on a machine with otherservers, determining optimal configuration requires careful planning and is typically done during thearchitecture phase of a project. There is no additional SAS software licensing for the placement of themetadata server on a separate machine of equal or smaller size than the SAS Server, as yourexisting license includes this, however platform specific software may need to be shipped. To put themetadata server on a separate machine, it needs to be specified as a separate machine in the order.

X Metadata ServerX SAS Application Server

Remote ServicesMiddle Tier

X Clients-AdministrationX Clients-End User

Clients-Analytics



Clients-Administration

Clients-Administration machines host SAS Management Console and its various plug-ins.

Clients-End User

Clients-End User machines host client interfaces such as SAS Enterprise Guide, SAS InformationMap Studio, SAS Add-in for Microsoft Office, and SAS Data Integration Studio.

Server, Part 2: Machine Specifications and Details

System Infrastructure Specification1 Fully Qualified Domain Name (DNS):2 IP Address:3 DNS Alias Name:4 Physical Location:5 Access Method (Console or Remote):6 Server Specifications6.1 Vendor:6.2 Type:6.3 Model:6.4 Operating System:6.5 OS Version:6.6 Disk:6.7 CPUs (Number, Type and Speed):6.8 RAM:6.9 Network:6.10 I/O Paths:6.11 Deployment:6.12 Authentication:7 Existing applications and concurrent

processes running:8 E-mail (SMTP) Server Host Name:



Server, Part 3: Pre-Installation Accounts and Groups

If you are migrating from 9.1.3 to 9.2, and you wish to continue using external IDs for your useraccounts, you must ensure that these IDs are set up on the corresponding machines in your 9.2environment. See the following page of the 9.1.3 to 9.2 Migration Guide for details: http://support.sas.com/documentation/cdl/en/bimig/61696/HTML/default/mig213.htm

Internal User AccountsCertain user accounts (internal to the SAS platform) will be created during the deployment process.Please note any password requirements or policies that you may have. The default accounts aresasadm@saspw, sastrust@saspw, and webanon@saspw.

External User Accounts on Windows

System Infrastructure Specification9 Multicast Address:

1. IPv4 - *must* be in the range224.0.0.0 - 239.255.255.255. In alllikelihood *should* be in the range239.0.0.0- 239.255.255.255. This latterrange is the locally administered blockscoped by RFC 3171.

2. IPv6 - *must* have the prefix ff00::/8.In all likelihood, the prefix *should* beff14::/16. This latter prefix is the locallyadministered block scoped by RFC4291.

10 Server Administrator Contact10.1 Name:10.2 Phone:10.3 E-mail:

File System Specification1 Path to SAS Software Depot or media

drive:2 SAS Installation Directory:3 SAS Configuration Directory:4 SAS Data Directory:5 SAS Work Directory or Unit:6 Web Report Studio Query Cache

Directory:7 Other:8 Other:



1.2.

-

-

-

3.

Groups on WindowsTo deploy SAS on Windows, the user must have certain local user rights on the machine hosting theserver. These rights are required before the user can start a process for a stored process server, apooled workspace server, or a standard workspace server. One suggestion for giving a user theserights is to create a group, add users to the group, and then assign the rights to the group.

To set up a group, complete these steps:

Create a SAS server users group. This can be a local group or a group with domain scope.Add the following users to the group:

SAS Spawned Servers account (automatically assigned 'Log on as a batch job' by the SASDeployment Wizard)SAS First User (optional account, automatically assigned 'Log on as a batch job' by the SASDeployment Wizard)any other external users that need to access a standard workspace server

Finally, grant the user right 'Log on as a batch job' to the group. Unless Integrated WindowsAuthentication (IWA) is implemented, this user right is required for any other external user whowants to access to a standard workspace server). For information about setting local user rights,see your Microsoft Windows documentation. If the users in the group need that right on morethan one Windows machine, the right needs to be assigned specifically on each machine.

Purpose Required Rights RecommendedUser ID

Actual User ID

SAS Installer Administrator rights (user must be alocal administrator on the machineand/or a member of the administratorsgroup)

my-domain\installer-ID*

SAS SpawnedServers Account

Log on as a batch job (can be assignedby the SAS Deployment Wizard)

my-domain\sassrv

SAS First User(optional)

Log on as a batch job (can be assignedby the SAS Deployment Wizard)

my-domain\sasdemo

* The user ID should be available in the long term for future SAS maintenance.

Purpose Group Members RecommendedGroup Name

Actual Group

Suggested method for assigning the'Log on as a batch job' user right to theSAS Spawned Servers account for thestored process server and pooledworkspace server.

SAS SpawnedServers Account

SAS Server Users

Suggested method for assigning the'Log on as a batch job' user right to theSAS First User and any other standardworkspace server users.

SAS First UserAny other users*

SAS Server Users

* Unless Integrated Windows Authentication (IWA) is implemented, add any other any external usersaccessing standard workspace servers.



Server, Part 4: Port Availability

The SAS servers and spawners in your system will use certain ports by default. The table below liststhe default ports and provides space to record alternate port numbers if necessary. If any of theseports are unavailable, alternate ports should be reserved. A range of port numbers may be displayedif multiple levels are available (for example, a port number ending in "1" represents Lev1 or PROD).

Port Name Port Description Default PortNumbers

(TCP, unlessnoted

otherwise)

PortType

DataDirection

Alternate PortNumber if Default

Port Number isUnavailable

mail Mail Server 25 TCP Outboundsastable SAS Table Server 2170 - 2179 TCP Inboundsasconnect SAS/CONNECT Server and

Spawner7550 - 7559 TCP Both

sasmetaconn Metadata UtilitySAS/CONNECT SpawnerNote that you would not runa productionSAS/CONNECT Spawnerat the same time as theUtility SAS/CONNECTSpawner so using the sameport for both is acceptable.

7550 - 7559 TCP Both

ossched Operating System Servicesscheduler

8450 - 8459 TCP Inbound

sasshare SAS/SHARE Server 8550 - 8559 TCP Inboundsasmeta SAS Metadata Server 8560 - 8569 TCP Bothsasmetawork SAS Metadata Utility

Workspace ServerNote: In SAS 9.2, two ormore workspace serverscan share the same porteven if they are running atthe same time.


sasobjspawno

SAS Object Spawner -Operator Port


saspool1 SAS Object Spawner:pooled workspace serverport bank 1






saswork SAS Workspace ServerNote: In SAS 9.2, two ormore workspace serverscan share the same porteven if they are running atthe same time.




Server, Part 5: Third Party Software


(TCP, unlessnoted

otherwise)

PortType

DataDirection



sassp SAS Stored ProcessServer: Bridge connection


sasspmb1 SAS Stored ProcessServer: load balancingconnection 1 (MultiBridge)






saspworksp SAS Pooled WorkspaceServer


sasdepltsrv SAS Deployment Tester -Server

10020 -10029

TCP Inbound

sasmulticast Multicast PortA multicast groupcommunications protocol isused to communicateconfiguration among middletier SAS applications in asingle SAS deployment (theset of applicationsconnected to the same SASMetadata Server).Therefore, the combinationof multicast IP address andmulticast UDP port shouldbe different for each SASdeployment and alsodifferent from those used byother multicast applicationsat your site.

The multicast port defaultsto the same value as themetadata server port, butthere is no conflict since itis a UDP port vs. a TCPport. Extra care should betaken in the assignment ofthis port, due to the SASDeployment Wizard'sinability to detect usageconflicts with the enteredvalue.

8560 - 8569 UDP Both

RDBMS client for SAS/ACCESSEnsure that the required DBMS client software is installed on the SAS application server ifSAS/ACCESS features are to be used.



1.2.

3.-

-

Server, Part 6: Special Installation Instructions for Machines Communicating toSAS Foundation Servers using IPv6 Addresses

You must perform the following manual steps if this Windows machine will communicate to a SASserver solely using IPv6 addressing.

Run the SAS Deployment Wizard in "Install" mode.Copy the sas.nioc.channels.jar from your SAS Software Depot (located in the third_party\ipv6\directory) to the extension directory of the JRE being used(e.g., C:\ProgramFiles\Java\jre1.5.0_12\lib\ext).This copy can be done anytime after the JRE is installed.Edit the deploywiz.ini file to point to the installed JRE.

Locate the alt_sku for deploywiz.In the 9.2 Maintenance 3 release, this would be the followingrelative path in the SAS Software Depot: .\products\deploywiz__92380__prt__xx__sp0__1 Edit the deploywiz.ini file and locate the corresponding platform in the file. It will looksomething like this: [win] copy1=setup.dat copy2=< DEPLOYWIZ_PRT_PKG>/deploywiz.exe copy3=< DEPLOYWIZ_PRT_PKG>/deploywiz.ini copy4=< DEPLOYWIZ_PRT_PKG>/deploywiz copy5=products/securejava__92120__prt__xx__sp0__1/sas.rutil.jar copy6=products/securejava__92120__prt__xx__sp0__1/sas.rutil.nls.jar

JUnitDescription Default Value Actual Value

JUnit jar file location N/AProduct Version 4.0 or greaterJUnit is required for validation of some components. Without JUnit these products may operateproperly but you will not be able to validate them using Deployment Tester. See the third partysoftware support page for details:http://support.sas.com/resources/thirdpartysupport/

Web BrowserPlatform Supported Browser

Windows XP Pro/Vista 32-bit and Windows XPPro 64-bit

Firefox 2.0 (or higher)Internet Explorer 7 (or higher)

Windows 7 32-bit and x64 Firefox 3.0 (or higher)Internet Explorer 8 32-bit compatibility (or higher)

Linux 32-bit, x64 Firefox 2.0, Firefox 3.0 (or higher)Note: A Web browser is required on each machine that will access SAS Web content. For moreinformation, view the third party software support page:http://support.sas.com/resources/thirdpartysupport/



-4.

copy7=< JAVARUNTIME_WIN_PKG>/lib jre=< JAVARUNTIME_WIN_PKG>/jre.exe launch=< DEPLOYWIZ_PRT_PKG>/deploywiz.exe launchercmd=../../< JAVARUNTIME_WIN_PKG>/bin/java launcherargs=-Xmx512M -jar deploywiz/setup.jar Change the launchercmd value to point to the installed JRE that includes the two additional.jar files. Something like this: launchercmd=C:\Program Files\Java\jre1.5.0_12\bin\java

Run the SAS Deployment Wizard in "Configure" mode to complete the deployment process.

Server, Part 7: Encoding

By default, your SAS Software will dynamically use the locale initiated by the language you use withyour SAS client application and determine the encoding used for reading and writing SAS data ortranscoding during data transfer. In cases where you cant make sure that all SAS users will use theirclient application in the same language, we recommend to set the appropriate encoding for your siteand make the required changes to the sasv9_usermods.cfg files as appropriate. For more informationon locales and encoding, consult the National Language Support Reference Guide: http://support.sas.com/documentation/cdl/en/nlsref/61893/PDF/default/nlsref.pdf

Server, Part 8: Minimum System Requirements

Server, Part 8.1: Operating System Alert Notes

http://support.sas.com/kb/?ct=51000&qm=3&la=en&qt=contenttype:%22Problem+Note%22&col=suppprd

Server, Part 8.2: Operating System Minimum Requirements

Go to Install Center and specify your operating system: http://support.sas.com/idsearch?ct=200000



Middle Tier: Pre-Installation Checklist

Middle Tier, Part 1: Architecture Details

Remote Services

Remote Services is a server within the SAS Platform. Its role is to coordinate among SAS Javaapplications in support of their communication with the SAS Metadata Server.

SAS Middle Tier

The middle tier handles all the Web traffic from browser-based applications such as SAS Web ReportStudio and the SAS Information Delivery Portal. In addition to these SAS products, third-partysoftware is installed on this machine to serve as the Web application server for the Java-basedapplications. No separate license file (SID file) is required for this server. SAS recommends thismachine to be separated from the metadata server and SAS application server machines for securitypurposes, typically so that a firewall can be placed between users accessing the Web server andsensitive data and metadata residing on the other servers.

You cannot use the "_" character in the host name or DNS alias of the middle tier machine. Otherunreserved characters (including !~'()*) in the host name can also cause problems.



Middle Tier, Part 2: Machine Specifications and Details

Metadata ServerSAS Application Server

X Remote ServicesX Middle TierX Clients-Administration

Clients-End UserClients-Analytics

System Infrastructure Specification1 Fully Qualified Domain Name (DNS):2 IP Address:3 # of Network Cards (per server):



Multi Network Interface Card (NIC) Specific Requirements

SAS Note SN-035086 indicates that if the value chosen by JGroups for the SAS Remote Servicesapplication and the value chosen by the Web application server for the SAS mid-tier applications donot match, the communication protocol used by JGroups might not function correctly. This can be dueto multiple NIC cards, or being logged into a VPN. To resolve this problem, set the JVM option to

System Infrastructure Specification4 DNS Alias Name:5 Physical Location:6 Access Method (Console or Remote):7 Server Specifications7.1 Vendor:7.2 Type:7.3 Model:7.4 Operating System:7.5 OS Version:7.6 Disk:7.7 CPUs (Number, Type and Speed):7.8 RAM:7.9 Network:7.10 I/O Paths:7.11 Deployment:7.12 Authentication:8 Existing applications and concurrent

processes running:9 SAS Shared Services database:

For additional Shared Servicesdocumentation, go to:http://support.sas.com/resources/thirdpartysupport/v92m3/appservers/SharedServicesAlternativeDatabase.pdf

Choose one:__DB2 v8 or higher__MS SQL 2008 or higher__MySQL 5.1 or higher__Oracle 10g or higher__PostgreSQL 8.4 or higher__SAS Table Server

9.1 If the SAS Shared Services database you chose above is not SAS Table Server, then providethe following information:

9.2 Database host:9.3 Database port:9.4 Database name:9.5 Database user ID:9.6 Database password:9.7 Directory containing JDBC .jar files

(directory should preferably contain allrequired .jar files for the JDBC driverand no additional .jar files):

10 Server Administrator Contact10.1 Name:10.2 Phone:10.3 E-mail:



--

ensure that the Web application server and the JGroups software use the same bind address. Tolearn more about setting JVM options see the SAS Note: http://support.sas.com/kb/35/086.html

Increase per process limit on open file descriptors

It is recommended that you increase the per process limit on the number of open file descriptors onUNIX platforms to at least 10240. This is required when running Java 5 to allow the opening of classfiles within the various Web applications. Before modifying any system resource settings, determinethe current hard limit on file descriptors by running the "ulimit" shell command.

An example command submitted on Solaris where the number of file descriptors needs to beincreased: $> ulimit -Hn 1024An example command submitted on Solaris where the number of file descriptors does not needto be increased: $> ulimit -Hn unlimited

Middle Tier, Part 3: Pre-Installation Accounts and Groups


drive:2 SAS Installation Directory:3 SAS Configuration Directory:

Permissions within the configurationdirectory are set correctly for mostcommonuse cases. These permissions take intoaccount the need to provide security tosensitive data, and secruity credentialsstored within the configuration directory.However, the diretories that are parentdirectories of the configuration directoryshould not block read or search accessto the configuration directory. Everyoneshould be able to read and search thecontents of the top level configurationdirectory as the individual files anddirectories located therein are protectedat lower directory and individual filelevels.

4 SAS Data Directory:5 Other:6 Other:





External User Accounts on UNIX

The SAS Deployment Wizard requires that you supply the root password during configuration.Certain SAS products and features employ functionality that requires SAS to check user IDauthentication and file access authorizations. This in turn necessitates that certain files within yourSAS installation have setuid permissions and be owned by root.

Middle Tier, Part 4: Port Availability

The SAS servers and spawners in your system will use certain ports by default. The table below liststhe default ports and provides space to record alternate port numbers if necessary. If any of theseports are unavailable, alternate ports should be reserved. A range of port numbers may be displayedif multiple levels are available (for example, a port number ending in "1" represents Lev1 or PROD).

On UNIX, we recommend that you document each third-party port that you reserve in the followingstandard locations on each machine: /etc/services. This practice will help to avoid port conflicts on theaffected machines.


Actual User ID

SAS Installer You must have a password for thisaccount. Sudo access is not sufficient.

sas*

* Do not use root.


(TCP, unlessnoted

otherwise)

PortType

DataDirection



sasrmi SAS Remote Servicesapplication


saseventadm Event Broker Admin Port 6050 - 6059 TCP Inbound




(TCP, unlessnoted

otherwise)

PortType

DataDirection



saswrsudp1 Web Report Studio IPScheduling UDP Port 1

7570 UDP Both


7571 UDP Both


7572 UDP Both

saseventhttp Event Broker HTTP Port 8110 - 8119 TCP Inboundsasdepltsrv SAS Deployment Tester -

Server10020 -10029

TCP Inbound

saswashttp WebSphere HTTP ServerPort

9080 TCP Inbound

saswashttps WebSphere HTTPS ServerPort

9443 TCP Inbound

saswasrmi WebSphere RMI Port 9811 TCP Bothsaswassoap WebSphere SOAP Port 8880 TCP Bothsaswashttpa WebSphere HTTP Admin

Server Port9061 TCP Inbound

saswashttpsa

WebSphere HTTPS AdminServer Port

9044 TCP Inbound

sasdmgrsoap

Deployment ManagerSOAP Port

8879 TCP Both

sasdmgrrmi Deployment Manager RMIPort

9809 TCP Both

sasdmgrhttp Deployment ManagerHTTP Port

9060 TCP Inbound

sasdmgrhttps

Deployment ManagerHTTPS Port

9043 TCP Inbound

sasnodesoap Node Agent SOAP Port 8878 TCP Bothsasnodermi Node Agent RMI Port 2810 TCP Bothsaswashttp1 WebSphere HTTP Server 1

Port9080 TCP Inbound

saswashttps1

WebSphere HTTPS Server1 Port

9443 TCP Inbound

saswasrmi1 WebSphere RMI 1 Port 9811 TCP Bothsaswassoap1

WebSphere SOAP 1 Port 8880 TCP Both

saswashttpa1

WebSphere HTTP AdminServer 1 Port

9061 TCP Inbound

saswashttpsa1

WebSphere HTTPS AdminServer 1 Port

9044 TCP Inbound

saswashttp2 WebSphere HTTP Server 2Port

9081 TCP Inbound

saswashttps2


9444 TCP Inbound



saswashttpa2


9062 TCP Inbound



Middle Tier, Part 5: Third Party Software


(TCP, unlessnoted

otherwise)

PortType

DataDirection



saswashttpsa2


9045 TCP Inbound

saswashttp6 WebSphere HTTP Server 6Port

9085 TCP Inbound

saswashttps6


9448 TCP Inbound



saswashttpa6


9066 TCP Inbound

saswashttpsa6


9049 TCP Inbound

IBM WebSphere Application Server Network DeploymentDescription Default Value Actual Value

Installation Directory N/AProduct Version 6.1Required Maintenance - Install WebSphere Application Server V6.1 Fixpack 21 to bring

WAS 6.1 to 6.1.0.21Notes: Install the Web server making use of the manufacturer's distribution package, apply anynecessary hotfixes, and verify the Web server's operation. The Web server should be stoppedbefore deploying your SAS software. For more information, view the third party software supportpage: http://support.sas.com/resources/thirdpartysupport/

IBM recommends installing as root.

If you wish to deploy using WebSphere Application Server Base instead of Network Deployment,view the following document for instructions:http://support.sas.com/resources/thirdpartysupport/v92/appservers/ConfiguringWASBase.pdf

JUnitDescription Default Value Actual Value

JUnit jar file location N/AProduct Version 4.0 or greaterJUnit is required for validation of some components. Without JUnit these products may operateproperly but you will not be able to validate them using Deployment Tester. See the third partysoftware support page for details:http://support.sas.com/resources/thirdpartysupport/



Middle Tier, Part 6: UNIX Windowing Environments

If you are installing your software on a UNIX system, make sure that a windowing environment --such as X11 -- is installed. The SAS Deployment Wizard has a graphical user interface that requiresit.

Any PCs accessing UNIX via X-Windows with a terminal emulator require X-Windows serveremulator software to be installed on the PC. Middle Tier, Part 7: Minimum System Requirements

Middle Tier, Part 7.1: Operating System Alert Notes


Middle Tier, Part 7.2: Operating System Minimum Requirements









Clients: Pre-Installation Checklist

Clients, Part 1: Architecture Details



Clients-End User

Clients-End User machines host client interfaces such as SAS Enterprise Guide, SAS InformationMap Studio, SAS Add-in for Microsoft Office, and SAS Data Integration Studio.

Clients, Part 2: Machine Specifications and Details

Metadata ServerSAS Application ServerRemote ServicesMiddle Tier

X Clients-AdministrationX Clients-End User

Clients-Analytics

System Infrastructure Specification1 Fully Qualified Domain Name (DNS):2 IP Address:3 DNS Alias Name:4 Physical Location:5 Access Method (Console or Remote):6 Server Specifications6.1 Vendor:6.2 Type:6.3 Model:6.4 Operating System:6.5 OS Version:6.6 Disk:6.7 CPUs (Number, Type and Speed):6.8 RAM:6.9 Network:6.10 I/O Paths:



Clients, Part 3: Pre-Installation Accounts and Groups



External User Accounts on Windows

System Infrastructure Specification6.11 Deployment:6.12 Authentication:7 Existing applications and concurrent

processes running:8 Server Administrator Contact8.1 Name:8.2 Phone:8.3 E-mail:


drive:2 SAS Installation Directory:3 SAS Configuration Directory:4 SAS Data Directory:5 Other:6 Other:


Actual User ID

SAS Installer Administrator rights (user must be alocal administrator on the machineand/or a member of the administratorsgroup)

my-domain\installer-ID*

* The user ID should be available in the long term for future SAS maintenance.



1.2.

3.-

-

Clients, Part 4: Third Party Software

Clients, Part 5: Special Installation Instructions for Machines Communicating toSAS Foundation Servers using IPv6 Addresses

You must perform the following manual steps if this Windows machine will communicate to a SASserver solely using IPv6 addressing.

Run the SAS Deployment Wizard in "Install" mode.Copy the sas.nioc.channels.jar from your SAS Software Depot (located in the third_party\ipv6\directory) to the extension directory of the JRE being used(e.g., C:\ProgramFiles\Java\jre1.5.0_12\lib\ext).This copy can be done anytime after the JRE is installed.Edit the deploywiz.ini file to point to the installed JRE.

Locate the alt_sku for deploywiz.In the 9.2 Maintenance 3 release, this would be the followingrelative path in the SAS Software Depot: .\products\deploywiz__92380__prt__xx__sp0__1 Edit the deploywiz.ini file and locate the corresponding platform in the file. It will looksomething like this: [win] copy1=setup.dat copy2=< DEPLOYWIZ_PRT_PKG>/deploywiz.exe copy3=< DEPLOYWIZ_PRT_PKG>/deploywiz.ini copy4=< DEPLOYWIZ_PRT_PKG>/deploywiz copy5=products/securejava__92120__prt__xx__sp0__1/sas.rutil.jar copy6=products/securejava__92120__prt__xx__sp0__1/sas.rutil.nls.jar

Microsoft OfficeDescription Default Value Actual Value

Product Version Microsoft Office 2000 ServicePack 3 (minimum)

Note: You must close all Microsoft Office programs before installing your SAS software.








-4.

copy7=< JAVARUNTIME_WIN_PKG>/lib jre=< JAVARUNTIME_WIN_PKG>/jre.exe launch=< DEPLOYWIZ_PRT_PKG>/deploywiz.exe launchercmd=../../< JAVARUNTIME_WIN_PKG>/bin/java launcherargs=-Xmx512M -jar deploywiz/setup.jar Change the launchercmd value to point to the installed JRE that includes the two additional.jar files. Something like this: launchercmd=C:\Program Files\Java\jre1.5.0_12\bin\java

Run the SAS Deployment Wizard in "Configure" mode to complete the deployment process.

Clients, Part 6: Minimum System Requirements

Clients, Part 6.1: Operating System Alert Notes


Clients, Part 6.2: Operating System Minimum Requirements




__field__1: 602396__field__2: __field__3: 99FQ5F__field__4: __field__5: __field__6: __field__7: __field__8: __field__9: __field__10: __field__11: __field__12: __field__13: __field__14: __field__15: __field__16: __field__17: __field__18: __field__19: __field__20: __field__21: __field__22: __field__23: __field__24: __field__25: __field__26: __field__27: __field__28: __field__29: __field__30: __field__31: __field__32: __field__33: __field__34: Microsoft Windows for x64__field__35: __field__36: __field__37: __field__38: __field__39: __field__40: __field__41: __field__42: __field__43: __field__44: __field__45: __field__46: __field__47: __field__48: __field__49: __field__50: __field__51: __field__52: __field__53: __field__54: __field__55: __field__56: __field__57: __field__58: __field__59: __field__60: __field__61: __field__62: __field__63: __field__64: __field__65: __field__66: __field__67: __field__68: __field__69: __field__70: __field__71: __field__72: __field__73: __field__74: __field__75: __field__76: __field__77: __field__78: __field__79: __field__80: __field__81: __field__82: __field__83: __field__84: __field__85: __field__86: __field__87: __field__88: __field__89: __field__90: __field__91: __field__92: 64-bit Enabled AIX__field__93: __field__94: __field__95: __field__96: __field__97: __field__98: __field__99: __field__100: __field__101: __field__102: __field__103: __field__104: __field__105: __field__106: __field__107: __field__108: __field__109: __field__110: __field__111: __field__112: __field__113: __field__114: __field__115: __field__116: __field__117: __field__118: __field__119: __field__120: __field__121: __field__122: __field__123: __field__124: __field__125: __field__126: __field__127: __field__128: __field__129: __field__130: __field__131: __field__132: __field__133: __field__134: __field__135: __field__136: __field__137: __field__138: __field__139: __field__140: __field__141: __field__142: __field__143: __field__144: __field__145: __field__146: __field__147: __field__148: __field__149: __field__150: __field__151: __field__152: __field__153: __field__154: __field__155: __field__156: __field__157: __field__158: __field__159: __field__160: __field__161: __field__162: __field__163: __field__164: __field__165: Windows__field__166: __field__167: __field__168: __field__169: __field__170: __field__171: __field__172: __field__173: __field__174: __field__175: __field__176: __field__177: __field__178: __field__179: __field__180: __field__181: __field__182: __field__183: __field__184: __field__185:

Documents

SAS - Checklist