Configuration Guide For SAS 9.4 Foundation For Microsoft Windows For x64

Configuration Guide for SAS 9.
4 Foundation for Microsoft Windows for x64
Copyright Notice
The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2013. Configuration Guide for SAS 9.4 Foundation for Microsoft Windows for x64, Cary, NC: SAS Institute Inc. Configuration Guide for SAS 9.4 Foundation for Microsoft Windows for x64 Copyright 2013, SAS Institute Inc., Cary, NC, USA 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. The scanning, uploading, and distribution of this book via the Internet or any other means without the permission of the publisher is illegal and punishable by law. Please purchase only authorized electronic editions and do not participate in or encourage electronic piracy of copyrighted materials. Your support of others rights is appreciated. 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. June 2013 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/bookstore 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.
Configuration Guide for SAS 9.4 Foundation for Microsoft Windows for x64
Table of Contents Post-Installation Setup for SAS 9.4 Foundation ................................................... iv

About this Guide .............................................................................................iv Running SAS 9.4 from a Command Console in any Folder ...............................iv
Chapter 1: Post-Installation Setup for the Metabase Facility ............................... 1

Setting Up the System Repository Manager Files............................................ 1 Registering the SASHELP Repository in the Repository Manager .................... 1 Converting Version 6 SAS/EIS Metabases to Version 8 Repositories .............. 2
Chapter 2: Post-Installation Instructions for National Language Support (NLS) ......................................................................................................................... 3

Introduction ................................................................................................... 3 Selecting LOCALE During SASFoundation deployment .................................... 4 Chinese, Japanese, and Korean DBCS Support................................................ 4
Asian Font Catalogs ...................................................................................................... 4 Installing Traditional Chinese Fonts ................................................................................ 4 Specifying the Font Catalog in the Configuration File for Traditional Chinese Fonts ..................................4 Specifying the Font Catalog in a SAS Session for Traditional Chinese Fonts ............................................5 Chinese Localizations .................................................................................................................................5
Chapter 3: Restricted Options ................................................................................ 6

Global Restrictions ......................................................................................... 6 User Restrictions ............................................................................................ 6 Additional information .................................................................................... 6
Chapter 4: Configuring Hadoop JAR Files ............................................................ 8

Make Required Hadoop JAR Files Available on Your SAS Machines ................. 8 Set the SAS_HADOOP_JAR_PATH Environment Variable ................................ 8 Additional Requirements for MapR-based Hadoop Systems ............................ 9 Supporting Multiple Hadoop Versions and Upgrading Hadoop Version ........... 9
Chapter 5: Configuring SAS Analytics Accelerator for Teradata ...................... 10

Database Permission for Registering the UDFs ............................................. 10 UDF Installation Step Requires LATIN1 ........................................................ 10 Database Requirements and Configuration .................................................. 10 Registering the UDFs .................................................................................... 10 Alternative to PROC TSSQL ........................................................................... 11 Re-enable the Default HTML ODS Destination............................................... 12 Documentation for Using the UDFs ............................................................... 12
i 24 December 2013
Chapter 6: SAS/ACCESS Interfaces ..................................................................... 13

Configuring SAS/ACCESS Interface to Aster nCluster ................................... 13
Installing and Configuring the ODBC Driver and Bulk Loader ............................................ 13
Configuring SAS/ACCESS Interface to Cloudera Impala Software ................ 13 Configuring SAS/ACCESS Interface to Greenplum ........................................ 13
Bulkload .................................................................................................................... 14
Configuring SAS/ACCESS Interface to Hadoop ............................................. 15

Prerequisite: Required Hadoop UTF-8 Format ................................................................ Read Access Security for Hive ...................................................................................... Read Access Security for HiveServer2 ........................................................................... HDFS /tmp and Write Access ....................................................................................... Assumed HDFS Service and Hive Service Configuration ................................................... Writing Data to Hive: HDFS /tmp and the Sticky Bit ..................................................... Kerberos Security....................................................................................................... Requirement for HiveServer2 ....................................................................................... Running the Hive or HiveServer2 Service on Your Hadoop Server ..................................... Successful SAS/ACCESS Connections ............................................................................ Unsuccessful SAS/ACCESS Connections ........................................................................ Starting with Hive ...................................................................................................... Proliferation of Hive Logs Files in /tmp .......................................................................... 15 15 15 15 15 15 16 16 16 16 17 17 18
Configuring SAS/ACCESS Interface to MySQL .............................................. 18 Configuring SAS/ACCESS Interface to ODBC Software ................................. 19 Configuring SAS/ACCESS Interface to Oracle ............................................... 20 Configuring SAS/ACCESS Interface to PC Files ............................................. 21 Configuring SAS/ACCESS Interface to PostgreSQL ....................................... 21 Configuring SAS/ACCESS Interface to R/3 ................................................... 22 Configuring SAS/ACCESS Interface to SAP HANA ......................................... 22
Create a Data Source.................................................................................................. 22 Bulkload .................................................................................................................... 23
Configuring SAS/ACCESS Interface to Sybase .............................................. 23 Configuring SAS/ACCESS Interface to Sybase IQ ......................................... 23 Configuring SAS/ACCESS to Teradata ........................................................... 23
Teradata Parallel Transporter ....................................................................................... 24 TPT or Legacy Teradata Utility (FastExport and Multiload) ............................................... 25 Legacy Teradata Utility Configuration ............................................................................ 25 FastExporting ............................................................................................................................................25 MultiLoad ..................................................................................................................................................25
Configuring SAS/ACCESS Interface to Vertica .............................................. 26 Configuring and Administering SAS In-Database Products ........................... 26
Chapter 7: Post-Installation Setup for SAS/ASSIST Software ........................... 27

Adding a Master Profile ................................................................................ 27
Chapter 8: SAS/CONNECT Configuration ............................................................ 29

Storing and Locating SAS/CONNECT Script Files .......................................... 29 TCP/IP ......................................................................................................... 29 Configuring the SAS Windows Spawner Program ......................................... 29
ii
Chapter 9: Post-Installation Configuration for SAS/IntrNet Software ............... 31

Overview ...................................................................................................... 31 Installing and Configuring SAS/IntrNet Software ........................................ 32
Install Your Web Server Software ................................................................................. 32 Install Your SAS Software ........................................................................................... 32 CGI Tools Installation Dialogs ...................................................................................................................32 Installing CGI Tools and SAS Foundation on Machines with Different Operating Systems ......................34 Test the Web Server ................................................................................................... 35 Internet Information Services (IIS) 6.0+ Post-Install Configuration for Broker ...........................................35 Test the Application Broker .......................................................................................... 35 Configure a Default Application Dispatcher Service ......................................................... 36 Starting and Stopping the Default Service ..................................................................... 37 Testing the Socket Service .......................................................................................... 37 Configure Additional Services....................................................................................... 38
Chapter 10: Installing SAS/SECURE Software Client Components .................. 39

SAS/SECURE for Windows Clients ................................................................ 39 SAS/SECURE for Java Clients ....................................................................... 39 FIPS-Compliant Encryption ........................................................................... 39
Chapter 11: Post-Installation Setup for SAS/SHARE Software .......................... 40

Using the TCP/IP Communications Access Method ....................................... 40 System Configuration for the TCP/IP Access Method ................................... 40 Client-Side Components ............................................................................... 41
SAS/SHARE Data Provider ........................................................................................... SAS ODBC Driver ....................................................................................................... SAS/SHARE Driver for JDBC ........................................................................................ SAS/SHARE SQL Library for C ...................................................................................... 41 41 41 41
NLS Information ........................................................................................... 41
Chapter 12: Windows Performance Monitor and Event Log Support ............... 42
iii
Post-Installation Setup for SAS 9.4 Foundation

About this Guide
This document provides configuration instructions for SAS 9.4 Foundation, which is made up of server-side Base SAS and a variety of server-side SAS products (the exact products vary by customer). The server-side configuration instructions contained in this document are for the configuration of a generic SAS server. For information about configuring OLAP, workspace and stored process servers, please see SAS 9.4 Intelligence Platform: Installation and Configuration Guide: Introduction to Installing the SAS Intelligence Platform. This material can be found at http://support.sas.com/documentation/cdl/en/biig/63852/HTML/default/p01 intellplatform00installgd.htm
Running SAS 9.4 from a Command Console in any Folder

If you add {SASHOME}\SASFoundation\9.4 to your system PATH, SAS 9.4 can run from a command console in any folder when you type SAS. For information about setting the PATH Environment Variable, refer to Microsoft Windows Help.
iv
Chapter 1: Post-Installation Setup for the Metabase Facility

In Version 7 of the SAS System, the SAS/EIS Metabase facility was converted to the V7 Common Metadata Repository. The Common Metadata Repository is a general-purpose metadata management facility that provides common metadata services to various metadata-driven applications. Using the Common Metadata Repository requires a one-time setup of the system the repository manager. If the repository manager was set up in a previous release it may not need to be set up again. The steps in the following sections should be completed before you attempt to use the Metabase Facility. For Metabase Facility users who were using a release prior to Version 7, using the Common Metadata Repository requires a conversion. For more information, see the Version 8 OLAP Server Topic Converting Legacy Metabases.
Setting Up the System Repository Manager Files

Complete the following steps to set up the necessary system repository manager files. You must have write access to SASHELP in order to specify the system repository manager. Note: This process sets the default location for the repository manager for your site. Individual users may specify their own repository manager location by following the steps below and not selecting the Write values to system registry check box. Create a directory that will be dedicated exclusively to the storage of repository manager files, for example: !SASROOT\RPOSMGR. This directory should not be used to store other SAS files. 2. 3. At a SAS command line, type REPOSMGR and then select Setup Repository Manager. In the Repository Manager Setup window, Library will default to RPOSMGR. For Path, specify the path from Step 1, above, and then select the Write values to system registry check box. Then select OK. In the resulting dialog window, select Yes to generate the necessary repository manager files.
1.
4.
This completes the setup for the System Repository Manager. You can create additional repository managers (a user repository manager, for example) by repeating the steps above and by using a different path.
Registering the SASHELP Repository in the Repository Manager

