SAS 9.2 Intelligence Platform: Installation and Configuration Guide

Loading...

®

SAS 9.2 Intelligence Platform Installation and Configuration Guide

The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2009. SAS ® 9.2 Intelligence Platform: Installation and Configuration Guide. Cary, NC: SAS Institute Inc. SAS® 9.2 Intelligence Platform: Installation and Configuration Guide Copyright © 2009, SAS Institute Inc., Cary, NC, USA ISBN 978–1–59994–329–9 All rights reserved. Produced in the United States of America. For a hard-copy book: No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, or otherwise, without the prior written permission of the publisher, SAS Institute Inc. For a Web download or e-book: Your use of this publication shall be governed by the terms established by the vendor at the time you acquire this publication. U.S. Government Restricted Rights Notice. Use, duplication, or disclosure of this software and related documentation by the U.S. government is subject to the Agreement with SAS Institute and the restrictions set forth in FAR 52.227–19 Commercial Computer Software-Restricted Rights (June 1987). SAS Institute Inc., SAS Campus Drive, Cary, North Carolina 27513. 1st electronic book, February 2009 2nd electronic book, June 2009 3rd electronic book, September 2009 4th electronic book, November 2009 5th electronic book, December 2009 1st printing, March 2009 2nd printing, June 2009 SAS Publishing provides a complete selection of books and electronic products to help customers use SAS software to its fullest potential. For more information about our e-books, e-learning products, CDs, and hard-copy books, visit the SAS Publishing Web site at support.sas.com/publishing or call 1-800-727-3228. SAS® and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration. Other brand and product names are registered trademarks or trademarks of their respective companies.

Contents What’s New v Overview v New SAS Deployment Tools v Security Enhancements v Deployment Enhancements vi SAS Port Changes vi Third-Party Software Port Changes Documentation Enhancements vii

Chapter 1

vi

4 Introduction to Installing the SAS Intelligence Platform

What is the SAS Intelligence Platform? 1 What Is Covered in This Document? 2 Deploying the SAS Intelligence Platform 2 Accessibility Features in the SAS Intelligence Platform Products

Chapter 2

4 Setting Up Users, Groups, and Ports

Overview: Users, Groups, and Ports 5 Defining User Accounts 6 Defining Groups 14 Additional z/OS Pre-Installation Tasks 17 Designating Ports and Multicast Addresses

Chapter 3

4 Creating a SAS Software Depot

Overview: SAS Software Depots 25 About SAS Software Depots 25 Benefits of a SAS Software Depot 27 Best Practices for SAS Software Depots Creating SAS Software Depots 29 Managing SAS Orders 45

Chapter 4

1

3

5

19

25

29

4 Installing Third-Party Products

53

Overview: Installing Third-Party Products 53 About Installing Third-Party Products 54 Review Web Application Server Configuration Documentation 54 Choose Whether to Automatically Configure Your Web Application Server Choose Whether to Automatically Deploy the SAS Web Applications 56 Install Third-Party Products Using the SAS Software Depot 56 Install Third-Party Products Using the Software Web Site 57 Installing Platform Suite for SAS 57 Pre-installation Checklists for Third-Party Products 58

Chapter 5

4 Installing and Configuring Your SAS Software

Overview: Installing and Configuring Your SAS Software

65 65

55

iv

Preparing to Install and to Configure 66 Install and Configure SAS Interactively 76 Validate the SAS 9.2 Servers 92 About SAS Deployment Tester 95 Automating the SAS Installation on Multiple Machines

Chapter 6

4 What to Do Next: Administration Tasks

Overview of Administration Tasks First-Priority Setup Tasks 104 Standard Setup Tasks 107

95

103

103

Optional Setup Tasks 108 Ongoing System Administration Tasks 110 Best Practices for Ensuring the Integrity of Your System

Appendix 1

111

4 Troubleshooting Your Initial SAS 9.2 Deployment

113

Overview of Troubleshooting Your Initial SAS 9.2 Deployment 113 Review SAS Deployment Wizard Documents and Reports 114 Troubleshooting the SAS Server Tier 115 Troubleshooting SAS Web Applications 117

Appendix 2

4 Managing Your SAS Deployment

119

Overview of Managing Your SAS Deployment 119 Deploying Products, Installing Additional Software, and Applying Updates Configuring or Adding SAS Products 125 Renewing Your Software License for SAS Solutions Removing a SAS Configuration 148

Appendix 3

144

4 Uninstalling the SAS Intelligence Platform

Overview of Uninstalling the SAS Intelligence Platform Stopping SAS Servers That Are Running 158 Uninstalling Your SAS Software 158 Uninstalling Third-Party Software 159 Uninstalling the SAS JRE and the JDK 160

Appendix 4

4 Recommended Reading

Recommended Reading

Glossary Index

163 171

161

161

157 157

120

v

What’s New

Overview 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:

3 3 3 3 3

new SAS deployment tools security enhancements deployment enhancements SAS port changes Third-party software port changes

New SAS Deployment Tools SAS 9.2 has new deployment tools:

3 The SAS Download Manager enables you to download your SAS order by using an HTTP connection over the Internet.

3 The SAS Deployment Wizard combines SAS installation and initial configuration into one wizard, replacing the SAS Software Navigator and the SAS Configuration Wizard.

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

Security Enhancements SAS 9.2 has the following security enhancements:

3 Fewer operating system accounts are required to run SAS 9.2. 3 Internal accounts are new to SAS 9.2 and are used by default for some of the required users (such as sastrust and sasadm).

vi What’s New

3 Integrated Windows authentication (IWA) provides single sign-on functionality for Windows desktop users. 3 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. 3 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.

Deployment Enhancements SAS 9.2 has the following deployment enhancements: 3 Automated, initial SAS configuration eliminates most post-installation manual configuration scripts. 3 Up-front user inputs enable you to avoid having to monitor the entire wizard session. 3 Installation includes an automated check for required third-party software. 3 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: http://support.sas.com/legaldocs/eregistration.html. 3 The initial SAS installation data file is contained within the SAS Software Depot. 3 Automated deployment is possible across multiple machines (capture-replay feature). 3 Space and time estimates are provided for SAS software depot creation. 3 You can create disc images of your SAS order, so that you can burn to CDs or DVDs at a later time. 3 On z/OS, you no longer need to define a SAS/C executable library to be program controlled. 3 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 ports have been added or changed: 3 a new SAS Pooled Workspace Server port: 8701 3 a new SAS Table Server port: 2171 3 three new SAS Object Spawner port banks: 8801, 8811, and 8821 3 a change to the SAS Remote Services Application port from 5099 to 5091 3 elimination of the SAS Object Spawner load balancing port 3 a metadata utilities SAS Workspace Server port: 8591 3 a SAS Deployment Tester Server port: 10021

Third-Party Software Port Changes The following Platform LSF ports in the Platform Suite for SAS have been added or changed: 6878, 6881, 6882, 7869, 7870, 7871, 7872

What’s New

vii

The following JBoss Web application server ports have been added or changed: 3 RMI port for managed servers: 1099, 1199, (additional managed servers increment by 100)

3 Listen port for managed servers: 8080, 8180, (additional managed servers increment by 100)

3 Secure listen port for managed servers: 8443, 8543, (additional managed servers increment by 100) The following Oracle WebLogic Web application server ports have been added or changed: 3 WebLogic Nodemanager port: 5556

3 Secure listen port for managed servers: 7002, 7102, (additional managed servers increment by 100) The following IBM WebSphere Web application server ports have been added or changed:

3 SOAP port for administrative console: 8879 3 SOAP ports for application servers: 8880, 8881, (additional application servers increment by one)

3 Secure HTTPS port for administrative console: 9043 3 Non-secure HTTP port for administrative console: 9060 3 Secure HTTPS ports for application server administrative console: 9044, 9045, (additional administrative consoles increment by one)

3 RMI port for administrative console: 9809 3 RMI ports for application servers: 9811, 9812, (additional application servers increment by one)

Documentation Enhancements SAS deployment troubleshooting information is now contained in the SAS Intelligence Platform: Installation and Configuration Guide.

viii

What’s New

1

CHAPTER

1 Introduction to Installing the SAS Intelligence Platform What is the SAS Intelligence Platform? 1 What Is Covered in This Document? 2 Deploying the SAS Intelligence Platform 2 Overview: Deploying the SAS Intelligence Platform 2 Step 1: Review Additional Documentation 2 Step 2: Create Operating System Users and Groups and Designate Ports Step 3: Create a SAS Software Depot 3 Step 4: Install Required Third-Party Software 3 Step 5: Install and Configure SAS 3 Accessibility Features in the SAS Intelligence Platform Products 3

3

What is the SAS Intelligence Platform? The SAS Intelligence Platform is a comprehensive, end-to-end infrastructure for creating, managing, and distributing enterprise intelligence. The SAS Intelligence Platform comprises four software offerings:

3 3 3 3

SAS BI Server SAS Enterprise BI Server SAS Data Integration Server SAS Enterprise Data Integration Server

Solutions for enterprise intelligence, customer intelligence, and financial intelligence are built on the Intelligence Platform, as well as turnkey solutions for specialized markets in life sciences, health care, retail, manufacturing, and others. Therefore, if your SAS deployment plan includes a SAS solution, then the SAS Intelligence Platform documentation also pertains to you. The SAS Intelligence Platform library provides information for the four platform offerings, which include products and components such as the SAS Metadata Server, SAS Integration Technologies, and the SAS OLAP Server. See http:// support.sas.com/92administration for more information about these four software offerings and their components.

2

What Is Covered in This Document?

4

Chapter 1

What Is Covered in This Document? This document begins where you and your SAS representative have decided what software you need and on what machines you will install the software. At this point, you can begin performing some pre-installation tasks, such as creating operating system user accounts and designating the ports that you will use during installation. This document covers all of the pre-installation, installation, and configuration tasks that you must perform to deploy the SAS Intelligence Platform on either a single machine or in a distributed, mixed operating system environment. By the time you reach the end of this document, all of your SAS servers, middle-tier servers, and clients will be functional. Installing the software will be easier if you read the following documents as well: 3 SAS Intelligence Platform: Overview to understand the architecture of the system. 3 configuration documentation for SAS solutions. Many of the solutions leverage the functionality of the SAS Intelligence Platform. If your SAS deployment plan includes a solution, then you might also be referred to additional solution-specific configuration information. Note: If you have licensed SAS solutions, consult with your SAS representative for more information. 4

Deploying the SAS Intelligence Platform Overview: Deploying the SAS Intelligence Platform The following table summarizes the steps required to install and configure the SAS Intelligence Platform on a single machine or in a distributed, heterogeneous environment. The first three steps are pre-installation tasks and can be performed in any order. Perform step 4 after steps 1 through 3 are completed: 1. Review additional documentation. 2. Create operating system users and groups and designate ports. 3. Create a SAS Software Depot. 4. Install required third-party software. 5. Install and configure SAS. The sections below provide a brief description of each of these tasks. Subsequent chapters in the guide provide the step-by-step instructions that you will need to perform them.

Step 1: Review Additional Documentation Review the QuickStart Guide that is shipped with your SAS software. Follow its instructions, including reviewing the system requirements and any alert-level SAS Notes. If you are deploying a SAS solution, review any solution-specific installation documents.

Introduction to Installing the SAS Intelligence Platform

4

Accessibility Features in the SAS Intelligence Platform Products

3

These documents are also available online:

3 QuickStart Guides: http://support.sas.com/documentation/installcenter/92/documents

3 SAS 9.2 system requirements: http://support.sas.com/documentation/installcenter/92/documents

3 Alert-level SAS Notes: http://support.sas.com/kb/?ct=51000

(Click “Search Problem Notes” in the left-hand navigation pane.)

3 SAS solution installation guide: Installation Instructions–Release 5.1 of the SAS Performance Management Solutions Available at http://support.sas.com/documentation/installcenter/en/ ikfmofrii/63034/PDF/default/install.pdf.

Step 2: Create Operating System Users and Groups and Designate Ports Create a set of operating system users and groups that will be required during the installation and configuration of your system, and designate a set of ports to use. For more information, see “Overview: Users, Groups, and Ports” on page 5.

Step 3: Create a SAS Software Depot Create a SAS Software Depot, which enables you to install the SAS software over your site’s network, rather than from the installation media. Note: If you have elected to receive SAS through Electronic Software Delivery, a SAS Software Depot is automatically created for you. 4 For more information, see “Overview: SAS Software Depots” on page 25.

Step 4: Install Required Third-Party Software Install any third-party products, such as a Java Development Kit and a Web application server, that are necessary for your installation. These products are identified in your deployment plan. For more information, see “Overview: Installing Third-Party Products” on page 53.

Step 5: Install and Configure SAS Install and configure your SAS software using the SAS Deployment Wizard, an installation and configuration tool that is supplied by SAS. For more information, see “Overview: Installing and Configuring Your SAS Software” on page 65.

Accessibility Features in the SAS Intelligence Platform Products For information about accessibility for any of the products mentioned in this book, see the documentation for that product. If you have questions or concerns about the accessibility of SAS products, send e-mail to [email protected] or visit the SAS accessibility site at: http://www.sas.com/govedu/accessibility.html.

4

5

CHAPTER

2 Setting Up Users, Groups, and Ports Overview: Users, Groups, and Ports 5 Defining User Accounts 6 Overview: Defining User Accounts 6 Internal User Accounts 6 Required External User Accounts for SAS 7 Rights Required by External User Accounts for SAS 8 Required External User Accounts for Third-Party Software 9 Rights Required by External User Accounts for Third-Party Software 10 Local or Directory Service Accounts? 10 Password Policies 11 Pre-installation Checklist for External User Accounts for SAS on Windows and UNIX Pre-installation Checklist for External User Accounts for Third-Party Software 12 Pre-installation Checklist for External User Accounts for SAS on z/OS 13 Defining Groups 14 Overview: Defining Groups 14 The SAS Server Users Group (Windows) 14 The sas Group (UNIX) 15 The SASGRP Group (z/OS) 15 Pre-installation Checklist for Groups for SAS on Windows and UNIX 15 Pre-installation Checklist for Groups for Third-Party Software 16 Pre-installation Checklist for Groups for SAS on z/OS 16 Additional z/OS Pre-Installation Tasks 17 About Additional z/OS Pre-Installation Tasks 17 Create a Configuration Directory and Define the SAS Library on z/OS 17 Install the SAS 9.2 SVC Routine 18 Install the SASCP Module 18 Designating Ports and Multicast Addresses 19 About Ports and Multicast Addresses 19 Multicast Address Considerations 19 Pre-installation Checklist for Ports for SAS 21

11

Overview: Users, Groups, and Ports Before you begin installing and configuring your software, you must create a set of required users and groups at the operating system level, and you must designate a set of TCP/IP ports for the servers to use. This is the second of five tasks required to install and configure the SAS Intelligence Platform.

6

Defining User Accounts

4

Chapter 2

1. Review additional documentation.

I 2. Create operating system users and groups and designate ports. 3. Create a SAS Software Depot. 4. Install required third-party software. 5. Install and configure SAS.

Defining User Accounts Overview: Defining User Accounts There are two types of user accounts to understand when deploying SAS:

3 Internal user accounts are accounts known only to SAS and are created and authenticated internally in metadata rather than externally. 3 External user accounts are user accounts defined outside of SAS metadata. These accounts are local to a machine or are defined in a network directory service of which the machine is a member, such as LDAP. The following sections describe the user accounts that SAS and third-party software require, and provide information to help you answer these questions: 3 What are internal and external user accounts?

3 What user rights or to what groups must each account be assigned? 3 Should I create local or network directory service accounts? 3 What password policies should I enforce?

Internal User Accounts Internal user accounts are accounts known only to SAS and are created and authenticated internally in metadata rather than externally. SAS identifies internal accounts by appending a special string to the user ID. This string begins with an at sign (@) and contains saspw: @saspw. For two of the required user accounts, the SAS Administrator and the SAS Trusted User, the SAS Deployment Wizard prompts you by default to create internal user accounts. The following table shows the default internal user accounts required by SAS. (SAS internal accounts are authenticated on the metadata server.)

Setting Up Users, Groups, and Ports

4

Required External User Accounts for SAS

7

Table 2.1 SAS Internal User Accounts Description

User ID

SAS Administrator—

[email protected]

The user account that has privileges associated with the SAS Metadata Unrestricted Users role. SAS Trusted User—

[email protected]

The user account that can impersonate other users on connections to the metadata server. Some SAS processes use this account to communicate with the metadata server on a client’s behalf.

For more information about SAS internal user accounts and their purposes, see “Understanding the State of Your System” in the SAS Intelligence Platform: System Administration Guide. Here are some benefits of internal accounts: 3 less maintenance. The account is defined only once in SAS, and you do not define this account externally using the authentication provider. 3 isolation from the host machine security policy. The SAS Administrator and the SAS Trusted User credentials are referenced in many locations within SAS. For example, forcing a recurring password change (a common security policy) might make unnecessary work for the person administering SAS. 3 independence from IT. You can create additional SAS unrestricted user and administrative user accounts for metadata management without involvement of your IT department. 3 reduced “headless” external user accounts. The SAS Trusted User is an account used for SAS inter-process communication, and it will not be mistaken for a human user. 3 minimal security exposure to your enterprise. The SAS Administrator and the SAS Trusted User are highly privileged accounts and only provide access to SAS—not to operating system resources.

Required External User Accounts for SAS External user accounts are user accounts defined outside of SAS metadata. These accounts are local to a machine or are defined in a network directory service of which the machine is a member, such as LDAP. SAS requires certain external user accounts for two purposes: installation and running certain SAS server processes. During installation and configuration, the SAS Deployment Wizard must run under an external account with the necessary privileges on the target machine to write SAS program and log files. To run servers such as the stored process server and the pooled workspace server, SAS requires an external user account to be the server process owner. For more information about external user accounts and their purposes, see the SAS Intelligence Platform: System Administration Guide. As you create these external user accounts, record information about them in “Pre-installation Checklist for External User Accounts for SAS on Windows and UNIX” on page 11 or in “Pre-installation Checklist for External User Accounts for SAS on z/ OS” on page 13. You will need this information when you run the SAS Deployment Wizard later.

8

Rights Required by External User Accounts for SAS

4

Chapter 2

Note: To validate your SAS deployment, you will need an external user account that is representative of a SAS client user, such as SAS Data Integration Studio, that must be the temporary process owner when its jobs are run on a standard workspace server. If Integrated Windows authentication (IWA) is not being implemented, it can be helpful to have the SAS Deployment Wizard create a SAS First User account in metadata during deployment for validation purposes. The wizard will also assign the required Log on as a batch job Windows user right for you. 4 The following table shows external user accounts required by SAS and the machines on which they are authenticated. Table 2.2 Required External User Accounts for SAS

Description

Recommended User ID

Machine Where Authenticated

SAS Installer—

sas

Every machine

sassrv

Stored process server

The account used to install SAS. SAS Spawned Servers account— The process owner for stored process servers and pooled workspace servers.

Pooled workspace server

Note:

3 For information about the user rights that each external account requires, see “Rights Required by External User Accounts for SAS” on page 8.

3 Windows: The SAS Installer user ID must be available in the long term for future SAS maintenance.

3 UNIX: Do not use root for the SAS Installer user ID. 3 AIX: For both user IDs, make sure that the User can LOGIN? setting is set to true.

3 z/OS: The SAS Installer and the SAS Spawned Servers account must have a TSO segment defined.

3 z/OS: By default, the SAS Installer: 3 is the started task owner for the servers. 3 is the owner of the configuration directory structure. 3 must have a writable home directory in the UNIX file system. 3 must have an OMVS segment definition with the following minimum settings: 3 ASSIZEMAX of at least 800 MB 3 CPUTIMEMAX of at least 5000 seconds 3 PROCUSERMAX of at least 50 users

4

Rights Required by External User Accounts for SAS Operating systems require that you assign certain rights to the external user accounts used to deploy and to run SAS. The following table describes the user rights needed by the required external user accounts to deploy and run SAS.

Setting Up Users, Groups, and Ports

4

Required External User Accounts for Third-Party Software

9

Table 2.3 Rights Required by External User Accounts for SAS External User Account

Operating System

User Rights Needed

SAS Installer

Windows

Administrator rights

UNIX

Member of a group that is the primary group for the SAS Spawned Servers account

z/OS

Default member of a group that also includes the SAS Spawned Servers account

Windows1

Log on as a batch job

UNIX

Member of a group that is the primary group for the SAS Installer

z/OS

Member of a group that also includes the SAS Installer user

SAS Spawned Servers account

1 The SAS Deployment Wizard automatically assigns the Windows user right Log on as a batch job to the SAS Spawned Servers account.

On Windows, if you choose how to run your SAS servers using management scripts—instead of running them as Windows services—then the user account that runs the object spawner must meet the following requirements on the object spawner machine: 3 be the administrator or a member of the Windows Administrator’s group

3 have the following Windows local user rights: 3 Adjust memory quotas for a process 3 Replace a process level token

Required External User Accounts for Third-Party Software The following table describes the external user accounts required by third-party software and the machines on which they are authenticated—either as local accounts or in a network directory service that the machine can access.

10

Rights Required by External User Accounts for Third-Party Software

4

Chapter 2

Table 2.4 Required External User Accounts for Third-Party Software

Description

Recommended User ID

Machine Where Authenticated

LSF Administrator—

lsfadmin

Every Platform Process Manager and Platform LSF machine

lsfuser

Platform Process Manager

Process owner for Platform LSF services and daemons. Required if you install Platform Suite for SAS to support scheduling or grid computing. Also owns the LSF configuration and log files and has permission to perform cluster-wide operations, edit configuration files, and reconfigure a cluster. LSF User— Sometimes referred to as the scheduling user. Required by SAS Web Report Studio to run the Output Generation Tool, which creates scheduled reports in batch mode.

As you create these external user accounts, record information about them in “Pre-installation Checklist for External User Accounts for SAS on Windows and UNIX” on page 11. You will need this information when you run the SAS Deployment Wizard (in Chapter 6). Note: For information about the user rights that each account requires, see “Rights Required by External User Accounts for Third-Party Software” on page 10. 4

Rights Required by External User Accounts for Third-Party Software The following table describes the user rights needed by the required external user accounts to deploy and run third-party software: Table 2.5 Rights Required by External User Accounts for Third-Party Software External User Account

Operating System

User Rights Needed

LSF Administrator

Windows

Administrator rights Adjust memory quotas for a process Debug programs Log on as a service Replace a process level token

LSF User

Windows

Log on as a batch job or Log on locally

Local or Directory Service Accounts? SAS relies on its various server machines to authenticate external user accounts. In turn, the SAS server machine authenticates user accounts using an authentication provider. An authentication provider refers to an authentication service that is one of the following:

3 local to a machine and used to authenticate local host user accounts

Setting Up Users, Groups, and Ports

4

Pre-installation Checklist for External User Accounts for SAS on Windows and UNIX

11

3 available to a machine through a computer network and used to authenticate directory service accounts such as LDAP or Active Directory You can create either local or directory service accounts for external users. The only requirement is that each user shown in Table 2.2 on page 8 can be authenticated by the machine’s authentication provider—be that an authentication provider that is local to the machine, or an authentication provider that is available to the machine through a directory service. The main advantage of local accounts is that if account information were to get into the wrong hands, the credentials could be used only to log on to the machine or machines that can authenticate the credentials. A secondary benefit is that the host could continue to authenticate users even if the directory service authentication provider were unavailable. The advantage of directory service accounts is that you do not have to create the same accounts on multiple machines or keep the account information synchronized across machines—the directory service authentication provider does this for you. For example, setting up the SAS Spawned Server user account is usually straightforward. The spawned server account must be able to be authenticated by the pooled workspace server and stored process server machine. If these servers are distributed on more than one machine, then each machine must be a member of the same directory service or in different directory services between which a trust has been established. For more information, see “Ensure Access to Servers” in the SAS Intelligence Platform: Security Administration Guide.

Password Policies Note: In this section, we are talking only about the passwords for the few external user accounts SAS requires, not the passwords for regular users of the system. 4 When you set up passwords for your SAS system users, we highly recommend that these passwords do not have to be reset when a user first logs on. If, for some reason, it is required that you create passwords that have to be reset, you will have to log on using each account and change the password before you install and configure your software. And, of course, you will need to know the changed password for each account. By default, passwords for internal accounts are set not to expire. When passwords for system accounts change, you must update a set of configuration files and some metadata objects. SAS provides instructions for updating these files and metadata objects. However, you can save yourself some time if the passwords do not expire.

Pre-installation Checklist for External User Accounts for SAS on Windows and UNIX Use the following pre-installation checklist to create the necessary external user accounts to deploy and run SAS on Windows and UNIX. Note: These checklists are superseded by more complete and up-to-date checklists that can be found at http://support.sas.com/installcenter/plans. This Web site also contains a corresponding deployment plan and an architectural diagram. 4

12

4

Pre-installation Checklist for External User Accounts for Third-Party Software

Chapter 2

Table 2.6 Pre-installation Checklist for External User Accounts for SAS on Windows and UNIX Account SAS Installer

Recommended User ID

Actual User ID 1

Windows: my-domain\installer-ID UNIX: sas2, 3

SAS Spawned Servers account

Windows: my-domain\sassrv UNIX: sassrv

1 On Windows, the user ID should be available in the long term for future SAS maintenance. 2 On AIX, make sure that the User can LOGIN? setting is set to true for the user. 3 On UNIX, do not use root.

Note these important items:

3 For information about the user rights that each external account requires, see “Rights Required by External User Accounts for SAS” on page 8. 3 The SAS Deployment Wizard prompts you for the Installer account and the SAS Spawned Servers account information, and you cannot complete the installation without supplying it. 3 On UNIX systems, the SAS Deployment Wizard requires that you supply the root password during configuration. Certain SAS products and features use functionality that requires SAS to check user ID authentication and file access authorizations. This in turn necessitates that certain files within your SAS installation have setuid permissions and be owned by root. 3 If your UNIX system uses an authentication method other than /etc/passwd or / etc/shadow, then you must configure authentication before you begin your SAS software deployment, or SAS 9.2 will not function properly. For more information, see the Configuration Guide for SAS 9.2 Foundation for UNIX Environments available at http://support.sas.com/installcenter.

Pre-installation Checklist for External User Accounts for Third-Party Software Use the following pre-installation checklist to create the necessary external user accounts to deploy and run third-party software. Note: The SAS Deployment Wizard prompts you for this information, and you cannot complete the installation without it. 4 Note: These checklists are superseded by more complete and up-to-date checklists that can be found at http://support.sas.com/installcenter/plans. This Web site also contains a corresponding deployment plan and an architectural diagram. 4

Setting Up Users, Groups, and Ports

4

Pre-installation Checklist for External User Accounts for SAS on z/OS

13

Table 2.7 Pre-installation Checklist for External User Accounts (Third-Party) Account

Recommended User ID

LSF Administrator

Windows: my-domain\lsfadmin

LSF User

Windows: my-domain\lsfuser

Actual User ID

UNIX: lsfadmin

UNIX: lsfuser

Note: For information about the user rights that each account requires, see “Rights Required by External User Accounts for Third-Party Software” on page 10. 4

Pre-installation Checklist for External User Accounts for SAS on z/OS Use the following pre-installation checklist to create the necessary external user accounts to deploy and run SAS on z/OS. Note: The SAS Deployment Wizard prompts you for this information, and you cannot complete the installation without it. 4 Note: These checklists are superseded by more complete and up-to-date checklists that can be found at http://support.sas.com/installcenter/plans. This Web site also contains a corresponding deployment plan and an architectural diagram. 4 Table 2.8 Pre-installation Checklist for External User Accounts for SAS on z/OS Account

Recommended User ID

SAS Installer

sas

SAS Spawned Servers account

sassrv

Actual User ID

Note: 3 For information about the user rights that each external account requires, see “Rights Required by External User Accounts for SAS” on page 8. 3 The SAS Installer and the SAS Spawned Servers account must have a TSO segment defined. 3 By default, the SAS Installer: 3 is the started task owner for the servers. 3 is the owner of the configuration directory structure. 3 must have a writable home directory in the UNIX file system. 3 must have an OMVS segment definition with the following minimum settings: 3 ASSIZEMAX of at least 800 MB 3 CPUTIMEMAX of at least 5000 seconds

14

Defining Groups

4

Chapter 2

3 PROCUSERMAX of at least 50 users

4

Defining Groups Overview: Defining Groups On UNIX, adding users to a group is required to assign the necessary operating system privileges to deploy and run SAS. Using a group is one method for granting the corresponding user rights needed on Windows.

The SAS Server Users Group (Windows) To deploy SAS on Windows, the user must have certain local user rights on the machine hosting the server. These rights are required before the user can start a process for a stored process server, a pooled workspace server, or a standard workspace server. One suggestion for giving a user these rights is to create a group, add users to the group, and then assign the rights to the group. (The scheduling user, lsfuser—which is required if you are scheduling reports—also must have this same right.) Note: Not all of these user accounts will exist in every installation. You add only those that you have created. In addition, if you are working in a multi-machine environment and are using local groups, not all of the users that you have created need to be included in every local group. You need only include the users who will be authenticated by a stored process server, pooled workspace server, or standard workspace server on a given machine. On some machines (for example, a machine hosting middle-tier components) there might be no need for the group at all. 4 To set up a group, complete these steps: 1 Create a SAS server users group. This can be a local group or a group with domain scope. 2 Add the following users to the group: 3 SAS Spawned Servers account 3 SAS First User (optional account) 3 LSF User 3 any other external users that need to access a standard workspace server Note:

The SAS Deployment Wizard automatically grants the Windows user right

Log on as a batch job to the SAS Spawned Servers account. If you choose to

have the wizard create the optional SAS First User account in metadata, the wizard also automatically grants the Log on as a batch job Windows user right to this First User account. If Integrated Windows authentication (IWA) is implemented, this user right is not required for the SAS First User and other regular SAS users who access standard workspace servers, such as SAS Data Integration Studio or SAS Enterprise Guide users.

4

3 Finally, grant the user right Log on as a batch job to the group. For

information about setting local user rights, see your Microsoft Windows documentation. If the users in the group need that right on more than one Windows machine, the right needs to be assigned specifically on each machine.

Setting Up Users, Groups, and Ports

4

Pre-installation Checklist for Groups for SAS on Windows and UNIX

15