The SASHELP repository is used in various samples, including the SAS/EIS Report Gallery templates. Before beginning the steps below, a repository manager must be created (see previous section). Complete the following steps to register the SASHELP repository in the Repository Manager: 1. 2. 3. At a SAS command line, type REPOSMGR and then select Repository Registration. In the Repository Registration window, select New. In the Register Repository (New) window, type SASHELP (in uppercase) in the Repository field, and then type the full directory path where the CORE catalog is located in the Path field, for example: !SASROOT\CORE\SASHELP
Page 1
4.
In the Description field, you can type any character string (for example, SASHELP Repository). Select OK to close the Register Repository (New) window. Select Close to exit the Repository Registration window. Repositories cannot span multiple directories because the path cannot contain concatenated directories. If you have existing metabases in concatenated directories, you should copy the metabases to a single path that will be referenced as a repository.
Note:
Converting Version 6 SAS/EIS Metabases to Version 8 Repositories

For step-by-step instructions on converting Version 6 metabases to Version 8 repositories, please refer to the topic Converting existing SAS/EIS metabases in the SAS/EIS online Help.
Chapter 2: Post-Installation Instructions for National Language Support (NLS)

This chapter contains information on post-installation configuration for Asian and European language support. Important: To run a localized SAS image, your operating system must be configured to use a Windows for x64 regional setting appropriate to the localized image. You may experience unexpected results if the regional setting and the localized image are not consistent. If multiple SAS localizations have been installed on the system, you may need to change the regional setting for each localized SAS image before invocation. For information on how to change or to use regional settings, refer to your Microsoft Windows for x64 documentation.
Introduction
The SAS Deployment Wizard allows users to decide which set of languages to install for the SAS products that are listed. However, three images are automatically deployed for SAS on all Windows and UNIX machines: English English with DBCS and Unicode Support
When SAS 9.4 Foundation is installed, the installer creates a configuration file called !SASROOT\sasv9.cfg. When you open the file, you will find that the only option specified is the CONFIG option, which points to another configuration file. That configuration file contains the options used to establish your SAS session, including the LOCALE system option that establishes the NLS environment for SAS. Beginning with 9.4, the ENCODING system option is set explicitly in the configuration file for singlebyte languages and Unicode support. It is not set for double-byte languages. Occasionally, other NLS options will also be included in the configuration file. At least three NLS configuration files are created during the installation process: one in !SASROOT\nls\en for the default single-byte (SBCS) image that uses English messages one in !SASROOT\nls\1d for the default double-byte (DBCS) image that uses English messages one in !SASROOT\nls\u8 for the SAS Unicode server
If you have chosen to install any of the localized SAS images, you will find a folder under !SASROOT\nls for each. The folders are named with a SAS specific 2-character language code. Each contains its own configuration file with a LOCALE option value set to match the localization. As mentioned above, the configuration file also contains the ENCODING for single-byte languages. For example, the configuration file for French (fr) will have a LOCALE value with a French language code.
Page 3
Selecting LOCALE During SASFoundation deployment

The SAS Deployment Wizard (SDW) includes a dialog that allows the installer to select the locale. The locale that initially displays in this dialog is the users locale on the Windows machine where SASFoundation is being installed. If you prefer to use a different locale for SASFoundation, you can select a locale from dialog. The selected locale is set as the value of the SAS LOCALE system option in the configuration file used to initialize SAS. If the selected locale matches a localization installed for the SASFoundation image, the sasv9.cfg file for that localization becomes the default configuration file for SAS. Otherwise, the default configuration file is the configuration file that uses English, which is one of these two files: !SASROOT\nls\1d\sasv9.cfg for any language that requires DBCS support !SASROOT\nls\en\sasv9.cfg for all other languages
For example, if the installer selects the Polish localization and the Polish locale, the LOCALE system option is set to pl_PL and the ENCODING option is set to wlatin2 in both the Polish configuration file and the English configuration file. The Polish configuration file is used to initialize SASFoundation, by default.
Chinese, Japanese, and Korean DBCS Support

This section explains how to specify Asian font catalogs and how to determine the localization used for Chinese.
Asian Font Catalogs

The default configuration files for Asian language editions already contain font definitions. (However, the configuration file for DBCS extensions does not contain font definitions.) Asian fonts reside in the SASHELP.FONTS catalog. Simplified and Traditional Chinese fonts have been added. Asian font catalogs reside in subdirectories (by language) for easy installation. If you want to change the font catalog, you can specify it in either the configuration file or in your SAS session.
Installing Traditional Chinese Fonts

To use Traditional Chinese fonts, you must install the Traditional Chinese localization. You will also need to modify your configuration file, as described in the following section.
Specifying the Font Catalog in the Configuration File for Traditional Chinese Fonts
If you are not running a Traditional Chinese localization but you want to use the Traditional Chinese fonts, you need to modify the configuration file to set GFONTx to -set gfontx !SASROOT/nls/zt/font-name In this statement, x represents a value from 0-9. font-name represents the name of the font catalog you want to use.
Specifying the Font Catalog in a SAS Session for Traditional Chinese Fonts
To specify the font catalog in a SAS session, submit the following libref statement: -libname gfontx !sasroot\nls\langcode\font-name In this statement, x represents a value from 0-9. font-name represents the name of the font catalog you want to use.
Chinese Localizations
The installer has the option to install localizations for both Simplified Chinese and Traditional Chinese. Several Chinese-based locales are supported by SAS. In some cases, the localization selected for the locale may not be intuitive. The following table shows which language SAS uses when you select one of the five Chinese locales. Note that the default language may be English.
Locale
Chinese (China) [zh_CN] Chinese (Hong Kong) [zh_HK] Chinese (Macau) [zh_MO] Chinese (Singapore) [zh_SG] Chinese (Taiwan) [zh_TW]
Location of sasv9.cfg file

!SASROOT\nls\zh !SASROOT\nls\zt !SASROOT\nls\1d !SASROOT\nls\\1d !SASROOT\nls\zt
Language
Simplified Chinese Traditional Chinese English English Traditional Chinese
Chapter 3: Restricted Options

SAS 9.4 Foundation options can be restricted by a site administrator so that once they are set by the administrator, they may not be changed by a user. An option can be restricted globally and by user. To restrict an option it must be added to the appropriate SAS 9.4 Foundation configuration file and this file must have the permissions set by the administrator so that it cannot be updated by users. The option files are processed by global and then by user. If an option is specified in multiple files then the last occurrence gets used.
Global Restrictions
Create the file !SASROOT\rstropts\rsasv9.cfg and add options to this file in the normal config file format.
User Restrictions
Create a file of the following format: !SASROOT\rstropts\users\<user ID>_rsasv9.cfg and add options to this file in the normal config file format. Example: For user smith, the file name is smith_rsasv9.cfg.
Additional information
To determine which options can be restricted, follow this example: Proc Options LISTRESTRICT; run; To verify that an option has been set correctly, follow this example: 1. 2. Assume the option -EMAILSYS=SMTP was specified in one of the restricted configuration files. Submit the following code: proc options restrict; run; The SAS log should then show a message similar to Option Value Information For SAS Option EMAILSYS Option Value: SMTP Option Scope: SAS Session How option value set: Site Administrator Restricted The following describes the process when a user attempts to change the option value. 1. 2. Assume the option -NOTHREADS was specified in one of the restricted configuration files. Submit the following code: options THREADS;
Page 6
The SAS log should then show a message similar to the following: options THREADS; ----36 WARNING 36-12: SAS option THREADS is restricted by your Site Administrator and cannot be updated.
Chapter 4: Configuring Hadoop JAR Files

Make Required Hadoop JAR Files Available on Your SAS Machines
The information in this section applies to the following SAS components that access Hadoop: Hadoop Procedure FILENAME Statement, Hadoop Access Method SAS/ACCESS to Hadoop SPD Engine
These SAS components require that Hadoop JAR files be accessible to the SAS machines in your organization which will access Hadoop. Create a directory that is accessible to all SAS users. In the directory place Hive, Hadoop HDFS, and Hadoop authorization JAR files. Additional JAR files will be needed due to JAR file interdependencies. Here are the required JAR files for Cloudera CDH4.0.1; the set is different for other Hadoop editions: guava hadoop-auth hadoop-common hadoop-core hadoop-hdfs hive-exec hive-jdbc hive-metastore hive-service libfb303 pig protobuf-java
You may need assistance from your Hadoop administrator to locate the appropriate JAR files. Except for libfb303, JAR files include version numbers. For example, the pig JAR file might be pig-0.8.0, pig-0.9.1, etc. A superset of the JAR files that SAS requires is fine, but do not include Thrift JAR files such as libthrift in the JAR directory.
Set the SAS_HADOOP_JAR_PATH Environment Variable

SAS must be able to find the JAR files. Create an operating environment variable named SAS_HADOOP_JAR_PATH as the directory path of the JAR files. For example, if the JAR files are copied to directory C:\third_party\Hadoop\jars, then the following DOS command sets the environment variable appropriately: setx SAS_Hadoop_JAR_PATH C:\third_party\Hadoop\jars Set SAS_HADOOP_JAR_PATH in a permanent manner for all SAS users who access Hadoop from this machine.
A SAS_HADOOP_JAR_PATH directory must not have multiple versions of a Hadoop JAR file; this can cause unpredictable behavior when SAS runs. Note: For SAS/ACCESS Interface to Hadoop to operate properly, your SAS_HADOOP_JAR_PATH directory must not contain any Thrift jars such as libthrift*.jar.
Additional Requirements for MapR-based Hadoop Systems

In addition to the Hive, Hadoop HDFS, and Hadoop authorization JAR files, you need the JAR files provided in the MapR client installation. For example,
set SAS_HADOOP_JAR_PATH=C:\third_party\Hadoop\jars;C:\mapr\hadoop\hadoop0.20.2\lib
where C:\third_party\Hadoop\jars is as described above, containing hive-*.jars, etc., and where C:\mapr\hadoop\hadoop-0.20.2\lib is the JAR directory laid down by the MapR client installation software. In addition, set the SAS java.library.path property to the directory that contains the 64-bit MapRClient sharable library. For example on Windows if the 64-bit MapRClient sharable library location is C:\mapr\lib, then add this line to the JREOPTIONS in the SAS configuration file: -Djava.library.path=C:\mapr\lib Note: The MapR 64-bit library must be selected. Use of the MapR 32-bit library will produce undesirable results.
Supporting Multiple Hadoop Versions and Upgrading Hadoop Version

The JAR files in the SAS_HADOOP_JAR_PATH directory must match the Hadoop server to which SAS connects. If you have multiple Hadoop servers running different Hadoop versions, then create and populate separate directories with version-specific Hadoop JAR files for each Hadoop version. SAS_HADOOP_JAR_PATH then must be dynamically set depending on which Hadoop server a SAS job or SAS session will connect to. One means to dynamically set SAS_HADOOP_JAR_PATH is to create a wrapper script associated with each Hadoop version. SAS is invoked via a wrapper script that sets SAS_HADOOP_JAR_PATH appropriately to pick up the JAR files that match the target Hadoop server. Upgrading your Hadoop server version may involve having multiple Hadoop versions active. The same multi-version instructions apply.
Chapter 5: Configuring SAS Analytics Accelerator for Teradata

This chapter describes registering user-defined function (UDFs) that are included with your SAS Analytics Accelerator software in your Teradata database. The chapter assumes that you have successfully installed SAS Foundation, including SAS/STAT. To leverage Enterprise Miner and ETS UDFs, you also need to install SAS Enterprise Miner and SAS/ETS, respectively.
Database Permission for Registering the UDFs

Since the SAS Analytics Accelerator UDFs are going to be registered in database SYSLIB, the Teradata database user account you use to install the UDFs as described below must have the following privileges for the SYSLIB database. CREATE FUNCTION ALTER FUNCTION EXECUTE FUNCTION GLOP GLOP MEMBER
To obtain the appropriate permissions, contact your database administrator.
UDF Installation Step Requires LATIN1

SAS in-Database analytics procedures can be run with all supported encodings. However, the UDF installation step requires LATIN1 for the session encoding. If the system has a different encoding, it can be temporarily set to LATIN1 by changing the configuration file as described in SAS 9.4 National Language Support (NLS): Reference Guide at this location: http://support.sas.com/documentation/cdl/en/nlsref/64811/HTML/default/view er.htm#titlepage.htm.
Database Requirements and Configuration

To successfully install the UDFs and execute them, the Teradata database must be version 13.00 or higher. Additionally the database must have DBCEXTENSION installed to support operations on GLOP sets. Please contact your database administrator to ensure DBCEXTENSION has been installed prior to the next steps.
Registering the UDFs

To register the SAS Analytics Accelerator UDFs in your Teradata database, you should invoke three installation macros called udftdstt.sas, udftdem.sas and udftdets.sas that have been installed under !SASROOT/dmine/sasmacro/as part of SAS Analytics Accelerator. Note: During UDF installation, SAS creates temporary files under the folder referenced by the work library. If the absolute path of this folder is very long, UDF installation may fail due to the limit on external file names in Teradata Warehouse. If you encounter this situation, start the SAS session with the work library temporarily assigned to a directory with shorted path, e.g., C:\ and proceed with the installation as described above. After installation is complete, the work library can be reassigned to
10
the original folder. For information about the options available when reassigning the work library, please refer to SAS documentation. To run the macros, submit the following commands in the Program Editor from SAS: ods html select none; ods listing; %let indconn = server=myserver user=myuserid password=XXXX database=SYSLIB; %udftdstt; %udftdem; %udftdets; proc tssql nolibs noerrorstop noprompt="(&credentials.)"; CREATE GLOP SET syslib.sas_vars; call DBCExtension.glop_add('syslib.sas_vars', 'SE', NULL, 'dmdb', 'N', 0, 'Y', 'M', 'E', 0, 256000, 1, '00'XB); CREATE GLOP SET syslib.sas_dmvars; call DBCExtension.glop_add('syslib.sas_dmvars', 'SE', NULL, 'dmine', 'N', 0, 'Y', 'M', 'E', 0, 256000, 1, '00'XB); quit; The first two statements in the program allow the registration macros to write and read temporary files without these files being redirected to the default HTML ODS destination of the SAS dms mode. The INDCONN macro variable provides credentials to connect to the Teradata machine. You must specify the server, user, password, and database to access the machine on which you have installed the Teradata data warehouse: myserver is the server on which the Teradata warehouse resides. myuserid is a valid user ID for that server that is granted the permissions described above. XXXX is the password for the user ID you are using. Because the SAS Analytics Accelerator UDFs must be registered in the SYSLIB database, database must be SYSLIB.
The statements executed by PROC TSSQL will create the GLOP sets and add the GLOPs used by SAS analytical procedures while executing the UDFs in Teradata database.
Alternative to PROC TSSQL

As an alternative to running PROC TSSQL, your database administrator may directly execute the following SQL commands on Teradata through the database client such as BTEQ. CREATE GLOP SET syslib.sas_vars; call DBCExtension.glop_add('syslib.sas_vars', 'SE', NULL, 'dmdb', 'N', 0, 'Y', 'M', 'E', 0, 256000, 1, '00'XB); CREATE GLOP SET syslib.sas_dmvars; call DBCExtension.glop_add('syslib.sas_dmvars', 'SE', NULL, 'dmine', 'N', 0, 'Y', 'M', 'E', 0, 256000, 1, '00'XB);
11
Re-enable the Default HTML ODS Destination

After the UDF registration macros have completed, you can re-enable the default HTML ODS destination by running the following command: ods html select all;
Documentation for Using the UDFs

For information about how to use your newly registered UDFs, please see the SAS Analytics Accelerator for Teradata: Guide at http://support.sas.com/documentation/onlinedoc/analyticsaccel/index.html.
12
Chapter 6: SAS/ACCESS Interfaces

Configuring SAS/ACCESS Interface to Aster nCluster
Installing and Configuring the ODBC Driver and Bulk Loader
Before you configure the ODBC driver, the bulk loader should be installed in <SASHOME>\SASFoundation\9.4\ or somewhere that is in the PATH environment variable. After they have been installed, you can configure the ODBC data source. SAS recommends (but does not require) that you create a data source, using the instructions below. If you have more than one user who may use the same workstation to access the Aster nCluster database, you may choose to create it as a system DSN rather than a user DSN. Complete the following steps to create a data source for Aster nCluster database access: 1. 2. 3. 4. 5. 6. 7. 8. 9. Run ODBC Administrator from the Control Panel or Start menu. Select the User DSN or System DSN tab, depending on the number of users, as stated above. Click Add and choose Aster Data ODBC Driver for nCluster from the popup window. Click Finish. Enter any name in the Data Source field. Enter the hostname or IP Address in the Server field. Enter the port number in the Port field. Enter the database name in the Database field. Enter the user name in the User Name field. Enter the password in the Password field.
10. Click Test. After a message appears that indicates that the test was successful, click OK. 11. Click Save.
Configuring SAS/ACCESS Interface to Cloudera Impala Software

Before you can use SAS/ACCESS Interface to Cloudera Impala software, the following products are required: Base SAS Software SAS/ACCESS Interface to Cloudera Impala Software the Cloudera Impala ODBC driver
Configuring SAS/ACCESS Interface to Greenplum

SAS/ACCESS Interface to Greenplum uses the DataDirect Technologies Greenplum Wire Protocol ODBC driver component. To install the Greenplum driver in an appropriate location, follow these steps:
Page 13
1.
Use Windows Explorer to navigate to the !SASROOT\access\sasmisc directory where the <platform>gplm60.zip is located and where <platform> is specific to your operating system. This zip file contains a directory, gpl6.0 which includes the driver and the installation instructions for installing it. Use an unzip utility to unzip the contents to C:\. This should result in a directory C:\gpl6.0. Navigate to C:\gpl6.0 and follow the instructions in the Readme.txt file.
2. 3.
After you install the software, configure a Data Source Name (DSN) to access a Greenplum database. You can use the ODBC administrator to add it. If you have more than one user who may use the same workstation to access the Greenplum database, you can create it as a system DSN instead of a user DSN. Complete the following steps to create a data source for Greenplum database access: 1. 2. 3. 4. 5. 6. 7. 8. 9. Run Data Sources (ODBC) from Administrator Tools of the Control Panel. Click the User DSN or System DSN tab, depending on the number of users, as stated above. Click the Add button and choose SAS ACCESS to Greenplum from the pop-up window. Enter any name in the Data Source Name field. This will be the name that you will use inside of SAS when referencing this database connection. Enter a Description for this connection. Enter the host name as the name of the server where Greenplum resides (this may be an IP address). Enter the Port Number that the host is listening on for Greenplum connections. The default is 5432. Enter the Database Name of the database on the Greenplum server. Click Test Connection and enter your userid and password. A test connection will be initiated.
10. Click OK to close the ODBC Administrator and to save your new DSN entry.
Bulkload
SAS/ACCESS can interface with the Greenplum Client Loader interface for loading large volumes of data. To perform bulkloading, the Greenplum Client Loader Package must be present on the system where you installed SAS. SAS recommends using the gpfdist protocol for bulkloading. For this protocol you must set the GPLOAD_HOME environment variable to point to the location where the gpfdist utility allocates the files to be loaded onto the Greenplum tables. Additional information about how to use the bulkloading feature can be found in the SAS/ACCESS 9.4 for Relational Databases: Reference documentation.
14
Configuring SAS/ACCESS Interface to Hadoop

Note: Before you configure SAS/ACCESS Interface to Hadoop, please follow the instructions in Configuring Hadoop JAR Files on page 8 to set up the directory that contains Hadoop JAR files and the SAS_HADOOP_JAR_PATH variable.
Prerequisite: Required Hadoop UTF-8 Format

SAS/ACCESS requires Hadoop data to be in Hadoop standard UTF-8 format. If SAS/ACCESS detects data that may not be in UTF-8 format, it issues the error Unable to transcode Hadoop data from UTF-8 and suggests adding -Dfile.encoding=UTF-8 to the SAS invocation. If your JREOPTIONS already contain -Dfile.encoding=UTF-8 and the transcode error is issued, your data is not in UTF-8 format. It must be converted to UTF-8 for use by SAS/ACCESS. Note: If your data contains only US-ASCII characters, it is already in UTF-8 format.
Read Access Security for Hive

SAS/ACCESS supports standard USER= and PASSWORD= security options. SAS/ACCESS propagates the supplied username and password to the JDBC connection string passed to Hive. However, the Hive Service ignores JDBC user IDs and passwords. Instead, permissions are those of the Linux user ID that started the Hive Service. The effect is that any SAS user can connect and have read access to data accessible to the Hive Service.
Read Access Security for HiveServer2

When configured appropriately, HiveServer2 honors the username and password to address the lack of read security in Hive.
HDFS /tmp and Write Access

SAS/ACCESS uses the Hadoop HDFS service to create a new Hive table or to append to an existing one. To write data, the USER= connection option should specify a valid Linux user ID on the Hadoop server with write permission HDFS /tmp. SAS/ACCESS does not restrict a SAS user from specifying a USER= connection value that does not match that user s SAS machine login ID.
Assumed HDFS Service and Hive Service Configuration