The sas Group (UNIX) To deploy SAS on UNIX, you should create an operating system group and make this the primary group for the UNIX SAS Installer user. The SAS Spawned Servers account should also be made a member of the sas group. (Members of this group will be given access to certain directories and files created by the SAS Deployment Wizard.) For information about creating groups and adding user accounts, see your UNIX documentation.

The SASGRP Group (z/OS) To deploy SAS on z/OS, you should create a RACF group named SASGRP. This group is used to control access to directories and files in the configuration directory created in the HFS file system. The definition of this RACF group must include an OMVS segment and must be set as the default group for the SAS Installer and the SAS Spawned Servers account. For information about creating groups and adding user accounts, see your IBM z/OS documentation.

Pre-installation Checklist for Groups for SAS on Windows and UNIX Use the following pre-installation checklist to make sure that you have created the necessary groups to deploy and run SAS on Windows and UNIX: Note: These checklists are superseded by more complete and up-to-date checklists that can be found at http://support.sas.com/installcenter/plans. This Web site also contains a corresponding deployment plan and an architectural diagram. 4 Table 2.9 Pre-installation Checklist for Groups for SAS on Windows and UNIX Recommended Group Name

Group Members

Operating System and Purpose

SAS Server Users1

SAS Spawned Servers account

Windows—

SAS First User Any other users

Suggested method for assigning the Log on as a batch job user right to the SAS Spawned Servers account for the stored process server and pooled workspace server. Suggested method for assigning the Log on as a batch job user right to the SAS First User and any other standard workspace server users.

Actual Group Name

16

Pre-installation Checklist for Groups for Third-Party Software

4

Chapter 2

Recommended Group Name

Group Members

Operating System and Purpose

sas2

SAS Installer

UNIX—

Actual Group Name

Primary group for the SAS Installer user. Enables the SAS Deployment Wizard to create the necessary log and configuration directories required by SAS. SAS Spawned Servers account

Through group membership, grants Write permissions to the SAS Spawned Server account for modifying SAS log and configuration directories.

1 Unless Integrated Windows authentication (IWA) is implemented, add any other any external users accessing standard workspace servers. 2 Limit membership because this privileged group has operating system access to certain configuration files.

Pre-installation Checklist for Groups for Third-Party Software Use the following pre-installation checklist to create the necessary groups to deploy and run third-party software. Note: These checklists are superseded by more complete and up-to-date checklists that can be found at http://support.sas.com/installcenter/plans. This Web site also contains a corresponding deployment plan and an architectural diagram. 4 Table 2.10

Pre-installation Checklist for Groups for Third-Party Software

Recommended Group Name

Group Members

Operating System and Purpose

SAS Server Users

Scheduling user (lsfuser)

Windows—

Actual Group Name

Suggested method for assigning the Log on as a batch job user right to scheduling users.

Pre-installation Checklist for Groups for SAS on z/OS Use the following pre-installation checklist to create the necessary groups to deploy and run SAS on z/OS: Note: These checklists are superseded by more complete and up-to-date checklists that can be found at http://support.sas.com/installcenter/plans. This Web site also contains a corresponding deployment plan and an architectural diagram. 4

Setting Up Users, Groups, and Ports

Table 2.11

4

Create a Configuration Directory and Define the SAS Library on z/OS

17

Pre-installation Checklist for Groups for SAS on z/OS

Recommended Group Name

Group Members

Purpose(s)

Actual Group Name

SASGRP1

SAS Installer

Default group for the SAS Installer user.

SAS Spawned Servers account

Through group membership, grants write permissions to the SAS Spawned Server account for modifying SAS log and configuration directories.

1 The definition of this RACF group must include an OMVS segment. Limit membership because this privileged group has operating system access to certain configuration files.

Additional z/OS Pre-Installation Tasks About Additional z/OS Pre-Installation Tasks In addition to creating the necessary users, groups, and ports, to deploy the SAS Intelligence Platform on z/OS, you must also do the following:

3 Create a directory that will serve as the configuration directory for the SAS server tier on the z/OS machine.

3 Define the SAS executable library to be program-controlled. 3 Install the SAS 9.2 SVC routine 3 Install the SASCP module

Create a Configuration Directory and Define the SAS Library on z/OS In addition to creating the necessary users, groups, and ports, to deploy the SAS Intelligence Platform on z/OS, you must also do the following:

3 Create a directory that will serve as the configuration directory for the SAS server tier on the z/OS machine.

3 Define the SAS executable library to be program-controlled. Record this information in the following checklist: Table 2.12 Configuration Directory and SAS Executable Library Checklist on z/OS Task

Actual Directory or Library Name 1

Create a configuration directory for the SAS server tier

Define the SAS executable library to be program-controlled

1 A typical path is /usr/lpp/SAS/SAS_9.2/config-directory.

18

Install the SAS 9.2 SVC Routine

4

Chapter 2

Install the SAS 9.2 SVC Routine In addition to creating the necessary users, groups, and ports, to deploy the SAS Intelligence Platform on z/OS, you must also install the SAS 9.2 SVC routine. To install the SAS 9.2 SVC routine, follow these steps: 1 Download the instsvc.xmit file from the SAS FTP Web site at ftp://

ftp.sas.com/techsup/download/mvs/. 2 Using FTP, transfer the instsvc.xmit file (in binary mode) to your z/OS system.

You should preallocate the target data set with the following DCB characteristics: LRECL=80 BLKSIZE=3120 RECFM=FB 3 Use the following RECEIVE command to create a PDS that will contain the JCL

members that are required to install the SVC routine, where sas92.instsvc.xmit is the name of the file to which you transferred the instsvc.xmit file, using FTP. receive indataset(sas92.instsvc.xmit)

Respond with the name of a data set that will contain the JCL members (that you will use to complete the installation) by issuing the following command: da(sas92.instsvc.cntl)

4 Create the library that will contain the load modules by issuing the following

command, where SAS92.INSTSVC.CNTL is the data set that you created in the previous step: receive indataset(sas92.instsvc.cntl(svcmod))

5 Respond with the name of a data set that will contain the load modules by issuing

the following command: da(sas92.instsvc.library)

6 Continue your SVC installation by following the instructions in “Installing the

SAS 9.2 SVC Routine” in the Configuration Guide for SAS 9.2 Foundation for z/OS, with the following exceptions:

3 Anywhere that the documentation references the BAMISC data set, use the CNTL data set that you created in step 3.

3 Anywhere that the documentation refers to the SAS.LIBRARY data set, use the data set that you created in step 4. The Configuration Guide for SAS 9.2 Foundation for z/OS is located on the SAS Install Center Web site at http://support.sas.com/idsearch?ct=200000 (search for the document title).

Install the SASCP Module In addition to creating the necessary users, groups, and ports, to deploy the SAS Intelligence Platform on z/OS, you must also install the SAS 9.2 SASCP module. To install the SAS 9.2 SASCP module, follow these steps: 1 Download the instsascp.xmit file from the SAS FTP Web site at ftp://

ftp.sas.com/techsup/download/mvs/.

Setting Up Users, Groups, and Ports

4

Multicast Address Considerations

19

2 Using FTP, transfer the instsascp.xmit file (in binary mode) to your z/OS system.

You should preallocate the target data set with the following DCB characteristics: LRECL=80 BLKSIZE=3120 RECFM=FB 3 Use the following RECEIVE command to create a PDS that will contain the SASCP load module, where sas92.insascp.xmit is the name of the file to which you transferred the instsascp.xmit file, using FTP. receive indataset(sas92.insascp.xmit) Respond with the name of the target data set to contain the SASCP load module by issuing the following command: da(sas92.insascp.load)

4 Copy the SASCP module to a load library that contains TSO commands.

This can be a STEPLIB library defined in a LOGON procedure, a system link list library, or a link pack area library. For more information about the SASCP module see “Implementing SAS TSO Support” in the Configuration Guide for SAS 9.2 Foundation for z/OS located on the SAS Install Center Web site at http://support.sas.com/ idsearch?ct=200000 (search for the document title).

Designating Ports and Multicast Addresses About Ports and Multicast Addresses While you are creating operating system user accounts and groups, you need to review the set of ports that the SAS servers, third-party servers, and spawners in your system will use by default. If any of these ports is unavailable, select an alternate port, and record the new port on the following ports pre-installation checklists: 3 “Multicast Address Considerations” on page 19 3 “Pre-installation Checklist for Ports for SAS” on page 21 For third-party software ports, see “Pre-installation Checklists for Third-Party Products” on page 58. You also need to plan for designating Internet Protocol (IP) multicast addresses for the all the machines in your SAS deployment. Multicasting simplifies the on-going management and deployment of SAS Web applications, by providing the flexibility to customize the SAS middle-tier, and to distribute SAS Web components to implement load balancing.

Multicast Address Considerations The SAS Deployment Wizard prompts you to supply a multicast address for inter-machine communication. The wizard supplies you with a default multicast address that it generates based on the machine’s IP address and the admin local scope that is recommended in RFC 3171 (IPv4) or RFC 4291 (IPv6). A multicast group communications protocol is used to communicate among middle-tier SAS applications in a single SAS deployment (the set of applications

20

Multicast Address Considerations

4

Chapter 2

connected to the same SAS Metadata Server). The combination of multicast IP address and multicast UDP port should be different for each SAS deployment and also different from those used by other multicast applications at your site. The multicast group communication includes all information needed to bootstrap SAS middle-tier applications. Because this includes sending the SAS environment credentials (such as the sasadm account name and its password), scoping and encryption options are provided. The defaults are most appropriate for deployments in a firewall, isolated data center environment. The IP multicast address must be valid for IP multicasting and should be in the range 224.0.0.0 to 239.255.255.255 for IPv4 or have the prefix ff00::/8. Typically, the chosen address will be in the admin-local scoped block which corresponds to 239/8 for IPv4 and ff14::/8 for IPv6. The sample address provided during configuration by the SAS Deployment Wizard conforms to these standards. The address should be unique to SAS applications for the subnet they are installed on. The IP Multicast UDP port should be open and usable on any machine a middle-tier application is to be installed. This is a UDP port and does not conflict with any previous TCP port definitions such as the metadata server. The multicast group communication is intended to be used only within your data center environment. Many sites keep their data center network separated from end users via a firewall that will automatically isolate the multicast protocol. Alternatively, the time to live (TTL) parameter can be used to restrict the scope of multicast communication. Your network administrator can suggest a TTL setting to limit the scope of the multicast. The TTL option and the authentication token option both have security implications. The multicast TTL property (default = 1) affects the number of network hops a multicast packet will take before being dropped. This TTL value must be greater than or equal to the largest number of hops between any two servers containing SAS products. In addition, some network router documentation recommends that multicast datagrams with initial TTL=0 are restricted to the same host, multicast datagrams with initial TTL=1 are restricted to the same subnet, and multicast datagrams with initial TTL=32 are restricted to the same site. Consult your network router documentation or your network administration staff to determine the correct values for your environment. Note: You must make sure that all of the machines in your SAS 9.2 deployment are members of the same subnet, or be sure to set the default TTL value to a number higher than 1. The deployment wizard gives you the opportunity to set the TTL value during SAS 9.2 deployment. For information about how to change these options after deployment, see “Multicast Options” in the SAS Intelligence Platform: Web Application Administration Guide. 4 Because the multicast protocol conveys credentials, it is protected via encryption. By default, group communication is protected only with a fixed encryption key that is built into the software. If your middle-tier is not running in an environment that is well-isolated from end-user access, then you might want better protection against eavesdroppers and unauthorized group participants. For such situations, choose a multicast authentication token known only to your SAS middle-tier administrative staff. The authentication token is a password-like string needed to connect to the group and create a site-specific encryption key. The deployment wizard default simplifies configuration using the authentication token that is built into the software. This option is best used in development and other low-security environments. It might also be appropriate in higher-security environments where the multicast group communication is isolated from the end-user community, either via firewall or TTL option, and where all data center administrative and operations staff have sufficient security approval. If your multicast group communication is not contained within an isolated data center environment, or if the security procedures at your site require protections among

Setting Up Users, Groups, and Ports

4

Pre-installation Checklist for Ports for SAS

21

administrative and operational staff in various roles, you should specify an authentication token that is known only to the administrators of the SAS environment. The same token string must be supplied on each tier in the configuration. By default, there is a code level authentication token shared between all SAS middle-tier applications to prevent access to the multicast group from unauthorized listeners. If you choose to use a customized authentication token, use the deployment wizard to enter an authentication token value that meets your organization’s security guidelines. The authentication token can be any password-like string. In a multi-tier configuration, this prompt appears on each tier that has an application participating in the SAS multicast groups. You must provide the same authentication token string to each tier in the same SAS deployment (that is, each tier associated with the same metadata server). For more information about configuring Web application servers to use with SAS 9.2, 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.

Pre-installation Checklist for Ports for SAS The following checklist indicates what ports are used for SAS by default, and gives you a place to enter the port numbers that you will actually use. Note: The SAS Deployment Wizard prompts you for this information, and you cannot complete the installation without it. 4 On UNIX and z/OS, we recommend that you document each SAS port that you reserve in the following standard locations on each machine: 3 UNIX—/etc/services 3 z/OS—your TCP/IP PROFILE data set This practice will help to avoid port conflicts on the affected machines. On z/OS, the SAS servers are configured and initially started as TSO processes invoked from the USS shell using /bin/tso. When these servers are started under tso, the job name is the user ID that is starting the server with a character appended to the end. If your site makes use of the reserved ports facility in TCP/IP, each port definition should include the started task and this SAS installer ID job name as valid users of this port. You can use an asterisk (such as, sas*) in this definition. On all operating systems, the last digit of the default port number reflects the configuration level that you select in the SAS Deployment Wizard. For example, when you select Lev1, the default port for the metadata server is 8561. If you choose another level, such as Lev2, the wizard changes the default port to 8562. Note: These checklists are superseded by more complete and up-to-date checklists that can be found at http://support.sas.com/installcenter/plans. This Web site also contains a corresponding deployment plan and an architectural diagram. If you are a SAS solutions customer, consult the pre-installation checklist provided by your SAS representative for a complete list of ports that you must designate. 4

22

Pre-installation Checklist for Ports for SAS

Table 2.13

4

Chapter 2

Pre-installation Checklist for Ports (SAS)

Server or Spawner

Default Port

E-mail server

25

HTTP server

80

HTTP server (secure port)

443

SAS Table Server

2171

SAS Remote Services application

5091

SAS OLAP Server

5451

Event Broker administration

6051

SAS/CONNECT server and spawner

7551

Event Broker HTTP

8111

Operating System Services scheduler

8451

SAS/SHARE server

8551

Multicast (UDP port)

8561

SAS Metadata Server

8561

SAS object spawner: operator port

8581

SAS Workspace Server

8591

Metadata utilities SAS Workspace Server1

8591

SAS Stored Process Server: bridge connection

8601

Actual Port

Setting Up Users, Groups, and Ports

4

Pre-installation Checklist for Ports for SAS

Server or Spawner

Default Port

SAS Stored Process Server: load balancing connection 1 (MultiBridge)

8611

SAS Stored Process Server: load balancing connection 2 (MultiBridge)

8621

SAS Stored Process Server: load balancing connection 3 (MultiBridge)

8631

SAS Pooled Workspace Server

8701

SAS object spawner: pooled workspace server port bank 1

8801

SAS object spawner: pooled workspace server port bank 2

8811

SAS object spawner: pooled workspace server port bank 3

8821

SAS Deployment Tester server

10021

23

Actual Port

1 In SAS 9.2, two or more workspace servers can share the same port even if they are running at the same time.

24

25

CHAPTER

3 Creating a SAS Software Depot Overview: SAS Software Depots 25 About SAS Software Depots 25 Benefits of a SAS Software Depot 27 Best Practices for SAS Software Depots 29 Creating SAS Software Depots 29 Overview: Creating SAS Software Depots 29 Prerequisites for Creating a SAS Software Depot 30 Create a Depot by Using the SAS Download Manager Create a Depot by Using the SAS Deployment Wizard Managing SAS Orders 45 Overview: Managing SAS Orders 45 Change Order Details 45 Delete an Order 47 Create a Disc Image of Your Order 49

30 40

Overview: SAS Software Depots One prerequisite for deploying SAS is to create a special file system of SAS product and order data—a SAS Software Depot—that the SAS Deployment Wizard then uses to install and configure SAS. Creating a SAS Software Depot is the third of five steps required to install and configure the SAS Intelligence Platform: 1. Review additional documentation. 2. Create operating system users and groups and designate ports.

I 3. Create a SAS Software Depot. 4. Install required third-party software. 5. Install and configure SAS.

About SAS Software Depots A SAS Software Depot is a file system that consists of a collection of SAS installation files that represents one or more orders. The depot is organized in a specific format that

26

About SAS Software Depots

4

Chapter 3

is meaningful to the SAS Deployment Wizard, which is the tool that is used to install and initially configure SAS. The depot contains the SAS Deployment Wizard executable, one or more deployment plans, a SAS installation data file, order data, and product data.

Figure 3.1

SAS Software Depot File Structure

Before you can install SAS, you must first have a software depot to install from. During a SAS software download, the SAS Download Manager downloads your order, verifies it, and automatically creates a SAS Software Depot. If you receive your SAS order in the form of physical media, then you create a depot using the SAS Deployment Wizard.

Creating a SAS Software Depot

4

Benefits of a SAS Software Depot

27

Figure 3.2 Methods for SAS Software Depot Creation

Benefits of a SAS Software Depot The main advantage of a SAS Software Depot is that it resides on the network at a location that you can share access to. Thus it provides a faster and more reliable means of installation compared to traditional removable media (cartridges, CDs, DVDs, and so on).

28

Benefits of a SAS Software Depot

Figure 3.3

4

Chapter 3

Shared SAS Software Depot Model

If you have remote sites running SAS without access to the network on which your depot resides, you can use the SAS Deployment Wizard to create your own SAS media image to write to the removable media of your choice. Here are some other benefits of using a SAS Software Depot:

3 centralizes SAS orders. The depot enables you to place multiple SAS orders in one location to simplify initial SAS deployment and future maintenance.

3 saves disk space. Storing multiple orders in a single depot saves disk space, as any content shared between orders is not duplicated, but rather shared, in the depot. A single depot in SAS 9.2 can store SAS software installation files for more than one operating system, making the single, multi-system SAS 9.2 depot cumulatively smaller than the multiple, single-system depots in SAS 9.1.3.

3 saves download time. Because there is a shared copy of common files, the SAS 9.2 single, multi-operating system depot requires smaller amounts to download.

3 organizes license keys (also known as SAS installation data files). The depot enables you to place SAS installation data files in a standard location to better associate license keys with their corresponding orders. (These files are stored in the sid_files directory, directly under the depot’s root.)

3 identifies multiple orders. The depot supports the SAS Deployment Wizard’s feature that enables you to customize order descriptions and enter notes to better identify multiple orders residing in a single depot. Because depots contain your personal SAS software order, it is important to use the following best practices for securing and backing up your depot.

Creating a SAS Software Depot

4

Overview: Creating SAS Software Depots

29

Best Practices for SAS Software Depots For customers who download SAS, their SAS Software Depot is the only copy of their SAS order. The depot contains the files from which SAS is initially installed. For this reason, it is important to use these best practices when managing your depot:

3 Perform routine backups. As with your SAS production system, it is important to routinely back up your SAS Software Depot and verify the integrity of these backups. Note: Another important reason for securing and backing up your SAS Software Depot is that there are limits on the number of times that you can download your order from SAS. 4

3 Secure the depot location. Problems such as data loss, virus infection, and file corruption can compromise your investment in SAS. It is thus imperative that you have a comprehensive security policy in place to protect your depot.

3 Store SAS installation data files with your depot. The SAS installation data file for your orders contains information that is integral to successfully deploying SAS. As you get these data files from SAS—such as the file that contains your permanent SAS license key—it is important that you store them with your depot in the sid_files directory. CAUTION:

If you do not use the installation data file that supports the products you are planning to install and configure on this machine, you might experience errors later when you are trying to use the products. 4

3 Create a depot administrator. Consider designating one or a few users to serve as SAS Software Depot administrators. Persons needing to deploy SAS software or to apply future SAS software maintenance require depot Read and Execute privileges. Depot administration tasks such as initially creating the depot, storing SAS installation data files, and updating order details require depot Write privileges. Separating depot administration from routine depot usage is a best practice that will further protect your SAS Software Depot.

Creating SAS Software Depots Overview: Creating SAS Software Depots There are two ways you can create a SAS Software Depot:

3 Download SAS software. When you download a SAS order, the SAS Download Manager automatically creates a SAS Software Depot on your system.

3 Run the SAS Deployment Wizard. Creating SAS Software Depots is an option on one of the wizard pages. Before creating a depot, make sure that you have met the necessary requirements described in the following section.

30

Prerequisites for Creating a SAS Software Depot

4

Chapter 3

Prerequisites for Creating a SAS Software Depot Before you start creating a SAS Software Depot, make sure that you have met the following prerequisites: 3 Choose a machine that has the following: 3 Internet access: If you are downloading your SAS order, you will need a machine that can access the SAS download Web site. Also, ideally this machine should be networked so that you can perform deployments directly from the machine, without having to physically relocate the depot to another machine. 3 Java SDK for z/OS installed (z/OS only): For more information, go to http://support.sas.com/ thirdpartysupport. 3 a Windowing environment: If you will be creating the depot on a UNIX or a z/OS system, make sure that a windowing environment—such as the Common Desktop Environment or X11—is installed. The program that you use to create the depot has a graphical user interface.

3 Designate a target directory. Decide where you will create the SAS Software Depot. It is helpful if this directory can be shared on a network and accessible to all of the machines on which you will be installing software from the depot. Note: SAS recommends that you not copy a depot from one location to another. Choose a permanent location before you create the depot.

4

3 Grant required access permissions. The SAS installer user must have Write access on the depot target directory. Windows Vista and later requires that you run the SAS Download Manager installation program using administrator privileges. 3 Check disk space requirements. Make sure you have enough free disk space available on the target directory. Finally, just before creating a depot, the SAS Deployment Wizard and the SAS Download Manager both present you with an estimate for required disk space.

Create a Depot by Using the SAS Download Manager A SAS Software Depot contains SAS order data, an initial SAS installation data file, one or more deployment plan files, order data, and product data. The depot also contains the SAS Deployment Wizard executable—the tool required to install and initially configure SAS. Note: There is no expiration date for downloading your SAS order. However, if the time period for your initial SAS installation data file has expired, you will have to obtain a current SAS installation data file before you can run the SAS Deployment Wizard. 4 Before you can create a depot by using the SAS Download Manager, you must first download and install the manager itself. The installer automatically launches the SAS Download Manager after installing it. Therefore, the following procedure actually consists of three logical sections: 1 downloading the SAS Download Manager

Creating a SAS Software Depot

4

Create a Depot by Using the SAS Download Manager

31

2 installing the SAS Download Manager 3 downloading a SAS order and creating a software depot using the SAS Download

Manager Although these sections flow one after the other, at the end of each section, you can stop and resume the process later. Follow these steps to download a SAS software order and automatically create a depot by using the SAS Download Manager: 1 Locate your software order e-mail sent by SAS. In this e-mail, find the URL for the SAS Web site from where you will download the SAS Download Manager. Note: It is very important that you locate your original software order e-mail for the correct order and SAS installation key to download the software. You cannot use a renewal order number. The renewal order is a license update and it cannot be used to download software. If you cannot locate your original software order e-mail, contact your SAS Installation Representative or SAS Contracts at the following URLs: http://support.sas.com/adminservices/contact.html http://support.sas.com/adminservices/sasrep.html http://support.sas.com/techsup/license

4

2 Ensure that you have fulfilled the necessary requirements described in

“Prerequisites for Creating a SAS Software Depot” on page 30. 3 Log on to the machine as a SAS Software Depot administrator or a user with

depot Read, Write, and Execute privileges. Note: Consider designating one or a few users to serve as SAS Software Depot administrators. Persons needing to deploy SAS software or to apply future SAS software maintenance require depot Read and Execute privileges. Depot administration tasks such as initially creating the depot, storing SAS installation data files, and updating order details require depot Write privileges. Windows Vista and later requires that you run the SAS Download Manager installation program using administrator privileges. 4 4 Launch a Web browser and navigate to the URL specified in your software order

e-mail. 5 At the prompt in the dialog box, select Save it to disk.

6 Choose a path accessible to the machine to save the download.

32

Create a Depot by Using the SAS Download Manager

4

Chapter 3

Your download begins.

7 When your browser has finished downloading the SAS Download Manager, you

can install it. Perform the step appropriate for your operating system:

3 Windows: In Windows Explorer, navigate to the download path and double-click the download’s filename. For example, on Windows machines: esdclient.exe. Note: Windows Vista and later requires that you run the SAS Download Manager installation program using administrator privileges. Right-click esdclient.exe, select Run as administrator, and provide Windows administrative credentials.

4

3 UNIX and z/OS: In a console, navigate to the download path and type the download’s filename. On 64–bit enabled Solaris, for example: ./Setup_Solaris_Sparc. Note: Remember to assign execute permissions before running the downloaded file. For more information, refer to your UNIX or z/OS documentation. 4 You should see the SAS Download Manager installer welcome page.

Creating a SAS Software Depot

4

Create a Depot by Using the SAS Download Manager

8 Choose a path where you want to install the SAS Download Manager.

9 Review the path and disk space requirements, and make one of the following

choices:

3 Click Next to begin installing the SAS Download Manager in the target directory. 3 Click Back to navigate to earlier pages to change installation information previously entered. 3 Click Cancel to terminate the install session. Note that you will lose the information previously entered.

33

34

Create a Depot by Using the SAS Download Manager

4

Chapter 3

The installation begins.

10 When you see a page similar to the following, the installation is complete. Click

Finish to dismiss the installation program.

Creating a SAS Software Depot

4

Create a Depot by Using the SAS Download Manager

35

The installer automatically launches the SAS Download Manager. Note: If you want to run the download manager at a later time, you can run it using the method appropriate for your operating system: 3 Windows: Start

I Programs I SAS I SAS Download Manager 1.4

3 UNIX and z/OS:

installation-directory/SAS/SASDownloadManager/1.4/esdclient.sh&

4

11 Run the SAS Download Manager and choose the language in which the SAS

Deployment Wizard will display messages and prompts.

36

Create a Depot by Using the SAS Download Manager

4

Chapter 3

12 At some sites, you might see the page that prompts for proxy information. If so,

supply the necessary proxy server settings for the SAS Download Manager to access the Internet. If needed, contact your site’s system administrator for help with these settings.

13 When prompted, enter your order number and SAS installation key.

14 Confirm the list of SAS offerings contained in your order. If you want, you can

update the description for your order and include any notes to distinguish it from

Creating a SAS Software Depot

4

Create a Depot by Using the SAS Download Manager

37

other SAS orders. The SAS Deployment Wizard will display this order information during the SAS installation.

Note: At any time after the download, you can run the SAS Deployment Wizard to add or modify SAS order information details. For more information, see “Change Order Details” on page 45. 4 15 Specify a location where you want to download SAS and build the SAS Software Depot. For more information, see “Prerequisites for Creating a SAS Software Depot” on page 30.

38

Create a Depot by Using the SAS Download Manager

4

Chapter 3

16 If the directory you specify does not exist, the wizard prompts you. If you want it

to create the directory for you, click Yes.

17 The SAS Download Manager has finished collecting order input. This is your last

opportunity to change any information before downloading the SAS order and writing files to the target directory. Make one of the following choices: 3 Click Download to begin downloading the SAS order and writing files in the target directory. 3 Click Back to navigate to earlier pages to change order information previously entered. 3 Click Cancel to terminate the SAS Download Manager session. Note that you will lose the information previously entered. Note: SAS tracks downloads and counts only a complete download toward your download limit. 4

The SAS Download Manager begins downloading, uncompressing, and creating a depot of your SAS order.

Creating a SAS Software Depot

4

Create a Depot by Using the SAS Download Manager

When you see a page similar to the following with the progress indicator at 100%, the SAS Download Manager is finished:

18 Click Next to go to the final page, which describes post-download instructions.

39

40

Create a Depot by Using the SAS Deployment Wizard

4

Chapter 3

19 Click Finish to close the SAS Download Manager. 20 To continue with the software installation, proceed to Chapter 4, “Installing

Third-Party Products,” on page 53.

Create a Depot by Using the SAS Deployment Wizard You can use the SAS Deployment Wizard to create a copy of your SAS Software Depot in another directory. If the new depot location is a remote directory on another machine, the directory must be on a shared network drive accessible from the machine running the wizard. To create a depot on a machine that does not have shared network storage, you must use another mechanism such as SFTP or SCP to copy the depot. (For more information about these programs, refer to your operating system documentation.) To create a SAS Software Depot by using the SAS Deployment Wizard, follow these steps: 1 Log on to the machine that will contain the depot as a SAS Software Depot administrator or a user with depot Read, Write, and Execute privileges. Note: Consider designating one or a few users to serve as SAS Software Depot administrators. Persons needing to deploy SAS software or to apply future SAS software maintenance require depot Read and Execute privileges. Depot administration tasks such as initially creating the depot, storing SAS installation data files, and updating order details require depot Write privileges. 4 2 Ensure that you have fulfilled the necessary requirements described in “Prerequisites for Creating a SAS Software Depot” on page 30. 3 Start the SAS Deployment Wizard, using one of two methods: 3 If you are starting the wizard from removable media, proceed as follows, depending on your operating system: 3 Windows: The setup.exe program starts automatically when the media is inserted into the drive.

Creating a SAS Software Depot

4

Create a Depot by Using the SAS Deployment Wizard

41

Note: If the SAS Deployment Wizard does not start automatically, open Windows Explorer, navigate to the root of the DVD, and double-click setup.exe. 4 3 UNIX: Navigate to the media’s root directory, and type ./setup.sh at a command prompt. 3 z/OS: Navigate to the media’s root directory, and type ./setup.rexx at a command prompt.

3 If you are starting the wizard from an existing SAS Software Depot, proceed as follows: Navigate to the depot’s root directory and do one of the following, depending on your operating system: 3 Windows: Double-click setup.exe. 3 UNIX: Type ./setup.sh at a command prompt. 3 z/OS: Type ./setup.rexx at a command prompt. 4 Choose the language in which the SAS Deployment Wizard will display messages

and prompts. 5 Select Create a New SAS Software Depot. Do not select Install SAS Software.