SAS/ACCESS assumes the HDFS Streaming Service and the Hive Service are co-located, and use ports 8020 and 10000 respectively. If the services run on different Hadoop nodes, then the SAS/ACCESS option CONFIG= must be pointed to a copy of the Hadoop core-site.xml. If the services are co-located but not running on ports 8020 and 10000, the BL_PORT= and PORT= options are provided.
Writing Data to Hive: HDFS /tmp and the Sticky Bit

SAS/ACCESS assumes HDFS /tmp exists, and writes data there. After data is written, SAS/ACCESS issues a LOAD command to move the data to the Hive warehouse. The USER= connection option should specify a valid user ID on the Hadoop server with write permission to HDFS /tmp. If the sticky bit is set on HDFS /tmp, the LOAD command may fail. One option to resolve this LOAD
15
failure is to disable the sticky bit on HDFS /tmp. If the sticky bit cannot be disabled, SAS data can be written to an alternate location specified by the HDFS_TEMPDIR= option. In this example of a Hadoop file system command, the sticky bit is set for HDFS /tmp. It is denoted by the t attribute. $ hadoop fs -ls / hdfs supergroup 0 2013-01-21 13:25 /tmp 0 2013-01-21 11:46 /user drwxrwxrwt - hdfs drwxr-xr-x - hdfs
Kerberos Security
Most SAS/ACCESS platforms can be configured for Kerberos ticket cache based login authentication using MIT Kerberos 5 with Cloudera CDH4.1.2 and higher running HiveServer2. However, SAS/ACCESS on the AIX platform requires Cloudera CDH4.2 and higher running HiveServer2. For SAS/ACCESS on both AIX and HP-UX, add this line to the JREOPTIONS in the SAS configuration file: -Djavax.security.auth.useSubjectCredsOnly=false
Requirement for HiveServer2

SAS/ACCESS assumes a Hive connection. To successfully connect to HiveServer2, use the connection option SUBPROTOCOL=HIVE2. Otherwise SAS/ACCESS may hang as it attempts to make the connection.
Running the Hive or HiveServer2 Service on Your Hadoop Server

SAS/ACCESS reads Hadoop data via a JDBC connection to a Hive or HiveServer2 Service. A good practice is to launch the service as a daemon that kicks off on system restarts. This assures consistent service. This example starts a Hive service at an operating system prompt: $ export HIVE_PORT=10000 $ HIVE_HOME/bin/hive --service hiveserver
Successful SAS/ACCESS Connections

SAS code connects to Hive or HiveServer 2 either with a libref or a PROC SQL CONNECT TO. The libref outputs information upon a successful connection whereas PROC SQL is silent on a successful connection. In these examples, Hive is listening on default port 10000 on Hadoop node hadoop01. Sample libref connection: libname hdplib hadoop server=hadoop01 user=hadoop_usr password=hadoop_usr_pwd; NOTE: Libref HDPLIB was successfully assigned as follows: Engine: HADOOP Physical Name: jdbc:hive://hadoop01:10000/default
16
Sample PROC SQL connection: proc sql; connect to hadoop (server=hadoop01 user=hadoop_usr password=hadoop_usr_pwd); Sample libref connection to HiveServer2: libname hdplib hadoop server=hadoop_h2 user=hadoop_usr password=hadoop_usr_pwd subprotocol=hive2; NOTE: Libref HDPLIB was successfully assigned as follows: Engine: HADOOP Physical Name: jdbc:hive2://hadoop_h2:10000/default
Unsuccessful SAS/ACCESS Connections

SAS failure to connect can have different causes. Error messages will assist in diagnosing the issue. In this sample failure, Hive is not active on port 10000 on Hadoop node hadoop01. libname hdplib hadoop server=hadoop01 port=10000 user=hadoop_usr password=hadoop_usr_pwd; ERROR: java.sql.SQLException: Could not establish connecton to hadoop01:10000/default: java.net.ConnectException: Connection refused: connect ERROR: Unable to connect to server or to call the Java Drivermanager. ERROR: Error trying to establish connection. ERROR: Error in the LIBNAME statement. In this sample failure, the hive-metastore JAR file is missing from SAS_HADOOP_JAR_PATH. libname hdplib hadoop server=hadoop01 port=10000 user=hadoop_usr password=hadoop_usr_pwd; ERROR: java.lang.NoClassDefFoundError: org/apache/hadoop/hive/metastore/api/MetaException ERROR: Unable to connect to server or to call the Java Drivermanager. ERROR: Error trying to establish connection. ERROR: Error in the LIBNAME statement. In this sample failure, the LIBNAME hangs because HiveServer2, not Hive, is running. Assuming that SAS notes are enabled, a hang has occurred if this note does not appear: Libref HDPLIB was successfully assigned as follows: For HiveServer2 the connection option subprotocol=hive2 must be added: libname hdplib hadoop server=hadoop01 port=10000 user=hadoop_usr password=hadoop_usr_pwd;
Starting with Hive

If you do not currently run Hive on your Hadoop server, then your Hadoop data likely resides in HDFS files initially invisible to Hive. To make HDFS files (or other formats) visible to Hive, a Hive CREATE TABLE is issued. The following simple scenario demonstrates how to access HDFS files
17
from Hive using the Hive CLI. For more information, perform a web search for Hive CLI and locate the appropriate Apache documentation. 1. Assume there are HDFS files weblog1.txt and weblog2.txt with data lines containing in order, a date field, a text integer field, and a string field. The fields are comma-delimited and lines \n terminated. $ hadoop fs -ls /user/hadoop/web_data Found 2 items -rw-r--r-- 3 hadoop [owner] [size/date] /user/hadoop/web_data/weblog1.txt -rw-r--r-- 3 hadoop [owner] [size/date] /user/hadoop/web_data/weblog2.txt Begin by terminating the Hive service if it is running. Next, at a Linux prompt, bring up the Hive CLI: $ hive 2. At the Hive command prompt, make the weblogs visible to Hive: hive> CREATE EXTERNAL TABLE weblogs (extract_date STRING, extract_type INT, webdata STRING) ROW FORMAT DELIMITED FIELDS TERMINATED BY ',' STORED AS TEXTFILE LOCATION '/user/hadoop/web_data'; 3. At the Hive command prompt, test that weblog1.txt is now accessible to Hive: hive> SELECT * FROM weblogs LIMIT 1; 4. If the SELECT works, quit the Hive CLI and start the Hive Service on default port 10000. For example, if you start the Hive service on node hadoop_cluster, a test access from SAS would be as follows: libname hdplib hadoop server=hadoop_cluster user=hadoop_usr password=hadoop_usr_pwd; data work.weblogs; set hdplib.weblogs(obs=1); put _all_; run; This is a complete but intentionally simple scenario intended for new Hive users. It is likely not representative of a mature Hive environment since the default Hive schema is used implicitly and the Hive default Derby metadata store may be in use. Consult Hadoop and Hive documentation to begin to explore Hive in detail. SAS/ACCESS user documentation provides more information on how SAS/ACCESS interacts with Hive.
Proliferation of Hive Logs Files in /tmp

Data access through Hive can create log files in Hadoop HDFS /tmp. Over time many log files can accumulate. You may want to disable the logging or periodically run a process to delete logs.
Configuring SAS/ACCESS Interface to MySQL

During the initial installation of SAS/ACCESS Interface to MySQL, the SAS Deployment Wizard provides a dialog in which you can specify the version of MySQL that you are using. If you want to
18
update that information, use the SAS Deployment Manager. The procedure for updating the version is described in the Configure SAS/ACCESS Interface to MySQL section of SAS Deployment Wizard and SAS Deployment Manager 9.4: Users Guide, located at http://support.sas.com/documentation/installcenter/en/ikdeploywizug/66034/PDF/ default/user.pdf Before you can use SAS/ACCESS Interface to MySQL software, the following products are required: Base SAS software SAS/ACCESS Interface to MySQL software
Before you use SAS/ACCESS interface to MySQL software, verify that the MySQL client library (libmysql.dll) has been appended to Path, a system variable. The MySQL client library is often located in C:\mysql\bin or C:\program files\mysql\mysql server 5.1\bin. To locate the Path system variable, follow the instructions for your operating system. For Windows NT, right-click My Computer and choose Properties. Select the Environment tab and you will see Path in your list of system variables. For Windows 2000, right-click My Computer and choose Properties. Select the Advanced tab and select the Environment Variables button. You will see Path in your list of System Variables. For Windows XP, click Start then select Control Panel. Double-click System. Select the Advanced tab and select the Environment Variables button. You will see Path in your list of System Variables.
For more information about SAS/ACCESS Interface to MySQL, refer to the MySQL chapter in SAS/ACCESS 9.4 for Relational Databases: Reference.
Configuring SAS/ACCESS Interface to ODBC Software

Before you can use SAS/ACCESS Interface to ODBC software, the following products are required: Base SAS Software SAS/ACCESS Interface to ODBC Software A 32-bit ODBC driver for the source from which you want to access data
The ODBC solution allows different technologies to be used by defining a standard interface. SAS/ACCESS Interface to ODBC software with ODBC drivers provides you with access to different databases. An ODBC driver processes ODBC function calls from--and returns results to-SAS/ACCESS software. You can get drivers from Microsoft, your database vendor, or other third party software vendors. To run SAS/ACCESS software on 32-bit Windows, you need 32-bit drivers. The application calls the 32-bit Driver Manager (ODBC32.DLL), which in turn calls the 32-bit drivers. The following figure illustrates the architecture:
19
SAS/ACCESS
32-Bit Drive r M ana ger (ODBC32.DLL)
32-Bit Drive r
32-Bit Drive r
32-Bit Drive r
Data Source
Data Source
Data Source
The ODBC Driver Manager and Administrator are Microsoft products that are included with all ODBC drivers. When you install an ODBC driver, the ODBC Driver Manager and Administrator are also installed. The ODBC Administrator should appear as an icon in the control panel. However, it can appear as an icon in the Start menu instead. After you install the ODBC driver, you can use the ODBC Administrator to define and manage the data sources. A data source associates a particular ODBC driver with the data you want to access through that driver. It can consist of information about the data you want to access and its associated operating system, DBMS, and network platform (if any) used to access the DBMS. For information about how to configure your data sources, refer to the documentation provided with your ODBC drivers. For more information about SAS/ACCESS to ODBC, refer to the ODBC chapter in SAS/ACCESS 9.4 for Relational Databases: Reference. For more information about ODBC, refer to Microsoft ODBC 3.0 Programmers Reference and SDK Guide.
Configuring SAS/ACCESS Interface to Oracle

During the initial installation of SAS/ACCESS Interface to Oracle, the SAS Deployment Wizard provides a dialog in which you can specify the version of Oracle that you are using. If you want to update that information, use the SAS Deployment Manager. The procedure for updating the version is described in the Configure SAS/ACCESS Interface to Oracle sec tion of SAS Deployment Wizard and SAS Deployment Manager 9.4: Users Guide, located at http://support.sas.com/documentation/installcenter/en/ikdeploywizug/66034/PDF/ default/user.pdf Before SAS/ACCESS Interface to Oracle software can be used, the following products are required: Base SAS software SAS/ACCESS Interface to Oracle software Oracle client/server
After the Oracle client/server installation process is complete, ensure that the path to the Oracle client libraries is appended to the PATH system variable. The Oracle libraries are usually located in the directory ORACLE_HOME/bin.
20
If the PATH variable does not have ORACLE_HOME/bin, you will see the following error: ERROR: The SAS/ACCESS Interface to ORACLE cannot be loaded. ERROR: Image SASORA found but not loadable. For more information about SAS/ACCESS Interface to Oracle, refer to the Oracle chapter in SAS/ACCESS 9.4 for Relational Databases: Reference.
Configuring SAS/ACCESS Interface to PC Files

Use of ACCESS or EXCEL LIBNAME engine requires the installation of a 64-bit Microsoft ACE driver. If the message ERROR: Connect: Class not registered appears while you are using the LIBNAME ACCESS or EXCEL LIBNAME engine, you have the incompatible 32-bit Microsoft Access database engine(ACE) installed. If you have to use the 32-bit ACE driver with 64-bit SAS installed, a 32-bit SAS PC Files Server must be used to bridge the bitness gap between the ACE driver and PCFILES LIBNAME engine. You may run SAS PC Files Server as a Windows service or as an application server listening to the PCFILES LIBNAME engine. SAS PC Files Server provides data encryption and Authentication features with default port number 9621, which can be configured through the PC Files Server application console. Note that the bitness (32-bit or 64-bit) of the SAS PC Files server must match that of the Microsoft ACE driver on the same Windows machine. When you install SAS PC Files Server, check the Start Service Now and Automatically when Windows Starts dialog box to run SAS PC Files Server as a Windows Service in the background. This is the default and actually starts the service and sets the service start-up type to automatic. To run SAS PC Files Server as a desktop application, ensure that this option is cleared. Note: Only one instance of SAS PC Files Server can run at a given time. You cannot run SAS PC Files Server as a Windows Service and an Application Server at the same time.
Both server mode and service mode store the server configuration settings in the Windows registry. If the settings are changed in server mode, the server running service mode will be affected after it is restarted. The default configuration should be sufficient for most installations. To change the configuration options, run the SAS PC Files Server in server mode. 1. 2. 3. 4. 5. Go to Windows Services (Start > Run and enter services.msc), locate and Stop the SAS PC Files Server Service. Start the PC Files Server in Server mode by clicking Start > SAS > PC Files Server. Change the options that you want to change on the PC Files Server application console. Click the Shutdown button to stop the PC Files Server in Server mode. Go to Windows Services again, locate and start the SAS PC Files Server Service.
Configuring SAS/ACCESS Interface to PostgreSQL

Install the ODBC driver psqlodbc and the PostgreSQL Database, version 9.0.1 or later. To verify that the installation was performed correctly, view the Drivers TAB in the ODBC Data Source Administrator dialog in the control panel. The PostgreSQL driver is listed in the Driver TAB.
21
If the DSN (data source) is created in ODBC Data Source Administrator, the DSN is used as in the following example: libname db postgres dsn=<dsn name> user=xxx password=xxxxxx; If no DSN is created, connect to the database directly as in the following example: libname db postgres server="xxx " database=xxxx; port=5433 user=xxx password=xxxx
Configuring SAS/ACCESS Interface to R/3

SAS/ACCESS Interface to R/3 software requires extensive post-installation configuration before it can be used. For detailed information, refer to the Configuration Instructions for SAS/ACCESS 9.4 Interface to R/3 on Install Center: http://support.sas.com/documentation/installcenter/en/ikr3cg/66652/PDF/ default/config.pdf
Configuring SAS/ACCESS Interface to SAP HANA

SAS/ACCESS Interface to SAP HANA uses an ODBC interface to access SAP HANA. SAS/ACCESS Interface to SAP HANA requires the 64-bit ODBC driver for SAP HANA. The ODBC driver is part of the SAP HANA CLIENT 1.00. These are the prerequisites for configuration of SAS/ACCESS Interface to SAP HANA: You have downloaded the SAP HANA client software from SAP Service Marketplace and installed and configured the ODBC driver. For more information about how to obtain the software, please see the SAP HANA Master Guide on http://help.sap.com/hana_appliance/. For information how to install and configure the ODBC driver, please see the SAP HANA Client Installation Guide on http://help.sap.com/hana_appliance/.
Create a Data Source

After the ODBC client has been installed, you can configure the ODBC data source. SAS recommends (but does not require) that you create a data source, using the instructions below. If you have more than one user who may use the same workstation to access the SAP HANA database, you may choose to create it as a system DSN rather than a user DSN. Complete the following steps to create a data source for SAP HANA database access: 1. 2. 3. 4. 5. 6. Run ODBC Administrator from the Control Panel or Start menu. Select the User DSN or System DSN tab, depending on the number of users, as stated above. Click Add and choose HDBODBC from the pop-up window. Click Finish. Enter any name in the Data Source field. Enter the hostname or IP Address and the port number in the Server:Port field. Click Settings... for additional advanced parameters. Enter additional parameters. Click OK.
22
7. 8. 9.
Click Connect. Enter the user name in the User field. Enter the password in the Password field.
10. Click OK. After a message appears that indicates that the test was successful, click OK. 11. Click OK.
Bulkload
The bulkload for SAS/ACCESS Interface to SAP HANA uses SFTP to transfer files to the SAP HANA server. If you want to use bulkload, you need to configure SFTP for accessing the SAP HANA server from the SAS server.
Configuring SAS/ACCESS Interface to Sybase

During the initial installation of SAS/ACCESS Interface to Sybase, the SAS Deployment Wizard provides a dialog in which you can specify the version of Sybase that you are using. If you want to update that information, use the SAS Deployment Manager. The procedure for updating the version is described in the Configure SAS/ACCESS Interface to Sybase section of SAS Deployment Wizard and SAS Deployment Manager 9.4: Users Guide, located at http://support.sas.com/documentation/installcenter/en/ikdeploywizug/66034/PDF/ default/user.pdf In SAS 9.4, the administrator or user must install two Sybase-stored procedures on the target server. Two files have been included in the !SASROOT\access\sasmisc directory to assist in the installation: sas-spcp.txt is a text file containing instructions on how to do the installation. sas-spdf.txt is the first of two actual stored procedure scripts for ASE 12.x server. sas-spdf_15.txt is the first of two actual stored procedure scripts for ASE 15.x server. sassp2df.txt is the second of two stored procedure scripts for ASE 12.x server. sassp2df_15.txt is the second of two stored procedure script for ASE 15.x server.
The process utilizes two Sybase facilities, defncopy and isql. To complete your installation, add -set sassyb sywx6150 to your sasv9.cfg file.
Configuring SAS/ACCESS Interface to Sybase IQ

SAS/ACCESS Interface to Sybase IQ requires the installation of Sybase IQ client software, which is available from Sybase. On Windows for x64, there are no additional steps required to set up the environment and libraries.
Configuring SAS/ACCESS to Teradata

Before you use SAS/ACCESS Interface to Teradata software, verify connectivity by logging into your Teradata account with the Teradata BTEQ utility. If BTEQ is unavailable, establish connectivity as
23
documented in the SAS/ACCESS to Teradata white paper, available at http://support.sas.com/resources/papers/teradata.pdf. If BTEQ fails to connect to the Teradata server, you may need an entry in the hosts file on your PC to provide the network address of the Teradata server. Typically, this means adding a dbccop1 entry to your hosts file. For more details about the entry, see your Teradata Client for Windows Installation Guide.
Teradata Parallel Transporter

SAS/ACCESS supports the Teradata Parallel Transporter API for loading data using Multiload (TPT UPDATE operator), Fastload (TPT LOAD operator) and multi-statement inserts (TPT STREAM operator). The API also supports reading data using FastExport (TPT EXPORT operator). Note: TPT API is now the default and recommended Method that is used for all Teradata Utility processing in SAS Access to Teradata.
The following two requirements must be met: 1. The TPT API must be installed on the system where SAS Access is installed. The Teradata installation process installs both 32-bit and 64-bit libraries on x64 platforms, and the 64-bit libraries need to be referenced first in the PATH. Sometimes the TTU 13.10 installation process puts the 32-bit libraries first in the PATH, so you may need to check this, and manually adjust it. From our experience, TTU 14 does not have this issue. The 64-bit libraries must be listed before the 32-bit in your PATH! A normal Teradata installation of TPT will create the environment variable TWB_ROOT. Example: TWB_ROOT = C:\Program Files\Teradata\Client\13.10\Teradata Parallel Transporter. You can then reference this TWB_HOME env variable at the beginning of your PATH env variable, as: %TWB_ROOT\bin64\ %TWB_ROOT\msg64\ This sets the 64 bit libraries and message files first in your PATH env variable. 2. The system variable TKPATHX8664 must be modified. If the variable does not exist already, it must be added. To modify the variable, append the directory where sasiotpt.dll is located. Usually sasiotpt.dll is located in your SAS product tree. Example: C:\Program Files\SASHome\SASFoundation\9.4\access\sasexe (or the directory path where sasiotpt.dll resides) To locate and edit the TKPATHX8664 system variable, follow the instructions for your Windows operating system. To find out if TPT is installed correctly, perform a quick test within SAS. Issue a Teradata libref, and then invoke fastload with a single row: /* quick test to see if TPT is installed correctly */ /* TPT = YES b default */
24
Libname x teradata server=mydbc user=dtest pw=xxxxx ; Data x.new (fastload=yes) ; x=99; run; NOTE: The data set X.new has 1 observations and 1 variables NOTE: Teradata connection: TPT Fastload has inserted 1 row(s). NOTE: Data statement used(Total process time): real time cpu time 4.39 0.29
TPT or Legacy Teradata Utility (FastExport and Multiload)