6 Confirm the list of SAS offerings contained in your order.

If you want, you can update the description for your order and include any notes to distinguish it from other SAS orders. The SAS Deployment Wizard will display this order information during the SAS installation.

42

Create a Depot by Using the SAS Deployment Wizard

4

Chapter 3

Note: At any time after the download, you can rerun the SAS Deployment Wizard to add or modify SAS order information details. For more information, see “Change Order Details” on page 45. 4 7 If you have multiple orders in your depot, you must pick the order for which you

want to create a new depot. 8 Specify a location where you want to download SAS and build the software depot.

(This location can be shared storage that physically resides on another machine.) For more information, see “Prerequisites for Creating a SAS Software Depot” on page 30.

Creating a SAS Software Depot

4

Create a Depot by Using the SAS Deployment Wizard

43

9 If the directory you specify does not exist, the wizard prompts you. If you want it

to create the directory for you, click Yes.

10 The SAS Deployment Wizard has finished collecting order input. This is your last

opportunity to change any information you have provided before the wizard begins writing files to the target directory. Make one of the following choices:

3 Click Start to begin creating the depot in the target directory. 3 Click Back to navigate to earlier wizard pages to change order information previously entered.

3 Click Cancel to terminate the wizard session. Note that you will lose order information previously entered.

11 If you are running the SAS Deployment Wizard from removable media, the SAS

Deployment Wizard prompts you for a DVD. Continue to supply discs as prompted. Note: If you are working on a UNIX system without an automounter, mount the DVD drive. For information about the privileges required to mount a device and the syntax of the mount command for your system, see the SAS Deployment Wizard User’s Guide, which is available on the Install Center: http://support.sas.com/documentation/installcenter/. (Search for SAS Deployment Wizard User’s Guide.) 4 The SAS Deployment Wizard begins creating a depot of your SAS order.

44

Create a Depot by Using the SAS Deployment Wizard

4

Chapter 3

12 When you see a page similar to the following with the progress indicator at 100%,

the SAS Deployment Wizard is finished:

13 Click Next to go to the final page, which contains instructions for what to do after

creation of the software depot. 14 Click the depotsummary.html link on the page to review the SAS QuickStart Guide.

Creating a SAS Software Depot

4

Change Order Details

45

15 Click Finish to close the SAS Deployment Wizard. 16 If you are using removable media on a UNIX system where an automounter is

being used, use the eject command to remove the DVD. On a UNIX system without an automounter, you must unmount the drive by using the umount command and then manually opening the drive. For information about the umount command that is needed to unmount a device on your system, see the SAS Deployment Wizard User’s Guide, which is available on the Install Center: http://support.sas.com/documentation/installcenter/. (Search for SAS Deployment Wizard User’s Guide.) 17 To continue with the software installation, proceed to Chapter 4, “Installing Third-Party Products,” on page 53.

Managing SAS Orders Overview: Managing SAS Orders Using the SAS Deployment Wizard, you can do the following with your SAS order: 3 change order details 3 delete an order 3 create an image of your order to write to CDs or DVDs

Change Order Details Being able to identify a SAS order is important, especially when your SAS Software Depot contains multiple orders. To change the details of a SAS order, follow these steps: 1 Log on to the depot machine as a SAS Software Depot administrator or a user with depot Read, Write, and Execute privileges.

46

Change Order Details

4

Chapter 3

Note: Consider designating one or a few users to serve as SAS Software Depot administrators. Persons needing to deploy SAS software or to apply future SAS software maintenance require depot Read and Execute privileges. Depot administration tasks such as initially creating the depot, storing SAS installation data files, and updating order details require depot Write privileges. 4 2 Start the SAS Deployment Wizard. Navigate to the SAS Software Depot’s root directory and, depending on your operating system, do the following: 3 Windows: Double-click setup.exe.

3 UNIX: Type ./setup.sh at a command prompt.

3 z/OS: Type ./setup.rexx at a command prompt. 3 Choose the language in which the SAS Deployment Wizard will display messages

and prompts. 4 Select Manage this SAS Software Depot.

5 Choose the order for which you want to change details, and then select Change

Details.

Creating a SAS Software Depot

4

Delete an Order

47

6 Update the description for your order and include any notes about your order that

might help you to distinguish it from any other SAS orders. The SAS Deployment Wizard will display this order information during the SAS installation.

7 When you are finished adding order details, select OK. 8 Select Finish to close the SAS Deployment Wizard.

Delete an Order To delete a SAS order, follow these steps: CAUTION:

It is a best practice to always make sure that you have backed up the SAS Software Depot before deleting an order. Keep in mind that there are limits on the number of times you can download an order from SAS. 4 1 Log on to the depot machine as a SAS Software Depot administrator or a user

with depot Read, Write, and Execute privileges. Note: Consider designating one or a few users to serve as SAS Software Depot administrators. Persons needing to deploy SAS software or to apply future SAS

48

Delete an Order

4

Chapter 3

software maintenance require depot Read and Execute privileges. Depot administration tasks such as initially creating the depot, storing SAS installation data files, and updating order details require depot Write privileges. 4 2 Start the SAS Deployment Wizard. Navigate to the SAS Software Depot’s root directory, and, depending on your operating system, do the following:

3 Windows: Double-click setup.exe. 3 UNIX: Type ./setup.sh at a command prompt.

3 z/OS: Type ./setup.rexx at a command prompt. 3 Choose the language in which the SAS Deployment Wizard will display messages

and prompts. 4 Select Manage this SAS Software Depot.

5 Choose the order you want to delete, and then select Delete Order.

Creating a SAS Software Depot

4

Create a Disc Image of Your Order

49

6 Confirm that you want to delete the order by selecting Yes.

The SAS Deployment Wizard begins to delete your order. When all the order’s files have been removed, the Manage SAS Software Depot page appears again, without the deleted order listed. 7 Select Finish to close the SAS Deployment Wizard.

Create a Disc Image of Your Order If you have SAS running on remote sites that don’t have access to the network on which your SAS Software Depot resides, you can use the SAS Deployment Wizard to create an ISO image of your SAS software order. Then, using a media creation tool of your choice, you can write the image to the removable media format that you specify: either CDs or DVDs. You can create a disc image on a per order basis only. If your SAS Software Depot consists of more than one order, then you have to make multiple disc images. To create a disc image of your SAS order, follow these steps: 1 Log on to the depot machine as a SAS Software Depot administrator or a user with depot Read, Write, and Execute privileges. Note: Consider designating one or a few users to serve as SAS Software Depot administrators. Persons needing to deploy SAS software or to apply future SAS software maintenance require depot Read and Execute privileges. Depot administration tasks such as initially creating the depot, storing SAS installation data files, and updating order details require depot Write privileges. 4

50

Create a Disc Image of Your Order

4

Chapter 3

2 Start the SAS Deployment Wizard. Navigate to the SAS Software Depot’s root

directory, and, depending on your operating system, do the following:

3 Windows: Double-click setup.exe. 3 UNIX: Type ./setup.sh at a command prompt.

3 z/OS: Type ./setup.rexx at a command prompt. 3 Choose the language in which the SAS Deployment Wizard will display messages

and prompts. 4 Select Manage this SAS Software Depot.

5 Choose the order for which you want to create a disc image, and then select

Create Media-Ready Image.

Creating a SAS Software Depot

4

Create a Disc Image of Your Order

51

6 Choose the type of media (CDs or DVDs) for which you want to create an image of

your SAS software order. Also, provide the path where you want the SAS Deployment Wizard to write this image. When you are ready, select Start.

The SAS Deployment Wizard begins writing SAS order files to the target directory. 7 When the progress indicator displays 100%, the image is complete and you can

select OK.

8 Select Finish to close the SAS Deployment Wizard.

The file system that the SAS Deployment Wizard has created is an ISO image of your SAS order that is logically arranged into directories that map to either

52

Create a Disc Image of Your Order

4

Chapter 3

CD-ROM or DVD disc. Each directory also contains a summary to enable you to maintain media labels.

9 Using a media creation tool of your choice, you can now write the installable image

of your SAS order to the type of removable media that you specified earlier: either CDs or DVDs.

53

CHAPTER

4 Installing Third-Party Products Overview: Installing Third-Party Products 53 About Installing Third-Party Products 54 Review Web Application Server Configuration Documentation 54 Choose Whether to Automatically Configure Your Web Application Server Choose Whether to Automatically Deploy the SAS Web Applications 56 Install Third-Party Products Using the SAS Software Depot 56 Install Third-Party Products Using the Software Web Site 57 Installing Platform Suite for SAS 57 What Is Platform Suite for SAS? 57 Where to Install Platform Suite for SAS 58 Install Platform Suite for SAS 58 Pre-installation Checklists for Third-Party Products 58 Java Development Kit (JDK) 58 WebLogic Server 59 WebSphere Application Server 60 JBoss Application Server 61 Platform Suite for SAS 63

55

Overview: Installing Third-Party Products Third-party products play an important role in the SAS Intelligence Platform. For example, if your system includes Web applications such as SAS Web Report Studio or the SAS Information Delivery Portal, you will need to install third-party products such as a Java Development Kit (JDK) and a Web application server in order to compile and execute these applications. Installing required third-party software is the fourth of five steps in deploying SAS: 1. Review additional documentation. 2. Create operating system users and groups and designate ports. 3. Create a SAS Software Depot.

I 4. Install required third-party software. 5. Install and configure SAS.

54

About Installing Third-Party Products

4

Chapter 4

About Installing Third-Party Products The SAS desktop client applications and majority of Java applications are supported on Microsoft Windows systems only. The exception is SAS Management Console, which also runs on several UNIX platforms. All of the Java applications require the Java Runtime Environment (JRE), which includes a Java Virtual Machine (JVM) that executes the application and a set of standard Java class libraries. The SAS Deployment Wizard will install the default version of the JRE with which SAS has been tested. If a different version of the JRE is required, it can be obtained from the appropriate vendor’s Web site. Links to the appropriate JRE vendor’s Web site can be found on the SAS 9.2 third-party support site located at http://support.sas.com/ resources/thirdpartysupport/v92. During a first-time SAS 9.2 deployment, the SAS Deployment Wizard prompts you for the version of the JRE that you want to use with the SAS Java applications. Your options are to have the deployment wizard install a JRE that SAS has certified to run with SAS 9.2, or to point to a JRE that you have already installed. (In most situations where you are updating or adding a product to SAS 9.2, the deployment wizard does not prompt you for a JRE. However, you can override this behavior. For more information, see “Specify a Different JRE” on page 124.) On z/OS only, your options are to point to a JRE that you have already installed, or install your software without a JRE. Before you can install and configure a SAS 9.2 middle tier, you must have installed one of the Web application servers supported by SAS. If you are using JBoss Application Server or WebLogic Server, then you must have the Java Development Kit (JDK) installed. (WebSphere Application Server ships with its own version of the JDK which is installed when you install WebSphere Application Server.) The SAS Deployment Wizard prompts you for paths to these third-party software products, and will not allow you to complete the SAS deployment without this software installed. Use the manufacturer’s distribution package to install the JDK. Make sure that you have a properly defined Java environment. (On Windows, a reboot of the machine might be required.) Open a DOS command prompt on Windows, or a console on UNIX, and at the operating system prompt, type the following command to validate the Java environment and return the version information for the installed package: java -version. Use the manufacturer’s distribution package to install your Web application server, applying any necessary hotfixes and verifying the server’s operation. For more information about configuration steps for your Web application server, go to http://support.sas.com/resources/thirdpartysupport/v92 and search for the product name of your Web application server.

Review Web Application Server Configuration Documentation SAS provides post-installation documentation that describes how to configure your Web application server. For example, some of the topics include information about how to run your Web application server on different ports, install SAS with one user account, install your Web application server with a different user account, and so on. For more information about configuration steps for your Web application server, go to http://support.sas.com/resources/thirdpartysupport/v92 and search for the product name of your Web application server.

Installing Third-Party Products

4

Choose Whether to Automatically Configure Your Web Application Server

55

Choose Whether to Automatically Configure Your Web Application Server The SAS Deployment Wizard gives you the option of automatically building and configuring the SAS Web applications as well as configuring a Web application server for use with SAS 9.2. (To use this wizard feature, make sure that your Web application server is not running before you start the wizard. For WebSphere, it’s necessary to stop all deployment manager servers, all node agent servers, and all application servers before running the wizard.) When the SAS Deployment Wizard configures the SAS 9.2 middle tier, by default, it automatically creates and configures an instance of a Web application server to host the SAS Web applications. The wizard creates a series of configuration files that enable you to run an instance of your Web application server with the SAS Web applications. The automatic configuration feature and the automatic deployment feature (described later) provide the opportunity to enable the automatic configuration of your Web application server, but not deploy the applications if you prefer to review the configuration to ensure it meets your site’s needs. You can then deploy the SAS Web applications afterward. Some of the configuration tasks performed by the SAS Deployment Wizard include setting options such as the following:

3 3 3 3 3 3

HTTP ports optimized JVM options a mail session JAAS login modules for SAS services JMS queues a JDBC data source

Depending on the Web application server you are using, the SAS Deployment Wizard modifies your Web application server configuration differently: WebLogic makes no changes to the WebLogic installation directory. The deployment wizard creates a sample domain in the SAS configuration directory. WebSphere creates deployment manager and application server profiles in the WebSphere installation directory. JBoss creates a Web application server instance in the JBoss installation directory. The deployment wizard adds a start-stop script to the JBoss bin directory. JAR files for the SAS Drivers for JDBC are copied to the JBoss lib directory. If you choose to disable this feature during SAS Deployment Wizard execution, the wizard generates instructions that describe how to perform these configuration steps manually after you finish running the wizard. To disable the auto configuration feature, run the wizard using either the Typical or Custom prompting levels. For more information, see “Interactive Prompting Levels” on page 69. For samples of the instructions that describe how to manually configure your Web application server for SAS Web applications, go to the Third-Party Software Web site at http://support.sas.com/resources/thirdpartysupport/v92 and search for the product name of your Web application server.

56

Choose Whether to Automatically Deploy the SAS Web Applications

4

Chapter 4

Choose Whether to Automatically Deploy the SAS Web Applications In addition to the automatic configuration feature, the SAS Deployment Wizard offers a feature to automatically start the Web application server and deploy the SAS Web applications. (This feature is turned on by default.) Regardless of whether you choose to automatically deploy your SAS Web applications, when building Web applications, the wizard also automatically explodes Web application archive files (.ear files). For more information, go to http://support.sas.com/resources/ thirdpartysupport/v92. To disable the auto deployment feature, run the wizard using either the Typical or Custom prompting levels. For more information, see “Interactive Prompting Levels” on page 69.

Install Third-Party Products Using the SAS Software Depot Some third-party products ship with SAS 9.2. Such products’ installation files and documentation are located in the SAS Software Depot under the third_party directory.

Figure 4.1

third_party Directory in the SAS Software Depot

Platform Suite for SAS is an example of one third-party application that you install in this way. To determine whether any of your third-party software is distributed with your order, refer to your SAS Software Summary that resides in your SAS Software Depot in your order_number directory under install_doc. For example:

Installing Third-Party Products

4

What Is Platform Suite for SAS?

57

C:\SAS Software Depot\install_doc\order_number\ordersummary.html

Install Third-Party Products Using the Software Web Site SAS maintains a third-party software Web site to help you do the following: 3 determine what version of the product to install 3 obtain the product, if you don’t already have it 3 find installation instructions 3 learn about any patches required Note: Some third-party software ships with your SAS order. For more information, see “Install Third-Party Products Using the SAS Software Depot” on page 56. If you are installing Platform Process Manager, Platform LSF, or Platform Grid Management Service, you must use the installation instructions and installation programs provided in your SAS order. For more information, see “Installing Platform Suite for SAS” on page 57. 4 To install the Java Development Kit or a Web application server, complete these steps: 1 Go to the Third-Party Software Web site at http://support.sas.com/ resources/thirdpartysupport/v92. 2 Select the link for the product (or type of product) that you are installing. There are columns that either have links directly to the vendor’s site, or an indication that the third-party software ships with SAS. 3 Install the product. For most installations, you can use the instructions provided by the vendor. For products that are more complex to install—such as the Web application servers—the Third-Party Software Web site contains links to brief installation instructions. These instructions are not meant to replace the vendor documentation. However, they will enable you to create a simple configuration that will work well with your SAS software. Note to users in Russia: SAS cannot export the Java Runtime Environment (JRE) to Russia. You will need to locate the appropriate link on the Third-Party Software Web site and download the JRE. Install it in the default location, and it will be ready for use when you install your SAS software.

Installing Platform Suite for SAS What Is Platform Suite for SAS? If you will use products from Platform Computing Incorporated either for scheduling or for grid computing, you must install several of the products from the Platform Suite for SAS offering. Platform Suite for SAS includes three products: Platform Process Manager provides scheduling capabilities. Process Manager submits jobs to Platform LSF and manages dependencies between jobs. Platform LSF (Load Sharing Facility)

58

Where to Install Platform Suite for SAS

4

Chapter 4

manages resource requirements and provides for load balancing. Platform Grid Management Service includes a monitoring daemon that enables administrators to monitor the load on machines running Platform LSF.

Where to Install Platform Suite for SAS If you are interested in using the Platform Suite for SAS to perform scheduling tasks for objects like SAS Data Integration Studio jobs or SAS Web Report Studio reports, then you must install Platform Process Manager on the machine that you want to use as your scheduling server. When you install Platform Process Manager, Platform LSF will be installed as well. If you will be using the Platform Suite for SAS for grid computing, you must install Platform LSF and the Platform Grid Management Service. If you want to schedule jobs to run on the grid, you must install Platform Process Manager as well. For information about where to install each of these products, see “SAS Grid Topology” in Grid Computing in SAS.

Install Platform Suite for SAS Platform Suite for SAS is distributed with SAS. You install these products directly from the SAS Software Depot, using the installation instructions and installation programs that reside in your depot under the third_party directory. You can also find the Platform Suite for SAS installation instructions on the SAS Scalability and Performance focus area on the Web at http://support.sas.com/rnd/ scalability/grid/gridinstall.html.

Pre-installation Checklists for Third-Party Products As you install third-party products, print and fill out the appropriate third-party software checklists. Note: You must have the necessary third-party software installed on the current machine, or the utility that you use to deploy SAS, the SAS Deployment Wizard, will not let you complete your SAS deployment. 4

Java Development Kit (JDK) For more information about JDK version requirements, go to http:// support.sas.com/thirdpartysupport/ and locate “Other Third Party Software Products ”under the applicable SAS release. Note: These checklists are superseded by more complete and up-to-date checklists that can be found at http://support.sas.com/installcenter/plans. This Web site also contains a corresponding deployment plan and an architectural diagram. 4

Installing Third-Party Products

4

WebLogic Server

59

Table 4.1 Java Development Kit Description

Default Value

Product version

Dependent on the Web application server and the operating system.

Actual Value

See http://support.sas.com/ thirdpartysupport/. Installation directory

Not applicable

WebLogic Server For more information about pre- and post-installation configuration steps for the Oracle WebLogic Server, go to http://support.sas.com/thirdpartysupport/ and locate “Web Application Servers and HTTP Servers” under the applicable SAS release. To change the default port, you must use the SAS Deployment Wizard Typical or Custom prompting level. For more information, see Select Configuration Prompting Level. Note: These checklists are superseded by more complete and up-to-date checklists that can be found at http://support.sas.com/installcenter/plans. This Web site also contains a corresponding deployment plan and an architectural diagram. 4 Table 4.2 WebLogic Server Description

Default Value

Product version

9.2

Installation directory

Not applicable

Name of domain

SASDomain

Name of managed servers

SASServer1, SASServer2, and so on

WebLogic Nodemanager port

5556

Non-secure listen port for managed servers

7001, 7101, (additional managed servers increment by 100)

Actual Value

60

WebSphere Application Server

4

Chapter 4

Description

Default Value

Secure listen port for managed servers

7002, 7102, (additional managed servers increment by 100)

Listen port for administration server

7501

Actual Value

WebSphere Application Server For more information about pre- and post-installation configuration steps for the IBM WebSphere Application Server, go to http://support.sas.com/ thirdpartysupport/ and locate “Web Application Servers and HTTP Servers” under the applicable SAS release. To change the default port, you must use the SAS Deployment Wizard Typical or Custom prompting level. For more information, see Select Configuration Prompting Level. Note: These checklists are superseded by more complete and up-to-date checklists that can be found at http://support.sas.com/installcenter/plans. This Web site also contains a corresponding deployment plan and an architectural diagram. 4 Table 4.3 WebSphere Application Server Description

Default Value

Product version

6.1.0.21

Name of application servers

SASServer1, SASServer2, and so on

Profile name for managed nodes (contains node agent and Web application server)

SASlocal-hostname01, SASlocal-hostname02, and so on

Node name for managed nodes

SASlocal-hostname01Node, SASlocal-hostname02Node, and so on

Profile name for deployment manager

SASDmgr01

Cell name for deployment manager

SASDmgr01Cell

Node name for deployment manager

SASDmgr01Node

SOAP port for administrative console

8879

Actual Value

Installing Third-Party Products

Description

Default Value

SOAP ports for application servers

8880, 8881 (additional application servers increment by one)

Secure HTTPS port for administrative console

9043

Secure HTTPS ports for application server

9044, 9045 (additional application servers increment by one)

Non-secure HTTP port for administrative console

9060

Non-secure HTTP ports for application server

9080, 9081, (additional application servers increment by one)

RMI port for administrative console

9809

RMI ports for application servers

9811, 9812, (additional application servers increment by one)

4

JBoss Application Server

61

Actual Value

JBoss Application Server For more information about pre- and post-installation configuration steps for the JBoss Application Server, go to http://support.sas.com/thirdpartysupport/ and locate “Web Application Servers and HTTP Servers” under the applicable SAS release. To change the default port, you must use the SAS Deployment Wizard Typical or Custom prompting level. For more information, see Select Configuration Prompting Level. Note: These checklists are superseded by more complete and up-to-date checklists that can be found at http://support.sas.com/installcenter/plans. This Web site also contains a corresponding deployment plan and an architectural diagram. 4 Table 4.4 JBoss Application Server Description

Default Value

Product version

4.2.

Name of managed servers

SASServer1, SASServer2, and so on

RMI port for managed servers

1099, 1199, (additional managed servers increment by 100)

Actual Value

62

JBoss Application Server

4

Chapter 4

Description

Default Value

Listen port for managed servers

8080, 8180, (additional managed servers increment by 100)

Secure listen port for managed servers

8443, 8543, (additional managed servers increment by 100)

Actual Value

Installing Third-Party Products

4

Platform Suite for SAS

63

Platform Suite for SAS For more information about Platform Suite for SAS version requirements, go to http://support.sas.com/thirdpartysupport/ and locate “Other Third Party

Software Products ”under the applicable SAS release. Note: These checklists are superseded by more complete and up-to-date checklists that can be found at http://support.sas.com/installcenter/plans. This Web site also contains a corresponding deployment plan and an architectural diagram. 4 Table 4.5 Platform Suite for SAS Description

Default Values

Platform Process Manager port

1966

Product version

7.0

Platform LSF ports

6878, 6881, 6882, 7869, 7870, 7871, 7872

Product version

7.02

Platform Grid Management Service port

1976

Product version

7.0

Actual Values

64

65

CHAPTER

5 Installing and Configuring Your SAS Software Overview: Installing and Configuring Your SAS Software 65 Preparing to Install and to Configure 66 SAS Deployment Wizard Options 66 About Deployment Plans 66 Content Repository Considerations 67 Installation Order Rules for Multiple Machine Deployments 67 IPv6 Windows Machines that Communicate with SAS Foundation Servers 67 Interactive Prompting Levels 69 Installing SAS OnlineDoc for the Web 74 Install and Configure SAS Interactively 76 Validate the SAS 9.2 Servers 92 About SAS Deployment Tester 95 Automating the SAS Installation on Multiple Machines 95 Overview of Automating the SAS Installation on Multiple Machines 95 Recording a SAS Deployment Wizard Response File 96 Playing Back a SAS Deployment Wizard Response File 97 Overview of Playing Back a SAS Deployment Wizard Response File 97 Installing SAS in Quiet Mode 97 Managing a Machine Reboot During Playback (Windows) 98 Installing SAS in Partial Prompt Mode 98 Installing SAS in Full Prompt Mode 99 Verifying the Playback Install 99 Monitoring the SAS Deployment Wizard During Playback 100 More About Monitoring the SAS Deployment Wizard on UNIX and z/OS 101

Overview: Installing and Configuring Your SAS Software This chapter describes how to use the SAS Deployment Wizard to install and configure all of the SAS software components called for in your deployment plan on each host in your environment. Installing and configuring SAS is the fifth and final step in deploying SAS. 1. Review additional documentation. 2. Create operating system users and groups and designate ports. 3. Create a SAS Software Depot. 4. Install required third-party software.

66

Preparing to Install and to Configure

4

Chapter 5

I 5. Install and configure SAS.

Preparing to Install and to Configure 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:

3 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” on page 76.

3 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” on page 95.

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.

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

3 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

Installing and Configuring Your SAS Software

4

IPv6 Windows Machines that Communicate with SAS Foundation Servers

67

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:

3 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” on page 69. 3 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: 3 Always install SAS software on the metadata server machine first. 3 Install the SAS application servers (such as workspace or stored process servers) on machines other than the metadata server machine. 3 Install the middle tier with SAS Foundation Services (that is, Remote Services). 3 Install the middle tier with SAS Web Infrastructure Platform 3 Install the middle tier with other Web applications (such as SAS BI Dashboard, SAS Web OLAP Viewer, SAS Web Report Studio, and so on). 3 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: 3 uses IPv6 (Internet Protocol version 6) Note: For more information, see “Designating Ports and Multicast Addresses” on page 19. 4 3 runs Windows 3 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

68

IPv6 Windows Machines that Communicate with SAS Foundation Servers

4

Chapter 5

SAS Software check box is not selected. For more information, see “Install and Configure SAS Interactively” on page 76.

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” on page 76.

Installing and Configuring Your SAS Software

4

Interactive Prompting Levels

69

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

70

Interactive Prompting Levels

4

Chapter 5

Table 5.1 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

*

X

X

X

X

X

X

X

X

X

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

Installer account credentials

Metadata server port and host name Unrestricted administrator account credentials Trusted user account credentials

*

*

*

X

X

*

X

X

Windows options: create shortcuts option

X

X

X

X

X

X

Anonymous Web access

X

X

First user account credentials

X

X

Object spawner port

X

X

Local machine name

Windows shortcuts scope Integrated Windows authentication (IWA) *

*

Installing and Configuring Your SAS Software

Configuration Option in the SAS Deployment Wizard

4

Interactive Prompting Levels

Prompt Level That Displays the Option Express

Typical

Custom

X

X

X

X

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

X

X

Metadata utility SAS DATA step batch server deployed jobs information*

X

X

Deployment Tester port and JUnit JAR file

X

X

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

X

X

X

X

X

X

X

X

Shared themes for SAS Web applications host name, protocol, and port

X

X

IP multicast address, UDP port, TTL, authentication token option1*

X

X

SAS Remote Services application host name and port

X

X

Event broker HTTP port and admin port

X

X

X

X

Object spawner port bank ports SAS Application Server: server context

*

Workspace server port *

Table server port

*

Web application server automatic configuration

*

*

Web application server administrator

WebSphere application server node SOAP port and RMI port *

Web application server: managed server name and ports Web application server automatic deployment

Enable SAS Web Report Studio scheduling

*

*

BI Web Services: new Web services deployment method

X

X

*

X

X

SAS Information Delivery Portal samples

X

X

SAS Content Server repository directory

71

72

Interactive Prompting Levels

4

Chapter 5

Configuration Option in the SAS Deployment Wizard

Prompt Level That Displays the Option Express

Typical

Custom

DataFlux Integration server name and host name

X

X

DataFlux Integration server: server component name

X

X

Database type for SAS Shared Services

X

X

SAS BI Portlets RMI port and Portal server

X

X

SAS BI Portlets Portal server connection information

X

X

2

Select products to configure

X

*

Authentication domain

X

Windows options: run as managed scripts or services

*

Metadata server: server librefs

X 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

*

SAS BI Web Services authentication method

X *

X

SAS General Servers group

X

SAS Table Server Admins group

X

SAS BI Web Services Users group

X

Common directories for logs, users, data, 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

Installing and Configuring Your SAS Software

4

Interactive Prompting Levels

Prompt Level That Displays the Option

Configuration Option in the SAS Deployment Wizard

Express

Typical

Custom

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 *

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

Query cache library directory and libref

Web application server: proxy information

*

X *

WebSphere application server node additional JVM options

X

73

74

Installing SAS OnlineDoc for the Web

4

Chapter 5

Configuration Option in the SAS Deployment Wizard

Prompt Level That Displays the Option Express

Typical

Custom

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 and typical prompting when the configuration directory and level pre-exists. 2 Option displays during express 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.)

Installing and Configuring Your SAS Software

4

Installing SAS OnlineDoc for the Web

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.

75

76

Install and Configure SAS Interactively

4

Chapter 5

Install and Configure SAS Interactively Installing and configuring SAS interactively with the SAS Deployment Wizard consists of two main phases: 3 Providing installation information such as the following: 3 installation type (planned or unplanned) 3 deployment plan location (if planned) 3 machine type (single machine, server machine, and so on) 3 SAS components to be installed on the machine 3 valid paths to any required pre-installed, third-party software

3 Providing configuration information such as the following: 3 prompting level (express, typical, custom) 3 SAS components to be configured on the machine 3 configuration directory name 3 single sign-on preference (Windows only) 3 required user account credentials 3 server port numbers This topic describes some of the more important configuration pages that you will encounter during the configuration phase of a SAS 9.2 deployment. The type and number of configuration-related pages that you will see depend upon the prompt level that you choose, the SAS tier that you are currently deploying, and the contents of your SAS 9.2 custom order. For information about all SAS Deployment Wizard prompts, see the online Help for the wizard page in question. To install and configure SAS interactively, complete these steps: 1 Verify that you have performed the earlier required steps outlined in “Overview: Installing and Configuring Your SAS Software” on page 65. Note: A few pages into the SAS installation, the SAS Deployment Wizard prompts you for paths to the requested third-party software. You must have the necessary third-party software installed on the current machine, or the SAS Deployment Wizard will not let you continue with the installation. In this situation, you will have to end the SAS Deployment Wizard session and install the required third-party software before you can continue.