The following are the advantages of using TPT instead of Legacy Teradata Utility: High performance, multi-session interface for bulk load, bulk update, and bulk export data transfer TPT API allows SAS to perform In-Stream Processing via API Calls; no control files or intermediate data movement Use of 64-bit libraries on 64-bit operating systems Enhanced Performance now, improving in the future Configuration is less complex; no loading and launching of separate Teradata utility processes, no inter-process communication links required. TPT is integrated with Teradata Active System Management and Teradata Multi Systems Manager suite of support products
Legacy Teradata Utility Configuration

FastExporting
For optimal reads of large tables, SAS/ACCESS can perform FastExporting. To perform FastExporting, the Teradata FastExport Utility must be present on the system where you install SAS. You must also modify Path, a system variable. Append two directory paths to the end of Path: 1. 2. The directory where fexp.exe (the FastExport Utility) is located. Often this is C:\Program Files\Teradata\Client\13.0\bin. The directory where sasaxsm.dll is located (sasaxsm.dll is usually located in your SAS product tree, in the !sasroot\access\sasexe directory.)
The FastExport Utility is not required; SAS/ACCESS reads large tables quite efficiently without it. For further information, see the DBSLICEPARM option in your SAS/ACCESS to Teradata documentation. Please contact Teradata if you want to obtain the Teradata FastExport Utility. For more information about SAS/ACCESS Interface to Teradata software, please see the Teradata chapter in SAS/ACCESS 9.4 for Relational Databases: Reference, and the SAS/ACCESS to Teradata white paper, which can be found at http://support.sm/resources/papers/teradata.pdf.
MultiLoad
SAS/ACCESS can load large volumes of data to non-empty tables using MultiLoad. To perform MultiLoading, the Teradata MultiLoad Utility must be present on the system where you install SAS. You must also modify Path, a system variable.
25
Append two directory paths to the end of Path: 1. 2. The directory where mload.exe (the MultiLoad Utility) is located. Often this is C:\Program Files\Teradata\Client\13.0\bin. The directory where sasmlam.dll and sasmlne.dll are located (sasmlam.dll and sasmlne.dll are usually located in your SAS product tree, in the !sasroot\access\sasexe directory.)
The MultiLoad Utility is not required; SAS/ACCESS provides other options for loading tables. For further information, see the MULTISTMT option in your SAS/ACCESS to Teradata documentation. Please contact Teradata if you want to obtain the Teradata MultiLoad Utility.
Configuring SAS/ACCESS Interface to Vertica

Install an ODBC driver version 6.1 or later that is associated with Vertica Analytic Database. To verify that the installation was performed correctly, view the Drivers TAB in the ODBC Data Source Administrator dialog in the control panel. You will see Vertica driver listed in the Driver TAB. SAS Code Examples 1. If DSN (data source) is created in ODBC Data Source Administrator, we can use that DSN as in this example: libname db vertica dsn=<dsn name> user=xxx password=xxxxxx; 2. If no DSN is created, we can connect to the database directly, as in this example: libname db vertica server="xxx " password=xxxx database=xxxx; port=5433 user=xxx
Configuring and Administering SAS In-Database Products

Deployment of SAS In-Database products, including the SAS Embedded Process, requires detailed configuration and administration steps that are addressed after the initial installation. Follow the steps in your Software Order E-mail and QuickStart Guide to perform the initial deployment. Then refer to the Administrator's Guide chapter of the SAS In-Database Products: Administrators Guide for your particular database. This chapter contains instructions on how to install and configure the in-database deployment packages for your specific database. These packages are needed for the following actions: using the SAS Scoring Accelerator using the In-Database Code Accelerator reading and writing data to a Hadoop Distributed File System in parallel for HighPerformance Analytics publishing formats using the SAS_PUT function any other software that requires the SAS Embedded Process
When you have completed the instructions described there, your software will be ready for use. The SAS In-Database Products: Administrator's Guide is located at http://support.sas.com/documentation/onlinedoc/indbtech/index.html.
26
Chapter 7: Post-Installation Setup for SAS/ASSIST Software

This chapter describes how to add an optional master profile to SAS/ASSIST software. You can use a master profile to override the default settings as sent by SAS. This allows you to provide a customized setup for SAS/ASSIST software. With the master profile, you can control the profile options of all SAS/ASSIST users from one central place. For information on the profile options, refer to SAS/ASSIST Administrators Guide.
Adding a Master Profile

Complete the following steps to add a master profile to SAS/ASSIST software: 1. Specify the location of the master profile by creating a new directory that all users of SAS/ASSIST software will have read access to. All users with write access to this directory will automatically also have write access to the master profile in SAS/ASSIST software. Select a name that conforms to the naming conventions at your installation. The name of this new directory must be stored in an entry in the SASHELP library. This requires that you have write access to the SASHELP library. On line 1 of the Editor window of the SAS Display Manager System, type the physical pathname of the master profile directory. Execute the Save command to store this in the SASHELP.QASSIST catalog. For example: SAVE SASHELP.QASSIST.PARMS.SOURCE 00001 S:\SAS\ASSIST\PARMS 00002 00003 The location of the master profile is now known by SAS/ASSIST software. 2. Create the master profile. The first time SAS/ASSIST software is started, a master profile is created if SASHELP.QASSIST.PARMS.SOURCE contains the name of an existing physical pathname, and the person who starts SAS/ASSIST software has write access to this physical pathname. 3. Customize the master profile by starting SAS/ASSIST software and selecting Setup > Profiles > Master/group... If you have write access to the SAS library containing the master profile, you can specify default values for your installation. New users will use these values as they start SAS/ASSIST software. Note: If you restrict values by typing R in Status, users will not be allowed to change the values you define.
You can run SAS/ASSIST software in two different styles - workplace or block menu. The block menu can be new style or old style. You can control this using the profile options below. Run workplace: SAS/Assist style: Run block menu new style: SAS/Assist style: Block Menu Workplace
27
Save selections on end: Menu Style: Run old style: SAS/Assist style: Save selections on end: Menu Style:
Yes New Block Menu Yes Old
By setting the default values in the master profile, you can control if users should use the new or old style of SAS/ASSIST software. In addition, there are many other profile options. For more information on these options, refer to SAS/ASSIST Administrators Guide. 4. Create group profiles. From the master profile, it is possible to create group profiles to allow groups of users to have different setups. The master profile controls group profiles and user profiles when a user is not a member of any group. All users are indirectly controlled by the master profile when option values are set to a restricted (R) status. From Setup > Master/Group..., select Tools > Create Group Profile. To add users to a group profile, select Tools > Update User Group. By default, the user ID is found in the macro variable &SYSJOBID. This value is set in the option user ID in the master profile (option type System Administration). Change the value if your site uses another variable to keep the user ID. If the value name starts with &, it is a macro variable; otherwise, it is an environment variable, which is set before the start of SAS 9.4.
28
Chapter 8: SAS/CONNECT Configuration

TCP/IP is the access method supported for SAS 9.4 on Windows for x64. For information about the access methods supported by other systems, refer to Communications Access Methods for SAS/CONNECT 9.4 and SAS/SHARE 9.4. This document can be found at http://support.sas.com/documentation/onlinedoc/connect/index.html Note: The APPC access method is no longer supported for the Windows operating system.
Storing and Locating SAS/CONNECT Script Files

Several sample script files are shipped with SAS/CONNECT software. SAS/CONNECT software uses these script files to establish a connection to a remote SAS session. The SASSCRIPT configuration option points to the location of the SAS/CONNECT script files. The SASSCRIPT option is used by SAS/ASSIST software and can be used by user-written SCL applications. Under Windows, the script files are installed into the !SASROOT\CONNECT\SASLINK directory by default. The following line is added to the SASV9.CFG file when SAS/CONNECT software is installed: -SASSCRIPT !SASROOT\CONNECT\SASLINK If you want to move the script files to another directory, you must edit the SASV9.CFG file and update the SASSCRIPT option with the new directory location. This option can also be specified from the Tools/Options/System/Communications/Networking and encryption selection in DMSEXP mode.
TCP/IP
TCP/IP is the access method supported for SAS 9.4 on Windows for x64. SAS/CONNECT software supports Microsofts TCP/IP System Driver, which is provided with Windows.
Configuring the SAS Windows Spawner Program

The SAS Windows Spawner is stored in the !SASROOT directory and can be executed manually from the !SASROOT directory at any time. You can run the SAS Windows Spawner as a service by executing cntspawn with the -install option. By default, the SAS Windows Spawner will be installed to run with security. For complete documentation on the Windows Spawner and the supported options, see Communications Access Methods for SAS/CONNECT 9.4 and SAS/SHARE 9.4. Note: If you are upgrading to SAS 9.4 and you run a spawner from a previous release as a service, you should stop and delete the existing spawner service. The SAS 9.4 CONNECT spawner can then be installed as a Windows service.
By default, when the SAS Windows Spawner is installed as a Windows service, it runs under the LocalSystem user ID that has all required User Rights for running the SAS Windows Spawner. If you do not install the SAS Windows Spawner as a Windows service (run it from your system prompt), the Windows user ID that is used to start the SAS Windows Spawner must be the local Administrator of the machine and must have the following User Rights:
Page 29
act as part of the operating system bypass traverse checking (the default is everyone) increase quotas replace a process level token log on locally (the default is everyone)
The Windows user ID specified at sign on needs only the User Right log on as a batch job.
30
Chapter 9: Post-Installation Configuration for SAS/IntrNet Software

This chapter has information for your SAS/IntrNet installation. It will help you install, configure, and test your SAS/IntrNet components. The procedures for installing SAS software using the SAS Deployment Wizard are described in other documentation and are not available in this chapter. In addition, the installation of a web server is not described in SAS documentation because it is the administrators responsibility. When SAS/IntrNet software has been installed, configured and tested using the procedures described in this chapter, review the latest version of the SAS/IntrNet product documentation online at http://support.sas.com/documentation/onlinedoc/IntrNet/index.html. The What's New page at this web site lists any recent changes to the product or documentation.
Overview
All SAS/IntrNet installations are made up of two components: 1. 2. The SAS/IntrNet server (also referred to as the Application Server). This is where SAS Foundation is installed. CGI Tools (also referred to as the Broker). This is where the broker.cfg file and its supporting files are installed.
When you install SAS/IntrNet, choose between these two installation configurations: Type A - The SAS/IntrNet server and CGI Tools components are both installed on the same system machine. The web server must be installed before starting the SAS installation. Type B -The SAS/IntrNet server component is installed on one system machine and the CGI Tools component is installed on a different system machine. The web server must be installed on the CGI Tools system machine prior to installing CGI Tools.
Type A and Type B require different installation steps: Type A Installation Steps Confirm that the web server software (IIS, Apache etc.) is on the same system machine as your SAS/IntrNet software. Install your SAS products. Check CGI Tools for the web Server in the Select Products to Install menu. Type B Installation Steps Confirm that the web server software (IIS, Apache, etc.) is on the system machine where you will install CGI Tools. On your application server system machine, start your SAS installation. Uncheck CGI Tools for the web Server in the Select Products to Install menu. On your web server system machine, start your SAS installation. Uncheck all products except CGI Tools for the web Server in the Select Products to Install menu. You can optionally check the IntrNet
31
Type A Installation Steps
Type B Installation Steps Monitor or Connect Drivers. Test the Broker
Configure a Socket Service Start the Socket Service Test the Socket Service Refer to your web servers documentation for its installation procedures.
Installing and Configuring SAS/IntrNet Software

Install Your Web Server Software
Refer to your web servers documentation for its installation procedures.
Install Your SAS Software

Refer to your QuickStart Guide for a description of how to start your SAS software installation. If you are performing a Type A installation (as described in the Overview above), perform the following steps: 1. 2. Confirm that your web server software is installed before starting your SAS software installation. Check CGI Tools for the Web Server in the Select Products to Install dialog.
If you are performing a Type B installation (as described in the Overview above), do both of the following: 1. 2. Install the SAS software on the SAS System side, unchecking CGI Tools for the Web Server in the Select Products to Install dialog. Start the SAS software install on the web server and check CGI Tools for the Web Server in the Select Products to Install dialog. SAS/IntrNet Monitor and SAS/CONNECT Driver for Java are optional selections. Uncheck everything else.
CGI Tools Installation Dialogs

The following windows appear for CGI Tools for the Web Server for all installations. For information about the fields, click Help on any dialog. Customary entries are documented following each screen shown below. Customize the entries according to your environment.
32
The following are examples of common entries for popular web servers. Customize your entries according to your own web server environment. These fields will tell SAS where your web server software is located. Physical path corresponding to http://<your_server>/sasweb: IIS: C:\Inetpub\wwwroot\sasweb
Apache (Windows): C:\program files\Apache Software Foundation\Apache2.2\ htdocs\sasweb Apache (UNIX): /usr/local/apache2/htdocs/sasweb
Physical path for SAS/IntrNet CGI Executables: IIS: C:\Inetpub\scripts
Apache (Windows): C:\program files\Apache Software Foundation\Apache2.2 \cgi-bin Apache (UNIX): /usr/local/apache2/cgi-bin
URL for CGI Executables: IIS: http://<web_servername>/scripts Example: http://abcserver.comp.com/scripts Apache (Windows): http:// <web_servername>/cgi-bin Example: http://abcserver.comp.com/cgi-bin Apache (UNIX): http://<web_servername>/cgi-bin Example: http://abcserver.comp.com/cgi-bin
33
Note that your entries for this dialog are added to the broker.cfg file. The broker.cfg file is a text file that can be edited after the installation is complete. Name of the Service Administrator: (optional) Enter the name of the administrator (for example, John Doe). Email Address of the Service Administrator: (optional) Enter the e-mail address of the administrator (for example, NetAdmin@comp.com). DNS Name or IP Address of Application Server Host: Enter the DNS name or IP address of the application server host where SAS Foundation is located. TCP Port Number for Application Server: The customary default port number is 5001, but you can use any valid available port on your system between 256 65535.
Installing CGI Tools and SAS Foundation on Machines with Different Operating Systems
Your SAS Foundation systems operating system might be different than your CGI Tools systems operating system. For example, your SAS Foundation might be installed on a Windows system and your CGI Tools might be installed on a UNIX system. The CGI Tools installation from the SAS Deployment Wizard will detect the destination operating system and install the appropriate operating system-specific software. There are two methods to make the SAS Software Depot available to the installer on the destination CGI Tools system. Choose the method that is appropriate for your sites available facilities:
34
Launch the set-up from a SAS Software Depot that resides on a remote system. You might need to use a cross-platform file access method such as NFS or SAMBA to connect the two systems. Create media from an existing depot using the SAS Deployment Wizard and use that media on the host machine. This process is described more thoroughly in the SAS Deployment Wizard and SAS Deployment Manager 9.4: Users Guide, available from Install Center, http://support.sas.com/documentation/installcenter/en/ikdeploywizug/66034 /PDF/default/user.pdf SAS/IntrNet operation requires TCP/IP connectivity between the SAS Foundation system and the CGI Tools system, regardless of the operating systems on which these components are installed.
Note:
Test the Web Server

To determine if the web server is running, launch the web servers browser and enter http://localhost. This will return a web page if the web server is running. If you do not receive a web page, you must debug or reinstall your web server before continuing.
Internet Information Services (IIS) 6.0+ Post-Install Configuration for Broker

In IIS 6.0 and later, you need to take manual steps in order for IIS to recognize the Broker as an application. For more information, please visit http://support.sas.com/kb/10/496.html.
Test the Application Broker

To verify that CGI Tools was installed correctly and can access the broker.cfg file, point your web browser to the following URL: Windows: IIS: http://<web_servername>/scripts/broker.exe
Apache: http://<web_servername>/cgi-bin/broker.exe Other hosts: http://your_webserver/cgi-bin/broker Replace your_webserver with the name of the web server. The URL path might also need to be changed if you installed CGI Tools to a different directory. You should see a web page similar to the following: SAS/IntrNet Application Dispatcher Application Broker Version 9.4 (Build 1502) Application Dispatcher Administration SAS/IntrNet Samples SAS/IntrNet Documentation - requires Internet access If you do not receive this page, you must debug your web server installation before continuing. Verify that your web server is enabled for CGI execution in the directory where you installed the Application Broker (broker.exe and broker.cfg files). This directory was determined by what was entered for Physical path for SAS/IntrNet CGI Executables during the CGI Tools installation above.
35
Configure a Default Application Dispatcher Service

You must create a default Application Dispatcher service to run any of the sample programs supplied with SAS/IntrNet. You should create the default service with the SAS Deployment Manager which is accessible from the Start menu. Perform the following steps to create and start the default service: 1. 2. 3. From the Start menu, select Programs SAS SAS Deployment Manager.
When the Choose Language window comes up, select the desired language and click OK. The SAS Deployment Manager (SDM) will display the Select SAS Deployment Manager Task window. Under SAS/IntrNet Service Tasks select Create Socket Service and click Next to continue. The Specify Service Name window displays. The default value for the Service Name field is default. Create this as your first service because this is what is used when you run the samples. Click Next to continue. The Specify Service Directory window displays. The SDM selects a default service root directory based on the location that you chose for user files when you installed SAS Software. This default location is recommended for most users, although you can use the Browse button to select a different directory. Click Next to continue. The Specify Service Ports window displays. Type the TCP/IP port number that you reserved for the default Application Dispatcher service. Click Next to continue. The Specify Administrator Password window displays. A password is not necessary for the default service. You can add an administrator password later if you use this service for production applications. Click Next to continue. The Summary window displays. It indicates Stage 1: Create Socket Service. If the information you have entered is correct, click Start. If you want to go back and change any of the values you entered, you can step backward through the windows by clicking the Back button.
4.
5.
6. 7.
8.
9.
The In Progress window displays while SDM creates the service.
10. The Deployment Complete screen displays when the task is finished. If the service is created correctly, a green checkmark appears next to the 1. SAS/IntrNet under Stage 1: Create Socket Service . If there was a problem, a yellow exclamation or red X appears and you should check the log for a description of the problem. The logs reside in <SASHOME>\SASFoundation\9.4\intrnet\sasmisc.
11. From the Start menu, select Programs SAS (or other program group where SAS is installed) IntrNet default Service Start Interactively. Your default Application Server should now be running.
36
Starting and Stopping the Default Service

As stated above, from the Start menu, select Programs SAS (or other program group where SAS is installed) IntrNet default Service Start Interactively. Your default Application Server should now be running.
Testing the Socket Service

1. To make sure that the service was installed and started correctly, point your web browser to this URL: Windows: IIS: http://<web_servername>/scripts/broker.exe
Apache: http://<web_servername>/cgi-bin/broker.exe Other hosts: http://your_webserver/cgi-bin/broker Replace your_webserver with the name of the web server. The URL path might also need to be changed if you installed the Application Broker to a different directory. You should see the following web page: SAS/IntrNet Application Dispatcher Application Broker Version 9.4 (Build 1502) Application Dispatcher Administration SAS/IntrNet Samples SAS/IntrNet Documentation - requires Internet access 2. 3. Click on the Application Dispatcher Administration link to see if the Application Broker can read the broker.cfg file. The Application Dispatcher Services web page should open. Verify connectivity between the Application Server and the web server. Click on the Application Dispatcher Administration link and then click on the ping link under SocketService default heading. If the ping is successful, you should see: Ping. The Application Server <hostname>:<port_number> is functioning properly. 4. To complete installation testing, type this URL in your browser address line: Windows: IIS: http://your_webserver/scripts/broker.exe?_service=default&_progra m=sample.webhello.sas Apache: http://your_webserver/cgibin/broker.exe?_service=default&_program=sample.webhello.sas Other hosts: http://your_webserver/cgi-bin/broker?_service=default&_program= sample.webhello.sas
37
You should see the string Hello World! in large bold type in your browser. If you do not, add the debug option to create a log: Windows: IIS: http://your_webserver/scripts/broker.exe?_service=default&_progra m=sample.webhello.sas&_debug=131 Apache:
http://your_webserver/cgibin/broker.exe?_service=default&_program=sample.webhello.sas&_debug=131
Other hosts:
http://yourwebserver/cgibin/broker?_service=default&_program=sample.webhello.sas&_debug=131
Save the log screen on the browser for SAS Technical Support.
Configure Additional Services

This chapter describes how to configure only a simple default Application Dispatcher service. There are many reasons you may want to configure additional services, including segregating applications by security or performance requirements and implementing more scalable servers. See the Using Services section of the SAS/IntrNet Application Dispatcher documentation at http://support.sas.com/documentation/onlinedoc/intrnet/index.html information on configuring additional services, using the Load Manager, and adding pool services.
38
Chapter 10: Installing SAS/SECURE Software Client Components