4

2 If you use any garbage collection scripts, temporarily suspend these scripts during

3 4 5

6

7

SAS Deployment Wizard execution. If any wizard temporary files are deleted during wizard execution, configuration failures can occur. Review information about where to source certain SAS content repositories described in the topic, “Content Repository Considerations” on page 67. Review information about SAS Deployment Wizard configuration prompting levels described in the topic, “Interactive Prompting Levels” on page 69. If you are deploying SAS on multiple machines, make sure that you are following the process described in “Installation Order Rules for Multiple Machine Deployments” on page 67. If you are deploying the SAS middle tier and intend on having the SAS Deployment Wizard automatically configure your Web application server, make sure that the server is installed, but not running. If any machines on which your are deploying SAS 9.2 use IPv6, then a different deployment procedure is required. For more information, see “IPv6 Windows Machines that Communicate with SAS Foundation Servers” on page 67.

Installing and Configuring Your SAS Software

4

Install and Configure SAS Interactively

8 Log on to the machine with a user ID that meets the requirements for the

appropriate operating system: 3 Windows: Use an account that is available for the long term (for future SAS maintenance) and is a member of the Administrators group. 3 UNIX: Use the same account on all machines on which you are deploying SAS. Do not use root. 3 z/OS: Use the same account on all machines on which you are deploying SAS. 9 Start the SAS Deployment Wizard from the highest-level directory in your SAS

Software Depot using the command appropriate for your operating system: Table 5.2 Startup Commands for the SAS Deployment Wizard Operating System

Command

Windows

setup.exe -record -deploy

UNIX

setup.sh -record -deploy

z/OS

setup.rexx -record -deploy To use a temporary directory other than /tmp, specify -templocation new-temp-dir.

Note: Using the -record -deploy options causes the wizard to create a response file that records the inputs that you supplied. This can be helpful when you want to repeat the deployment on other machines or when troubleshooting a deployment issue. 4 By default, the deployment wizard writes the response file in the following location: 3 Windows: C:\Documents and Settings\current-user\sdwresponse.properties

3 UNIX and z/OS: ~/sdwresponse.properties

You should see a welcome page similar to the following:

77

78

Install and Configure SAS Interactively

4

Chapter 5

10 Select the language that you want the SAS Deployment Wizard to use when it

displays text. 11 Select Install SAS Software. 12 If you have more than one SAS software order in your depot, the wizard prompts

you to select the order that you want to deploy. 13 Select Perform a Planned Deployment, and make sure that Install SAS Software and Configure SAS Software are both checked.

Note: If any machines on which your are deploying SAS 9.2 use IPv6, then a different deployment procedure is required. For more information, see “IPv6 Windows Machines that Communicate with SAS Foundation Servers” on page 67.

4

14 Specify the location (SAS Home) where you want to install SAS.

Note: The deployment wizard prompts you for SAS Home the first time that you run the wizard. On any subsequent sessions on this machine, the wizard uses the previously specified location for SAS Home. 4 15 Specify the type of deployment plan you are using:

3 customized deployment plan Choose Specify the full path to a customized deployment plan, and then click Browse to navigate to the plan file (plan.xml). 3 standard deployment plan Choose Select a standard deployment plan, and then choose the appropriate plan in the drop-down list. For more information, see “About Deployment Plans” on page 66.

Installing and Configuring Your SAS Software

4

Install and Configure SAS Interactively

16 Select the machine on which you are installing software, and select the SAS

products that you want to install, by doing the following: a Select the machine on which you are installing software from the Machine

drop-down list. Note: If you are deploying SAS on multiple machines, make sure that you are following the process described in “Installation Order Rules for Multiple Machine Deployments” on page 67.

4

b By default, all products displayed will be installed. Deselect any products

that you do not want to install.

79

80

Install and Configure SAS Interactively

4

Chapter 5

17 Specify the location of the SAS installation data file that contains information

about the software that you have licensed for the current machine. CAUTION:

If you do not use the installation data file that supports the products you are planning to install and configure on this machine, you might experience errors later when you are trying to use the products.

4

18 Deselect any languages that you do not want SAS to support. By default, SAS

attempts to support all languages that your machine’s operating system is configured for. 19 The deployment wizard prompts you to do one of the following: (z/OS only) No Java Runtime Environment

Select to have the deployment wizard install your software on z/OS without a Java Runtime Environment (JRE).

(UNIX and Windows only)

(Recommended) select to have the deployment wizard install the required JRE on this machine.

Use the recommended Java Runtime Environment

On UNIX, specify in the text field where you want the deployment wizard to extract the JRE.

Select an existing Java Runtime Environment

Select to specify the path to a JRE that you have already installed on this machine.

For more information, see http://support.sas.com/resources/ thirdpartysupport/v92/jres.html. 20 (z/OS only) Provide input for the following prompts:

Note: For more information, see the Configuration Guide for SAS 9.2 Foundation for z/OS, available on the SAS Install Center (http://support.sas.com/ documentation/installcenter/).

4

3 FTP Batch Generation Specify the fully qualified host name or IP address of the z/OS mainframe machine on which you are deploying SAS. Also supply a valid user ID and password with which the SAS Deployment Wizard will FTP deployment information to the mainframe machine.

3 Specify Jobcard Information Specify the job account, programmer-name, message class, message level, time, and region values. For more information, consult your z/OS documentation.

3 Select Installation Action Choose A - Install a new SAS system.

3 Specify New Installation Qualifier Specify the path where you want to install SAS. You can also choose to require Storage Management Subsystem (SMS) parameters. For more information, consult your z/OS documentation.

3 Specify IBM’s SMS Parameters If you chose to require Storage Management Subsystem (SMS) parameters on the previous page, enter them here. For more information, consult your z/OS documentation.

Installing and Configuring Your SAS Software

4

Install and Configure SAS Interactively

81

3 Specify Parameters These are all parameters that are used in various DD statements throughout the installation. For more information, consult your IBM JCL documentation.

3 Specify Entry Point Specify the parameters for various ways that SAS can be run with different performance implications. Choose SAS (default ENTRY point) to run the unbundled configuration. Choose SASB to run the bundled configuration. Choose SASLPA to run the bundled configuration with some modules installed in the Link Pack Area (LPA).

3 Specify Parameters Specify additional parameters for DD statements. VOLDISK designates the VOLSER that the installed data sets will go to. For more information, consult your IBM JCL documentation.

3 Specify Parameters Specify parameters used for reblocking the SAS load modules to a library with an optimum block size. 21 Review the list of third-party software that is required for the SAS software that

you are installing on the current machine. (The list of third-party software depends on the SAS software that you are installing on the current machine.) In the pages that immediately follow, be prepared to provide paths to these third-party applications. (The number of dialog boxes varies depending on the SAS software you are deploying on the current machine.) Note: You must provide valid paths to the requested third-party software, or the SAS Deployment Wizard will not let you continue with the installation. 4 22 Specify the amount of information to provide the SAS Deployment Wizard for configuring the SAS software you are installing on the current machine. Choose one of the three prompting levels: Note: When deploying the SAS 9.2 middle-tier, by default, the SAS Deployment Wizard automatically configures your Web application server. To disable this feature, run the wizard using either the Typical or Custom prompting levels. 4 Express

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

display the basic set of wizard pages needed to complete the SAS configuration. Custom

display all the wizard pages needed to complete the SAS configuration. Refer to “Interactive Prompting Levels” on page 69 for more information about the SAS Deployment Wizard prompting levels. 23 Provide the remaining configuration information as the wizard prompts you for it. Note: This topic describes some of the more important pages that you will encounter during the configuration phase of a SAS 9.2 deployment. The 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. For information about all SAS Deployment Wizard prompts, see the online Help for the wizard dialog box in question.

4

3 Specify Configuration Information

82

Install and Configure SAS Interactively

4

Chapter 5

Select the path where the SAS Deployment Wizard will write SAS configuration files and logs and the level you want to deploy. For example, Lev1 = production. Note: The last digit of the default port number reflects the configuration level that you select in the SAS Deployment Wizard. For example, when you select Lev1, the default port for the metadata server is 8561. If you choose another level, such as Lev2, the wizard changes the default port to 8562. 4 For more information, see “Overview of the Configuration Directory Structure” in the SAS Intelligence Platform: System Administration Guide. Note: Although your SAS Home and SAS configuration directories can share the same parent directory, one directory should not reside inside another. Defining the configuration directory under the SAS Home directory, or vice-versa, can lead to file permission issues arising from the need to manage installed files differently than site-specific configurations.

4

On z/OS, the mount point must exist. The SAS Deployment Wizard will create the necessary subdirectories. If you are deploying the SAS Table Server, then 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.

3 Local Machine Name Enter the complete name of the local host in Fully-qualified Local Host Name. The fully qualified local host name typically takes the form of the local host name plus the domain name server (for example, myserver.example.com). Enter a short host name in Short Local Host Name. The short local host name is the abbreviated, more common method of referring to the host, usually only a single word.

3 Migration Information Ignore this page and click Next. If you need to migrate SAS 9.1.3 content to SAS 9.2, see “Overview of Migrating Content to SAS 9.2” in the SAS Intelligence Platform: 9.1.3 to 9.2 Migration Guide.

3 Authentication Domain Accept the default value (DefaultAuth), unless the deployment that you are migrating uses a different SAS authentication domain for servers on this machine. For example, if the metadata server is on Windows and the workspace server is on UNIX, the workspace server might be assigned to a SAS authentication domain named UnixAuth. For more information, see “About Authentication Domains” in the SAS Management Console: Guide to Users and Permissions .

3 Windows Options (run as managed scripts or services) On Windows, choose how to run your SAS servers, either by using management scripts or running them as Windows services. If you choose the script option, then the user account that runs the object spawner must meet the following requirements on the object spawner machine: 3 be the administrator or a member of the Windows Administrator’s group 3 have the following Windows local user rights:

Installing and Configuring Your SAS Software

4

Install and Configure SAS Interactively

83

3 Adjust memory quotas for a process 3 Replace a process level token 3 Integrated Windows Authentication Select to use Integrated Windows authentication (IWA) for workspace servers running on Windows only. IWA supports a single sign-on feature in which a metadata server running on Windows accepts a user’s previous authentication to his or her Windows desktop when the user attempts to access a workspace server. Selecting this page when you are deploying a workspace server on Windows enables the workspace server to use IWA. You also encounter this page when deploying SAS Enterprise Guide and SAS Add-In for Microsoft Office. If you have not chosen IWA for the workspace server, then choosing IWA for these clients has no effect. For more information, see “Integrated Windows Authentication” in the SAS Intelligence Platform: Security Administration Guide. A metadata server running on Windows has IWA turned on by default. For more information, see “SSPI System Option” in the SAS Intelligence Platform: Application Server Administration Guide.

3 SAS Metadata Server If you have any changes for the metadata server, enter them in this page. The deployment wizard creates a separate server context (SASMeta) for the metadata server and the other servers required to perform metadata server utility functions, such as backup, replication, and promotion. A server context is a SAS IOM server concept that describes how SAS Application Servers manage client requests. A SAS Application Server has an awareness (or context) of how it is being used and makes decisions based on that awareness. The server context name is prepended to all server names defined in the server context. Therefore, we recommend that you not change the logical server or server prefix (SASMeta). For more information, see “Overview of the SAS Metadata Server and Its Initial Configuration” in the SAS Intelligence Platform: System Administration Guide.

3 Products SAS Folder Path Enter the path in SAS Folders for products to locate their shipped content objects. These objects can include libraries, tables and jobs for Data Mart creation, stored processes, cubes and information maps to be used as data sources for reporting, consumable reports, and domain-specific content. For more information, see “About the SAS Folder Structure” in the SAS Intelligence Platform: System Administration Guide.

3 Deployment Accounts:

Type of Accounts

Select whether to use internal accounts when appropriate. Internal user accounts are accounts known only to SAS and are created and authenticated internally in metadata rather than externally. Note: On Windows, whenever the deployment wizard prompts you for an external account, always enter a domain-qualified user account (for example, myDomain\myAccount).

4

For more information, see “Internal User Accounts” on page 6.

3 External Account:

Installer

84

Install and Configure SAS Interactively

4

Chapter 5

Enter the user ID and password for the external account to be used to install and configure SAS. Depending on the operating system, this account should meet the following requirements: 3 Windows: Use a domain-qualified account that is available in the long term (for future SAS maintenance) and is a member of the Administrators group. 3 UNIX: Use the same account on all machines on which you are deploying SAS. Do not use root. 3 z/OS: Use the same account on all machines on which you are deploying SAS. For more information, see “Defining User Accounts” on page 6.

3 SAS Internal Account:

Unrestricted Administrator

Enter a password for the internal account ([email protected]) that the wizard will create to serve as an unrestricted administrator for the purpose of configuring the SAS metadata server. For more information, see “Defining User Accounts” on page 6.

3 SAS Internal Account:

Trusted User

Enter a password for an internal account ([email protected]) that the wizard will create to enable SAS server and spawner components to communicate securely with each other. For more information, see “Defining User Accounts” on page 6.

3 SAS BI Web Services:

Authentication Method

Select the method by which users of SAS BI Web Services are authenticated: 3 SAS Authentication is managed by the metadata server. 3 Web Authentication is managed by the Web application server using container-based authentication or a third-party product. Selecting Web Authentication has these effects: 3 fully configures Web authentication for .NET BI Web Services. 3 partially configures Web authentication for Java BI Web Services. For more information, see “Securing SAS BI Web Services for Java” in the SAS Intelligence Platform: Web Application Administration Guide. 3 has no effect on the BI Web applications (such as SAS Web Report Studio, SAS Web Information Portal, and so on). You will have to configure Web authentication for these BI Web applications. 3 prevents you from being offered a chance to set up an anonymous Web user (as this is incompatible with Web authentication).

3 Anonymous Web Access When using SAS authentication you can select this option to set up a SAS identity for anonymous access to certain Web services and Web applications that support this feature. Currently, SAS BI Web Services for Java and .NET and the SAS Stored Process Web Application are the only components that support this feature. For more information, see “Using the SAS Anonymous Web User With SAS Authentication” in the SAS Intelligence Platform: Web Application Administration Guide.

Installing and Configuring Your SAS Software

3 SAS Internal Account:

4

Install and Configure SAS Interactively

85

Anonymous Web User

(Optional) Enter the user ID and password for the internal SAS account to be used to grant clients access to applicable SAS Web Infrastructure Platform applications such as SAS BI Web Services and the Stored Process Web Application. When SAS authentication is being used and the user has not preemptively specified credentials, the client will be given access to these Web applications under the anonymous user account. For more information, see “Using the SAS Anonymous Web User With SAS Authentication” in the SAS Intelligence Platform: Web Application Administration Guide.

3 External account:

SAS Spawned Servers Account

Enter the user ID and password for the external account to be used to start the pooled workspace server and the stored process server. On Windows, enter a domain-qualified user ID. For more information, see “Defining User Accounts” on page 6.

3 Create Common Directories Select to create common directories for server and spawner logs, user-specific files, data (SAS libraries for tables and cubes), and temporary work tables and files. When you select this option, the deployment wizard creates the specified directory (Logs, Users, Data, and Temp) under the SAS configuration directory.

3 Server Encryption Select the encryption level and algorithm that SAS clients and servers use to connect to the metadata server. Choose Credentials to encrypt only login credentials. Choose Everything to encrypt all communication with the metadata server. To specify an encryption algorithm other than SASPROPRIETARY, you must have a license for SAS/SECURE software. The other algorithms are: RC2, RC4, DES, TripleDES, and AES. For more information, see “Encryption Model” in the SAS Intelligence Platform: Security Administration Guide.

3 Client-side Credentials Policy Select this option to set the policy to allow users to save their user IDs and passwords in client-side connection profiles on the metadata server for desktop applications. This input sets the value for OMA_SASSEC_LOCAL_PW_SAVE in omaconfig.xml. For more information, see “Reference Information for omaconfig.xml” in the SAS Intelligence Platform: System Administration Guide.

3 E-mail Server Enter the port and host name for an SMTP e-mail server that the SAS Metadata Server uses to send e-mail alerts to an administrator if journaling issues arise. The SAS Deployment Wizard also uses this e-mail server as the default for the SAS Application Server to provide e-mail services to various SAS clients. For example, with SAS Data Integration Studio, you can use a Publish to Email transformation to alert users about various data changes. In order for the SAS BI Dashboard to send alerts by e-mail to dashboard users and administrators, the port and host name must be configured for the e-mail server. For more information, see “Overview of Adding or Modifying E-Mail Settings for SAS Application Servers” in the SAS Intelligence Platform: Application Server Administration Guide.

86

Install and Configure SAS Interactively

4

Chapter 5

3 SAS Application Server:

Server Context

Enter the name of the server context for the SAS Application Server definition. A server context is a SAS IOM server concept that describes how SAS Application Servers manage client requests. A SAS Application Server has an awareness (or context) of how it is being used and makes decisions based on that awareness. The server context name is prepended to all server names defined in the server context. For more information, see “What Is a SAS Application Server?” in the SAS Intelligence Platform: Application Server Administration Guide.

3 Metadata Utility Workspace Server Enter the name of the logical workspace server and the workspace in metadata. You also need to enter the name of the machine on which the workspace server runs and the port on which the object spawner will listen for client requests to launch workspace servers. The machine name should match the name specified to the object spawner. Unlike a regular workspace server, access to this server is limited to members of the SAS Administrators group, and its use is limited to metadata server administration tasks such as replication, promotion, and backup. In SAS 9.2, two or more workspace servers can share the same port even if they are running at the same time. For more information about ports, see “Designating Ports and Multicast Addresses” on page 19.

3 SAS Pooled Workspace Server Enter the name of the logical pooled workspace server and the pooled workspace in metadata. You also need to enter the name of the machine on which the pooled workspace server runs and the port on which the object spawner will listen for client requests to launch pooled workspace servers. The machine name should match the name specified to the object spawner. For more information, see “Overview of Workspace Servers and Stored Process Servers” in the SAS Intelligence Platform: System Administration Guide.

3 SAS Table Server Enter the name of the logical table server in metadata. You also need to enter the name of the machine on which the table server runs and the TCP/IP port on which the table server will listen to. For more information, see “Understand the SAS Table Server” in the SAS Table Server Administrator’s Guide.

3 Metadata Utility SAS DATA Step Batch Server Enter the various values required to configure a SAS DATA step batch server. The directory fields identify where the deployed SAS program is stored and the name of the deployed SAS DATA step program job. Access to this server is limited to members of the SAS Administrators group, and its use is limited to metadata server backup. For more information, see “Contents of the Metadata Server Subdirectory (SASMeta)” in the SAS Intelligence Platform: System Administration Guide.

3 Query Cache Library Enter the physical location on the file system where the SAS library will exist for temporary files used when creating optimized tables for query look-up. In Query Cache Libref, enter the SAS library reference which SAS will use to refer to the query optimizer SAS library. The name must be eight characters or shorter and should be unique from other librefs used within this repository.

Installing and Configuring Your SAS Software

4

Install and Configure SAS Interactively

87

Librefs must start with a letter or underscore and contain only letters, numerals, or underscores. The typical installation libref name is wrstemp. The libref will be used in conjunction with the server context name to form the SAS library name for the optimizer library. Select Enable Query Cache to allow the query optimizer to run. If this selection is not made, then the query optimizer will not attempt to optimize queries and will not create temporary data sets for improving performance during rendering. A typical installation will have this selection turned on. The temporary files created within the query cache library will be visible to anyone with Read permission on the Renderer Optimizer directory, so if you have security concerns with the authorization on this folder you might want to leave the optimizer off. For more information, see “Using the Query Cache” in the SAS Intelligence Platform: Web Application Administration Guide.

3 Output Management Library Enter the physical location on the file system where the SAS library will exist for burst set definition tables for reports which will be distributed by e-mail. A burst definition table will contain e-mail addresses, channels, and possibly by group information. In Output Management Library Libref, enter the SAS library reference that SAS will use to refer to the output management SAS library. The name must be eight characters or shorter and should be unique from other librefs used within this Repository. Librefs must start with a letter or underscore and contain only letters, numerals, or underscores. The typical installation libref name is wrsdist. The libref will be used in conjunction with the server context name to form the SAS library name for the distribution library. For more information, see “Verifying Permissions for the Distribution Library” in the SAS Intelligence Platform: Web Application Administration Guide.

3 Web Application Server:

Automatic Configuration

Select this option for the deployment wizard to automatically build and configure the SAS Web applications as well as configuring a sample Web application server for use with SAS 9.2. (To use this wizard feature, be sure that your Web application server is not running before proceeding. For WebSphere, it’s necessary to stop all deployment manager servers, all node agent servers, and all application servers before continuing with your SAS 9.2 deployment.) For more information, see “Choose Whether to Automatically Configure Your Web Application Server” on page 55. If you choose not to automatically configure your Web application server, you will still be prompted for Web application server information, and deployment stages such as Configure Products, Deploy Web Applications, and Start Web Application Servers will execute to create instructions for manual deployment. When configuration is complete, follow these manual instructions on how to configure your server and deploy your Web applications. If you manually configure WebLogic, a reference domain will be created in your SAS configuration area, but no servers will be started. If you manually configure JBoss, sample start scripts will be created, but not launched. For more information, go to http://support.sas.com/resources/ thirdpartysupport/v92 and search for the product name of your Web application server.

3 Web Application Server:

Multiple Managed Servers

Select to have the deployment wizard automatically configure multiple managed servers for you using SAS best practices for choosing the server to deploy each application to.

88

Install and Configure SAS Interactively

4

Chapter 5

In some situations it might be preferable to split the SAS Web applications across multiple managed servers. This is usually done for performance reasons. If you chose to manually configure your application servers, you will be provided with recommended configuration settings in a generated instructions file (Instructions.html) when the SAS Deployment Wizard completes. More advanced performance configuration considerations are documented in the SAS Intelligence Platform: Web Application Administration Guide, which can be found at http://support.sas.com/92administration.

3 Web Application Server:

Managed Server

Enter a logical name for your managed server. This name will be displayed in your application server administrative console and used in administrative scripting. In HTTP Port, enter the unsecured port on which the managed server will listen. In HTTPS Port, enter the SSL port to be assigned to the managed server. In SOAP Port, (WebSphere only) enter the SOAP port that the WebSphere administrative services will use to communicate with this managed server, if SOAP was selected. This port can also be used by the wsadmin utility. In RMI Port, enter a port using these considerations: 3 WebSphere This maps to the RMI BOOTSTRAP port. Each server contains an administrative services component and a separate and unique port is required for each application server. 3 JBoss This maps to the default JNDI port. Clients connecting to applications running on JBoss, such as the JBoss shutdown command, would use this port. 3 WebLogic No RMI port is required for WebLogic. In Configured Protocol, select the communication protocol for the administration server: HTTP or HTTPS. Automated configuration through the SAS Deployment Wizard only supports the HTTP protocol. If you perform a manual configuration, you can set up HTTPS. In Additional JVM Options, enter any additional Java options that you want the managed server JVM (Java Virtual Machine) to use. These JVM options are tagged onto the end of the managed server’s command line. Options that are deployment wizard defaults can be overridden in this way. For more information, go to http://support.sas.com/resources/ thirdpartysupport/v92 and search for the product name of your Web application server.

3 Web Application Server:

Automatic Deployment

Select to automatically deploy SAS 9.2 Web applications to the Web application server. For more information, see “Choose Whether to Automatically Deploy the SAS Web Applications” on page 56. Regardless of whether you choose to automatically deploy your SAS Web applications, when building Web applications, the wizard also automatically explodes Web application archive files (.EAR files). If you choose not to automatically deploy SAS Web applications, the deployment wizard writes manual deployment instructions to Instructions.html during the Web application deployment stage, that you will need to complete

Installing and Configuring Your SAS Software

4

Install and Configure SAS Interactively

89

after the wizard finishes executing. For more information, go to http:// support.sas.com/resources/thirdpartysupport/v92 and search for the product name of your Web application server. Note: The SAS Deployment Wizard does not automatically deploy SAS OnlineDoc for the Web, even when you choose the automatic deployment option. You must manually deploy SAS OnlineDoc for the Web. For more information, see “Manual Deployment of SAS OnlineDoc for the Web” in the SAS Intelligence Platform: Web Application Administration Guide.

4

3 External Account:

Web Application Server Administrator

Enter the user ID and password for the WebSphere Application Server or WebLogic Server administrator account. On Windows, enter a domain-qualified user ID. You are prompted for this information if your site uses the WebSphere or WebLogic application server. For more information about configuring Web application servers to support the SAS middle tier, go to http://support.sas.com/resources/ thirdpartysupport/v92 and search for “WebSphere” or “WebLogic”.

3 Web Application Server:

Proxy Information

If you are using SAS Information Delivery Portal RSS feeds, then you will have to provide proxy server information. Enter the fully qualified host name for the proxy server and its port that your site uses to access the Internet. For NonProxy Hosts, enter the DNS names of all the machines that should not be accessed through the proxy server. Be sure to include other machines where application servers are configured as part of a common WebLogic Domain or are part of a WebSphere cell. Separate each machine name with a vertical line character (|). Use an asterisk (*) as a wildcard for an entire subnet. For example, *.subnet.com excludes all machines with a DNS name that ends with .subnet.com. If your site does not allow Internet access on production systems, refer to configuration information available at this SAS Web site: http:// support.sas.com/resources/thirdpartysupport/v92. (Search for your Web application server.)

3 WebSphere Application Server:

Node

In Profile Name, enter a profile name, or accept the default (SAShostname01). The profile name is used for the directory that contains the node agent and the SAS Web application server. The node agent name is required, but cannot be configured using the deployment wizard. In Node Name, enter a node name or accept the default (SAShostnameNode). The node name is the WebSphere node that contains one or more of the Web application servers. In Additional JVM Options, enter any additional Java options that you want the Web application servers to use.

3 IP Multicast Accept these IP multicast settings or enter new ones. A multicast group communications protocol is used to communicate among middle-tier SAS applications in a single SAS deployment (the set of applications connected to the same metadata server). The combination of multicast IP address and multicast UDP port should be different for each SAS deployment and also different from those used by other multicast applications at your site.

90

Install and Configure SAS Interactively

4

Chapter 5

The defaults are most appropriate for deployments in a firewall-isolated data center environment. For more information, see “Designating Ports and Multicast Addresses” on page 19.

3 SAS Remote Services Application:

JVM

Enter the desired initial heap size for the remote services application using the JVM option format. In Max JVM Heap Size, enter the desired maximum heap size for the remote services application using the JVM option format. In Additional JVM Options, enter any additional Java options that you want the Remote Services VM to use. For example, you might want to add -Dmulticast_udp_ip_ttl=1 to restrict multicast traffic to a single subnet based on your network topology. For more information, go to http://support.sas.com/resources/ thirdpartysupport/v92 and search for “SAS 9.2 Web Applications: Tuning for Performance and Scalability”.

3 SAS Web Report Studio:

Scheduling

Choose whether to enable scheduling for SAS Web Report Studio. If Platform Suite for SAS is in your deployment plan, then you have a choice between using Platform Process Manager, provided by Platform Computing, Inc., or SAS In-Process Services. For more information, see “Setting Up Scheduling Using Platform Suite for SAS” or “Setting Up Scheduling Using SAS In-Process Scheduling” in Scheduling in SAS.

3 SAS Content Server:

Repository Directory

Enter the location on the disk for the actual contents of the content repository. For more information, see “Administering the SAS Content Server” in the SAS Intelligence Platform: System Administration Guide. 24 When you see the Deployment Summary page, the deployment wizard has finished

collecting installation and configuration input. This is the last opportunity to go back and change any information you have provided in previous pages before the wizard begins writing to your system. Make one of the following choices:

3 Click Start to begin installing SAS files and writing the configuration to the current machine.

3 Click Back to navigate to earlier wizard pages to change installation and configuration information previously entered. 3 Click Cancel to terminate the wizard session. Note that you will lose installation and configuration information previously entered.

Installing and Configuring Your SAS Software

4

Install and Configure SAS Interactively

91

On UNIX, When you are installing the server tier, you will be prompted enter the root password. As the message in the installation program explains, certain SAS products and features use functionality that requires SAS to check user ID authentication and file access authorizations. This in turn necessitates that certain files within your SAS installation have setuid permissions and be owned by root. When you see a page similar to the following, the SAS Deployment Wizard is finished:

The deployment wizard has installed, configured, and started SAS processes on your machine.

92

Validate the SAS 9.2 Servers

4

Chapter 5

25 Click Review Manual Configuration Instructions and complete any

necessary manual configuration steps. The SAS Deployment Wizard writes the Instructions.html file to the Documents directory under the SAS configuration path. For example:

3 UNIX and z/OS: /opt/SAS/Lev1/Documents/Instructions.html

3 Windows: C:\SAS\Config\Lev1\Documents\Instructions.html 26 Click Finish to close the deployment wizard. 27 For multi-machine deployments, 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. 3 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. 3 Back up your Web application server directories. 3 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. 28 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. 29 When you are finished completing any manual configuration tasks, and you have made the necessary backups, repeat the steps listed in this topic on each machine defined in your deployment plan. 30 Be sure to restart any servers that you stopped for purposes of creating a backup. 31 When you are finished installing and configuring SAS on each machine called for in your deployment plan, proceed to the next section.

Validate the SAS 9.2 Servers There are a few simple steps required to confirm that the various SAS servers you have deployed are running properly. The following table summarizes server validation information:

Installing and Configuring Your SAS Software

4

Validate the SAS 9.2 Servers

93

Table 5.3 Validation Summary for the SAS Server Tier Server

Validation Method

Metadata server

Successful login using the SAS Management Console.

Metadata utility (SASMeta) workspace server

The metadata utility workspace server can be used only by those members of the SAS Administrators group who have an external account that is known to the server’s host and is associated with their SAS identity. If the server is on Windows and uses credential-based host authentication, the account must have the Log on as a batch job user right. Right-click the validate command in SAS Management Console using external account credentials that meet the criteria described above. Default path: Server Manager

I SASMeta I Logical Workspace Server.

Object spawner

If either the stored process server or one of the workspace servers validates (see below), then the object spawner is running.

OLAP server

Right-click the validate command in SAS Management Console. Default path: Server Manager

Pooled workspace server

1

I SASApp I Logical Stored Process Server.

1

Right-click the validate command in SAS Management Console using external account credentials. Default path: Server Manager

DATA step batch server

I SASApp I Logical Pooled Workspace Server.

Right-click the validate command in SAS Management Console. Default path: Server Manager

Workspace server

1

Right-click the validate command in SAS Management Console. Default path: Server Manager

Stored process server

I SASApp I Logical OLAP Server.

I SASApp I Logical Workspace Server.

1

Successful launch of SAS when running the sasbatch script (Windows and UNIX). On z/OS, use the Schedule Manager’s Deploy SAS DATA Step Program to browse the appserver_autoexec_usermods.sas file created in the AppServer context.

Grid server

Successful launch of the grid test program found on the SAS Scalability and Performance focus area: http://support.sas.com/rnd/ scalability/grid/gridfunc.html#testprog. For more information, see “Verifying SAS Job Execution” in Grid Computing in SAS.

1 Use the value you entered during the deployment for the server context name. The default is SASApp.

This procedure is meant to provide validation for an out-of-the-box, basic deployment. For more complex server configurations, please refer to the appropriate SAS documentation for the server in question. To validate the SAS server tier that has been deployed using the SAS Deployment Wizard, follow these steps: 1 Log on to the machine hosting one or more SAS servers. 2 Start SAS Management Console, using the following command for the appropriate

operating system:

3 Windows:

94

Validate the SAS 9.2 Servers

4

Chapter 5

Start menu

3 UNIX:

I Programs I SAS I SAS Management Console 9.2

Type the following command: sas-installation-directory/sasmc For example: /opt/sas/SASManagementConsole/9.2/sasmc

3 z/OS: Use a Windows or UNIX machine on which SAS Management Console is installed and connect to the z/OS machine(s) where the SAS 9.2 server tier is running. 3 Log on to the metadata server using a set of valid credentials, such as for the SAS 4 5 6 7

Administrator. In SAS Management Console, on the Plug-ins tab, expand the Server Manager node. Expand the SAS Application Server node. (The default name is SASApp.) Highlight the server you want to validate, such as the SASApp - Logical OLAP Server. Right-click the highlighted server, and select Validate. You should see the following message: Validation Successful!

8 Repeat steps 6 and 7 for the other SAS servers:

3 pooled workspace server 3 stored process server 3 workspace server 9 When validating the workspace server, if you are prompted for credentials, we

suggest that you enter the credentials for the SAS Spawned Servers account (sassrv). Alternatively, you can enter a user ID and password that meet all of these requirements: 3 The account is known to the host of the workspace server. (An ID that ends in @saspw does not meet this requirement.) 3 The account has the Windows right Log on as a batch job (if the server is on Windows). 3 The account has a corresponding metadata identity. 10 To validate the DATA step batch server on Windows and UNIX, SAS should

successfully launch when you run the following command, appropriate for the server host operating system: 3 Windows: Start menu

I Run I sas-configuration-directory\sasbatch.bat

For example: Start menu > Run > C:\SAS\AllServers\Lev1\SASApp\BatchServer\sasbatch.bat

3 UNIX: Type the following command: sas-configuration-directory/SASApp/BatchServer/sasbatch.sh For example: /opt/sas/AllServers/Lev1/SASApp/BatchServer/sasbatch.sh

Installing and Configuring Your SAS Software

4

Overview of Automating the SAS Installation on Multiple Machines

95

11 To validate the DATA step batch server on z/OS, use the Schedule Manager’s

Deploy SAS DATA Step Program to browse the appserver_autoexec_usermods.sas file created in the AppServer context. When the JCL pane comes up and contains JCL, then the deployment of the batch server is successful. a From SAS Management Console, right-click the Schedule Manager plug-in

(Plug-ins tab) and choose Deploy SAS DATA Step Program. b Click Browse and navigate to the appserver_autoexec_usermods.sas file

under a server context such as SASApp (for example, SAS-configuration-directory/Levn/SASApp). c You should see JCL in the bottom list box. 12 To verify that your grid servers are operational, follow the steps located in, “Verifying SAS Job Execution” in Grid Computing in SAS. 13 Repeat these steps on each machine in your deployment plan on which you have deployed one or more SAS servers.

About SAS Deployment Tester SAS 9.2 ships with a SAS Management Console plug-in that you can use to test your SAS deployment. For more information, see the SAS Management Console Help for the SAS Deployment Tester.

Automating the SAS Installation on Multiple Machines Overview of Automating the SAS Installation on Multiple Machines The SAS Deployment Wizard provides a record and playback feature that enables you to automate a SAS installation across multiple machines. This feature is designed for large-scale enterprise deployments where SAS 9.2 clients need to be deployed across many machines. Using the record and playback feature prevents users from having to manually provide input on every page every time the SAS Deployment Wizard is run on a machine. The SAS Deployment Wizard can be run in one of the three playback modes. Each requires you to launch the wizard from the command line with a particular option. After the wizard finishes, you review the log file to verify that the installation completed successfully. Users can choose among three levels of automation when playing back a SAS Deployment Wizard response file. Note: This same record and playback mechanism also works for the SAS Deployment Manager to automate configuration actions across multiple machines in a SAS deployment. 4 The following summarizes the SAS Deployment Wizard record and playback process: 1 Create a response file.

Run the SAS Deployment Wizard once in record mode to create a response file. SAS is not installed or configured; the only output is a response file. See “Recording a SAS Deployment Wizard Response File” on page 96. 2 Play back the response file to install SAS. Run the SAS Deployment Wizard to install and configure SAS using the values you previously recorded in the response file.

96

Recording a SAS Deployment Wizard Response File

4

Chapter 5

See “Playing Back a SAS Deployment Wizard Response File” on page 97. 3 Verify that the installation completed successfully. Check the SAS Deployment Wizard log file for the presence of any errors. See “Verifying the Playback Install” on page 99.

Recording a SAS Deployment Wizard Response File To use the SAS Deployment Wizard in playback mode, your first step is to create a response file. A response file is a text file that contains values for the SAS Deployment Wizard to use to install and configure SAS when running in one of the three playback modes. You create a response file by running the SAS Deployment Wizard in record mode. While in record mode, you interact with the SAS Deployment Wizard as if you are installing and configuring SAS. However, the SAS Deployment Wizard does not install or configure any software while in record mode. The only output is the response file. The SAS Deployment Wizard stores any passwords you choose to record in the response file using a fixed-key, 32–bit proprietary encryption algorithm. The SAS Deployment Wizard resides at the root of the SAS Software Depot directory, or on the root of the SAS media that you are installing from. The following command runs the SAS Deployment Wizard in record mode: 3 Windows: setup.exe -record

3 UNIX: setup.sh -record

3 z/OS: setup.rexx -record

To run the SAS Deployment Wizard, you must be a user who is known to the target machine and who will be available for the long term (to perform future SAS maintenance). On Windows, the installer user should be a member of the Administrators group; on UNIX, use the same account on all machines. For more information, see “Required External User Accounts for SAS” on page 7. By default, the SAS Deployment Wizard names the response file sdwresponse.properties and writes the file to the current user’s home directory. For example, the default path and filename on Windows is as follows: C:\Documents and Settings\current-user\sdwresponse.properties To specify a response file that does not use the default name, use the -responsefile

option. For example, on Windows you might type a command similar to this: setup.exe -record -responsefile "C:\Program Files\SAS\response.properties"

If you want, you can force the wizard to deploy SAS during recording mode by using the -deploy option. For example, on Windows you might type a command similar to this: setup.exe -record -deploy -responsefile "C:\Program Files\SAS\response.properties"

For information about verifying your deployment, see “Verifying the Playback Install” on page 99.

Installing and Configuring Your SAS Software

4

Playing Back a SAS Deployment Wizard Response File

97

Playing Back a SAS Deployment Wizard Response File Overview of Playing Back a SAS Deployment Wizard Response File There are three playback modes that give users varying levels of automation with the SAS Deployment Wizard: Table 5.4 Playback Modes for the SAS Deployment Wizard Level of Automation

Description

Mode Quiet

High

No visual feedback from the SAS Deployment Wizard. See “Installing SAS in Quiet Mode” on page 97.

Partial prompt

Medium

Users only see SAS Deployment Wizard pages for values not contained in the response file. See “Installing SAS in Partial Prompt Mode” on page 98.

Full prompt

Low

Users see all SAS Deployment Wizard pages with response file values supplied. Users can confirm these values or change them. See “Installing SAS in Full Prompt Mode” on page 99.

Installing SAS in Quiet Mode The SAS Deployment Wizard gives you flexibility in how you automate the SAS installation. The highest level of automated installation is running the SAS Deployment Wizard in quiet mode. In quiet mode, there is no user interface in which you provide installation inputs. The SAS Deployment Wizard uses inputs that you have already provided in the form of a response file to determine how to install and to configure SAS. The following command runs the SAS Deployment Wizard in quiet playback mode: 3 Windows: setup.exe -quiet -wait

Note: On Windows, you might also want to specify restart options. For more information, see “Managing a Machine Reboot During Playback (Windows)” on page 98. 4 3 UNIX: setup.sh -quiet

3 z/OS: setup.rexx -quiet -wait

Note: For information about -wait, see “Monitoring the SAS Deployment Wizard During Playback” on page 100. 4 To run the SAS Deployment Wizard, you must be a user who is known to the target machine and who will be available for the long term (to perform future maintenance). On Windows, the installer user should be a member of the Administrators group; on UNIX, use the same account on all machines. For more information, see “Required External User Accounts for SAS” on page 7. When running in quiet mode, the SAS Deployment Wizard’s default action is to look for its response file by default in the current user’s home directory. For example, the default path and filename on Windows is as follows: C:\Documents and Settings\current-user\sdwresponse.properties

98

Playing Back a SAS Deployment Wizard Response File

4

Chapter 5

To specify a response file that does not use the default name, use the -responsefile absolute-pathname option. For example, on Windows you might type a command similar to this: setup.exe -quiet -responsefile "C:\Program Files\SAS\response.properties"

For Windows machines, in the event that the machine must be rebooted, use the restart options to avoid having to manually log back on to the machine. For example, you might type a command similar to this: setup.exe -quiet -responsefile "C:\Program Files\SAS\response.properties" -restartdomain mydomain -restartuserid myuserid -restartpassword mypassword

See the following topics for more information: 3 “Managing a Machine Reboot During Playback (Windows)” on page 98 3 “Verifying the Playback Install” on page 99 3 “Monitoring the SAS Deployment Wizard During Playback” on page 100

Managing a Machine Reboot During Playback (Windows) During a deployment on Windows, the SAS Deployment Wizard runs the System Requirements Wizard to check the machine to make sure that it meets the minimum system requirements for SAS 9.2. If certain Microsoft system components that are required by SAS 9.2 are missing, the System Requirements Wizard shuts down the SAS Deployment Wizard, installs the missing components, and reboots the machine. If you are playing back a response file in quiet mode, you should use the following options in order to log back on to the machine automatically and continue the SAS Deployment Wizard session: -restartdomain domain

specifies the authentication domain for the SAS installer user account. -restartuserid SAS-installer-ID

specifies the user account that you are logged in under to run the SAS Deployment Wizard to deploy SAS 9.2. -restartpassword password

specifies the password for the specified user account. For example, you might type a command similar to this: setup.exe -quiet -wait -responsefile "C:\Program Files\SAS\response.properties" -restartdomain mydomain -restartuserid myuserid -restartpassword mypassword

Installing SAS in Partial Prompt Mode The SAS Deployment Wizard gives you flexibility with how you automate the SAS installation. You can fully automate the SAS installation (quiet mode), or you can pick and choose certain parts of the installation to automate (partial prompt mode). When you run the SAS Deployment Wizard in partial prompt mode, the user sees only those wizard pages for which there are no response file values. There might be situations where it is permissible to automate most of the installation inputs but necessary to prompt for certain sensitive pieces of information. For example, storing user account credentials—even in an encrypted form—might violate a site’s corporate security policy. It would require the user to interact with the SAS Deployment Wizard for those pages where user account credentials are entered. The SAS Deployment Wizard resides at the root of the SAS Software Depot directory, or on the root of the SAS media that you are installing from. The following command runs the SAS Deployment Wizard in partial prompt playback mode:

Installing and Configuring Your SAS Software

4

Verifying the Playback Install

99

3 Windows: setup.exe -partialprompt

3 UNIX: setup.sh -partialprompt

3 z/OS: setup.rexx -partialprompt

To run the SAS Deployment Wizard, you must be a user who is known to the target machine and who will be available for the long term (to perform future maintenance). On Windows, the installer user should be a member of the Administrators group; on UNIX, use the same account on all machines. For more information, see “Required External User Accounts for SAS” on page 7. When running in partial prompt mode, the SAS Deployment Wizard’s default action is to look for its response file by default in the current user’s home directory. For example, the default path and filename on Windows is as follows: C:\Documents and Settings\current-user\sdwresponse.properties To specify a response file that does not use the default name, use the -responsefile

option. For example, on Windows you might type a command similar to this: setup.exe -partialprompt -responsefile "C:\Program Files\SAS\response.properties"

For more information, see “Verifying the Playback Install” on page 99.

Installing SAS in Full Prompt Mode There are three levels of automation from which you can choose when running the SAS Deployment Wizard in playback mode: quiet, partial prompt, and full prompt. Full prompt mode is the least automated of the three modes. When running in full prompt mode, the SAS Deployment Wizard requires user confirmation for all of its pages. However, in full prompt mode, the user is prompted with default values that are stored in the response file. The SAS Deployment Wizard resides at the root of the SAS Software Depot directory, or on the root of the SAS media you are installing from. The following command runs the SAS Deployment Wizard in full prompt playback mode: Windows: setup.exe -responsefile absolute-pathname UNIX: setup.sh -responsefile absolute-pathname z/OS: setup.rexx -responsefile absolute-pathname To run the SAS Deployment Wizard, you must be a user who is known to the target machine and who will be available for the long term (to perform future maintenance). On Windows, the installer user should be a member of the Administrators group; on UNIX, use the same account on all machines. For more information, see “Required External User Accounts for SAS” on page 7. When running in full prompt mode, the SAS Deployment Wizard expects you to specify a path and filename to a valid response file. For example, on Windows type the following command: setup.exe -responsefile "C:\Program Files\SAS\response.properties"

For more information, see “Verifying the Playback Install” on page 99.

Verifying the Playback Install When running in quiet mode, the SAS Deployment Wizard logs the following message after a successful completion:

100

Monitoring the SAS Deployment Wizard During Playback

4

Chapter 5

Deployment completed successfully

If the SAS Deployment Wizard encounters an incorrect or a missing input in the response file, it records a message in its log file and returns an error code of -1. The SAS Deployment Wizard log file resides in the following location:

3 Windows: C:\Documents and Settings\current-user\Local Settings\Application Data\SAS\SAS Deployment Wizard\SDW.log

3 UNIX and z/OS: ~/.SASAppData/SASDeploymentWizard/9.2/SDW.log

Use the -loglevel n option to control the amount of information written by the SAS Deployment Wizard to its log. A change in the logging level is in effect for the current SAS Deployment Wizard invocation only. If you do not specify a log level, then the wizard uses the default (zero). n can be one of the following three values: 0 (default) specifies the least amount of information written to the log. Zero is acceptable for most SAS Deployment Wizard sessions. 1 specifies a medium amount of information written to the log. This value is generally used when working with SAS Technical Support to troubleshoot deployment issues. 2 specifies the greatest amount of information written to the log and should not be specified except when instructed to by SAS Technical Support. For example, on Windows, to increase the SAS Deployment Wizard logging level you might type a command similar to this: setup.exe -partialprompt -responsefile "C:\Program Files\SAS\response.properties" -loglevel 1

Monitoring the SAS Deployment Wizard During Playback Running the SAS Deployment Wizard in quiet mode provides the sought-after effect of suppressing the wizard’s user interface. One drawback with the quiet mode is not being able to see the interface, which enables you to monitor the install and to see whether any errors occur. To address this concern, you can use the Task Manager on Windows or periodically issue the ps command on UNIX and z/OS to track whether the SAS Deployment Wizard is running. On Windows, specify the -wait option when invoking the SAS Deployment Wizard in quiet mode to cause setup.exe to display and remain in the Windows Task Manager process list. For example: setup.exe -quiet -wait -responsefile "C:\Program Files\SAS\ response.properties" If you did not use -wait, monitor the process named java.exe.

Note: Use of network management software (such as SMS or Tivoli) might require you to use the -wait option when running the SAS Deployment Wizard in quiet mode in order for such software to determine when the SAS Deployment Wizard finishes executing. Refer to your network management platform documentation for more information. 4

Installing and Configuring Your SAS Software

4

More About Monitoring the SAS Deployment Wizard on UNIX and z/OS

101

On UNIX and z/OS, as with most processes, you issue the ps command to monitor the SAS Deployment Wizard running in quiet mode. For more information, see “More About Monitoring the SAS Deployment Wizard on UNIX and z/OS” on page 101.

More About Monitoring the SAS Deployment Wizard on UNIX and z/OS Remember that output from a ps command can be misleading because the process name returned is not always named setup.sh. The name might differ because the actual script that the SAS Deployment Wizard is running at any given time varies. However, the process ID remains the same. For example, if you were to run the SAS Deployment Wizard and immediately issue a ps command (before the language dialog box would be displayed), you would see output similar to this: 31762 pts/2 S 0:00 /bin/sh /depot/setup.sh Note that the shell, /bin/sh, runs the initial script, /depot/setup.sh. The shell is the parent process, and in this example has a process ID of 31762. When setup.sh is finished executing, it passes control to the script, deploywiz.sh. If you were to look at

the process list while the SAS Deployment Wizard is running, you would see something similar to the following in a process list: 31762 pts/2 S 0:00 /bin/sh /tmp/_setup31762/products/deploywiz__9220__prt__xx__sp0__1/deploywiz.sh -startuplocation /depot -templocation /tmp/_setup31762 The shell /bin/sh is still running and retains the same process ID. However, this shell is running a different script now, deploywiz.sh.

102

103

CHAPTER

6 What to Do Next: Administration Tasks Overview of Administration Tasks 103 First-Priority Setup Tasks 104 Summary of First-Priority Setup Tasks 104 Recommended Operating System Protections for Windows Machines 104 Default Operating System Protections for UNIX and z/OS Machines 106 Standard Setup Tasks 107 Optional Setup Tasks 108 Ongoing System Administration Tasks 110 Best Practices for Ensuring the Integrity of Your System 111 Allow Only the Metadata Server to Access Your Metadata Repositories 111 Use Best Practices for Working with SAS Folders 112

Overview of Administration Tasks Before you perform the administration tasks that are outlined in this chapter, you should have successfully completed the following tasks: 3 Use the SAS Deployment Wizard to install and configure your software on each machine in your environment. 3 Complete the post-installation tasks that are described in your Instructions.html file, which is located in the Documents subdirectory of your configuration directory. These tasks include performing manual configuration steps (if applicable), validating your SAS servers, validating your Web applications, and backing up your system. After the SAS Intelligence Platform has been installed, configured, and validated, you will have a functional system. You can now begin performing administration tasks that are necessary to fully implement the SAS Intelligence Platform in your environment. These include the following categories of tasks:

3 first-priority setup tasks that are necessary to protect the integrity of your system. You should perform these tasks first, as soon as possible after you have completed your installation. 3 standard setup tasks that enable the users in your organization to begin using SAS Intelligence Platform client applications to access and analyze your data.

3 optional setup tasks that you might want to perform to address specific requirements in your environment.

3 ongoing tasks to keep the SAS Intelligence Platform operational.

104

First-Priority Setup Tasks

4

Chapter 6

First-Priority Setup Tasks Summary of First-Priority Setup Tasks The following tasks are necessary to protect the integrity of your system. Complete these steps as soon as possible after installation, before you complete any of the other tasks that are outlined in this chapter. Table 6.1 First-Priority Setup Tasks Task

Description

Secure the SAS configuration on each server machine.

For a secure deployment, the configuration directory on each server machine must be protected by operating system controls. These controls will prevent inappropriate access to repository data sets, server scripts, server logs, and configuration files. On Windows systems, all configuration directories, files, and scripts are owned by the user who performs the installation. You must update the permissions as shown in “Recommended Operating System Protections for Windows Machines” on page 104. These recommendations assume that your SAS servers and spawners run as services under the Local System account. On UNIX and z/OS systems, the SAS Deployment Wizard automatically applies the appropriate permissions. The default permissions are shown in “Default Operating System Protections for UNIX and z/OS Machines” on page 106.

Establish a formal, regularly scheduled backup process.

Establish a formal, regularly scheduled backup process that includes your metadata repositories as well as the associated physical files. SAS provides backup and restore utilities that enable you to perform correct backups and restores of your metadata repositories, the repository manager, the metadata journal file, and the metadata server configuration files while minimizing disruptions in service. It is important to also back up the physical data that is associated with the metadata so that related information will be synchronized if a restore becomes necessary. Before you back up your SAS Intelligence Platform, read “Best Practices for Backing Up and Restoring Your System” in the SAS Intelligence Platform: System Administration Guide.

Recommended Operating System Protections for Windows Machines On Windows server machines, we recommend that you apply the following operating system protections to your configuration directory. All of these directories are located in SAS-configuration-directory\Levn.

What to Do Next: Administration Tasks

4

Recommended Operating System Protections for Windows Machines

105

Table 6.2 Recommended Operating System Protections on Windows Directories

Users

Recommended Permissions

SAS-configuration-directory

SYSTEM and Administrators

Full Control

\Levn subdirectories: Documents, ReportBatch, SASApp, SASMeta, Utilities, Web

All other users

List Folder Contents, Read

\Levn subdirectories: ConnectSpawner, Logs, ObjectSpawner, SASApp\OLAPServer, SASMeta\MetadataServer, SASTS, ShareServer

SYSTEM and Administrators

Full Control

SASApp subdirectories : PooledWorkspaceServer, StoredProcessServer

SYSTEM, Administrators, and SAS Spawned Servers (sassrv)

Full Control

SASApp subdirectories: ConnectServer\Logs, Data\wrsdist, Data\wrstemp, PooledWorkspaceServer\Logs, PooledWorkspaceServer\sasuser, StoredProcessServer\Logs , StoredProcessServer\sasuser, and WorkspaceServer\Logs

SYSTEM, Administrators, and SAS Spawned Servers (sassrv)

Full Control

SYSTEM and Administrators

Read and Write

The user who backs up the metadata server. You can add this user to the Administrators group to provide the required access.

Full Control

SAS-configuration-directory\Levn

Remove all other users and groups

Remove all other users and groups

SASMeta\WorkspaceServer\Logs sasv9_meta.cfg file

SASMeta subdirectories: MetadataServer, MetadataServer\rposmgr, MetadataServer\MetadataRepositories \Foundation Backup destination (for example, SASMeta\MetadataServer\SASBackup)

Remove all other users and groups

Note: 3 These recommendations assume that your SAS servers and spawners run as services under the Local System account. If servers and spawners are run under a different account, then grant that account the permissions that are recommended for SYSTEM. 3 You might have selected the custom installation option to place all of your log files in a single directory. If you selected this option, then you will need to grant the SAS Spawned Servers (sassrv) user Full Control of the central log destination (for example, SAS-configuration-directory\Levn\Logs). 3 If users will be using SAS Enterprise Guide to create stored processes, then the SAS Spawned Servers (sassrv) account must have Write access to the directory in which stored processes will be stored. 3 If you enable logging for a workspace server, then you will need to grant all users of the workspace server Full Control of the log directory. (See “Create a Log File

106

Default Operating System Protections for UNIX and z/OS Machines

4

Chapter 6

for Workspace Server Troubleshooting” in the SAS Intelligence Platform: System Administration Guide).

4 For information about backups, see “Using the Backup Wizard in SAS Management Console” and “Using the %OMABAKUP Macro to Perform Backups and Restores” in the SAS Intelligence Platform: System Administration Guide. For details about the configuration directory structure, see “Overview of the Configuration Directory Structure” in the SAS Intelligence Platform: System Administration Guide.

Default Operating System Protections for UNIX and z/OS Machines The following table shows the default operating system protections that are provided automatically for configuration directories on UNIX and z/OS machines. All of these directories are located in SAS-configuration-directory/Levn. Table 6.3 Default Operating System Protections on UNIX and z/OS Directories

Users

Default Permissions

SAS-configuration-directory

SAS Installer

Read, Write, and Execute

SAS-configuration-directory/Levn

All other users

Read and Execute

/Levn subdirectories: ConnectSpawner, Logs, ObjectSpawner, SASApp/OLAPServer, SASMeta/MetadataServer, SASTS, ShareServer

SAS Installer

Read, Write, and Execute

All other users

No access

SASApp subdirectories : PooledWorkspaceServer, StoredProcessServer

SAS Installer

Read, Write, and Execute

sas group

Read and Execute

SASApp subdirectories : ConnectServer/Logs, Data/wrsdist, Data/wrstemp, PooledWorkspaceServer/Logs, PooledWorkspaceServer/sasuser, StoredProcessServer/Logs , StoredProcessServer/sasuser, and WorkspaceServer/Logs

SAS Installer

Read, Write, and Execute

sas group

Read, Write, and Execute

SAS Installer

Read and Write

All other users

no access

/Levn subdirectories: Documents, ReportBatch, SASApp, SASMeta, Utilities, Web

SASMeta/WorkspaceServer/Logs sasv9_meta.cfg file

Note:

3 Make sure that the SAS Spawned Servers account (sassrv) is a member of the sas group, which has the necessary permissions to server configuration files and log directories.

3 You might have selected the custom installation option to place all of your log files in a single directory. If you selected this option, then you will need to grant either

What to Do Next: Administration Tasks

4

Standard Setup Tasks

107

the sas group or the SAS Spawned Servers (sassrv) user Read, Write, and Execute permission on the central log destination (for example, SAS-configuration-directory/Levn/Logs). 3 If users will be using SAS Enterprise Guide to create stored processes, then the SAS Spawned Servers (sassrv) account must have Write access to the directory in which stored processes will be stored. 3 If you enable logging for a workspace server, then you will need to grant all users of the workspace server Full Control of the log directory. (See “Create a Log File for Workspace Server Troubleshooting” in the SAS Intelligence Platform: System Administration Guide). 3 The user who backs up the metadata server must have full access to SAS-configuration-directory/Levn/SASMeta/MetadataServer, to its subdirectories rposmgr and MetadataRepositories/Foundation, and to the backup destination (for example, SAS-configuration-directory/Levn/SASMeta/MetadataServer/ SASBackup). The SAS Installer user has the required access. CAUTION:

Do not run a backup or a restore as the Root user. Doing so will change ownership of the metadata server files. 4

3 For information about backups, see “Using the Backup Wizard in SAS Management Console” and “Using the %OMABAKUP Macro to Perform Backups and Restores” in the SAS Intelligence Platform: System Administration Guide. For details about the configuration directory structure, see “Overview of the Configuration Directory Structure” in the SAS Intelligence Platform: System Administration Guide.

4

Standard Setup Tasks The following administration tasks are essential to enable the users in your organization to begin using SAS Intelligence Platform client applications to access and analyze your data.

108

Optional Setup Tasks

4

Chapter 6

Table 6.4 Standard Setup Tasks Task

Description

Add users and manage access.

Standard security setup activities include the following:

3 3

creating SAS administrators and regular SAS users managing access to metadata, data, and application functionality

For details, see “Security Tasks” in the SAS Intelligence Platform: Security Administration Guide. Establish connectivity to your data sources.

To enable the client applications in the SAS Intelligence Platform to access your data sources (including SAS data sets, third-party relational databases, and data from Enterprise Resource Planning systems), you must create metadata objects that represent your data. For example, to enable users to access data in a library of SAS data sets, you must define metadata objects that represent the SAS library and each of the tables in the library. For details, see “Connecting to Common Data Sources” in the SAS Intelligence Platform: Data Administration Guide.

Set up your metadata folder structure.

SAS Intelligence Platform clients use a hierarchy of SAS folders to store metadata for content such as libraries, tables, OLAP schemas, jobs, information maps, and reports. The initial structure provides private folders for individual users and provides a separate area for shared data. Within these folders, you should create a customized folder structure that meets your specific needs. For details, see “Working with SAS Folders” in the SAS Intelligence Platform: System Administration Guide.

Note: Be sure to secure access to the folders as described in the SAS Intelligence Platform: Security Administration Guide. 4

Optional Setup Tasks It might be necessary for you to modify your initial configuration to meet specific requirements in your environment. Optional administration and configuration tasks include the following.

What to Do Next: Administration Tasks

4

Optional Setup Tasks

Table 6.5 Optional Setup Tasks Task

Description

Optimize the performance and reliability of the metadata server.

The following are some steps that you might need to take to optimize the performance and reliability of the metadata server:

3 3

Move the metadata server journal file to another file system (see “Move the Journal File to Another File System” in the SAS Intelligence Platform: System Administration Guide). Adjust the maximum number of threads used by the metadata server (see “Configuring the Number of Threads Used by the Metadata Server” in the SAS Intelligence Platform: System Administration Guide).

For other performance-related tasks, see “Managing Metadata Server Performance” in the SAS Intelligence Platform: System Administration Guide. Modify the configuration of your processing servers.

The following are some server configuration changes that you might want to make for performance optimization or other reasons:

3

3

3

3

Define a cluster of load-balanced workspace servers in order to balance a load across workspace servers that you have installed on multiple hosts. This type of configuration is most useful when you have a large number of users (such as data integration specialists) using a workspace server for relatively long-running jobs. For details, see “Understanding Server Load Balancing” in the SAS Intelligence Platform: Application Server Administration Guide. Modify load balancing or algorithms for stored process servers and pooled workspace servers. For details, see “Modify Logical Pooled Workspace or Logical Stored Process Server Load-Balancing Properties” in the SAS Intelligence Platform: Application Server Administration Guide. If your SAS server metadata contains characters other than those typically found in the English language, then you must start your SAS server with an ENCODING= or LOCALE= system option that accommodates those characters. For details, see “Encoding and Locale Information” in the SAS Intelligence Platform: Application Server Administration Guide. If you will be submitting large jobs (for example, JAVA GRAPH jobs) on z/OS servers, then you might need to specify a larger region size. For details, see “Managing Memory” in the SAS Companion for z/ OS.

Optimize Web application performance.

For information about configuring middle-tier components for better efficiency and performance, see “Best Practices for Configuring Your Middle Tier” in the SAS Intelligence Platform: Web Application Administration Guide.

Adjust server logging.

You can change your server configurations to obtain additional logging information for troubleshooting, performance management, or other purposes. For details, see “Administering Logging for SAS Servers” in the SAS Intelligence Platform: System Administration Guide and SAS Logging: Configuration and Programming Reference.

109

110

Ongoing System Administration Tasks

4

Chapter 6

Task

Description

Enable job and report scheduling.

To enable SAS scheduling features, you can install and configure scheduling software, configure operating system scheduling, or configure in-process scheduling. For details, see Scheduling in SAS.

Set up test and development environments.

You can use the Replication Wizard in SAS Management Console to set up separate environments for your development and testing activities. For details, see “Using the Replication Wizard to Copy an Entire Metadata Repository” in the SAS Intelligence Platform: System Administration Guide.

Increase Java heap memory allocation for desktop applications.

To process large amounts of data, you might need to modify the Java heap memory allocation that is configured for SAS Management Console, SAS Data Integration Studio, SAS OLAP Cube Studio, and SAS Information Map Studio. For details, see “Managing the Java Heap Used By Desktop Applications” in the SAS Intelligence Platform: System Administration Guide.

Set up change management for SAS Data Integration Studio users.

If you want to implement change management for SAS Data Integration Studio, then you must set up project repositories and at least one change-managed folder. For details, see “Administering SAS Data Integration Studio” in the SAS Intelligence Platform: Desktop Application Administration Guide.

Collect ARM log information for SAS Data Integration Studio batch jobs.

If you want to collect ARM log information for SAS Data Integration Studio jobs that are run on a batch basis, then you must enable logging for the batch server that executes the jobs. For details, see “Collecting ARM Log Information for SAS Data Integration Studio Jobs” in the SAS Intelligence Platform: System Administration Guide.

Ongoing System Administration Tasks The following table lists important system administration tasks that you will need to perform on an ongoing basis to keep the SAS Intelligence Platform operational. Table 6.6 Ongoing System Administration Tasks

Task

Documentation Reference

Start, stop, pause, resume, and refresh the servers that are used in the system.

“Operating Your Servers” in the SAS Intelligence Platform: System Administration Guide

Check the status of a server of or of a metadata repository.

“Checking the Status of Servers” in the SAS Intelligence Platform: System Administration Guide

Monitor the activity of servers.

“Monitoring the Activity of SAS Servers” in the SAS Intelligence Platform: System Administration Guide

Perform regular full backups of the metadata server.

“Best Practices for Backing Up and Restoring Your System” in the SAS Intelligence Platform: System Administration Guide

What to Do Next: Administration Tasks

4

Allow Only the Metadata Server to Access Your Metadata Repositories

111

Task

Documentation Reference

Use server logs and configure logging options.

“Administering Logging for SAS Servers” in the SAS Intelligence Platform: System Administration Guide and SAS Logging: Configuration and Programming Reference

Create a new metadata repository.

“Creating, Registering, Moving, Copying, Renaming, and Deleting SAS Metadata Repositories” in the SAS Intelligence Platform: System Administration Guide

Promote individual metadata objects or groups of objects.

“Using the Promotion Tools” in the SAS Intelligence Platform: System Administration Guide

Note: The preceding table includes only the tasks that are documented in this guide. Other important administration tasks are described in the following documents:

3 SAS Intelligence Platform: Security Administration Guide. In this guide, you can use the “Checklist for a More Secure Deployment” to ensure that your environment remains secure on an ongoing basis.

3 3 3 3

SAS Intelligence Platform: Data Administration Guide

3 3 3 3

Scheduling in SAS

SAS Intelligence Platform: Application Server Administration Guide SAS Intelligence Platform: Desktop Application Administration Guide SAS Intelligence Platform: Web Application Administration Guide SAS/SHARE User’s Guide SAS/CONNECT User’s Guide SAS Table Server Administrator’s Guide

To access these documents, go to http://support.sas.com/92administration.

4

Best Practices for Ensuring the Integrity of Your System Allow Only the Metadata Server to Access Your Metadata Repositories The MetadataRepositories and rpsomgr subdirectories, which are located in the SAS configuration directory, are critical to the operation of your system. These data sets contain metadata that defines your servers, users, access levels, enterprise data sources, and data structures. They also contain metadata for resources that are created and used by SAS applications, including information maps, OLAP cubes, report definitions, stored process definitions, and jobs. To safeguard the integrity of your system:

3 Never move, delete, modify, or directly read the data sets in the MetadataRepositories and rpsomgr directories. These data sets should be

accessed only by metadata server processes.

3 Do not place other files in these directories. 3 Back up the contents of these directories regularly, as described in “Best Practices for Backing Up and Restoring Your System” in the SAS Intelligence Platform: System Administration Guide.

112

Use Best Practices for Working with SAS Folders

4

Chapter 6

Use Best Practices for Working with SAS Folders The folders that appear in the Folders tab of SAS Management console are used by client applications to store business intelligence content and system information. Inappropriate renaming, deleting, or moving of these folders or their contents could cause client applications to malfunction. When interacting with folders in SAS Management Console, be sure to follow the best practices that are provided in “Working with SAS Folders” in the SAS Intelligence Platform: System Administration Guide. If you need to move or copy the contents of these folders, use the procedures that are provided in “Using the Promotion Tools” in the SAS Intelligence Platform: System Administration Guide.

113

APPENDIX

1 Troubleshooting Your Initial SAS 9.2 Deployment Overview of Troubleshooting Your Initial SAS 9.2 Deployment 113 Review SAS Deployment Wizard Documents and Reports 114 Troubleshooting the SAS Server Tier 115 Troubleshooting SAS Web Applications 117

Overview of Troubleshooting Your Initial SAS 9.2 Deployment The SAS Deployment Wizard performs two major functions. Using inputs that you have provided, the wizard installs SAS, and then initially configures SAS. There are many components to a SAS Intelligence Platform deployment, but if one component happens not to deploy properly, it does not mean that you have to repeat the entire deployment. In most cases you can continue with the rest of the SAS deployment, and later troubleshoot the component that failed to deploy. If you encounter a configuration error while running the SAS Deployment Wizard, follow these steps: 1 Read the configuration alert box and, leaving the alert box displayed, take any steps that it suggests. 2 After you have performed the steps, go back to the configuration alert box and click Retry. 3 If the configuration alert box re-appears and you are unable to resolve the issue, try to finish the deployment by clicking Yes. 4 If the configuration continues to fail, after the wizard completes the entire SAS configuration, you can unconfigure the failed component and reconfigure it. For more information, see “Removing a SAS Configuration” on page 148.

114

Review SAS Deployment Wizard Documents and Reports

Figure A1.1

4

Appendix 1

Configuration Troubleshooting Flowchart

There can be situations when the configuration failed before the SAS Deployment Manager is properly configured. When this occurs, running the deployment manager is not an option. In these situations, you must do the following: 3 Stop the metadata server (if it is running). 3 Restore the most recent backup of the metadata repository and repository manager that you created before deploying. 3 Restore the most recent backup of the Web application server directories. 3 If any servers that failed to configure were installed as services on Windows, manually remove their service definitions. For more information, see your Microsoft Windows documentation. 3 Manually delete the configuration directories for the SAS components that failed to configure.

Review SAS Deployment Wizard Documents and Reports During configuration of SAS 9.2 the SAS Deployment Wizard creates various documents that can help you identify any remaining configuration tasks and errors. Use the following documents to perform any manual configuration steps and correct any configuration errors: 3 Instructions.html contains a list of SAS manual steps that must be performed to complete your deployment. Instructions.html resides under the SAS configuration directory in the Levn/Documents subdirectory (for example: C:\SAS\Config92\Lev1\Documents). 3 DeploymentSummary.html contains a list of the deployment tasks performed by the SAS Deployment Wizard and a brief status for each. The deployment summary is one source for a list of all the SAS products installed and configured in addition to information such as servers started, Web applications built, and Web applications deployed.

Troubleshooting Your Initial SAS 9.2 Deployment

4

Troubleshooting the SAS Server Tier

115

DeploymentSummary.html resides under the SAS configuration directory in the Levn/Documents subdirectory (for example: C:\SAS\Config\Lev1\Documents).

3 ConfigurationErrors.html contains a list of configuration errors that require further attention. ConfigurationErrors.html resides under the SAS configuration directory in the Levn/Documents subdirectory (for example: C:\SAS\Config\Lev1\Documents).

3 Configuration logs (as needed) provide a finer list of errors for each SAS component that the SAS Deployment Wizard migrates and configures. There is one log file for each SAS component. The configuration logs reside under the SAS configuration directory in the Levn/Logs/ Configure subdirectory (for example: C:\SAS\Config\Lev1\Logs\Configure).

Troubleshooting the SAS Server Tier The following table lists some SAS server-tier errors and what to do to resolve them. Table A1.1

Troubleshooting the SAS Server Tier

Error

Explanation

Resolution

When you attempt to run a SAS server for the first time, you receive an error message about the IOMServerAppender not finding a location for storing temporary utility files.

There is no temporary directory defined on the host machine’s operating system.

Use the method appropriate for the server machine’s operating system to define a temp directory. For more information, see “IOMServerAppender Usage and Best Practices” in SAS Logging: Configuration and Programming Reference.

Pooled workspace server fails to start during the configuration of SAS Shared Services.

One cause for this problem on Windows is that during installation, the SAS installer did not domain qualify the SAS Spawned Servers user account (sassrv). This account is entered as a login in the SAS General Servers group, so it is required to have a domain prefix as are all Windows logins. Without domain qualifying the login, connections by this account become PUBLIC connections. By default, PUBLIC users cannot access the repository, which prevents the pooled workspace server from launching successfully.

Using SAS Management Console, edit the login associated with the SAS General Servers group and add a domain to it (for example: myhost\sassrv). You can edit logins in the Plug-ins tab of SAS Management Console (User Manager I SAS General Servers I Accounts I Edit).

116

Troubleshooting the SAS Server Tier

4

Appendix 1

Error

Explanation

Resolution

You cannot validate the logical workspace server from SAS Management Console using the Server Manager plug-in.

By default, the unrestricted user is a SAS internal account. The workspace server needs an operating system user account to be able to authenticate itself to the machine on which it runs.

Re-try the validation from SAS Management Console. You should be prompted for user account credentials. Enter credentials for a user account that the workspace server can authenticate and that has (on Windows) the Log in as a batch job user rights. One account that meets these requirements is the SAS Spawned Servers account (sassrv).

After you have updated the user’s credentials to allow access, you are denied access when trying to connect to or validate a server or spawner.

The credentials cache must be cleared before you try to connect or validate again.

To clear the credentials cache, in SAS Management Console, click File I Clear Credentials Cache.

Unable to start a workspace server and unable to start a stored process server.

Most likely, something is wrong with the object spawner.

Make sure that the object spawner is running. For more information, see “Operating Your Servers” in the SAS Intelligence Platform: System Administration Guide.

The metadata server might not be able to authenticate the object spawner.

If you cannot start the object spawner, make sure that the metadata server is running.

If the object spawner denies access to a server because of the lack of ReadMetadata permissions, and the user is then granted the needed permission, you must reset the object spawner’s authorization cache before the user tries to connect again. To do so, expand the Server Manager tree in SAS Management Console. Next, expand the object spawner, right-click the host node, and choose Connect in the pop-up menu. After you have connected, right-click the host node again, and choose Refresh Spawner in the pop-up menu.

Check the log for the object spawner and determine whether the spawner is able to find the server’s definition. For more information, see “Using SAS Management Console to Monitor SAS Servers” in the SAS Intelligence Platform: System Administration Guide. Also check the event log on Windows or the syslog on UNIX or z/OS. You can correct the credentials used to authenticate the spawner in the SAS-configuration-directory/ ObjectSpawner/metadataConfig.xml file, or reconfigure the spawner using the SAS deployment tools. For more information, see “Overview of Managing Your SAS Deployment” on page 119.

Troubleshooting Your Initial SAS 9.2 Deployment

4

Troubleshooting SAS Web Applications

Error

Explanation

Resolution

You cannot start your SAS server.

The file sas.servers might not be automatically generated. This does not imply any issue with your configuration and does not indicate something is wrong.

Generate the sas.servers file manually by running SAS-configuration-directory/data/SAS/BIServer/ Levn/generate_boot_scripts.sh. For more information, see “Using the sas.servers Script on UNIX or z/OS to Start or Stop All Servers ”in the SAS Intelligence Platform: System Administration Guide.

You see an error message about the location of the JUnit JAR file not being specified for SAS Deployment Tester.

The SAS Deployment Tester tests other products that use JUnit for validation. Without JUnit, these products might operate properly, but you will not be able to validate them using the SAS Deployment Tester.

The JUnit JAR is available from the Third-Party Software Downloads site at http:// support.sas.com/resources/thirdpartysupport/ v92. Place the JUnit JAR in this location:

3

117

Windows:

C:\junit3.8.1\junit.jar

3

UNIX and z/OS:

/usr/local/junit3.8.1/junit.jar

Troubleshooting SAS Web Applications The following table lists some SAS Web application errors and what to do to resolve them. Table A1.2

Troubleshooting the SAS Web Applications

Error

Explanation

Resolution

SAS Web Report Studio or the SAS Information Delivery Portal displays a “Cannot find server” error.

Either your servlet container or Web application server is not running.

Make sure that your servlet container or Web application server is running. If it is not running, start it. This will probably solve the problem. If the server is already running, the problem could be with the URL that you are using to start the Web application.

There is problem with the URL that you are using to start the application.

Each time your Web application requests a new page, there is a long delay.

When a Java Server Page (JSP) is requested for the first time, you can expect a significant delay. When all of your JSPs have been converted to compiled servlets, the problem will be resolved.

Use the correct URL: http://host-name:port-number/ application-name. Make sure that the host name is the fully qualified name of the host on which your servlet container or Web application server is running. Make sure that the port number identifies the port on which the server is listening. For the JBoss Application Server, this will normally be port 8080. Finally, make sure that the application name in the URL matches the actual name of the Web application (including case). Tune your servlet container or Web application server. For example, if you are using the WebLogic Server, the server might be checking (on a per application basis) for updated JSPs and updated compiled servlets. You can suppress these checks by setting an application’s JSPPageCheck and ServletReloadCheck properties to -1. See your server vendor’s documentation for similar tips.

118

Troubleshooting SAS Web Applications

4

Appendix 1

Error

Explanation

Resolution

The SAS Information Delivery Portal displays a “Could not authenticate user” error.

The user is not registered in the metadata repository.

In SAS Management Console, add a login to the Person object that contains at least a user name. On Windows, make sure the user name has the form host\user-ID or domain\user-ID. For more information, see “About User Administration” in the SAS Intelligence Platform: System Administration Guide.

SAS stored processes run from the SAS Add-In for Microsoft Office, but don’t run from the SAS Information Delivery Portal.

The SAS Services Application might not be running.

Start the following in this order: WebDAV Server, SAS Services Application, and your servlet container or Web application server. For more information, see “Operating Your Servers” in the SAS Intelligence Platform: System Administration Guide.

You are unable to start the SAS Services Application.

Another application might be using the same port as the SAS Services Application (by default, 5091).

Configure the SAS Services Application to listen on a different port.

You receive a server error when accessing the Help menu from a SAS Web application.

SAS Help Viewer Metadata Configuration is not configured.

Rerun the SAS Deployment Wizard to install and configure SAS Help Viewer Metadata Configuration. For more information, see “Install and Configure SAS Interactively” on page 76.

An error page appears when you access the Help menu from a SAS application or the Help menu item for a SAS application does not display.

The online Help for the SAS application was not installed or the SAS Help Viewer Metadata Configuration Web application was not rebuilt after the online Help was installed.

Verify that the online Help was installed. If not, install it using the SAS Deployment Wizard. Once the Help is installed, rebuild the SAS Help Viewer Metadata Configuration Web application using the SAS Deployment Manager and redeploy the SAS Help Viewer Metadata Configuration EAR. For more information, see “Install and Configure SAS Interactively” on page 76 and “Rebuilding the SAS Web Applications” in the SAS Intelligence Platform: Web Application Administration Guide.

You are having problems running SAS OnlineDoc for the Web.

Most likely, an error occurred during installation and deployment.

You should reinstall SAS Help Viewer for the Web and SAS OnlineDoc for the Web in order to generate a new EAR. For more information, see “Installing SAS OnlineDoc for the Web” on page 74 and “Manual Deployment of SAS OnlineDoc for the Web” in the SAS Intelligence Platform: Web Application Administration Guide.

On Windows, if the user that is trying to log on is registered in the metadata, but the user name is not domain qualified, the user will not be able to log on.

119

APPENDIX

2 Managing Your SAS Deployment Overview of Managing Your SAS Deployment 119 Deploying Products, Installing Additional Software, and Applying Updates 120 Summary of Deploying Products, Installing Additional Software, and Applying Updates How the SAS Deployment Wizard Updates Software 120 Remove Update Backup Files 123 Specify a Different JRE 124 Configuring or Adding SAS Products 125 Overview: Configuring or Adding SAS Products 125 About SAS Software Orders and SAS Software Depots 126 Add SAS Products that Do Not Require Configuration 126 Add SAS Products that Require Configuration 131 Configure SAS Products 137 Renewing Your Software License for SAS Solutions 144 About Renewing Your Software License for SAS Solutions 144 Renew Your Software License for SAS Solutions 144 Removing a SAS Configuration 148 Overview of Removing a SAS Configuration 148 Summary of Steps for Removing a SAS Configuration 150 Identify Dependent SAS Products 151 Remove a Configuration 153

120

Overview of Managing Your SAS Deployment The sections that follow discuss how to use the SAS 9.2 deployment tools to add or configure a SAS product, remove a SAS product configuration, and renew your software license for certain SAS solutions. For information about removing a SAS installation, see “Overview of Uninstalling the SAS Intelligence Platform” on page 157.

120

Deploying Products, Installing Additional Software, and Applying Updates

4

Appendix 2

Deploying Products, Installing Additional Software, and Applying Updates Summary of Deploying Products, Installing Additional Software, and Applying Updates When you are deploying products, installing additional software, or applying updates to your SAS 9.2 deployment, the SAS Deployment Wizard is able to determine whether the order from which you are running the wizard contains SAS software with a newer, older, or identical release level than what is already deployed in the SAS installation directory (commonly referred to as SAS Home). If the wizard determines that there is newer SAS software in the current order than what’s already deployed, then the wizard automatically goes into update mode. Update mode forces you to install updates to your software before you can perform any other deployment task. For example, if you are adding new products or language support to an existing SAS deployment, you will install those in an additional SAS Deployment Wizard session, after the wizard (in update mode) has first updated the products on your machine to match the versions contained in your SAS order. For more information, see the following:

3 3 3 3 3 3

“How the SAS Deployment Wizard Updates Software” on page 120. “Remove Update Backup Files” on page 123. “Specify a Different JRE” on page 124. “Configuring or Adding SAS Products” on page 125. “Add SAS Products that Do Not Require Configuration” on page 126. Maintenance Planning for SAS 9.2.

How the SAS Deployment Wizard Updates Software This topic describes in greater detail how the SAS Deployment Wizard deploys products, installs additional software, and applies updates. The wizard compares the release version of the SAS software in the current order to the SAS software that is deployed on the machine. Three possibilities exist:

3 The software in the order has a newer release level than the software deployed on the machine.

3 The software in the order has an older release level than the software deployed on the machine.

3 The software in the order has an identical release level as the software deployed on the machine. Updates consist of a new version or an incremental delta update (also referred to as maintenance) to an installed product. If the deployment wizard detects that one or more products in the order have a newer release level than any products deployed in the specified SAS Home on the machine, the wizard goes into update mode. (SAS Home is shorthand for the SAS installation directory (for example, C:\Program Files\SAS). The wizard displays an updates page of all the products deployed on the machine for which there are updates in the current order.

Managing Your SAS Deployment

4

How the SAS Deployment Wizard Updates Software

121

The deployment wizard updates page is broken into two sections that list new product versions and new product delta updates (or maintenance). In the example of the updates page shown earlier, SAS Web Application Themes represents a new product version (for example, 9.2 to 9.21). SAS BI Dashboard Help and Documentation represents a delta update (for example, 4.2 to 4.2_M1). If you choose to proceed with your deployment from this order, to the specified SAS Home, the wizard requires that you install these updates to bring your existing deployment to the release level from which your new order was mastered. When you click Next, the wizard automatically upgrades the products to the release levels that are shown on the updates page. When running in update mode, the wizard displays no deployment plan, SAS installation data file, or language pages down this path. The wizard simply installs the newest versions and delta updates of the product set already deployed in the specified SAS Home. If the update contains updated language support for a specific product (such as, SAS, SAS Enterprise Guide, and SAS Add-In for Microsoft Office), the wizard installs only the update for the languages previously installed. If you are adding new products or language support to an existing SAS deployment, you will install those in an additional SAS Deployment Wizard session, after the update is installed and any customization or validation is performed. If the deployment wizard detects that one or more products in the software order has an older release level than any products deployed in the specified SAS Home on the machine, the wizard does not go into update mode. Instead, the wizard presents you with an alert box listing those products in your order that are older than the ones deployed on your machine.

122

How the SAS Deployment Wizard Updates Software

4

Appendix 2

SAS wants to make sure that you are always installing software from an order corresponding to a release level that is identical to or newer than the one used to originally deploy your SAS software. Your options are to use a different software order, designate a different SAS Home directory, or uninstall the products that are newer. If the deployment wizard detects that all the products in the order have an identical release level to all products deployed in the specified SAS Home on the machine, the wizard does not go into update mode. Instead, the wizard presents pages that enable you to perform normal deployment tasks such as deploying products, installing additional software, and so on. The following diagram summarizes how the SAS Deployment Wizard manages deploying products, installing additional software, and applying updates:

Managing Your SAS Deployment

Figure A2.1

4

Remove Update Backup Files

123

SAS Deployment Wizard Flowchart

Remove Update Backup Files Whenever the SAS Deployment Wizard updates software on a machine, it creates a backup copy of the software being updated. After you apply the updates, you can use the SAS Update File Cleanup Utility to remove the backup copies to reclaim disk space. To remove update backup files, follow these steps: 1 Log on as the SAS Installer user to the machine on which the SAS updates were

applied. 2 From an operating system prompt, change to the SASHome/InstallMisc/MIT

subdirectory. For example, issue one of the following commands:

3 UNIX: cd /opt/sas_92/InstallMisc/MIT

3 Windows: cd \Program Files\SAS\InstallMisc\MIT

3 z/OS: cd /usr/lpp/SAS/SAS_92/InstallMisc/MIT 3 Type the following command appropriate for your operating system:

3 UNIX and z/OS: ./cleanup.sh

3 Windows: cleanup.bat The SAS Update File Cleanup Utility window appears.

124

Specify a Different JRE

4

Appendix 2

4 Click Remove Backup Files.

The utility sweeps through the SAS Home directory structure and deletes backup files.

When the deletion process is complete, the Complete alert box displays.

5 Click OK.

The cleanup utility logs which files and directories that it removes in the following location: SASHome/InstallMisc/MIT/InstallLogs/Maintenance/ Cleanup_nnnnn.log.

Specify a Different JRE During a first-time SAS 9.2 deployment, the SAS Deployment Wizard prompts you for the version of the Java Runtime Environment (JRE) that you want to use with the SAS Java applications. Your options are to have the deployment wizard install a JRE that SAS has certified to run with SAS 9.2, or to point to a JRE that you have already installed.

Managing Your SAS Deployment

4

Overview: Configuring or Adding SAS Products

125

In most situations where you are updating or adding a product to SAS 9.2, the deployment wizard does not prompt you for a JRE. However, you can override this behavior. To specify a different JRE with which to run SAS Java applications, follow these steps: 1 Log on to the machine on which you run SAS Java applications using the SAS

2

3 4 5

Installer user. For more information, see “Required External User Accounts for SAS” on page 7. Run the deployment wizard using its command line invocation and add the option -forcejreprompt (for example, setup.exe -forcejreprompt). For more information, see “Install and Configure SAS Interactively” on page 76. During your deployment wizard session, you should see the Select Java Runtime Environment page that prompts you for a JRE path. After the deployment wizard has finished executing, change to the SAS installation directory (SAS Home) (for example, C:\Program Files\SAS). Open sassw.config in a text editor and update the JREHOME property with the path to the new JRE that you want to use. For example: JREHOME=C:\Program Files\Java\jre6\bin\java.exe

Configuring or Adding SAS Products Overview: Configuring or Adding SAS Products The SAS Deployment Wizard enables you to change your SAS 9.2 deployment. Here are some of the most common scenarios:

126

About SAS Software Orders and SAS Software Depots

4

Appendix 2

1 configuring new products from your initial SAS 9.2 order.

For one reason or another, you ordered the software and did not install it. Or you installed the software, but chose not to configure it. 2 deploying additional products from a new SAS 9.2 order. The additional products are not a part of your original SAS 9.2 order. So you made another order and now have to download and deploy the new order. 3 re-installing and reconfiguring (redeploying) a SAS product. You want to move the SAS product to a new machine. Most SAS products require that you install and configure them in a two-step process: you shut down the SAS server and middle tiers and run the SAS Deployment Wizard to install the new products. Then, you restart the SAS server and middle tiers and rerun the deployment wizard to configure the newly installed products. A few products, such as SAS Drivers for ODBC, do not require the configuration step. You simply shut down the SAS server and middle tiers, install the new products, and then restart what you shut down.

About SAS Software Orders and SAS Software Depots A SAS Software Depot is a file system that consists of a collection of SAS installation files that represents one or more orders. The depot is organized in a specific format that is meaningful to the SAS Deployment Wizard, which is the tool that is used to install and initially configure SAS. The depot contains the SAS Deployment Wizard executable, one or more deployment plans, SAS installation data files, order data, and product data. A SAS Software Depot is designed to contain your initial SAS 9.2 software order and additional orders that you make in the future. When you download your additional order to your pre-existing software depot, you download only those products that you don’t already have. If you are downloading an additional order and creating a new software depot, then your download time could be longer. When you add a new SAS software order to your pre-existing SAS Software Depot, you run the SAS Download Manager and specify the location of the original depot. For more information, see “Create a Depot by Using the SAS Download Manager” on page 30. If you decide that you want to create a new SAS Software Depot for your new software order, you also run the SAS Download Manager. However, first make sure that you have fulfilled the necessary requirements described in “Prerequisites for Creating a SAS Software Depot” on page 30.

Add SAS Products that Do Not Require Configuration Some SAS products such as SAS Drivers for ODBC do not require the SAS Deployment Wizard to configure them. If the products that you are adding to your SAS deployment do not require configuration, follow these steps: 1 Verify that you have installed all the necessary third-party software outlined in

“About Installing Third-Party Products” on page 54. Note: During the SAS installation, the SAS Deployment Wizard prompts you for paths to the requested third-party software. You must have the necessary third-party software installed on the current machine, or the SAS Deployment Wizard will not let you continue with the installation. In this situation, you will have to end the SAS Deployment Wizard session and install the required third-party software before you can continue.

4

Managing Your SAS Deployment

4

Add SAS Products that Do Not Require Configuration

127

2 Make sure that your SAS Software Depot is accessible to all the machines on

3

4

5

6

which you are installing SAS. If this is not possible, then you will have to copy the entire depot to a location that the target machine can access. For information about copying your depot to a location that is not on your network, see “Create a Disc Image of Your Order” on page 49. If you are installing a SAS 9.2 product that is not a part of your original order, make sure that you have downloaded the additional order. For more information, see “About SAS Software Orders and SAS Software Depots” on page 126. Shut down your SAS server and middle tier servers. For more information, see “Operating Your Servers” in the SAS Intelligence Platform: System Administration Guide. Log on to the machine as the SAS Installer user. This is the user with which your SAS deployment was installed. For more information, see “Required External User Accounts for SAS” on page 7. Start the SAS Deployment Wizard from the highest-level directory in your SAS Software Depot using the command appropriate for your operating system. Note: If you want to use a different Java Runtime Environment, you must invoke the deployment wizard with a special startup option, -forcejreprompt. For more information, see “Specify a Different JRE” on page 124.

4

Table A2.1

Startup Commands for the SAS Deployment Wizard

Operating System

Command

Windows

setup.exe -record -deploy

UNIX

setup.sh -record -deploy

z/OS

setup.rexx -record -deploy To use a temporary directory other than /tmp, specify -templocation new-temp-dir.

For more information, see “Creating SAS Software Depots” on page 29. You should see a welcome page similar to the following:

128

Add SAS Products that Do Not Require Configuration

4

Appendix 2

7 Select the language that you want the SAS Deployment Wizard to use when it

displays text. 8 Select Install SAS Software. 9 If you have more than one SAS software order in your depot, the wizard prompts

you to select the order that you want to install. 10 If the wizard detects that there are SAS software products in your order that are more recent than what you have deployed on your machine, then the wizard automatically goes into update mode. For more information, see “Deploying Products, Installing Additional Software, and Applying Updates” on page 120. If you need to install product updates, then follow these steps: a Install the updates using the SAS Deployment Wizard.

When the installation is complete, the Deployment Summary file opens. b Perform any required configuration steps.

For more information, see “Maintenance Configuration” in Maintenance Planning for SAS 9.2. c When you are finished performing any configuration steps, rerun the SAS Deployment Wizard. 11 On the Select Deployment Type page, choose Install Additional Software.

12 (UNIX and z/OS only) Specify the location (SAS Home) where you want to install

SAS. 13 In the Select Products to Install page, select the products that you want to install. Remember, that the deployment wizard will not configure any of your selections. The wizard only installs the software.

Managing Your SAS Deployment

4

Add SAS Products that Do Not Require Configuration

129

14 Specify the location of the SAS installation data file that contains information

about the software that you have licensed for the current machine. CAUTION:

If you do not use the installation data file that supports the products you are planning to install and configure on this machine, you might experience errors later when you are trying to use the products.

4

15 When you see the Deployment Summary page, the deployment wizard has finished

collecting installation input. This is the last opportunity to go back and change any information you have provided in previous pages before the wizard begins writing to your system. Make one of the following choices: 3 Select Start to begin installing SAS files to the current machine. 3 Select Back to navigate to earlier wizard pages to change installation information previously entered.

3 Select Cancel to terminate the wizard session. Note that you will lose installation information previously entered.

130

Add SAS Products that Do Not Require Configuration

4

Appendix 2

16 Provide the remaining information as the wizard prompts you for it. For more

information, see “Install and Configure SAS Interactively” on page 76. When you see a page similar to the following, the SAS Deployment Wizard is finished:

17 Click Next to go to the Additional Resources page. 18 Click Finish to close the deployment wizard. 19 Restart your SAS server and middle tiers.

For more information, see “Operating Your Servers” in the SAS Intelligence Platform: System Administration Guide.

Managing Your SAS Deployment

4

Add SAS Products that Require Configuration

131

Add SAS Products that Require Configuration Most SAS products that you add to your deployment require that you install and configure them in a two-step process: you shut down the SAS server and middle tiers and run the SAS Deployment Wizard to install the new products. Then, you restart the SAS server and middle tiers and rerun the deployment wizard to configure the newly installed products. If the products that you are adding to your SAS deployment require configuration, follow these steps: 1 Verify that you have installed all the necessary third-party software outlined in

“About Installing Third-Party Products” on page 54. Note: During the SAS installation, the SAS Deployment Wizard prompts you for paths to the requested third-party software. You must have the necessary third-party software installed on the current machine, or the SAS Deployment Wizard will not let you continue with the installation. In this situation, you will have to end the SAS Deployment Wizard session and install the required third-party software before you can continue.

4

2 Make sure that your SAS Software Depot is accessible to all the machines on

which you are installing SAS. If this is not possible, then you will have to copy the entire depot to a location that the target machine can access. For information about copying your depot to a location that is not on your network, see “Create a Disc Image of Your Order” on page 49. 3 If you are installing a SAS 9.2 product that is not a part of your original order, make sure that you have downloaded the additional order. For more information, see “About SAS Software Orders and SAS Software Depots” on page 126. 4 Make sure that you use a deployment plan that contains any add-on products as well as all original products for the machine that you are configuring. Table A2.2

Where is My Deployment Plan?

SAS 9.2 Products Being Added

Location of My Deployment Plan

Are part of my original SAS 9.2 order

In the plan_files directory in the original SAS Software Depot

Are on a machine where a SAS 9.2 server, middle tier, or data tier already resides

In the SAS configuration directory in the Utilities directory

Are part of my new SAS 9.2 order

In the plan_files directory in the SAS Software Depot

5 Shut down your SAS server and middle tier servers.

For more information, see “Operating Your Servers” in the SAS Intelligence Platform: System Administration Guide. 6 Log on to the machine as the SAS Installer user. This is the user with which your SAS deployment was installed. For more information, see “Required External User Accounts for SAS” on page 7. 7 Start the SAS Deployment Wizard from the highest-level directory in your SAS Software Depot using the command appropriate for your operating system: Note: If you want to use a different Java Runtime Environment, you must invoke the deployment wizard with a special startup option, -forcejreprompt. For more information, see “Specify a Different JRE” on page 124.

4

132

Add SAS Products that Require Configuration

Table A2.3

4

Appendix 2

Startup Commands for the SAS Deployment Wizard

Operating System

Command

Windows

setup.exe -record -deploy

UNIX

setup.sh -record -deploy

z/OS

setup.rexx -record -deploy To use a temporary directory other than /tmp, specify -templocation new-temp-dir.

For more information, see “Creating SAS Software Depots” on page 29. You should see a welcome page similar to the following:

8 Select the language that you want the SAS Deployment Wizard to use when it

displays text. 9 Select Install SAS Software. 10 If you have more than one SAS software order in your depot, the wizard prompts you to select the order that you want to install. 11 If the wizard detects that there are SAS software products in your order that are more recent than what you have deployed on your machine, then the wizard automatically goes into update mode. For more information, see “Deploying Products, Installing Additional Software, and Applying Updates” on page 120. If you need to install product updates, then follow these steps: a Install the updates using the SAS Deployment Wizard.

When the installation is complete, the Deployment Summary file opens. b Perform any required configuration steps.

For more information, see “Maintenance Configuration” in Maintenance Planning for SAS 9.2. c When you are finished performing any configuration steps, rerun the SAS Deployment Wizard. 12 On the Select Deployment Type page, choose Perform a Planned Deployment and Install SAS Software.

Managing Your SAS Deployment

4

Add SAS Products that Require Configuration

Note: Make sure that Configure SAS Software is deselected.

133

4

13 (UNIX and z/OS only) Specify the location (SAS Home) where you want to install

SAS. 14 Specify the type of deployment plan you are using.

3 customized deployment plan Choose Specify the full path to a customized deployment plan, and then click Browse to navigate to the plan file. 3 standard deployment plan Choose Select a standard deployment plan, and then choose the appropriate plan in the drop-down list.

134

Add SAS Products that Require Configuration

4

Appendix 2

15 Select the machine on which you are installing, and select the SAS products that

you want to install, by doing the following: a Select the machine on which you are installing software from the Machine

drop-down list. Note: If you are deploying SAS on multiple machines, make sure that you are following the process described in “Installation Order Rules for Multiple Machine Deployments” on page 67.

4

b By default, all products displayed will be installed. Leave all products

selected. If there are no product changes, then the deployment wizard will not re-install any pre-existing products. 16 If you are installing SAS on a Windows 64–bit operating system, you will see a wizard page that asks you which mode you want to install SAS Foundation in (32–bit or 64–bit mode). The advantage to installing SAS in 64–bit mode is that you can access memory beyond the four GB limit imposed by the 32–bit Windows operating system. For more information, consult the deployment wizard online Help. 17 Specify the location of the SAS installation data file that contains information about the software that you have licensed for the current machine. CAUTION:

If you do not use the installation data file that supports the products you are planning to install and configure on this machine, you might experience errors later when you are trying to use the products.

4

18 (z/OS only) Provide input for the following prompts:

Note: For more information, see the Configuration Guide for SAS 9.2 Foundation for z/OS, available on the SAS Install Center (http://support.sas.com/ documentation/installcenter/).

4

3 FTP Batch Generation Specify the fully qualified host name or IP address of the z/OS mainframe machine on which you are deploying SAS. Also supply a valid user ID and

Managing Your SAS Deployment

4

Add SAS Products that Require Configuration

135

password with which the SAS Deployment Wizard will FTP deployment information to the mainframe machine.

3 Specify Jobcard Information Specify the job account, programmer name, message class, message level, time, and region values. For more information, consult your z/OS documentation.

3 Select Installation Action Choose A - Install a new SAS system.

3 Specify New Installation Qualifier Specify the path where you want to install SAS. You can also choose to require Storage Management Subsystem (SMS) parameters. For more information, consult your z/OS documentation.

3 Specify IBM’s SMS Parameters If you chose to require Storage Management Subsystem (SMS) parameters on the previous page, enter them here. For more information, consult your z/OS documentation.

3 Specify Parameters These are all parameters that are used in various DD statements throughout the installation. For more information, consult your IBM JCL documentation.

3 Specify Entry Point Specify the parameters for various ways that SAS can be run with different performance implications. Choose SAS (default ENTRY point) to run the unbundled configuration. Choose SASB to run the bundled configuration. Choose SASLPA to run the bundled configuration with some modules installed in the Link Pack Area (LPA).

3 Specify Parameters Specify additional parameters for DD statements. VOLDISK designates the VOLSER that the installed data sets will go to. For more information, consult your IBM JCL documentation.

3 Specify Parameters Specify parameters used for reblocking the SAS load modules to a library with an optimum block size. 19 Deselect any languages that you do not want SAS to support. By default, SAS

attempts to support all languages that your machine’s operating system is configured for. 20 Review the list of required third-party software that is required for the SAS software that you are installing on the current machine. (The list of third-party software depends on the SAS software that you are installing on the current machine.) 21 In the pages that immediately follow, be prepared to provide paths to these third-party applications. (The number of pages varies depending on the SAS software you are deploying on the current machine.) Note: You must provide valid paths to the requested third-party software, or the SAS Deployment Wizard will not let you continue with the installation.

4

22 The SAS Deployment Wizard has finished collecting installation input. This is the

last opportunity to go back and change any information you have provided in previous pages before the wizard begins writing to your system. Make one of the following choices: 3 Select Start to begin installing SAS files to the current machine.

136

Add SAS Products that Require Configuration

4

Appendix 2

3 Select Back to navigate to earlier wizard pages to change installation information previously entered.

3 Select Cancel to terminate the wizard session. Note that you will lose installation information previously entered.

When you see a page similar to the following, the SAS Deployment Wizard is finished:

23 Click Next to go to the Additional Resources page.

Managing Your SAS Deployment

4

Configure SAS Products

137

24 Click Finish to close the deployment wizard. 25 To configure the SAS products that you just installed, proceed to “Configure SAS

Products” on page 137.

Configure SAS Products Follow these steps to use the SAS Deployment Wizard to configure SAS products that you have already installed. 1 Make sure that the machine where you want to add the new SAS 9.2 software

contains the necessary user accounts, groups, and ports. For more information, see Chapter 2, “Setting Up Users, Groups, and Ports,” on page 5. 2 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 configuration path that was specified during the initial SAS 9.2 deployment on the Specify Configuration Information wizard page. 3 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. 4 Make sure that your SAS server and middle tiers are running.

For more information, see “Operating Your Servers” in the SAS Intelligence Platform: System Administration Guide. 5 Make sure that you use a deployment plan that contains any add-on products as

well as all original products for the machine that you are configuring.

138

Configure SAS Products

4

Appendix 2

Table A2.4

Where is My Deployment Plan?

SAS 9.2 Products Being Added

Location of My Deployment Plan

Are part of my original SAS 9.2 order

In the plan_files directory in the original SAS Software Depot

Are on a machine where a SAS 9.2 server, middle tier, or data tier already resides

In the SAS configuration directory in the Utilities directory

Are part of my new SAS 9.2 order

In the plan_files directory in the SAS Software Depot

6 Log on to the machine on which you want to add the new SAS 9.2 products as the

SAS Installer user. This is the user with which your SAS deployment was installed. For more information, see “Required External User Accounts for SAS” on page 7. 7 Start the SAS Deployment Wizard from the highest-level directory in your SAS

Software Depot using the command appropriate for your operating system. Note: If you want to use a different Java Runtime Environment, you must invoke the deployment wizard with a special startup option, -forcejreprompt. For more information, see “Specify a Different JRE” on page 124.

4

Table A2.5

Startup Commands for the SAS Deployment Wizard

Operating System

Command

Windows

setup.exe -record -deploy

UNIX

setup.sh -record -deploy

z/OS

setup.rexx -record -deploy To use a temporary directory other than /tmp, specify -templocation new-temp-dir.

For more information, see “Creating SAS Software Depots” on page 29. You should see a welcome page similar to the following:

Managing Your SAS Deployment

4

Configure SAS Products

139

8 Select the language that you want the SAS Deployment Wizard to use when it

displays text. 9 Select Install SAS Software. 10 If you have more than one SAS software order in your depot, the wizard prompts

you to select the order that you want to configure. 11 If the wizard detects that there are SAS software products in your order that are

more recent than what you have deployed on your machine, then the wizard automatically goes into update mode. For more information, see “Deploying Products, Installing Additional Software, and Applying Updates” on page 120. If you need to install product updates, then follow these steps: a Install the updates using the SAS Deployment Wizard.

When the installation is complete, the Deployment Summary file opens. b Perform the required configuration steps. For more information, see “Maintenance Configuration” in Maintenance Planning for SAS 9.2. c When you are finished performing any configuration steps, rerun the SAS Deployment Wizard. 12 Select Perform a Planned Deployment and Configure SAS Software.

Note: Make sure that Install SAS Software is deselected.

4

13 Specify the type of deployment plan you are using.

3 customized deployment plan Choose Specify the full path to a customized deployment plan, and then click Browse to navigate to the plan file.

3 standard deployment plan Choose Select a standard deployment plan, and then choose the appropriate plan in the drop-down list.

140

Configure SAS Products

4

Appendix 2

14 If there are multiple machines in your SAS deployment, select the machine on

which you are configuring. The deployment wizard lists the SAS products in your order that should be installed on the machine. 15 Choose either the Typical or the Custom configuration prompting level. You want

to be able to access the configuration page where you can set the SAS Metadata Server. The Express prompt level does not allow you to access this SAS server configuration setting. Refer to “Interactive Prompting Levels” on page 69 for more information about the SAS Deployment Wizard prompting levels. 16 On the Specify Configuration Information page, specify the configuration directory

and level for your current SAS deployment to which you are adding the new configuration. 17 If you are adding the products you are configuring to an existing SAS deployment,

you are asked to confirm your selection.

18 In the Select Products to Configure page, choose only those products that you want

to configure on the machine. The SAS Deployment Wizard has queried the metadata about your current configuration and checked the appropriate products to be configured. We recommended that you accept the product selections displayed on this page.

Managing Your SAS Deployment

4

Configure SAS Products

141

19 Provide the remaining configuration information as the wizard prompts you for it.

(The actual number of configuration pages you must provide input for depends on the prompt level you chose.) For more information, see “Install and Configure SAS Interactively” on page 76. Note: If you are adding a SAS Web application to your deployment, you must also reconfigure your Web application server. It is important to reconfigure your Web application server in the same manner that it was configured initially. If you manually configured the Web application server when you deployed SAS 9.2, then configure it again manually. If the deployment wizard automatically configured your Web application server, then choose the automatic configuration option. 4 20 When you see the Deployment Summary page, the deployment wizard has finished collecting configuration input. This is the last opportunity to go back and change any information you have provided in previous pages before the wizard begins writing to your system. Make one of the following choices: 3 Select Start to begin writing the configuration to the current machine. 3 Select Back to navigate to earlier wizard pages to change configuration information previously entered. 3 Select Cancel to terminate the wizard session. Note that you will lose configuration information previously entered.

142

Configure SAS Products

4

Appendix 2

When you see a page similar to the following, the SAS Deployment Wizard is finished:

21 Click Next to go to the Additional Resources page.

Managing Your SAS Deployment

4

Configure SAS Products

143

22 Click Review Manual Configuration Instructions and complete any

necessary manual configuration steps. The SAS Deployment Wizard writes the Instructions.html file to the Documents directory on the SAS configuration path. For example: 3 UNIX and z/OS: /opt/SAS/Lev1/Documents/Instructions.html

3 Windows: C:\SAS\Config\Lev1\Documents\Instructions.html

Note: The wizard backs up your previous Instructions.html file to the Backup subdirectory under the Documents directory on the SAS configuration path (for example, C:\SAS\Config\Lev1\Documents\Backup\Instructions.html_YYYYMM-DD–HH.MM.bak). 4 23 Click Finish to close the deployment wizard. 24 When you are configuring SAS Web applications, restart the SAS Services Application (Remote Services). On Windows, you must restart the SAS Services Application (Remote Services) from a Windows command line, using the RemoteServices.bat -start command. For more information, see “Starting or Stopping the SAS Services Application” in the SAS Intelligence Platform: System Administration Guide. 25 For multi-machine deployments, 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. 3 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. 3 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.

144

Renewing Your Software License for SAS Solutions

4

Appendix 2

26 When you are finished completing any manual configuration tasks, and you have

made the necessary backups, repeat these steps listed in this topic on each machine defined in your deployment plan. 27 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” on page 92.

Renewing Your Software License for SAS Solutions About Renewing Your Software License for SAS Solutions SAS 9.2 ships with a 30-day initial license, or SETINIT. When your new SETINIT arrives, you must renew it on every machine that runs SAS 9.2 software using the typical method according to your operating system: SAS Renewal Tool (Windows), SAS Setup (UNIX), and RENEW job (z/OS). For more information, see the instructions appropriate for your operating system on the Install Center, located at http:// support.sas.com/documentation/installcenter/92/index.html (search for “renewal”). Some SAS 9.2 solutions that depend on a SAS middle tier require you to perform an additional step. You must run the SAS Deployment Manager on your middle tier machines. During the process the deployment manager locates the new SETINIT and loads it into SAS metadata, effectively renewing your SAS solution software. (For more information about the other Deployment Manager features, see “Overview of SAS Deployment Manager and SAS Web Administration Console” in the SAS Intelligence Platform: System Administration Guide.)

Renew Your Software License for SAS Solutions After you renew your SAS software, some SAS 9.2 solutions that depend on a SAS middle tier require you to perform an additional procedure for renewal. This procedure involves using the SAS Deployment Manager to update the software information data file (SID file) in your SAS metadata repository. Note: You can automate running the deployment manager when you need to perform the same configuration action on many machines in your deployment. The deployment manager uses the same record and playback mechanism as the SAS Deployment Wizard to perform a non-interactive, silent configuration. For more information, see “Overview of Automating the SAS Installation on Multiple Machines” on page 95. 4 To renew your software license for middle-tier SAS solutions, follow these steps: 1 Make sure that you have first done the following:

obtained your new SETINIT from your SAS representative. Your SETINIT is contained in a SAS installation data file (sometimes referred to as a SID) that is attached to your software order e-mail (SOE). renewed your software license on each machine that runs SAS 9.2. Follow the instructions appropriate for your operating system located at http://support.sas.com/documentation/installcenter/92/ index.html (search for “renewal”). 2 Make sure that you have saved the new SID file on the middle-tier machines that

contain your SAS Solutions.

Managing Your SAS Deployment

4

Renew Your Software License for SAS Solutions

145

Note: On z/OS machines only, save the new SID file to the following path: SASHome/SASFoundation/9.2/setinit.sas For example: /usr/lpp/SAS/SAS_92/SASFoundation/9.2/setinit.sas

4

3 Make sure that the metadata server is running. 4 Log on to the machine where the SAS Solution is installed as the SAS Installer

user. This is the user with which your SAS deployment was installed. For more information, see “Required External User Accounts for SAS” on page 7. 5 Navigate to SAS-installation-directory/SASDeploymentManager/9.2 and launch

config.exe (Windows), config.sh (UNIX), or config.rexx (z/OS). 6 In the SAS Deployment Manager, select Update SID File in Metadata.

7 On the next page, specify the configuration directory and the level (for example,

Lev1) for your SAS Solution.

146

Renew Your Software License for SAS Solutions

4

Appendix 2

8 On the next page, enter the user ID and password for an unrestricted

administrative user.

9 On the next page, enter the absolute path to the new SID file on the machine.

Managing Your SAS Deployment

4

Renew Your Software License for SAS Solutions

10 Click Start.

When the deployment manager has successfully updated your SETINIT, you should see a page similar to the following:

11 Click Finish.

The deployment manager has located the new SETINIT and loaded it into metadata. Your SAS solution software has been renewed. 12 Repeat steps 4 – 11 on any other machines that run a SAS Solution.

147

148

Removing a SAS Configuration

4

Appendix 2

Removing a SAS Configuration Overview of Removing a SAS Configuration The Remove Existing Configuration feature of the SAS Deployment Manager provides an automated way to remove one more products of a SAS Intelligence Platform configuration from your environment. With this feature, you can remove the configurations of all SAS products or just selected products from a machine. You can remove configuration information only, or you can also remove associated user-created content. (For more information about the other Deployment Manager features, see “Overview of SAS Deployment Manager and SAS Web Administration Console” in the SAS Intelligence Platform: System Administration Guide.) Note: You can automate running the deployment manager when you need to perform the same configuration action on many machines in your deployment. The deployment manager uses the same record and playback mechanism as the SAS Deployment Wizard to perform a non-interactive, silent configuration. For more information, see “Overview of Automating the SAS Installation on Multiple Machines” on page 95. 4

Note: The SAS Deployment Manager does not uninstall or otherwise affect the SAS software that is located in the SAS installation directory. To uninstall SAS software, see “Overview of Uninstalling the SAS Intelligence Platform” on page 157. 4 The Remove Existing Configuration feature of the SAS Deployment Manager is useful for the following purposes: 3 to remove a product that you will no longer be using 3 to move a product (for example, a SAS Application Server) from one machine to another. In this situation you would do the following:

Managing Your SAS Deployment

4

Overview of Removing a SAS Configuration

149

1 Use the SAS Deployment Manager to remove the product’s configuration

from the first machine. 2 Use the SAS Deployment Wizard to install and configure the product on the

second machine.

3 to recover from errors in the initial configuration of a product or to implement different configuration options for a product. In these situations you would do the following: 1 Use the SAS Deployment Manager to remove the product’s configuration. 2 Use the SAS Deployment Wizard to configure the product on the same

machine, and select different configuration options than you selected previously.

When you remove a product’s configuration, the SAS Deployment Manager performs the following tasks:

3 stops the product (or the associated service) if it is running, as well as any dependent products (or associated services). For example:

3 If you are removing the configuration of a running OLAP server, then it stops the server. If the server is installed as a Windows service, then it stops the service.

3 If you are removing the configuration of a running metadata server, then it stops the server (or the associated Windows service). It also stops any running servers and services that depend on the metadata server, OLAP servers, stored process servers, table servers, workspace servers, pooled workspace servers, batch servers, SAS/SHARE servers, and SAS/CONNECT servers. Note: The SAS Deployment Manager does not stop the object spawner. You must do this manually.

4

3 If you are removing the configuration for SAS Foundation Services, then it stops the SAS Services Application (Remote Services) or the associated Windows service.

3 deletes metadata objects that contain the product’s configuration information. For example, if you remove a server configuration, then the server’s metadata definition is removed and the server no longer appears in the Server Manager tree in SAS Management Console.

3 on Windows systems, deletes shortcuts that are associated with the product. For example, if you remove a server configuration, then any shortcuts for starting, stopping, pausing, or resuming the server are deleted.

3 on Windows systems, deletes the service (if applicable) that is associated with the product. For example, if you remove a server configuration, and if the server runs as a Windows service, then the service is removed.

3 deletes configuration files and directories that are associated with the product. For example, if you remove the configuration for a SAS OLAP server, then the server’s configuration directory, files, scripts, sasusers directory, and logs directory are deleted. The only exception is sasv9_usermods.cfg, which is retained if its contents have changed since the initial installation.

3 deletes site-specific portal content if you are removing the configuration for the SAS Information Delivery Portal and if you select the option to Remove user content for SAS Information Delivery Portal. The content that is removed includes portal pages; portlets; changes to page navigation, page layout, and package sort order; and other similar customizations.

150

Summary of Steps for Removing a SAS Configuration

4

Appendix 2

3 determines whether other products in your deployment depend on the removed products. If dependent products exist, and if you have not selected those products for removal, then the SAS Deployment Manager prompts you to remove them. For example, the SAS BI Dashboard depends on the SAS Information Delivery Portal. If you remove the configuration for the SAS Information Delivery Portal, but you do not remove the configuration for the SAS BI Dashboard, then the SAS Deployment Manager prompts you to remove it. For more information about dependencies, see “Identify Dependent SAS Products” on page 151.

3 creates an HTML page that lists the items that were removed and describes any additional manual tasks that you need to perform. The page is created in a temporary location. You should save it to a permanent location on your network or file system.

3 writes detailed log messages to a file called product-name_unconfigure_date-and-time, where product-name identifies the product that was removed. The deployment manager writes this file to SAS-configuration-directory\Levn\Logs\Configure.

Summary of Steps for Removing a SAS Configuration Here is a summary of the steps that you should take when removing a configuration: 1 Determine which products’ configurations to remove. 2 Determine which products depend on the products that you are removing. You will

need to remove the configuration for each of these products. For details, see “Identify Dependent SAS Products” on page 151. 3 For each product that you plan to remove, identify the machine where it is

installed. In a single-machine installation, you can remove the configurations of multiple products as well their dependent products in a single execution of the SAS Deployment Manager. In a multiple-machine installations, you should remove middle-tier products first. Then remove products on the SAS server tier. If you are removing the metadata server, you should remove it last. 4 Create a complete backup of your system before removing a configuration. This

backup should include a correct backup of the metadata server. (See “Best Practices for Backing Up and Restoring Your System” in SAS Intelligence Platform: System Administration Guide.) This step is important because it is not possible to undo the removal of a configuration. 5 If you are removing a server, you might want to stop the server (or its associated

service), although this is not required. However, you must stop the object spawner if you are removing one of the servers that it runs. Note: The only exception is the metadata server, which must be running.

4

6 If you are unconfiguring a SAS Web application, then depending on the operating

system and the Web application server that you are using, do the following:

3 JBoss: Always stop the JBoss Web application server before unconfiguring any of the SAS Web applications.

3 WebLogic: 3 On UNIX, keep the WebLogic Web application server running while unconfiguring the SAS Web application.

Managing Your SAS Deployment

4

Identify Dependent SAS Products

151

3 On Windows, always stop the WebLogic Web application server before unconfiguring any of the SAS Web applications. (Make sure that the WebLogic Node Manager is running.)

3 WebSphere: Keep the WebSphere Web application server running while unconfiguring the SAS Web application. 7 If you are unconfiguring a SAS middle tier on UNIX, first stop SAS Remote

Services before running the SAS Deployment Manager. 8 When all of the preparatory steps are complete, follow the steps that are described

in “Remove a Configuration” on page 153.

Identify Dependent SAS Products If you remove the configuration of a product that another product depends on, then the dependent product will not be able to function. Therefore, when you remove a product’s configuration, the SAS Deployment Manager requires that you also remove the configurations of any dependent products. Product dependencies are shown in the following table. If you remove the configuration for a product in the left column, then you must also remove the configurations for all of the products that are in the right column opposite that product. For example: 3 If you remove the SAS BI Dashboard configuration, then you do not need to remove any other products. No products depend on the SAS BI Dashboard.

3 If you remove the SAS BI Report Services Workspace Configuration, then you must also remove the following dependent products: BI Report Services, SAS BI Dashboard, SAS Web Report Studio, and SAS Web Report Viewer. 3 If you remove the SAS Metadata Server configuration, then you must remove all other products. Table A2.6

Dependencies in the SAS Intelligence Platform

Product

Dependent Products*

BI Report Services

None

MySQL Database Server

SAS Shared Services (unless SAS Shared Services is using the SAS Table Server) SAS Solutions Services

Platform Process Manager

SAS Web Report Studio and SAS BI Dashboard (if report scheduling is enabled via Platform Process Manager)

SAS Application Server Context

All products except Platform Process Manager

SAS BI Dashboard

None

SAS BI Report Services Workspace Configuration

BI Report Services SAS BI Dashboard SAS Web Report Studio SAS Web Report Viewer

152

Identify Dependent SAS Products

4

Appendix 2

Product

Dependent Products*

SAS Foundation Services

Web application server (JBoss, WebLogic, or WebSphere) SAS BI Dashboard SAS Help Viewer Metadata Configuration SAS Information Delivery Portal SAS Information Delivery Portal JPS Extension SAS Shared Services SAS Web OLAP Viewer SAS Web Report Studio SAS Web Report Viewer SAS Web Infrastructure Platform

SAS Grid Manager Control Server Configuration

SAS Grid Manager Node Configuration

SAS Grid Manager Control Server Configuration (with other grid middleware)

SAS Grid Manager Node Configuration (with other grid middleware)

SAS Information Delivery Portal

SAS BI Dashboard SAS BI Portlets SAS Shared Services

SAS Metadata Server

All products

SAS Object Spawner

BI Report Services Operating System Scheduling Services SAS BI Dashboard SAS BI Report Services Workspace Configuration SAS Pooled Workspace Server SAS Shared Services SAS Stored Process Server SAS Web Report Studio SAS Web Report Viewer SAS Workspace Server

SAS Pooled Workspace Server

SAS BI Dashboard SAS BI Report Services Workspace Configuration SAS Shared Services (if used by SAS Table Server)

SAS Shared Services

None

SAS Solutions Services

None

SAS Stored Process Server

None

SAS Table Server

SAS Shared Services (unless SAS Shared Services is using MySQL Database Server)

Managing Your SAS Deployment

Product SAS Web Infrastructure Platform

4

Remove a Configuration

153

Dependent Products* SAS BI Dashboard SAS BI Portlets SAS Information Delivery Portal SAS Web OLAP Viewer SAS Web Report Studio SAS Web Report Viewer SAS Themes

SAS Web Report Studio

SAS BI Dashboard SAS BI Portlets

SAS Workspace Server

SAS BI Dashboard

Web application server (JBoss, WebLogic, or WebSphere)

SAS BI Dashboard SAS BI Portlets SAS Help Viewer Metadata Configuration SAS Information Delivery Portal SAS Shared Services SAS Web OLAP Viewer SAS Web Report Studio SAS Web Report Viewer SAS Web Infrastructure Platform SAS Themes

* These products depend on the product in column 1. Therefore, they must be removed if the product in column 1 is removed.

When you remove a product’s configuration, the SAS Deployment Manager checks to see whether your deployment plan includes any products that depend on that product. If dependent products exist, and if you have not selected those products for removal, then the SAS Deployment Manager prompts you to remove them.

Remove a Configuration In a single-machine installation, you can remove the configurations of multiple products as well their dependent products in a single execution of the SAS Deployment Manager.

154

Remove a Configuration

4

Appendix 2

In a multiple-machine installations, you should remove middle-tier product configurations first. Then remove product configurations on the SAS server tier. If you are removing the metadata server configuration, then you should remove it last. Note: When removing a configuration, the SAS Deployment Manager does not delete any configuration log files associated with the configuration. However, server log files are removed. 4 Follow these steps to run the SAS Deployment Manager to remove the configurations from each machine: 1 Make sure that you have completed the preparatory steps that are described in

“Summary of Steps for Removing a SAS Configuration” on page 150. 2 On the host machine for the products whose configurations you are removing,

navigate to SAS-installation-directory/SASDeploymentManager/9.2 and launch config.exe (Windows), config.sh (UNIX), or config.rexx (z/OS). 3 In the SAS Deployment Manager, select Remove Existing Configuration.

If you are removing the SAS Information Delivery Portal, then you can also select the option to remove user content that is associated with the portal. If you select this option, the SAS Deployment Manager removes portal pages; portlets; changes to page navigation, page layout, and package sort order; and other similar customizations. CAUTION:

Use caution when choosing the option to remove user content for the SAS Information Delivery Portal. The content cannot be recovered unless you have a complete backup of your system. 4 4 In the next page, specify the configuration directory and the level (for example,

Lev1) from which the configuration is to be removed. 5 In the next page, enter the user ID and password for an unrestricted

administrative user.

Managing Your SAS Deployment

4

Remove a Configuration

155

6 On the next page, select the check boxes for the products that you want to remove.

For each product that you select, be sure to also include the other products on the machine that depend on that product (see “Identify Dependent SAS Products” on page 151). 7 Detailed log messages are written to a file called

product-name_unconfigure_date-and-time, where product-name identifies the product that was removed. The deployment manager writes this file to SAS-configuration-directory\Levn\Logs\Configure. 8 When the configuration removal is complete, the Additional Resources page is

displayed. In this page, click on the following document name: configuration-name-and-level_ConfigurationRemoval.html The document contains details about the products that were removed and additional manual steps that you might need to perform. The document is created in a temporary location. You should save it on your network or your file system so that you can refer to it later. For details about what occurs when you remove a configuration, see “Overview of Removing a SAS Configuration” on page 148. After removing the configuration, you might need to take one of the following additional steps, depending on the reason for the removal:

3 run the SAS Deployment Wizard to create a new configuration. For details, see “Configuring or Adding SAS Products” on page 125.

3 uninstall the associated software (if you will no longer be using the product on the current machine, or if you will be reinstalling the software on the current machine). For details, see “Overview of Uninstalling the SAS Intelligence Platform” on page 157.

156

157

APPENDIX

3 Uninstalling the SAS Intelligence Platform Overview of Uninstalling the SAS Intelligence Platform 157 Stopping SAS Servers That Are Running 158 Stop SAS Servers That Are Running on Windows 158 Stop SAS Servers That Are Running on UNIX 158 Uninstalling Your SAS Software 158 Overview of Uninstalling Your SAS Software 158 Uninstall SAS on Windows 158 Uninstall SAS on UNIX 159 Uninstalling Third-Party Software 159 Uninstalling the SAS JRE and the JDK 160 Deployed Web Applications 160 Overview of Uninstalling the SAS JRE and the JDK 160 Windows 160 UNIX 160

Overview of Uninstalling the SAS Intelligence Platform Remove software from machines deploying SAS 9.2 in the following order: 1 client-tier machines 2 middle-tier machines 3 server-tier machines 4 metadata server machine

To uninstall the SAS 9.2 Intelligence Platform, you need to perform the following steps—where applicable—on each machine in your deployment: 1 Unconfigure your SAS software.

See “Remove a Configuration” on page 153. 2 Stop SAS servers that are running.

See “Stopping SAS Servers That Are Running” on page 158. 3 Uninstall your SAS software.

See “Uninstalling Your SAS Software” on page 158. 4 Uninstall third-party software.

See “Uninstalling Third-Party Software” on page 159. 5 Uninstall the SAS JRE and the JDK.

See “Uninstalling the SAS JRE and the JDK” on page 160.

158

Stopping SAS Servers That Are Running

4

Appendix 3

Stopping SAS Servers That Are Running Stop SAS Servers That Are Running on Windows Before uninstalling any software on a machine, you must stop any SAS servers that are running there. To stop SAS servers running on Windows, follow steps:

3 Log on to the machine as the SAS Installer user (the user account used to install the SAS Software) or as the Administrator (or a user in the Administrators group).

3 Run the Windows Services snap-in (Start I Control Panel I Administrative Tools

I Services).

3 Stop all of the SAS services that are running. For more information, refer to your Microsoft Windows documentation.

Stop SAS Servers That Are Running on UNIX Before uninstalling any software on a machine, you must stop any SAS servers that are running there. To stop SAS servers running on UNIX, follow steps:

3 Log on to the machine as the SAS user. 3 From the Levn SAS configuration directory, run the following command: sas.servers stop

For example: /opt/SAS/Config/Lev1/sas.servers stop

Uninstalling Your SAS Software Overview of Uninstalling Your SAS Software You should now uninstall the SAS products. Do not uninstall the SAS JRE (Java Runtime Environment). The Java uninstallers need the JRE in order to execute.

Uninstall SAS on Windows To uninstall SAS software from a Windows machine, perform these steps: 1 Remove the configurations for any SAS software you are uninstalling by following

the instructions described in, “Remove a Configuration” on page 153. 2 Make sure that you are logged on as the SAS Installer user (the user account used

to install the SAS Software) or as the Administrator (or a user in the Administrators group). 3 Open the Control Panel by selecting Start

I Settings I Control Panel.

4 From the Control Panel, open the Add or Remove Programs window. 5 From the Add or Remove Programs window, remove SAS software components.

Note:

Remove the SAS Versioned Jar Repository last.

4

6 Close the Add or Remove Programs window and the Control Panel.

Uninstalling the SAS Intelligence Platform

4

Uninstalling Third-Party Software

159

7 Delete your SAS installation directory (SAS Home) (for example, C:\Program

Files\SAS). 8 Delete your SAS configuration directory (for example, C:\SAS\Config\Lev1). 9 Delete the SAS directory under \Local Settings\Application Data for the

SAS Installer user: \Documents and Settings\SAS-Installer-ID\Local Settings\Application Data\SAS

Uninstall SAS on UNIX To uninstall SAS software on a UNIX machine, perform these steps: 1 Make sure that you have first unconfigured the SAS software on the machine by following the directions in “Removing a SAS Configuration” on page 148. 2 Make sure that you have permission to delete files from the SAS home directory (the directory in which your SAS software is installed). 3 Make sure that you have permission to delete files from your configuration directory. 4 Make sure that you are logged on as the SAS Installer user (the user account used to install the SAS Software). 5 Remove the SAS 9.2 installation directories by executing the rm -rf command on the top-level SAS 9.2 installation directory. Note that you must not cd to this directory before executing the command. For example, if the top-level SAS 9.2 installation directory is /opt/SAS/SAS_92, then you would use the following command: rm -rf /opt/SAS/SAS_9.2

Uninstalling Third-Party Software The SAS Intelligence Platform often makes use of third-party products, such as a Web application server. You can determine whether third-party software was deployed on a particular machine by reviewing your deployment plan file (plan.xml). To uninstall these products, use the same procedures that you used to uninstall your SAS software. (See “Uninstalling Your SAS Software.”) The following table shows the main third-party products that are used with the SAS 9.2 Intelligence Platform.

160

Uninstalling the SAS JRE and the JDK

4

Appendix 3

Table A3.1 Type of Product Web application servers/servlet containers

Scheduling servers

Products

3 3 3 3

JBoss Application Server WebLogic Server WebSphere Application Server Platform Process Manager

Uninstalling the SAS JRE and the JDK Deployed Web Applications Undeploy and delete WAR and EAR files that are deployed to your Web application server/servlet container.

Overview of Uninstalling the SAS JRE and the JDK After you have uninstalled your SAS software and your third-party software, you can uninstall the Java Runtime Environment (JRE) that SAS uses. If the Java Development Kit (JDK) on the machine was being used only in support of SAS Web applications, you can also remove the JDK.

Windows To uninstall the JRE and the JDK used by SAS from a Windows machine, perform these steps: 1 Open the Control Panel by selecting Start

I Settings I Control Panel.

2 From the Control Panel, open the Add or Remove Programs window. 3 From the Add or Remove Programs window, remove the products. 4 Close the Add or Remove Programs window and the Control Panel.

UNIX This procedure applies only if you had the SAS Foundation installed. In any event, proceed with caution. Note: Make sure that the JRE and JDK are not being used for other software on the machine before you delete the products. 4 To uninstall the JRE and the JDK used by SAS from a UNIX machine, perform these steps: 1 Locate the directory where these products are installed, and make sure that you

have permission to delete files in this directory. 2 Delete the product with uninstallers whenever you can. Otherwise, use the rm

-rf command on the top-level installation folder.

161

APPENDIX

4 Recommended Reading Recommended Reading

161

Recommended Reading Here is the recommended reading list for this title: 3 Maintenance Planning for SAS 9.2 3 SAS Enterprise Miner: Single-User Installation Guide

3 3 3 3 3 3 3

SAS Intelligence Platform: Overview SAS Intelligence Platform: Data Administration Guide SAS Intelligence Platform: Security Administration Guide SAS Intelligence Platform: System Administration Guide SAS Intelligence Platform: Application Server Administration Guide SAS Intelligence Platform: Web Application Administration Guide SAS Intelligence Platform: Desktop Application Administration Guide

For a complete list of SAS publications, go to support.sas.com/bookstore. If you have questions about which titles you need, please contact a SAS Publishing Sales Representative at: SAS Publishing Sales SAS Campus Drive Cary, NC 27513 Telephone: 1-800-727-3228 Fax: 1-919-531-9439 E-mail: [email protected] Web address: support.sas.com/bookstore Customers outside the United States and Canada, please contact your local SAS office for assistance.

162

163

Glossary attribute

A003349521a characteristic that is part of the standard metadata for an object. Examples of attributes include the object’s name, creation date, and modification date. authentication

the process of verifying the identity of a person or process within the guidelines of a specific authorization policy. authentication domain

a SAS internal category that pairs logins with the servers for which they are valid. For example, an Oracle server and the SAS copies of Oracle credentials might all be classified as belonging to an OracleAuth authentication domain. cluster

a group of machines that participate in load balancing. Each machine in the cluster runs an object spawner that handles client requests for connections. component

a self-contained, reusable programming object that provides some type of service to other components in an object-oriented programming environment. connection profile

a client-side definition of where a metadata server is located. The definition includes a computer name and a port number. In addition, the connection profile can also contain user connection information. credentials

the user ID and password for an account that exists in some authentication provider. daemon

a process that starts and waits either for a request to perform work or for an occurrence of a particular event. After the daemon receives the request or detects the occurrence, it performs the appropriate action. If nothing else is in its queue, the daemon then returns to its wait state. data warehouse

a collection of data that is extracted from one or more sources for the purpose of query, reporting, and analysis. In contrast to a data mart, a data warehouse is better suited for storing large amounts of data that originates in other corporate applications or which is extracted from external data sources such as public databases.

164 Glossary

database management system

a software application that enables you to create and manipulate data that is stored in the form of databases. Short form: DBMS. database server

a server that provides relational database services to a client. Oracle, DB/2 and Teradata are examples of relational databases. DBMS

See database management system. deploy

to install an instance of operational SAS software and related components. The deployment process often includes configuration and testing as well. See also migrate. deployment plan

information about 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. domain

a database of users that has been set up by an administrator by using a specific authentication provider such as LDAP or the host operating system. The domain name should be unique within your enterprise. For example, you should not have a Windows domain and a UNIX domain that are both named "SALES". See also authentication domain. encryption

the act or process of converting data to a form that only the intended recipient can read or use. Extensible Markup Language

a markup language that structures information by tagging it for content, meaning, or use. Structured information contains both content (for example, words or numbers) and an indication of what role the content plays. For example, content in a section heading has a different meaning from content in a database table. Short form: XML. Integrated Windows authentication

a Microsoft technology that facilitates use of authentication protocols such as Kerberos. In the SAS implementation, all participating components must be in the same Windows domain or in domains that trust each other. Internet Protocol Version 6

a protocol that specifies the format for network addresses for all computers that are connected to the Internet. This protocol, which is the successor of Internet Protocol Version 4, uses hexadecimal notation to represent 128-bit address spaces. The format can consist of up to eight groups of four hexadecimal characters, delimited by colons, as in FE80:0000:0000:0000:0202:B3FF:FE1E:8329. As an alternative, a group of consecutive zeros could be replaced with two colons, as in FE80::0202:B3FF:FE1E:8329. Short form: IPv6 See also IP address and Internet Protocol Version 4. IPv6

See Internet Protocol Version 6. IWA

See Integrated Windows authentication.

Glossary 165

JAR file

a Java Archive file. The JAR file format is used for aggregating many files into one file. JAR files have the file extension .jar. Java

a set of technologies for creating software programs in both stand-alone environments and networked environments, and for running those programs safely. Java is a Sun Microsystems trademark. Java Database Connectivity

a standard interface for accessing SQL databases. JDBC provides uniform access to a wide range of relational databases. It also provides a common base on which higher-level tools and interfaces can be built. Short form: JDBC. Java Development Kit

a software development environment that is available from Sun Microsystems, Inc. The JDK includes a Java Runtime Environment (JRE), a compiler, a debugger, and other tools for developing Java applets and applications. Short form: JDK. JDBC

See Java Database Connectivity. JDK

See Java Development Kit. job

a metadata object that specifies processes that create output. load balancing

for IOM bridge connections, a program that runs in the object spawner and that uses an algorithm to distribute work across object server processes on the same or separate machines in a cluster. localhost

a keyword that is used to specify the machine on which a program is executing. If a client specifies localhost as the server address, the client connects to a server that runs on the same machine. login

a SAS copy of information about an external account. Each login includes a user ID and belongs to one SAS user or group. Most logins do not include a password. metadata identity

a metadata object that represents an individual user or a group of users in a SAS metadata environment. Each individual and group that accesses secured resources on a SAS Metadata Server should have a unique metadata identity within that server. metadata object

a set of attributes that describe a table, a server, a user, or another resource on a network. The specific attributes that a metadata object includes vary depending on which metadata model is being used. middle tier

in a SAS business intelligence system, the architectural layer in which Web applications and related services execute. The middle tier receives user requests, applies business logic and business rules, interacts with processing servers and data servers, and returns information to users. migrate

to populate a new deployment of SAS software with the content, data, or metadata (or a combination of these) from an existing deployment. Migrating might include

166 Glossary

upgrading to a new software release, converting data or metadata, or other changes to ensure compatibility. object

in object-oriented programming, an instantiation or specific representation of a class. object spawner

a program that instantiates object servers that are using an IOM bridge connection. The object spawner listens for incoming client requests for IOM services. When the spawner receives a request from a new client, it launches an instance of an IOM server to fulfill the request. Depending on which incoming TCP/IP port the request was made on, the spawner either invokes the administrator interface or processes a request for a UUID (Universal Unique Identifier). OLAP

See online analytical processing. online analytical processing

a software technology that enables users to dynamically analyze data that is stored in cubes. Short form: OLAP. planned deployment

a method of installing and configuring a SAS business intelligence system. This method requires a deployment plan that contains information about the different hosts that are included in the system and the software and SAS servers that are to be deployed on each host. The deployment plan then serves as input to an installation and configuration tool called the SAS Deployment Wizard. pre-installation checklist

a checklist that enumerates the tasks a customer must perform before installing the business intelligence platform. The primary task is to create a set of operating system user accounts on the metadata server host. See also metadata server. resource

any object that is registered in a metadata repository. For example, a resource can be an application, a data store, a dimension in an OLAP cube, a metadata item, an access control template, or a password. SAS Application Server

in the SAS Intelligence Platform, a logical entity that represents the SAS server tier. This logical entity contains specific servers (for example, a SAS Workspace Server and a SAS Stored Process Server) that execute SAS code. A SAS Application Server has relationships with other metadata objects. For example, a SAS library can be assigned to a SAS Application Server. When a client application needs to access that library, the client submits code to the SAS Application Server to which the library is assigned. SAS authentication

a form of authentication in which the target SAS server is responsible for requesting or performing the authentication check. SAS servers usually meet this responsibility by asking another component (such as the server’s host operating system, an LDAP provider, or the SAS Metadata Server) to perform the check. In a few cases (such as SAS internal authentication to the metadata server), the SAS server performs the check for itself. A configuration in which a SAS server trusts that another component has pre-authenticated users (for example, Web authentication) is not part of SAS authentication. SAS configuration directory

the location where configuration information for a SAS deployment is stored. The configuration directory contains configuration files, logs, scripts, repository files, and other items for the SAS software that is installed on the machine.

Glossary 167

SAS data set

a file whose contents are in one of the native SAS file formats. There are two types of SAS data sets: SAS data files and SAS data views. SAS data files contain data values in addition to descriptor information that is associated with the data. SAS data views contain only the descriptor information plus other information that is required for retrieving data values from other SAS data sets or from files that are stored in other software vendors’ file formats. SAS Deployment Manager

a cross-platform utility that manages SAS deployments. The SAS Deployment Manager supports functions such as updating passwords for your SAS deployment, rebuilding SAS Web applications, and removing configurations. SAS Deployment Wizard

a cross-platform utility that installs and initially configures many SAS products. Using a SAS installation data file and, when appropriate, 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. SAS Foundation Services

a set of core infrastructure services that programmers can use in developing distributed applications that are integrated with the SAS platform. These services provide basic underlying functions that are common to many applications. These functions include making client connections to SAS application servers, dynamic service discovery, user authentication, profile management, session context management, metadata and content repository access, activity logging, event management, information publishing, and stored process execution. See also service. SAS installation data file

a control file containing license information that is required in order to install SAS. SAS installation directory

the location where your SAS software is installed. This location is the parent directory to the installation directories of all SAS products. The SAS installation directory is also referred to as SAS Home in the SAS Deployment Wizard. SAS Management Console

a Java application that provides a single user interface for performing SAS administrative tasks. SAS Metadata Server

a multi-user server that enables users to read metadata from or write metadata to one or more SAS Metadata Repositories. The SAS Metadata Server uses the Integrated Object Model (IOM), which is provided with SAS Integration Technologies, to communicate with clients and with other servers. SAS OLAP Server

a SAS server that provides access to multidimensional data. The data is queried using the multidimensional expressions (MDX) language. SAS Pooled Workspace Server

a SAS Workspace Server that is configured to use server-side pooling. In this configuration, the SAS object spawner maintains a collection of workspace server processes that are available for clients. SAS Software Depot

a file system that consists of a collection of SAS installation files that represents one or more orders. The depot is organized in a specific format that is meaningful to the SAS Deployment Wizard, which is the tool that is used to install and initially

168 Glossary

configure SAS. The depot contains the SAS Deployment Wizard executable, one or more deployment plans, a SAS installation data file, order data, and product data. SAS Stored Process Server

a SAS IOM server that is launched in order to fulfill client requests for SAS Stored Processes. SAS Workspace Server

a SAS IOM server that is launched in order to fulfill client requests for IOM workspaces. SAS/CONNECT server

a server that provides SAS/CONNECT services to a client. When SAS Data Integration Studio generates code for a job, it uses SAS/CONNECT software to submit code to remote computers. SAS Data Integration Studio can also use SAS/ CONNECT software for interactive access to remote libraries. SAS/SHARE server

the result of an execution of the SERVER procedure, which is part of SAS/SHARE software. A server runs in a separate SAS session that services users’ SAS sessions by controlling and executing input and output requests to one or more SAS libraries. server context

a SAS IOM server concept that describes how SAS Application Servers manage client requests. A SAS Application Server has an awareness (or context) of how it is being used and makes decisions based on that awareness. For example, when a SAS Data Integration Studio client submits code to its SAS Application Server, the server determines what type of code is submitted and directs it to the correct physical server for processing (in this case, a SAS Workspace Server). service

one or more application components that an authorized user or application can call at any time to provide results that conform to a published specification. For example, network services transmit data or provide conversion of data in a network, database services provide for the storage and retrieval of data in a database, and Web services interact with each other on the World Wide Web. See also SAS Foundation Services. servlet

a Java program that runs on a Web server. Servlets can be considered a complementary technology to applets, which run in Web browsers. Unlike applet code, servlet code does not have to be downloaded to a Web browser. Instead, servlets send HTML or other appropriate content back to a browser or to another type of Web-based client application. servlet container

an execution environment for Java servlets that contains a Java Virtual Machine. The servlet container also provides other services for servlets and for the Web applications that those servlets are part of. For example, the servlet container converts HTTP requests that are sent by clients to Java objects that servlets can work with, and it converts the output of servlets to HTTP responses. An example of a popular servlet container is the JBoss server. single sign-on

an authentication model that enables users to access a variety of computing resources without being repeatedly prompted for their user IDs and passwords. For example, single sign-on can enable a user to access SAS servers that run on different platforms without interactively providing the user’s ID and password for each platform. Single sign-on can also enable someone who is using one application to launch other applications based on the authentication that was performed when the user initially logged on.

Glossary 169

spawner

See object spawner. SSO

See single sign-on. trusted user

a privileged service account that can act on behalf of other users on a connection to the metadata server. unrestricted user

a special user of a metadata server who can access all metadata on the server (except for passwords, which an unrestricted user can overwrite but cannot read). An unrestricted user can also perform administrative tasks such as starting, stopping, pausing, and refreshing the metadata server. You are an unrestricted user if your user ID is listed in the adminUsers.txt file and is preceded by an asterisk. update mode

an operating state of the SAS Deployment Wizard in which users are required to install software updates before they can perform any other deployment tasks. The SAS Deployment Wizard automatically goes into update mode when it determines that the current SAS order contains new versions or maintenance updates to the deployed products in a given SAS installation directory. Web application

an application that is accessed via a Web browser over a network such as the Internet or an intranet. SAS Web applications are Java Enterprise Edition (JEE) applications that are delivered via Web application archive (WAR) files. The applications can depend on Java and non-Java Web technologies. Web authentication

a configuration in which users of Web applications and Web services are verified at the Web perimeter and the metadata server trusts that verification. Web browser

a software application that is used to present Web content. To accomplish this task, the browser submits URL (Uniform Resource Locator) requests to a Web server and handles any results that the request generates. Web Distributed Authoring and Versioning

a set of extensions to the HTTP protocol that enables users to collaboratively edit and manage files on remote Web servers. Short form: WebDAV. WebDAV

See Web Distributed Authoring and Versioning. WebDAV server

an HTTP server that supports the collaborative authoring of documents that are located on the server. The server supports the locking of documents, so that multiple authors cannot make changes to a document at the same time. It also associates metadata with documents in order to facilitate searching. The SAS business intelligence applications use this type of server primarily as a report repository. Common WebDAV servers include the Apache HTTP Server (with its WebDAV modules enabled), Xythos Software’s WebFile Server, and Microsoft Corporation’s Internet Information Server (IIS). workspace

in the IOM object hierarchy for a SAS Workspace Server, an object that represents a single session in SAS. XML

See Extensible Markup Language.

170

171

Index A accessibility features 3 accounts See user accounts administration 103 setup tasks 104 system administration tasks 110

groups defining 14 pre-installation checklist for 15, 16 sas group (UNIX) 15 SAS Server Users group 14 SASGRP group (z/OS) 15 setting up 5

I

C changing SAS order details 45 checklists pre-installation for groups 15, 16 pre-installation for port numbers 21 pre-installation for users 11, 12, 13 configuration automatic for Web application server 55 information for SAS Deployment Wizard 81 interactive 76 logs 115 modifying to optimize performance 108 removing information or content 148 configuration directories protections on Windows 104 configuration directory creating for z/OS 17 Configuration Errors.html file 115

D deleting a SAS order 47 deployment plans 66 DeploymentSummary.html file 114 directory service accounts 10

installation 2 automating for multiple machines 95 from third-party software Web site 57 full prompt mode 99 interactive 76 partial prompt mode 98 products from Platform Suite for SAS 57 quiet mode 97 SAS OnlineDoc for the Web 74 third-party products 53 verifying 99 Instructions.html file 114 interactive prompting levels 69 internal user accounts 6 IPv6 (Internet Protocol version 6) 67

J Java Development Kit installing from third-party software Web site 57 recording information about 58 Java Runtime Environment (JRE) in Russia 57 uninstalling 160 JBoss Application Server recording information about 58

E L

external user accounts 7 rights required for 8

F full prompt mode installation

99

local accounts 10 logs configuration 115 LSF Administrator account 9 LSF User account 9

G

M

grid computing Platform Suite for SAS and 57

managing a SAS deployment 119 removing a configuration 148

172 Index

metadata repositories, accessing 111 multicast addresses 19 multiple machine deployments 67

S

N network accounts 10

O operating system protections for configuration directories on Windows optimizing performance changes to initial configuration 108

104

P partial prompt mode installation 98 passwords policies for SAS system accounts 11 permissions 106 Platform Grid Management Service installing 57 Platform LSF (Load Sharing Facility) installing 57 Platform Process Manager installing 57 Platform Suite for SAS installing products from 57 recording information about 58 playing back SAS Deployment Wizard response files full prompt mode 99 managing a machine reboot 98 monitoring the wizard 100 partial prompt mode 98 quiet mode 97 verifying the installation 99 ports designating 19 reserving for SAS servers and spawners 21 pre-installation checklists for groups 15, 16 for port numbers 21 for third-party products 58 for users 11, 12, 13

Q quiet mode installation

97

R reboot during response file playback 98 recording SAS Deployment Wizard response files removing a configuration 148, 150 identifying dependent components 151 running the SAS Deployment Manager 153 required user accounts 5 reserving ports SAS servers and spawners 21 response files playing back 97 recording 96 rights external user accounts 8

96

97

SAS Administrator account 6 SAS Deployment Manager removing a configuration 148, 153 SAS Deployment Tester 95 SAS Deployment Wizard 66 configuration information 81 creating SAS Software Depots 40 documents and reports 114 installing and configuring SAS 76 interactive prompting levels 69 monitoring during playback 100 options 66, 69 response files 96 SAS Download Manager creating SAS Software Depots 30 SAS folders 112 sas group (UNIX) 15 SAS Installer account 8 SAS Intelligence Platform deploying 2 software offerings 1 uninstalling 157 SAS OnlineDoc for the Web, installing 74 SAS orders and SAS Software Depots 126 changing order details 45 creating a disc image 49 deleting an order 47 SAS server tier, troubleshooting 115 SAS Server Users group 14 SAS servers reserving ports for 21 stopping 158 validation 92 SAS software uninstalling 158 SAS Software Depots 25 and SAS orders 126 benefits 27 best practices for 29 creating with SAS Deployment Wizard 40 creating with SAS Download Manager 30 installing third-party products 56 prerequisites for creating 30 SAS Spawned Servers account 8 SAS system accounts 5 passwords 11 SAS Trusted User account 6 SASGRP group (z/OS) 15 scheduling Platform Suite for SAS and 57 security protections for configuration directories on Windows setup tasks 104 permissions 106 spawners reserving ports for 21 stopping SAS servers 158 system administration 110

T temporary directory changing 76

104

Index

third-party products installing 53 installing from third-party software Web site 57 installing products from Platform Suite for SAS 57 installing with SAS Software Depot 56 pre-installation checklists 58 recording information about 58 uninstalling 159 user accounts for 9 third-party software Web site 57 troubleshooting 113 SAS server tier 115 SAS Web applications 117

U uninstalling the SAS Intelligence Platform 157 Java Development Kit 160 SAS JRE 160 SAS software 158 stopping servers 158 third-party software 159 UNIX sas group 15 user accounts 5 defining 6 directory service accounts 10 external 7 for third-party software 9 internal 6 local accounts 10

network accounts 10 password policies 11 pre-installation checklist for 11, 12, 13 SAS system accounts 5 setting up required accounts 5

V validating SAS servers 92

W Web application server automatic configuration 55 installing from third-party software Web site 57 Web applications automatic deployment 56 troubleshooting 117 WebLogic Server recording information about 58 WebSphere Application Server recording information about 58 Windows SAS Server Users group 14

Z z/OS creating a configuration directory SASGRP group 15

17

173

Your Turn We welcome your feedback. 3 If you have comments about this book, please send them to [email protected] Include the full title and page numbers (if applicable). 3 If you have comments about the software, please send them to [email protected]

SAS Publishing Delivers! ®

Whether you are new to the work force or an experienced professional, you need to distinguish yourself in this rapidly changing and competitive job market. SAS Publishing provides you with a wide range of resources to help you set yourself apart. Visit us online at support.sas.com/bookstore. ®

SAS Press ®

Need to learn the basics? Struggling with a programming problem? You’ll find the expert answers that you need in example-rich books from SAS Press. Written by experienced SAS professionals from around the world, SAS Press books deliver real-world insights on a broad range of topics for all skill levels.

SAS Documentation

support.sas.com/saspress

®

To successfully implement applications using SAS software, companies in every industry and on every continent all turn to the one source for accurate, timely, and reliable information: SAS documentation. We currently produce the following types of reference documentation to improve your work experience: • Online help that is built into the software. • Tutorials that are integrated into the product. • Reference documentation delivered in HTML and PDF – free on the Web. • Hard-copy books.

support.sas.com/publishing

SAS Publishing News ®

Subscribe to SAS Publishing News to receive up-to-date information about all new SAS titles, author podcasts, and new Web site features via e-mail. Complete instructions on how to subscribe, as well as access to past issues, are available at our Web site.

support.sas.com/spn

SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration. Other brand and product names are trademarks of their respective companies. © 2009 SAS Institute Inc. All rights reserved. 518177_1US.0109

Loading...

SAS 9.2 Intelligence Platform: Installation and Configuration Guide

® SAS 9.2 Intelligence Platform Installation and Configuration Guide The correct bibliographic citation for this manual is as follows: SAS Institut...

4MB Sizes 3 Downloads 5 Views

Recommend Documents

Installation and Configuration Guide - MicroStrategy
Resources. The MicroStrategy Installation and Configuration Guide provides comprehensive information ...... Agent will u

SAS 9.1.3 Intelligence Platform: System Administration - SAS Support
terms established by the vendor at the time you acquire this publication. U.S. Government Restricted Rights .... Chapter

SAS 9.2 Intelligence Platform: Web Application - SAS Support
SAS® 9.2 Intelligence Platform: Web Application Administration Guide, Fourth Edition. Cary, NC: SAS Institute ... For a

Business Intelligence Platform Installation Guide for Windows - SAP.com
Mar 25, 2014 - Web Intelligence Rich Client. .... This guide does not describe how to set up a supported host operating

Business Intelligence Platform Installation Guide for Windows - SAP.com
Jul 20, 2015 - Web Intelligence Rich Client. .... This guide does not describe how to set up a supported host operating

HPE USLAM Installation and Configuration Guide V4.0
HPE products and services are set forth in the express warranty statements accompanying such products and services. Noth

WS_FTP Server Installation and Configuration Guide - Ipswitch
Step 6: Configuring IIS for Log Viewing . ..... Microsoft IIS. When used with our WS_FTP Professional client, WS_FTP Ser

ArcSight ESM Installation and Configuration Guide - Community
Jan 29, 2015 - Software Version: 6.8c. Installation and Configuration Guide. January 29 .... Select Authentication Optio

JADE Installation and Configuration Guide - Jade Software
Jan 5, 2007 - Connecting to JADE Applications from Internet Information Server (IIS). 46. Connecting to JADE Application

Unlock an Internal Account :: SAS(R) 9.3 Intelligence Platform
This topic explains how to unlock the account immediately, so that you don't have to wait until the account lockout peri