SAS/SECURE software includes client components that non-SAS System client applications can use to communicate with a SAS server in a secure environment. To use encryption between a non-SAS System client and a SAS server, you must install the SAS/SECURE client components on the client machine. When SAS/SECURE software is included in a customers order, these SAS/SECURE client components can be selected for installation via the SAS Deployment Wizard. Note: This installation is not necessary if the SAS System is your client. The SAS System installs the components that it needs as part of the SAS System installation process.
SAS/SECURE for Windows Clients

The SAS/SECURE components needed by Windows clients can be installed by running the SAS Deployment Wizard to access the SAS/SECURE Windows Client Components.
SAS/SECURE for Java Clients

The SAS/SECURE components for Java clients provide encryption support for Java applications. You can incorporate this support into applications that are written using the following components: SAS/SHARE driver for JDBC SAS/CONNECT driver for Java IOM Bridge for Java
If the SAS/SECURE Java Component was part of your software order, the SAS/SECURE components needed by Java clients will be installed automatically when you run the SAS Deployment Wizard.
FIPS-Compliant Encryption
FIPS stands for Federal Information Processing Systems, and its 140-2 standard defines the security requirements for cryptographic modules. The 140-2 standard is detailed in the following document: http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf. The ENCRYPTFIPS option is an option added to SAS/CONNECT spawners, IOM spawners, and Base SAS so that the communication encryption will be compliant with FIPS 140-2. The ENCRYPTFIPS option is required for FIPS-compliant encryption. If you use ENCRYPTFIPS, the NETENCRALG option must be set to AES or SSL. In Windows 7 and later versions of Windows, you need to enable the System cryptography: Use FIPS-compliant algorithms for encryption, hashing, and signing setting under your Local Security Policy or as part of Group Policy. This setting informs applications that they should use only those cryptographic algorithms that are FIPS 140-2 compliant and in compliance with FIP- approved modes of operation. For more information about FIPS and encryption in general, refer to Encryption in SAS 9.4, available from SAS Knowledge Base Product Documentation: http://support.sas.com/documentation/cdl/en/secref/64866/HTML/default/view er.htm#titlepage.htm
Page 39
Chapter 11: Post-Installation Setup for SAS/SHARE Software

This chapter discusses the use of the TCP/IP access methods with SAS/SHARE software. TCP/IP is the access method supported for SAS 9.4 on Windows. For information about the access methods supported by other systems, please refer to Communications Access Methods for SAS/CONNECT 9.4 and SAS/SHARE 9.4. at http://support.sas.com/documentation/onlinedoc/connect/index.html
Using the TCP/IP Communications Access Method

Communication between a SAS/SHARE server and user is handled by the TCP/IP communications access method, which is a part of SAS 9.4 that uses underlying communications software to exchange messages and data. The TCP/IP access method requires Microsofts TCP/IP Network Protocol communications software. Note: The APPC access method is no longer supported for the Windows operating system.
To use the TCP/IP access method, you must have the supporting software on each workstation on which a SAS/SHARE server or user will execute.
System Configuration for the TCP/IP Access Method

SAS/SHARE software supports Microsofts TCP/IP Network Protocol, which is provided with Windows for x64. To define server names in the TCP/IP SERVICES file, complete the following steps: 1. Locate the SERVICES file. This file is located under the \Windows directory path depending on the specific Windows operating system and upgrade method. For example, under a machine configured with a Windows 7 operating system, the directory path is named <drive letter>:\Windows\System32\drivers\etc 2. Specify the server names and port assignments. Each SAS/SHARE server that runs on a network must be defined as a service in the SERVICES file. Each entry in this file associates a service name with the port number and protocol used by that service. An entry for a SAS/SHARE server has the form: <server name> <port number>/<protocol> # <comments>
The server name must be 1-8 characters in length. The first character must be a letter or underscore. The remaining seven characters can include letters, digits, underscores, the dollar ($) sign, or the at (@) sign. The port number must be above 1024, as any port number equal to or less than 1024 is reserved. The protocol must always be TCP. An entry for a server with the name MKTSERV might look like this: mktserv 5000/tcp # SAS server for Marketing and Sales
The server name is specified with the SERVER= option in the PROC SERVER statement in the servers SAS session and in the PROC OPERATE and LIBNAME statements in user and server
Page 40
administrator programs. If the server name is not defined, you must s pecify __<port#>, two consecutive underscores followed by the port number (e.g., server=__5012). For more information about the options used with PROC SERVER and PROC OPERATE procedures, please refer to the SAS/SHARE 9.4 User's Guide.
Client-Side Components
SAS/SHARE software includes client components that are used outside of your SAS installation. These components are available from the SAS 9.4 Software Download site and are described below:
SAS/SHARE Data Provider

The SAS/SHARE data provider enables you to access, update, and manipulate SAS data using OLE DB- and ADO-compliant applications on Windows platforms.
SAS ODBC Driver

The SAS ODBC driver enables you to access, update, and manipulate SAS data from ODBCcompliant applications on Windows platforms.
SAS/SHARE Driver for JDBC

The SAS/SHARE driver for JDBC enables you to write applets, applications, and servlets that access and update SAS data. The Java Tools package that includes the SAS/SHARE driver for JDBC also includes the SAS/CONNECT driver for Java. If you are writing Java programs using these interfaces, you may also want to use the tunnel feature. This optional feature can be used with the Java applets you write to solve some common configuration problems.
SAS/SHARE SQL Library for C

The SAS SQL Library for C provides an application programming interface (API) that enables your applications to send SQL queries and statements through a SAS/SHARE server to data on remote hosts.
NLS Information
Sites that develop or support international applications that use SAS/SHARE software should refer to the chapter Post-Installation Instructions for National Language Support (NLS) on page 3.
41
Chapter 12: Windows Performance Monitor and Event Log Support

Support for Windows Performance Monitor allows advanced users and administrators to observe some internal characteristics of SAS 9.4 Foundation. This facilitates performance analysis and tuning of SAS 9.4. Also, support for the Event Log allows the tracking of critical errors in SAS 9.4 Foundation and SAS Setup. The user account installing SAS 9.4 Foundation must have administrator privileges to install these features, so non-administrators will not get these features by default. They can be added later by invoking setup.exe (found under the sas folder on the Setup Disk) with the following command lines: To install the Windows Performance Monitor and Event Log: setup perfmon To uninstall the Windows Performance Monitor and Event Log: setup uperfmon
Page 42
43
SAS is the leader in business analytics software and services, and the largest independent vendor in the business intelligence market. Through innovative solutions delivered within an integrated framework, SAS helps customers at more than 50,000 sites improve performance and deliver value by making better decisions faster. Since 1976, SAS has been giving customers around the world THE POWER TO KNOW .

Configuration Guide For SAS 9.4 Foundation For Microsoft Windows For x64

Uploaded by

Copyright:

Available Formats

Configuration Guide For SAS 9.4 Foundation For Microsoft Windows For x64

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configuration Guide For SAS 9.4 Foundation For Microsoft Windows For x64

Uploaded by

Copyright:

Available Formats

What are the main components of SAS/SHARE software?

What are the main components of SAS/SHARE software?

What are the client-side components of SAS/SHARE?

What are the client-side components of SAS/SHARE?

Configuration Guide for SAS 9.

4 Foundation for Microsoft Windows for x64

Table of Contents Post-Installation Setup for SAS 9.4 Foundation ................................................... iv

Chapter 1: Post-Installation Setup for the Metabase Facility ............................... 1

Chapter 2: Post-Installation Instructions for National Language Support (NLS) ......................................................................................................................... 3

Chapter 3: Restricted Options ................................................................................ 6

Chapter 4: Configuring Hadoop JAR Files ............................................................ 8

Chapter 5: Configuring SAS Analytics Accelerator for Teradata ...................... 10

Chapter 6: SAS/ACCESS Interfaces ..................................................................... 13

Configuring SAS/ACCESS Interface to Hadoop ............................................. 15

Chapter 7: Post-Installation Setup for SAS/ASSIST Software ........................... 27

Chapter 8: SAS/CONNECT Configuration ............................................................ 29

Chapter 9: Post-Installation Configuration for SAS/IntrNet Software ............... 31

Chapter 10: Installing SAS/SECURE Software Client Components .................. 39

Chapter 11: Post-Installation Setup for SAS/SHARE Software .......................... 40

NLS Information ........................................................................................... 41

Post-Installation Setup for SAS 9.4 Foundation

Running SAS 9.4 from a Command Console in any Folder

Chapter 1: Post-Installation Setup for the Metabase Facility

Setting Up the System Repository Manager Files

Registering the SASHELP Repository in the Repository Manager

Converting Version 6 SAS/EIS Metabases to Version 8 Repositories

Chapter 2: Post-Installation Instructions for National Language Support (NLS)

Selecting LOCALE During SASFoundation deployment

Chinese, Japanese, and Korean DBCS Support

Asian Font Catalogs

Installing Traditional Chinese Fonts

Location of sasv9.cfg file

Chapter 3: Restricted Options

Chapter 4: Configuring Hadoop JAR Files

Set the SAS_HADOOP_JAR_PATH Environment Variable

Additional Requirements for MapR-based Hadoop Systems

Supporting Multiple Hadoop Versions and Upgrading Hadoop Version

Chapter 5: Configuring SAS Analytics Accelerator for Teradata

Database Permission for Registering the UDFs

To obtain the appropriate permissions, contact your database administrator.

UDF Installation Step Requires LATIN1

Database Requirements and Configuration

Registering the UDFs

Alternative to PROC TSSQL

Re-enable the Default HTML ODS Destination

Documentation for Using the UDFs

Chapter 6: SAS/ACCESS Interfaces

Configuring SAS/ACCESS Interface to Cloudera Impala Software

Configuring SAS/ACCESS Interface to Greenplum

Configuring SAS/ACCESS Interface to Hadoop

Prerequisite: Required Hadoop UTF-8 Format

Read Access Security for Hive

Read Access Security for HiveServer2

HDFS /tmp and Write Access

Assumed HDFS Service and Hive Service Configuration

Writing Data to Hive: HDFS /tmp and the Sticky Bit

Requirement for HiveServer2

Running the Hive or HiveServer2 Service on Your Hadoop Server

Successful SAS/ACCESS Connections