Configuration Guide for SAS 9.

2 Foundation for Microsoft Windows

Copyright Notice
Thecorrectbibliographiccitationforthismanualisasfollows:SASInstituteInc.,Configuration GuideforSAS9.2FoundationforMicrosoftWindows,Cary,NC:SASInstituteInc.,2010. ConfigurationGuideforSAS9.2FoundationforMicrosoftWindows Copyright2010,SASInstituteInc.,Cary,NC,USA. SomesoftwareincludedinSASFoundationmaydisplayareleasenumberotherthan9.2. Allrightsreserved.PrintedintheUnitedStatesofAmerica.Nopartofthispublicationmaybe reproduced,storedinaretrievalsystem,ortransmitted,byanyformorbyanymeans,electronic, mechanical,photocopying,orotherwise,withoutthepriorwrittenpermissionofthepublisher, SASInstituteInc.Limitedpermissionisgrantedtostorethecopyrightedmaterialinyoursystem anddisplayitonterminals,printonlythenumberofcopiesrequiredforusebythosepersons responsibleforinstallingandsupportingtheSASprogrammingandlicensedprogramsforwhich thismaterialhasbeenprovided,andtomodifythematerialtomeetspecificinstallation requirements.TheSASInstitutecopyrightnoticemustappearonallprintedversionsofthis materialorextractsthereofandonthedisplaymediumwhenthematerialisdisplayed. Permissionisnotgrantedtoreproduceordistributethematerialexceptasstatedabove. U.S.GovernmentRestrictedRightsNotice.Use,duplication,ordisclosureofthesoftwarebythe governmentissubjecttorestrictionsassetforthinFAR52.22719CommercialComputer SoftwareRestrictedRights(June1987). SASInstituteInc.,SASCampusDrive,Cary,NorthCarolina27513. SASandallotherSASInstituteInc.productorservicenamesareregisteredtrademarksor trademarksofSASInstituteInc.intheUSAandothercountries.
indicatesUSAregistration.

Otherbrandandproductnamesaretrademarksoftheirrespectivecompanies.

Table of Contents About this Guide ...................................................................................................... 1 Chapter 1: Post-Installation Setup for the Metabase Facility............................... 2
Setting Up the System Repository Manager Files............................................ 2 Registering the SASHELP Repository in the Repository Manager.................... 2 Converting Version 6 SAS/EIS Metabases to Version 8 Repositories .............. 3

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

Chinese, Japanese, and Korean DBCS Support ............................................... 4
Changing the Default DBCSLANG and DBCSTYPE Option Settings ...................................... 4 Changing the Configuration Files for Unicode Server ........................................................ 4 Asian Font Catalogs .................................................................................................... 5 Installing Traditional Chinese Fonts ............................................................................... 5 Specifying the Font Catalog in the Configuration File for Traditional Chinese Fonts ..................................5 Specifying the Font Catalog in a SAS Session for Traditional Chinese Fonts ............................................5

European Language Support .......................................................................... 5

Configuring SAS 9.2 for Locale ..................................................................................... 5 Changing the Default LOCALE Option Setting............................................................................................6 Running SAS in a Different Locale..............................................................................................................6 Additional Information ................................................................................................ 6 Locale Setup on the Remote Server ...........................................................................................................6 Devmaps and Keymaps for SAS/GRAPH Software....................................................................................7

Chapter 3: Post-Installation Setup for the SAS 9.2 Foundation........................... 9

PATH Environment Variable in Windows XP ................................................... 9
Other Windows Operating Systems ............................................................................... 9

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

SAS/STAT UDFs ............................................................................................ 10
Database Permission for Registering the UDFs .............................................................. 10 Registering the UDFs ................................................................................................ 10

SAS Enterprise Miner UDFs ........................................................................... 10

Database Permission for Registering the UDFs .............................................................. 10 Registering the UDFs ................................................................................................ 11

Documentation for Using the UDFs............................................................... 11

Chapter 5: SAS/ACCESS Interfaces ..................................................................... 12

Configuring SAS/ACCESS Interface to Aster nCluster Software.................... 12
Registering SAS/ACCESS Interface to Aster nCluster ..................................................... 12 Installing and Configuring the ODBC Driver and Bulk Loader ........................................... 12

Configuring SAS/ACCESS Interface to Greenplum Software ......................... 12

Bulkload ................................................................................................................. 13 Registering SAS/ACCESS Interface to Greenplum.......................................................... 13

Configuring SAS/ACCESS Interface to MySQL Software ............................... 14 Configuring SAS/ACCESS Interface to ODBC Software ................................. 14
SAS/ACCESS ODBC Conversion Utilities ....................................................................... 15 AS/400 Users............................................................................................................................................15 Microsoft SQL Server Users .....................................................................................................................16

Configuring SAS/ACCESS Interface to Oracle Software ................................ 17 Configuring SAS/ACCESS Interface to R/3 Software .................................... 17 Configuring SAS/ACCESS Interface to SYBASE Software.............................. 18
Page i 28 September 2010

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

Configuring SAS/ACCESS Interface to Teradata Software ............................ 18

FastExporting .......................................................................................................... 18 MultiLoad ................................................................................................................ 19 Teradata Parallel Transporter ..................................................................................... 19

Chapter 6: Post-Installation Setup for SAS/ASSIST Software ........................... 21

Adding a Master Profile ................................................................................ 21

Chapter 7: Post-Installation Setup for SAS/CONNECT Software....................... 23

Storing and Locating SAS/CONNECT Script Files .......................................... 23 TCP/IP ......................................................................................................... 23 Configuring the SAS Windows Spawner Program ......................................... 23

Chapter 8: Post-Installation Configuration for SAS/IntrNet Software ............... 25

Overview ...................................................................................................... 25 Installing and Configuring SAS/IntrNet Software ........................................ 26
Install Your Web Server Software ............................................................................... 26 Install Your SAS Software.......................................................................................... 26 CGI Tools Installation Dialogs...................................................................................................................26 Installing CGI Tools and SAS Foundation on Machines with Different Operating Systems ......................28 Test the Web Server ................................................................................................. 29 Internet Information Services (IIS) 6.0+ Post-Install Configuration for Broker...........................................29 Test the Application Broker ........................................................................................ 29 Configure a Default Application Dispatcher Service ........................................................ 30 Starting and Stopping the Default Service.................................................................... 30 Testing the Socket Service......................................................................................... 30 Configure Additional Services ..................................................................................... 32

Chapter 9: Installing SAS/SECURE Software Client Components .................... 33

SAS/SECURE for Windows Clients ................................................................ 33 SAS/SECURE for Java Clients ....................................................................... 33

Chapter 10: Post-Installation Setup for SAS/SHARE Software.......................... 34

Using the TCP/IP Communications Access Method....................................... 34 System Configuration for the TCP/IP Access Method ................................... 34 Client-Side Components ............................................................................... 35
SAS/SHARE Data Provider ......................................................................................... SAS ODBC Driver ..................................................................................................... SAS/SHARE Driver for JDBC....................................................................................... SAS/SHARE SQL Library for C .................................................................................... 35 35 35 35

NLS Information ........................................................................................... 35

Chapter 11: Windows Performance Monitor and Event Log Support ............... 37

ii

About this Guide

ThisdocumentprovidesconfigurationinstructionsforSAS9.2Foundation,whichismadeupof serversideBaseSASandavarietyofserversideSASproducts(theexactproductsvaryby customer). Theserversideconfigurationinstructionscontainedinthisdocumentarefortheconfigurationofa genericSASserver.ForinformationaboutconfiguringOLAP,workspaceandstoredprocessservers, pleaseseeSAS9.2IntelligencePlatform:InstallationandConfigurationGuide:IntroductiontoInstallingthe SASIntelligencePlatform.Thismaterialcanbefoundat http://sww.sas.com/dept/pub/doc/902s/gpp/prods/biig/win/biig.hlp/index.htm.

Page 1

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

Chapter 1: Post-Installation Setup for the Metabase Facility

InVersion7oftheSASSystem,theSAS/EISMetabasefacilitywasconvertedtotheV7Common MetadataRepository.TheCommonMetadataRepositoryisageneralpurposemetadatamanagement facilitythatprovidescommonmetadataservicestovariousmetadatadrivenapplications. UsingtheCommonMetadataRepositoryrequiresaonetimesetupofthesystemtherepository manager.Iftherepositorymanagerwassetupinapreviousreleaseitmaynotneedtobesetup again.Thestepsinthefollowingsectionsshouldbecompletedbeforeyouattempttousethe MetabaseFacility.ForMetabaseFacilityuserswhowereusingareleasepriortoVersion7,usingthe CommonMetadataRepositoryrequiresaconversion.Formoreinformation,seetheVersion8OLAP ServerTopicConvertingLegacyMetabases.

Setting Up the System Repository Manager Files

Completethefollowingstepstosetupthenecessarysystemrepositorymanagerfiles.Youmusthave writeaccesstoSASHELPinordertospecifythesystemrepositorymanager. Note: Thisprocesssetsthedefaultlocationfortherepositorymanagerforyoursite.Individualusersmay specifytheirownrepositorymanagerlocationbyfollowingthestepsbelowandnotselectingtheWrite valuestosystemregistrycheckbox. 1. Createadirectorythatwillbededicatedexclusivelytothestorageofrepositorymanagerfiles,for example:!SASROOT\RPOSMGR. ThisdirectoryshouldnotbeusedtostoreotherSASfiles. 2. 3. AtaSAScommandline,typeREPOSMGRandthenselectSetupRepositoryManager. IntheRepositoryManagerSetupwindow,LibrarywilldefaulttoRPOSMGR.ForPath,specifythe pathfromStep1,above,andthenselecttheWritevaluestosystemregistrycheckbox.Then selectOK. Intheresultingdialogwindow,selectYestogeneratethenecessaryrepositorymanagerfiles.

4.

ThiscompletesthesetupfortheSystemRepositoryManager.Youcancreateadditionalrepository managers(auserrepositorymanager,forexample)byrepeatingthestepsaboveandbyusinga differentpath.

Registering the SASHELP Repository in the Repository Manager

TheSASHELPrepositoryisusedinvarioussamples,includingtheSAS/EISReportGallerytemplates. Beforebeginningthestepsbelow,arepositorymanagermustbecreated(seeprevioussection). CompletethefollowingstepstoregistertheSASHELPrepositoryintheRepositoryManager: 1. 2. 3. AtaSAScommandline,typeREPOSMGRandthenselectRepositoryRegistration. IntheRepositoryRegistrationwindow,selectNew. IntheRegisterRepository(New)window,typeSASHELP(inuppercase)intheRepositoryfield, andthentypethefulldirectorypathwheretheCOREcatalogislocatedinthePathfield,for example: !SASROOT\CORE\SASHELP

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

4.

IntheDescriptionfield,youcantypeanycharacterstring(forexample,SASHELPRepository). SelectOKtoclosetheRegisterRepository(New)window.SelectClosetoexittheRepository Registrationwindow.

Note: Repositoriescannotspanmultipledirectoriesbecausethepathcannotcontainconcatenated directories.Ifyouhaveexistingmetabasesinconcatenateddirectories,youshouldcopythe metabasestoasinglepaththatwillbereferencedasarepository.

Converting Version 6 SAS/EIS Metabases to Version 8 Repositories

ForstepbystepinstructionsonconvertingVersion6metabasestoVersion8repositories,pleaserefer tothetopicConvertingexistingSAS/EISmetabasesintheSAS/EISonlineHelp.

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

ThischaptercontainsinformationonpostinstallationconfigurationforAsianandEuropean languagesupport. Important: TorunalocalizedSASimage,youroperatingsystemmustbeconfiguredtouseaWindows regionalsettingappropriatetothelocalizedimage.Youmayexperienceunexpectedresultsif theregionalsettingandthelocalizedimagearenotconsistent. IfmultipleSASlocalizationshavebeeninstalledonthesystem,youmayneedtochangethe regionalsettingforeachlocalizedSASimagebeforeinvocation.Forinformationonhowto changeortouseregionalsettings,refertoyourMicrosoftWindowsdocumentation.

Chinese, Japanese, and Korean DBCS Support

ThissectionexplainshowtochangethedefaultsettingsfortheDBCSLANGandDBCSTYPEsystem optionsandhowtospecifyAsianfontcatalogs. Note: TheDBCSLANGandDBCSTYPEsystemoptions(describedinthenextsection)shouldbeusedtoset localeforAsiancharactersetsonly.TheLOCALEandENCODINGsystemoptions,describedinthe SASHelpSystem,areusedtosetlocaleforEuropeanlanguages.

Changing the Default DBCSLANG and DBCSTYPE Option Settings

WhenyouinstallSAS9.2FoundationandchoosetoloadNLSlanguagetranslations,theinstallation automaticallysetsdefaultvaluesfortheDBCSLANGandDBCSTYPEsystemoptionsbasedonthe languageselectionandplatform.Forexample,ifyouinstallPrimaryJapaneseonWindows2000,the configurationfile(!sasroot\nls\ja\sasv9.cfg)setsDBCSLANGtoJAPANESEandDBCSTYPEto PCMS.

Changing the Configuration Files for Unicode Server

Therearetwoconfigurationfiles.Thefirst,c:\program files\sas\sas 9.2\sasv9.cfg, pointstothesecond,c:\program files\sas\sas 9.2\nls\1d\sasv9.cfg.TorunSASasa UnicodeServer,edittheconfigurationfilesforyoursystemwiththefollowingchanges: 1. DBCSsettingsareinthesecondconfigurationfileabove.CommentouttheDBCSLANGand theDBCSTYPEoptionsinthatfile.Forexample: /* -DBCSTYPE PCMS */ /* -DBCSLANG JAPANESE */ 2. AddtheENCODINGoptionandsetthevaluetoUTF-8 (ENCODING=UTF-8): -ENCODING=UTF-8 3. AddtheFONTandSYSGUIFONToptionsandsetthevaluestoaTrueTypefonte.g., ThorndaleDuospace.

Page 4

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

Asian Font Catalogs

ThedefaultconfigurationfilesforAsianlanguageeditionsalreadycontainfontdefinitions. (However,theconfigurationfileforDBCSextensionsdoesnotcontainfontdefinitions.)Asianfonts resideintheSASHELP.FONTScatalog.InSAS9.2, Simplified and Traditional Chinese fonts have been added. Asianfontcatalogsresideinsubdirectories(bylanguage)foreasyinstallation.Ifyouwanttochange thefontcatalog,youcanspecifyitineithertheconfigurationfileorinyourSASsession.

Installing Traditional Chinese Fonts

TouseTraditionalChinesefonts,youmustinstalltheTraditionalChineselocalization.Youwillalso needtomodifyyourconfigurationfile,asdescribedinthefollowingsection.

Specifying the Font Catalog in the Configuration File for Traditional Chinese Fonts
IfyouarenotrunningaTraditionalChineselocalizationbutyouwanttousetheTraditionalChinese fonts,youneedtomodifytheconfigurationfiletosetGFONTxto -set gfontx !SASROOT/nls/zt/font-name Inthisstatement, xrepresentsavaluefrom09. font-namerepresentsthenameofthefontcatalogyouwanttouse.

Specifying the Font Catalog in a SAS Session for Traditional Chinese Fonts
TospecifythefontcataloginaSASsession,submitthefollowingLIBNAMEstatement: -libname gfontx !sasroot\nls\langcode\font-name Inthisstatement, xrepresentsavaluefrom09. font-namerepresentsthenameofthefontcatalogyouwanttouse.

European Language Support

Note: ThephraseEuropeanLanguageSupportreferstoanylanguagethatisnotChinese,Japanese,or Korean. Thefollowingsectionsexplaindifferentmethodsforconfiguringyoursystemforlocale,describe howtosetupyourlocalsessiontotransferdatatoaremotesession,andprovidealistofdevmapand keymapvaluesthatmatchthelocalesonyouroperatingsystem.

Configuring SAS 9.2 for Locale

IfyouwanttoconfigureyourSASsessionforalocaleotherthanthedefaultlocale,youhavetwo methodsfromwhichtochoosetoachievethatgoal.Thissectionexplainsthosemethods.

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

Changing the Default LOCALE Option Setting

WhenyouinstallSAS9.2FoundationandyouchoosetoloadNLSlanguagetranslations,the installationautomaticallysetstheLOCALEsystemoptiontothedefaultvalueforthelanguage installed.TheLOCALEoptionissetinthesystemconfigurationfileforeachlanguageinstalled. Forexample, !SASROOT\nls\fr\sasv9.cfgsetsLOCALEtoFrench_Francebydefault. IfyouwanttochangethedefaultlocalesettingforSAS,youcansettheLOCALEsystemoptiontothe appropriatelanguageinyoursystemconfigurationfile. Forexample,youcanedit!SASROOT\nls\fr\sasv9.cfgandchange-locale French_France to-locale French_Canada.

Running SAS in a Different Locale

TosetthelocaleforSAS9.2atyoursite,addtheLOCALEsystemoptiontoyourconfigurationfile. YoucanfindalistoflocalevaluesintheSAS9.2NationalLanguageSupport(NLS):UsersGuide. Whenyoureadorwriteafile,SAS9.2expectsthedataintheexternalfilestobeinthesession encoding.Tospecifyadifferentencoding,refertothedocumentationfortheENCODINGsystem optionintheFILENAME,INFILE,orFILEstatementintheSAS9.2NationalLanguageSupport(NLS): UsersGuide. WhenLOCALEisset,theENCODINGsystemoptionwillbesettoanencodingthatsupportsthe languageforthelocale.SAS9.2expectsuserdatatobeintheencodingthatmatchestheENCODING option.Ifyoupreferanencodingotherthanthemostcommonencodingforthelocale,youcanalso settheENCODINGsystemoptionintheconfigurationfile. WhentheENCODINGoptionisset,theTRANTABoptionwillalwaysbesettomatchtheENCODING systemoption.Thetransportformattrantabs(translationtables),setbytheTRANTABoption,areused bytheCPORTandCIMPORTprocedurestotransferSASdatafiles.Thesetrantabsarealsousedbythe UPLOADandDOWNLOADproceduresfortransferringfilesandcatalogs,remotelysubmittingcodeto theserver,andreturninglogsandlistingstotheclient. TheOutputDeliverySystem(ODS)willcreateoutputusingtheencodingthatmatchesthe ENCODINGsystemoption.Ifyouwouldlikeyouroutputcreatedusingadifferentencoding,please refertothedocumentationfortheOutputDeliverySystem. Formoreinformation,refertotheBaseSAS9.2ProceduresGuideinbaseSASsoftwarefor documentationaboutPROC CPORTandPROC CIMPORT.RefertotheSAS/CONNECT9.2Users GuidefordocumentationonPROC UPLOADandPROC DOWNLOAD.

Additional Information
Dependingontheapplicationsyourun,additionalsetupmayberequiredforyoursystem.Refertothe followingsectionsformoreinformationaboutconfiguringyoursystemtorunwithalternatelocales.

Locale Setup on the Remote Server

Note: The%LS( )macrowasintroducedinSAS9.1.ThismacroreplacedthefunctionalityoftheLocale SetupWindowthatwasusedinpreviousreleases. ReferencestoSASSystem9inthefollowingsectionrefertoallreleasesofSASsoftware fromSASSystem9forward.

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

IfyouarerunningSASSystem9asbothyourclientandserversessions,itisnotusuallynecessaryto runthe%LS( )macrotodoanyfurtherlocalesetup.Thelocaleofaservershouldbecompatible withthelocaleofyourclientsession;otherwise,yourdatamaybecorrupted. IfyourSASSystem9clientisconnectingtoasessionrunningareleaseofSASpriortoSASSystem9, youcanusethe%LS( )macrotosetuptheremoteSASenvironmentfordatatransfer.AstheLocale SetupWindowdidinpreviousreleases,the%LS( )macrocopiesthehosttohosttranslationtables fromtheLOCALEcatalogintoSASUSER.PROFILE.The%LS( )macrodoesnotsettheencodingfor theSASsession. IfyouuseSAS/CONNECTtoconnecttoaremoteSASserver,youwillneedtosetuptheserver sessionforthelocalethattheSASclientisusing.Youmustsetuptheserveraftersigningontothe remotesessionfromtheclient. Thefollowingexamplesshowhowtosetlocaleforremoteconnections: ConnectingSASSystem9toSASSystem9:UsetheLOCALEoptionatstartup.TheLOCALEoption valueoftheSASclientandserversessionsshouldbethesame.Forexample, sas -locale Spanish_Spain ConnectingSASSystem9andapreviousreleaseofSAS: SASSystem9receivesthedata:UsetheLOCALEoptionontheSASSystem9sideatstartup. Example:sas -locale Spanish_Mexico Previousreleasereceivesthedata:StartSASSystem9withtheLOCALEoptionatstartup. Example:sas -locale Spanish_Guatemala Thenusethe%LS( )macroinSASSystem9tosetupthehosttohosttranslationtablesonthe previousreleaseafterconnectionisestablished.Forexample,submitthefollowingcodefromthe ProgramEditor: %ls(locale=Spanish_Guatemala, remote=on);

Devmaps and Keymaps for SAS/GRAPH Software

IfyouarerunningSAS/GRAPHsoftwareandyouwanttodisplaynonASCIIcharacters,setthe appropriatedevmapsandkeymapstomatchyourcurrentencoding.Thedevmapandkeymap entriesarelocatedintheSASHELP.FONTScatalog.Togetthecorrectdevmapsandkeymapsfor yourencoding,youshouldusethe%LSGRAPHmacro. Therearetwowaysinwhichthe%LSGRAPHmacroautomaticallysetsupanenvironment: copiesthedevmapandkeymapentriesthatmatchyourencodingtotheGFONT0.FONTS catalog changesthenameoftheentrytothenameDEFAULTsothedevmapsandkeymapswillbe loadedforyou.

Thefollowingexampleuses%LSGRAPHtosetthecorrectdevmapandkeymap(WLT2)foraPolish userontheWindowsplatform: libname gfont0 'your-font-library'; %lsgraph(wlt2);

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

Hereisalistofthedevmapsandkeymapsthatmatchthelocalesonyourplatform: LocaleDevmapand KeymapName Arabic_Algeria Arabic_Bahrain Arabic_Egypt Arabic_Jordan Arabic_Kuwait Arabic_Lebanon Arabic_Morocco Arabic_Oman Arabic_Qatar Arabic_SaudiArabia Arabic_UnitedArabEmirates Arabic_Tunisia Bulgarian_Bulgaria Byelorussian_Belarus Croatian_Croatia Czech_CzechRepublic Danish_Denmark Dutch_Belgium Dutch_Netherlands English_Australia English_Canada English_HongKong English_India English_Ireland English_Jamaica English_NewZealand English_Singapore English_SouthAfrica English_UnitedKingdom English_UnitedStates Estonian_Estonia Finnish_Finland French_Belgium French_Canada French_France French_Luxembourg French_Switzerland German_Austria German_Germany German_Lichtenstein German_Luxembourg wara wara wara wara wara wara wara wara wara wara wara wara wcyr wcyr wlt2 wlt2 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wbal wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 LocaleDevmapand KeymapName German_Switzerland Greek_Greece Hebrew_Israel Hungarian_Hungary Icelandic_Iceland Italian_Italy Italian_Switzerland Latvian_Latvia Lithuanian_Lithuania Norwegian_Norway Polish_Poland Portuguese_Brazil Portuguese_Portugal Romanian_Romania Russian_Russia w Serbian_Yugoslavia Slovakian_Slovakia Slovenian_Slovenia Spanish_Argentina Spanish_Bolivia Spanish_Chile Spanish_Colombia Spanish_CostaRica Spanish_DominicanRepublic Spanish_Ecuador Spanish_ElSalvador Spanish_Guatemala Spanish_Honduras Spanish_Mexico Spanish_Nicaragua Spanish_Panama Spanish_Paraguay Spanish_Peru Spanish_PuertoRico Spanish_Spain Spanish_UnitedStates Spanish_Uruguay Spanish_Venezuela Swedish_Sweden Turkish_Turkey Ukrainian_Ukraine wlt1 wgrk wheb wlt2 wlt1 wlt1 wlt1 wbal wbal wlt1 wlt2 wlt1 wlt1 wlt2 cyr wcyr wlt2 wlt2 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wlt1 wtur wcyr

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

Chapter 3: Post-Installation Setup for the SAS 9.2 Foundation

Ifyouadd{SASHOME}\SASFoundation\9.2toyoursystemPATH,SAS9.2canrunfroma commandconsoleinanyfolderwhenyoutypeSAS.

PATH Environment Variable in Windows XP

ForWindowsXP,ThePATHEnvironmentvariablecanbemodifiedasfollows: 1. 2. 3. 4. 5. GotoStart>Settings>ControlPanel.IntheControlPanelclassicview,doubleclickthe Systemicon. WithintheSystemPropertiesGUI,selecttheAdvancedtab.ClicktheEnvironment Variablesbutton(nearthebottomoftheGUI). UnderSystemVariables,scrolldownandselectPath. ClickEdit. InthetinyVariableValue:window,scrolltotherightandaddthefollowingtotheendof theline: ;c:\program files\sas\sasfoundation\9.2\ Note: IfyouhaveinstalledyourSASsoftwareinadifferentlocation,useyouractualsas.exe pathnameinstead. Besuretoincludethesemicolon(;)toseparatethispathfromalltheotherpaths. 6. ClickOK,OK,andOK.

NowthatthisfolderisinyoursearchPATH,youcaneasilyexecuteanycommandinitbytypingthe nameofthatcommand(suchassas.exe)attheDOScommandlineprompt.

Other Windows Operating Systems

ForinformationaboutsettingthePATHEnvironmentVariableforotherversionsandeditionsofthe WindowsOperatingSystem,refertoMicrosoftWindowsHelp.

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

Chapter 4: Configuring SAS Analytics Accelerator for Teradata

Thischapterdescribesregisteringuserdefinedfunction(UDFs)thatareincludedwithyourSAS EnterpriseMinersoftwareinyourTeradatadatabase.

SAS/STAT UDFs
ThechapterassumesthatyouhavesuccessfullyinstalledSASFoundation,includingSAS/STAT.

Database Permission for Registering the UDFs

SincetheSAS/STATUDFsaregoingtoberegisteredindatabaseSYSLIB,youmustbegrantedthe CREATEFUNCTIONprivilegeintheSYSLIBdatabase. Toobtaintheappropriatepermission,contactyourdatabaseadministrator.

Registering the UDFs

ToregistertheSAS/STATUDFsinyourTeradatadatabase,youshouldinvoketheinstallmacro indtdudf.sasthathasbeeninstalledundersasautosaspartofSAS/STAT.Torunthemacro, submitthefollowingcommandsintheProgramEditorfromSAS: %let indconn = server=myserver user=myuserid password=XXXX database=SYSLIB; % udftdstt; TheINDCONNmacrovariableprovidescredentialstoconnecttotheTeradatamachine.Youmust specifytheserver,user,password,anddatabasetoaccessthemachineonwhichyouhaveinstalled theTeradatadatawarehouse: myserveristheserveronwhichtheTeradatawarehouseresides userisavaliduserIDforthatserver XXXXisthepasswordfortheuserIDthatyouareusing BecausetheSAS/STATUDFsmustberegisteredtotheSYSLIBdatabase,databasemustbe SYSLIB.

SAS Enterprise Miner UDFs

ThesectionassumesthatyouhavesuccessfullyinstalledSASFoundation,includingSASEnterprise Miner.

Database Permission for Registering the UDFs

SincetheSASEnterpriseMinerUDFsaregoingtoberegisteredindatabaseSYSLIB,youmustbe grantedtheCREATEFUNCTIONprivilegeintheSYSLIBdatabase. Toobtaintheappropriatepermission,contactyourdatabaseadministrator.

10

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

Registering the UDFs

ToregistertheSASEnterpriseMinerUDFsinyourTeradatadatabase,youshouldinvoketheinstall macroudftdem.sasthathasbeeninstalledundersasautosaspartofSAS/ENTERPRISEMINER. Torunthemacro,submitthefollowingcommandsintheProgramEditorfromSAS: %let indconn = server=myserver user=myuserid password=XXXX database=SYSLIB; %udftdem; TheINDCONNmacrovariableprovidescredentialstoconnecttotheTeradatamachine.Youmust specifytheserver,user,password,anddatabasetoaccessthemachineonwhichyouhaveinstalled theTeradatadatawarehouse: myserveristheserveronwhichtheTeradatawarehouseresides userisavaliduserIDforthatserver XXXXisthepasswordfortheuserIDthatyouareusing BecausetheSASEnterpriseMinerUDFsmustberegisteredtotheSYSLIBdatabase,database mustbeSYSLIB.

Documentation for Using the UDFs

ForinformationabouthowtouseyournewlyregisteredUDFs,pleaseseetheSASAnalytics AcceleratorforTeradata:Guideat http://support.sas.com/documentation/onlinedoc/analyticsaccel/index.html.

11

Chapter 5: SAS/ACCESS Interfaces

Configuring SAS/ACCESS Interface to Aster nCluster Software
Registering SAS/ACCESS Interface to Aster nCluster
ThefollowingSASproceduremustberunsothattheSAS/ACCESStoAsternClusterproductis registeredwiththeSASsystemcatalog: PROC NICKNAME CAT=sashelp.core engine; add nickname=aster module=sasioast desc="SAS/ACCESS to Aster" preferred eng; quit;

Installing and Configuring the ODBC Driver and Bulk Loader

BeforeconfiguringtheODBCdriver,thebulkloadershouldbeinstalledin <SASHOME>\SASFoundation\9.2\orsomewherethatisinthePATHenvironmentvariable.After theyhavebeeninstalled,youmustconfiguretheODBCdatasource.SASrecommends(butdoesnot require)thatyoucreateadatasourcename,usingtheinstructionsbelow.Ifyouhavemorethanone userwhomayusethesameworkstationtoaccesstheAsternClusterdatabase,youmaychooseto createitasasystemDSNratherthanauserDSN. CompletethefollowingstepstocreateadatasourceforAsternClusterdatabaseaccess: 1. 2. 3. 4. 5. 6. 7. 8. 9. RunODBCAdministratorfromtheControlPanelorStartmenu. SelecttheUserDSNorSystemDSNtab,dependingonthenumberofusers,asstatedabove. ClickAddandchoosenClusterfromthepopupwindow.ClickFinish. EnteranynameintheDataSourcefield. EnterthedatabasenameintheDatabasefield. EnterthehostnameorIPAddressintheServerfield. EntertheusernameintheUserNamefield. EnterthepasswordinthePasswordfield. ClickTest.Afteramessageappearsthatindicatesthatthetestwassuccessful,clickOK.

10. ClickSave.

Configuring SAS/ACCESS Interface to Greenplum Software

SAS/ACCESSInterfacetoGreenplumusestheDataDirectTechnologiesGreenplumWireProtocol ODBCdrivercomponent,whichshouldbedownloadedfromSAS.Pleaseseethesectionentitled SAS/ACCESSInterfacetoGreenplumSoftwareintheSystemRequirementsdocumentationfor informationaboutthedownload.AfteryouhavereceivedtheODBCdriver,usethefollowingsteps tounzipitandputitintheappropriatelocation.

Page 12

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

1.

UseWindowsExplorertonavigatetothe!SASROOT\access\sasmiscdirectorywherethe <platform>gplm60.zipislocatedandwhere<platform>isspecifictoyouroperating system. Unzipthe<platform>gplm60.zipfile. FollowtheinstructionsintheReadme.txtfilecontainedinthezipfile.

2. 3.

Afteryoudownloadandinstallthesoftware,configureaDataSourceName(DSN)toaccessa Greenplumdatabase.YoucanusetheODBCadministratortoaddit.Ifyouhavemorethanoneuser whomayusethesameworkstationtoaccesstheGreenplumdatabase,youcancreateitasasystem DSNinsteadofauserDSN. CompletethefollowingstepstocreateadatasourceforGreenplumdatabaseaccess: 1. 2. 3. 4. 5. 6. 7. 8. 9. RunODBCAdministratorfromtheControlPanelorStartmenu. ClicktheUserDSNorSystemDSNtab,dependingonthenumberofusers,asstatedabove. ClicktheAddbuttonandchooseSASACCESStoGreenplumfromthepopupwindow. EnteranynameintheDataSourceNamefield.Thiswillbethenamethatyouwilluseinside ofSASwhenreferencingthisdatabaseconnection. EnteraDescriptionforthisconnection. EnterthePortNumberthatthehostislisteningonforGreenplumconnections.Thedefaultis 5432. EntertheDatabaseNameofthedatabaseontheGreenplumserver. ClickTestConnectionandenteryouruseridandpassword.Atestconnectionwillbe initiated. ClickOKtoclosetheODBCAdministratorandtosaveyournewDSNentry.

Bulkload
SAS/ACCESScaninterfacewiththeGreenplumClientLoaderinterfaceforloadinglargevolumesof data.Toperformbulkloading,theGreenplumClientLoaderPackagemustbepresentonthesystem whereyouinstalledSAS. SASrecommendsusingthegpfdistprotocolforbulkloading.Forthisprotocolyoumustsetthe GPLOAD_HOMEenvironmentvariabletopointtothelocationwheretheGreenplumClientLoaderis installed.Additionalinformationabouthowtousethebulkloadingfeaturecanbefoundinthe SAS/ACCESS9.2forRelationalDatabases:Referencedocumentation.

Registering SAS/ACCESS Interface to Greenplum

ThefollowingSASprocedurecanberunsothattheSAS/ACCESSInterfacetoGreenplumproductis registeredwiththeSASsystemcatalog: PROC NICKNAME CAT=sashelp.core engine; add nickname=greenplm module=sasiogpl desc="SAS/ACCESS to Greenplum" preferred eng; quit;

13

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

Configuring SAS/ACCESS Interface to MySQL Software

BeforeyoucanuseSAS/ACCESSInterfacetoMySQLsoftware,thefollowingproductsarerequired: BaseSASsoftware SAS/ACCESSInterfacetoMySQLsoftware

BeforeyouuseSAS/ACCESSinterfacetoMySQLsoftware,verifythattheMySQLclientlibraryhas beenappendedtoPath,asystemvariable.TheMySQLclientlibraryisoftenlocatedin C:\mysql\bin. TolocatethePathsystemvariable,followtheinstructionsforyouroperatingsystem. ForWindowsNT,rightclickMyComputerandchooseProperties.SelecttheEnvironment tabandyouwillseeinyourlistofsystemvariables. ForWindows2000,rightclickMyComputerandchooseProperties.SelecttheAdvancedtab andselecttheEnvironmentVariablesbutton.YouwillseePathinyourlistofSystem Variables. ForWindowsXP,clickStartthenselectControlPanel.DoubleclickSystem.Selectthe AdvancedtabandselecttheEnvironmentVariablesbutton.YouwillseePathinyourlistof SystemVariables.

IfyouuseMySQLClientversion4.1.0orlater,youwillneedtomakeachangebecauseofclient incompatibilities.TheSASMYL SASoptionmustbeupdatedsothattheSAS/ACCESSInterfaceto MySQLcanidentifyyourversionoftheMySQLclient.Thiscanbedoneeitherinthebeginningof yourSASprogramorinyourSASV9.cfgfile. IfyouwanttosettheSASMYLoptioninyourSASProgram,addthefollowinglineatthetopofyour SASprogram: options set=SASMYL MYWIN417 TheSASV9.cfgfileislocatedinyour!SASROOTdirectory.TosettheSASMYL SASoptioninyour configfile,addthefollowingline -set SASMYL MYWIN417 FormoreinformationaboutSAS/ACCESSInterfacetoMySQL,refertotheMySQLchapterin SAS/ACCESS9.2forRelationalDatabases:Reference.

Configuring SAS/ACCESS Interface to ODBC Software

BeforeyoucanuseSAS/ACCESSInterfacetoODBCsoftware,thefollowingproductsarerequired: BaseSASSoftware SAS/ACCESSInterfacetoODBCSoftware A32bitODBCdriverforthesourcefromwhichyouwanttoaccessdata

TheODBCsolutionallowsdifferenttechnologiestobeusedbydefiningastandardinterface. SAS/ACCESSInterfacetoODBCsoftwarewithODBCdriversprovidesyouwithaccesstodifferent databases.AnODBCdriverprocessesODBCfunctioncallsfromandreturnsresultsto SAS/ACCESSsoftware.YoucangetdriversfromMicrosoft,yourdatabasevendor,orotherthird partysoftwarevendors.

14

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

TorunSAS/ACCESSsoftwareon32bitWindows,youneed32bitdrivers.Theapplicationcallsthe 32bitDriverManager(ODBC32.DLL),whichinturncallsthe32bitdrivers.Thefollowingfigure illustratesthearchitecture:

SAS/ACCESS

32-Bit Driver Manager (ODBC32.DLL)

32-Bit Driver

32-Bit Driver

32-Bit Driver

Data Source

Data Source

Data Source

TheODBCDriverManagerandAdministratorareMicrosoftproductsthatareincludedwithall ODBCdrivers.WhenyouinstallanODBCdriver,theODBCDriverManagerandAdministratorare alsoinstalled.TheODBCAdministratorshouldappearasaniconinthecontrolpanel.However,it canappearasaniconintheStartmenuinstead. AfteryouinstalltheODBCdriver,youcanusetheODBCAdministratortodefineandmanagethe datasources.AdatasourceassociatesaparticularODBCdriverwiththedatayouwanttoaccess throughthatdriver.Itcanconsistofinformationaboutthedatayouwanttoaccessanditsassociated operatingsystem,DBMS,andnetworkplatform(ifany)usedtoaccesstheDBMS.Forinformation abouthowtoconfigureyourdatasources,refertothedocumentationprovidedwithyourODBC drivers. FormoreinformationaboutSAS/ACCESStoODBC,refertotheODBCchapterinSAS/ACCESS9.2 forRelationalDatabases:Reference.FormoreinformationaboutODBC,refertoMicrosoftODBC3.0 ProgrammersReferenceandSDKGuide.

SAS/ACCESS ODBC Conversion Utilities

TheSAS/ACCESSODBCConversionUtilitiesareincludedintheSAS/ACCESSInterfacetoODBC software.IthelpsusersofVersion6SAS/ACCESSInterfacetoAS/400andSAS/ACCESSInterfaceto MicrosoftSQLServermovefromanativeDBMSinterfaceconnectiontoanODBCinterface connectiononSAS9.2.

AS/400 Users
BeforeyoucanusetheODBCConversionUtilitiesforAS/400Interface,youneedtoinstallIBMs ClientAccessODBCDriver(32bit)V3.00.0004orabove.IfyourAS/400ClientAccessinstallation loadedaClientAccessODBCDriverpriortothisrelease,youcandownloadProgramTemporaryFix (PTF)SF59504orlaterfromftp://ftp.software.ibm.com/foranupdate.Thisservicepackfor theClientAccessproductcanbefoundinthe /as400/products/clientaccess/win32/v3r1m2/servicepack/directory.Whenthis updateisapplied,Version3.00.0004orlateroftheODBCdrivershouldbeinstalled.

15

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

Youarealsorequiredtocreateadatasourcename.YoucanusetheODBCadministratortoaddit. ThedatasourcenameAS400isrecommended.Ifyouwanttouseanotherdatasourcename,setthe SASenvironmentvariableAS400DSN,locatedinyoursasv9.cfg,tothedatasourcenameyou assigned.Quotesarerequiredifblanksorspecialcharactersareincluded.Youmaywanttocreateit asasystemDSNinsteadofauserDSNifyouhavemorethanoneuserwhomightwanttousethe sameworkstationtoaccesstheAS/400database. CompletethefollowingstepstocreateadatasourceforAS/400databaseaccess: 1. 2. 3. 4. 5. 6. 7. 8. RunODBCAdministratorfromtheControlPanelorStartmenu:Start>Settings>Control Panel>(AdminTools>onXP)DataSources(ODBC). ClicktheUserDSNorSystemDSNtab,dependingonthenumberofusers. ClicktheAddbuttonandthenchooseClientAccessODBCdriver(32bit)fromthepopup windows. ClickFinish.ThisbringsuptheSetupdialog. ClicktheGeneraltabandenterAS400(oranothername)intheDataSourceNamefield.This nameneedstomatchthevalueyousetfortheSASenvironmentvariableAS400DSN. Fromthepulldownmenu,chooseanAS/400systemthatyouwanttoconnecttousingthis datasource. Tochangethemethodthatthisdatasourcewillusetoconnect,clickConnectionOptions. SelecttheappropriateoptionandclickOK. ClicktheServertab.ThedefaultlibraryisQGPL.Youcanchangethisdesignationby deletingitsnamefromundertheDefaultLibrariesfiledandeitherenteringanewlibraryto useorleavingitblank. ClicktheFormattab.UsingtheNamingConventionpulldownlist,selectSystemnaming convention(*SYS).

9.

10. ClickthePackage(s)tab.UnchecktheboxforEnableExtendedDynamicSupport. 11. ClickOKtoclosetheSetupwindow.

Microsoft SQL Server Users

AnODBCConversionUtilityisprovidedthatwillallowyoutoreadSASSystemVersion6viewsto accessdatainMicrosoftSQLServerwhichwerecreatedwithSAS/ACCESSInterfacetoSybaseand SQLServersoftwareonWindows.TheConversionUtilityhelpsusersmigratetoSAS/ACCESS InterfacetoODBCsoftwareonWindows. Note: TheConversionUtilityappliesonlytoviewsthataccessdatainMicrosoftSQLServer.Itdoesnot applytoSYBASESQLServer. TheODBCConversionUtilityrequirestheMicrosoftSQLServerODBCdriver(32bit)from Microsoft.ThisdriverisinstalledaspartofMicrosoftDataAccessComponents(MDAC). Itisrecommended(butnotrequired)tocreateadatasourcename.YoucanuseODBCadministrator toaddit.YoumustsettheSASenvironmentvariableMSSQLDSN,locatedinthesasv9.cfg,asthe datasourcenameyouassigned.Quotesarerequiredifblanksorspecialcharactersareincluded.You

16

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

cancreateitasasystemDSNinsteadofauserDSNifyouhavemorethanoneuserwhomayusethe sameworkstationtoaccesstheMicrosoftSQLServerdatabase. CompletethefollowingstepstocreateadatasourceforMicrosoftSQLServerdatabaseaccess: 1. 2. 3. 4. 5. 6. 7. 8. 9. RunODBCAdministratorfromtheControlPanelorStartmenu. ClicktheUserDSNorSystemDSNtab,dependingonthenumberofusers,asstatedabove. ClicktheAddbuttonandchooseSQLServerfromthepopupwindow. EnteranynameintheNamefield.ThisnameneedstomatchthevalueyousetfortheSAS environmentvariableMSSQLDSN. ChooseorentertheServerfieldwhichyoudefinedusingSQLClientConfigurationUtility. ClickNext.Selecttheradiobuttonthatdescribesyourloginmethod.Ifnecessary,entera loginIDandpassword. ClickNext.Aconnectionwillbeinitiated.Iftheconnectionsucceeds,pleaserefertoStep8 below.Iftheconnectionfails,anerrormessagewillprovideareasonforthefailure. Afteraconnectionsucceeds,yourdefaultdatabasesmaybechanged.ClickNexttoleavethis screen. Afterchangingyourdefaultdatabases,otheroptionsmaybeselected.ClickFinishwhenthis screeniscorrect.

10. ClickTestDataSource.Afteramessageappearsthatindicatesthatthetestwassuccessful, clickOkay.ClickOkayonthefollowingmessageaswell. Note: SAS9.2willautomaticallyinstallMicrosoftDataAccessComponents(MDAC)whenyouinstall SAS/ACCESSInterfacetoODBCsoftware.

Configuring SAS/ACCESS Interface to Oracle Software

BeforeSAS/ACCESSInterfacetoOraclesoftwarecanbeused,thefollowingproductsarerequired: Base SAS software SAS/ACCESS Interface to Oracle software Oracle client/server, Release 9i or above

AftertheOracleclient/serverinstallationprocessiscomplete,ensurethatthepathtotheOracleclient librariesisappendedtothePATHsystemvariable.TheOraclelibrariesareusuallylocatedinthe directoryORACLE_HOME/bin.IfthePATHvariabledoesnothaveORACLE_HOME/bin,youwillsee thefollowingerror: ERROR: The SAS/ACCESS Interface to ORACLE cannot be loaded. ERROR: Image SASORA found but not loadable. FormoreinformationaboutSAS/ACCESSInterfacetoOracle,refertotheOraclechapterin SAS/ACCESS9.2forRelationalDatabases:Reference.

Configuring SAS/ACCESS Interface to R/3 Software

SAS/ACCESSInterfacetoR/3softwarerequiresextensivepostinstallationconfigurationbeforeitcan beused.Fordetailedinformation,refertotheConfigurationInstructionsforSAS/ACCESS4.3Interfaceto

17

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

R/3onInstallCenter (http://support.sas.com/documentation/installcenter/92/documents/index.html).

Configuring SAS/ACCESS Interface to SYBASE Software

InSAS9.2,theadministratororusermustinstallaSybasestoredprocedureonthetargetserver.Two fileshavebeenincludedinthe!SASROOT\access\miscdirectorytoassistintheinstallation: sas-spcp.txtisatextfilecontaininginstructionsonhowtodotheinstallation. sas-spdf.txtistheactualstoredprocedurescript.TheprocessutilizestwoSybase facilities,defncopyandisql.

Tocompleteinstallation,youmustaddoneofthefollowingoptionstoyoursasv9.cfgfile: ForSybaseOpenClient15users:-set sassyb sywin150 ForSybaseOpenClient12.5users:-set sassyb sywin125

Configuring SAS/ACCESS Interface to Teradata Software

BeforeusingSAS/ACCESSInterfacetoTeradatasoftware,youshouldverifyconnectivitybylogging intoyourTeradataaccountwiththeTeradataBTEQutility.IfBTEQisunavailable,establish connectivityasdocumentedintheSAS/ACCESStoTeradatawhitepaper,availableat http://support.sas.com/resources/papers/teradata.pdf. IfBTEQfailstoconnecttotheTeradataserver,youmayneedanentryinthehostsfileonyourPCto providethenetworkaddressoftheTeradataserver.Typically,thismeansaddingadbccop1entryto yourhostsfile.Formoredetailsabouttheentry,seeyourTeradataClientforWindowsInstallation Guide.

FastExporting
Foroptimalreadsoflargetables,SAS/ACCESScanperformFastExporting.ToperformFastExporting, theTeradataFastExportUtilitymustbepresentonthesystemwhereyouinstallSAS.Youmustalso modifyPath,asystemvariable.AppendtwodirectorypathstotheendofPath: 1. 2. Thedirectorywherefexp.exe(theFastExportUtility)islocated.OftenthisisC:\Program Files\NCR\Teradata Client\bin. Thedirectorywheresasaxsm.dllislocated(sasaxsm.dllisusuallylocatedinyourSAS producttree,inthe!sasroot\access\sasexedirectory.)

TolocatethePathsystemvariable,followtheinstructionsforyouroperatingsystem: ForWindowsNT,rightclickMyComputerandchoseProperties.SelecttheEnvironment tabandyouwillseePathinyourlistofSystemVariables. ForWindows2000,rightclickMyComputerandchoseProperties.SelecttheAdvancedtab andselecttheEnvironmentVariablesbutton.YouwillseePathinyourlistofSystem Variables. ForWindowsXP,clickStartthenselectControlPanel.DoubleclickSystem.Selectthe AdvancedtabandselecttheEnvironmentVariablesbutton.YouwillseePathinyourlistof SystemVariables.

18

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

TheFastExportUtilityisnotrequired;SAS/ACCESSreadslargetablesquiteefficientlywithoutit.For furtherinformation,seetheDBSLICEPARMoptioninyourSAS/ACCESStoTeradatadocumentation. ContactNCRifyouwanttoobtaintheTeradataFastExportUtility. FormoreinformationaboutSAS/ACCESSInterfacetoTeradatasoftware,pleaseseetheTeradata chapterinSAS/ACCESS9.2forRelationalDatabases:Reference,andtheSAS/ACCESStoTeradatawhite paper,availableontheSASwebsiteat http://support.sas.com/resources/papers/teradata.pdf.

MultiLoad
SAS/ACCESScanloadlargevolumesofdatatononemptytablesusingMultiLoad.Toperform MultiLoading,theTeradataMultiLoadUtilitymustbepresentonthesystemwhereyouinstallSAS. YoumustalsomodifyPath,asystemvariable.AppendtwodirectorypathstotheendofPath: 1. 2. Thedirectorywheremload.exe(theMultiLoadUtility)islocated.Oftenthisis C:\Program Files\NCR\Teradata Client\bin Thedirectorywheresasmlam.dllandsasmlne.dllarelocated(sasmlam.dlland sasmlne.dllareusuallylocatedinyourSASproducttree,inthe !sasroot\access\sasexedirectory.)

TolocatethePathsystemvariable,followtheinstructionsforyouroperatingsystem: ForWindowsNT,rightclickMyComputerandchoseProperties.SelecttheEnvironment tabandyouwillseePathinyourlistofSystemVariables. ForWindows2000,rightclickMyComputerandchoseProperties.SelecttheAdvancedtab andselecttheEnvironmentVariablesbutton.YouwillseePathinyourlistofSystem Variables. ForWindowsXP,clickStartthenselectControlPanel.DoubleclickSystem.Selectthe AdvancedtabandselecttheEnvironmentVariablesbutton.YouwillseePathinyourlistof SystemVariables.

TheMultiLoadUtilityisnotrequired;SAS/ACCESSprovidesotheroptionsforloadingtables.For furtherinformation,seetheMULTISTMToptioninyourSAS/ACCESStoTeradatadocumentation. ContactNCRifyouwanttoobtaintheTeradataMultiLoadUtility.

Teradata Parallel Transporter

SAS/ACCESSsupportstheTeradataparalleltransporterAPIforloadingdatausingMultiload, Fastloadandmultistatementinserts.TheAPIalsosupportsreadingdatausingFastExport. Note: TheTeradataParallelTransporterAPIisnotrequired;SAS/ACCESSprovidesotheroptionsfor loadingandreadingdata. IfyouplantousetheTeradataparalleltransporterAPI,thefollowingtworequirementsmustbemet: 1. 2. TheAPImustbeinstalledonthesystemwhereSASisinstalled. ThesystemvariableTKPATHIA32mustbemodified.Ifthevariabledoesnotexistalready,it mustbeadded.

Tomodifythevariable,appendthedirectorywheresasiotpt.dllislocated.(Usually sasiotpt.dllislocatedinyourSASproducttree,inthe!sasroot\access\sasexedirectory.)

19

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

TolocatetheTKPATHIA32systemvariable,followtheinstructionsforyouroperatingsystem: ForWindowsNT,rightclickMyComputerandchoseProperties.SelecttheEnvironment tabandTKPATHIA32willappearinyourlistofSystemVariables. ForWindows2000,rightclickMyComputerandchoseProperties.SelecttheAdvancedtab andselecttheEnvironmentVariablesbutton.TKPATHIA32willappearinyourlistof SystemVariables. ForWindowsXP,clickStart,thenselectControlPanel.DoubleclickSystem.Selectthe AdvancedtabandselecttheEnvironmentVariablesbutton.TKPATHIA32willappearin yourlistofSystemVariables.

20

Chapter 6: Post-Installation Setup for SAS/ASSIST Software

ThischapterdescribeshowtoaddanoptionalmasterprofiletoSAS/ASSISTsoftware.Youcanusea masterprofiletooverridethedefaultsettingsassentbySAS.Thisallowsyoutoprovidea customizedsetupforSAS/ASSISTsoftware.Withthemasterprofile,youcancontroltheprofile optionsofallSAS/ASSISTusersfromonecentralplace.Forinformationontheprofileoptions,refer toSAS/ASSISTAdministratorsGuide.

Adding a Master Profile

CompletethefollowingstepstoaddamasterprofiletoSAS/ASSISTsoftware: 1. Specifythelocationofthemasterprofilebycreatinganewdirectorythatallusersof SAS/ASSISTsoftwarewillhavereadaccessto. Alluserswithwriteaccesstothisdirectorywillautomaticallyalsohavewriteaccesstothe masterprofileinSAS/ASSISTsoftware.Selectanamethatconformstothenaming conventionsatyourinstallation.Thenameofthisnewdirectorymustbestoredinanentryin theSASHELPlibrary.ThisrequiresthatyouhavewriteaccesstotheSASHELPlibrary. Online1oftheEditorwindowoftheSASDisplayManagerSystem,typethephysical pathnameofthemasterprofiledirectory.ExecutetheSavecommandtostorethisinthe SASHELP.QASSISTcatalog.Forexample: SAVE SASHELP.QASSIST.PARMS.SOURCE 00001 S:\SAS\ASSIST\PARMS 00002 00003 ThelocationofthemasterprofileisnowknownbySAS/ASSISTsoftware. 2. Createthemasterprofile. ThefirsttimeSAS/ASSISTsoftwareisstarted,amasterprofileiscreatedif SASHELP.QASSIST.PARMS.SOURCEcontainsthenameofanexistingphysicalpathname, andthepersonwhostartsSAS/ASSISTsoftwarehaswriteaccesstothisphysicalpathname. 3. CustomizethemasterprofilebystartingSAS/ASSISTsoftwareandselectingSetup>Profiles >Master/group... IfyouhavewriteaccesstotheSASlibrarycontainingthemasterprofile,youcanspecify defaultvaluesforyourinstallation.NewuserswillusethesevaluesastheystartSAS/ASSIST software. Note: IfyourestrictvaluesbytypingRinStatus,userswillnotbeallowedtochangethevalues youdefine. YoucanrunSAS/ASSISTsoftwareintwodifferentstylesworkplaceorblockmenu.The blockmenucanbenewstyleoroldstyle.Youcancontrolthisusingtheprofileoptions below. Run workplace: SAS/Assist style: Run block menu new style: Workplace

Page 21

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

SAS/Assist style: Save selections on end: Menu Style: Run old style: SAS/Assist style: Save selections on end: Menu Style:

Block Menu Yes New Block Menu Yes Old

Bysettingthedefaultvaluesinthemasterprofile,youcancontrolifusersshouldusethe neworoldstyleofSAS/ASSISTsoftware.Inaddition,therearemanyotherprofileoptions. Formoreinformationontheseoptions,refertoSAS/ASSISTAdministratorsGuide. 4. Creategroupprofiles. Fromthemasterprofile,itispossibletocreategroupprofilestoallowgroupsofuserstohave differentsetups.Themasterprofilecontrolsgroupprofilesanduserprofileswhenauseris notamemberofanygroup.Allusersareindirectlycontrolledbythemasterprofilewhen optionvaluesaresettoarestricted(R)status. FromSetup>Master/Group...,selectTools>CreateGroupProfile.Toadduserstoagroup profile,selectTools>UpdateUserGroup.Bydefault,theuseridisfoundinthemacro variable&SYSJOBID.ThisvalueissetintheoptionUseridinthemasterprofile(optiontype SystemAdministration).Changethevalueifyoursiteusesanothervariabletokeepthe userid.Ifthevaluenamestartswith&,itisamacrovariable;otherwise,itisanenvironment variable,whichissetbeforethestartofSAS9.2.

22

Chapter 7: Post-Installation Setup for SAS/CONNECT Software

TCP/IPistheaccessmethodsupportedforSAS9.2onWindows.Forinformationabouttheaccess methodssupportedbyothersystems,refertoCommunicationsAccessMethodsforSAS/CONNECT9.2 andSAS/SHARE9.2.Thisdocumentcanbefoundat http://support.sas.com/documentation/onlinedoc/. Note: TheAPPCaccessmethodisnolongersupportedfortheWindowsoperatingsystem.

Storing and Locating SAS/CONNECT Script Files

SeveralsamplescriptfilesareshippedwithSAS/CONNECTsoftware.SAS/CONNECTsoftwareuses thesescriptfilestoestablishaconnectiontoaremoteSASsession. TheSASSCRIPTconfigurationoptionpointstothelocationoftheSAS/CONNECTscriptfiles.The SASSCRIPToptionisusedbySAS/ASSISTsoftwareandcanbeusedbyuserwrittenSCLapplications. UnderWindows,thescriptfilesareinstalledintothe!SASROOT\CONNECT\SASLINKdirectoryby default.ThefollowinglineisaddedtotheSASV9.CFGfilewhenSAS/CONNECTsoftwareis installed: -SASSCRIPT !SASROOT\CONNECT\SASLINK Ifyouwanttomovethescriptfilestoanotherdirectory,youmustedittheSASV9.CFGfileand updatetheSASSCRIPToptionwiththenewdirectorylocation.Thisoptioncanalsobespecifiedfrom theTools/Options/System/Communications/NetworkingandencryptionselectioninDMSEXP mode.

TCP/IP
TCP/IPistheaccessmethodsupportedforSAS9.2onWindows.SAS/CONNECTsoftwaresupports MicrosoftsTCP/IPSystemDriver,whichisprovidedwithWindows.

Configuring the SAS Windows Spawner Program

TheSASWindowsSpawnerisstoredinthe!SASROOTdirectoryandcanbeexecutedmanuallyfrom the!SASROOTdirectoryatanytime.YoucanruntheSASWindowsSpawnerasaserviceby executingSPAWNER.EXEwiththe-installoption.Bydefault,theSASWindowsSpawnerwillbe installedtorunwithsecurity.ForcompletedocumentationontheWindowsSpawnerandthe supportedoptions,seeCommunicationsAccessMethodsforSAS/CONNECT9.2andSAS/SHARE9.2. Note: IfyouareupgradingtoSAS9.2andyourunaspawnerfromapreviousreleaseasaservice,you shouldstopanddeletetheexistingspawnerservice.TheSAS9.2CONNECTspawnercanthenbe installedasaWindowsservice. Bydefault,whentheSASWindowsSpawnerisinstalledasaWindowsservice,itrunsunderthe LocalSystemuseridthathasallrequiredUserRightsforrunningtheSASWindowsSpawner.Ifyou donotinstalltheSASWindowsSpawnerasaWindowsservice(runitfromyoursystemprompt),the WindowsuseridusedtostarttheSASWindowsSpawnermustbethelocalAdministratorofthe machineandmusthavethefollowingUserRights: actaspartoftheoperatingsystem

Page 23

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

bypasstraversechecking(thedefaultiseveryone) increasequotas replaceaprocessleveltoken logonlocally(thedefaultiseveryone)

TheWindowsuseridspecifiedatsignonneedsonlytheUserRightlogonasabatchjob.

24

Chapter 8: Post-Installation Configuration for SAS/IntrNet Software

ThischapterhasinformationforyourSAS/IntrNetinstallation.Itwillhelpyouinstall,configure,and testyourSAS/IntrNetcomponents. TheproceduresforinstallingSASsoftwareusingtheSASDeploymentWizardaredescribedinother documentationandarenotavailableinthischapter.Inaddition,theinstallationofaWebserveris notdescribedinSASdocumentationbecauseitistheadministratorsresponsibility. WhenSAS/IntrNetsoftwarehasbeeninstalled,configuredandtestedusingtheproceduresdescribed inthischapter,reviewthelatestversionoftheSAS/IntrNetproductdocumentationonlineat http://support.sas.com/documentation/onlinedoc/IntrNet/index.html.TheWhats NewpageatthisWebsitelistsanyrecentchangestotheproductordocumentation.

Overview
AllSAS/IntrNetinstallationsaremadeupoftwocomponents: 1. 2. TheSAS/IntrNetserver(alsoreferredtoastheApplicationServer).ThisiswhereSAS Foundationisinstalled. CGITools(alsoreferredtoastheBroker).Thisiswherethebroker.cfgfileandits supportingfilesareinstalled.

WhenyouinstallSAS/IntrNet,choosebetweenthesetwoinstallationconfigurations: TypeATheSAS/IntrNetserverandCGIToolscomponentsarebothinstalledonthesame systemmachine.TheWebservermustbeinstalledbeforestartingtheSASinstallation. TypeBTheSAS/IntrNetservercomponentisinstalledononesystemmachineandtheCGI Toolscomponentisinstalledonadifferentsystemmachine.TheWebservermustbe installedontheCGIToolssystemmachinepriortoinstallingCGITools.

TypeAandTypeBrequiredifferentinstallationsteps: TypeAInstallationSteps ConfirmthattheWebserversoftware(IIS, Apacheetc.)isonthesamesystemmachine asyourSAS/IntrNetsoftware. InstallyourSASproducts.CheckCGI ToolsfortheWebServerintheSelect ProductstoInstallmenu. TypeBInstallationSteps ConfirmthattheWebserversoftware(IIS, Apache,etc.)isonthesystemmachine whereyouwillinstallCGITools. Onyourapplicationserversystemmachine, startyourSASinstallation.UncheckCGI ToolsfortheWebServerintheSelect ProductstoInstallmenu. OnyourWebserversystemmachine,start yourSASinstallation.Uncheckallproducts exceptCGIToolsfortheWebServerinthe SelectProductstoInstallmenu. YoucanoptionallychecktheIntrNet

Page 25

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

TypeAInstallationSteps

TypeBInstallationSteps MonitororConnectDrivers.

TesttheBroker ConfigureaSocketService StarttheSocketService TesttheSocketService RefertoyourWebserversdocumentationforitsinstallationprocedures.

Installing and Configuring SAS/IntrNet Software

Install Your Web Server Software
RefertoyourWebserversdocumentationforitsinstallationprocedures.

Install Your SAS Software

RefertoyourQuickStartGuideforadescriptionofhowtostartyourSASsoftwareinstallation. IfyouareperformingaTypeAinstallation(asdescribedintheOverviewabove),performthe followingsteps: 1. 2. ConfirmthatyourWebserversoftwareisinstalledbeforestartingyourSASsoftware installation. CheckCGIToolsfortheWebServerintheSelectProductstoInstalldialog.

IfyouareperformingaTypeBinstallation(asdescribedintheOverviewabove),dobothofthe following: 1. 2. InstalltheSASsoftwareontheSASSystemside,uncheckingCGIToolsfortheWebServer intheSelectProductstoInstalldialog. StarttheSASsoftwareinstallontheWebserverandcheckCGIToolsfortheWebServerin theSelectProductstoInstalldialog.SAS/IntrNetMonitorandSAS/CONNECTDriverfor Javaareoptionalselections.Uncheckeverythingelse.

CGI Tools Installation Dialogs

ThefollowingwindowsappearforCGIToolsfortheWebServerforallinstallations.Forinformation aboutthefields,clickHelponanydialog. Customaryentriesaredocumentedfollowingeachscreenshownbelow.Customizetheentries accordingtoyourenvironment.

26

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

ThefollowingareexamplesofcommonentriesforpopularWebservers.Customizeyourentries accordingtoyourownWebserverenvironment.ThesefieldswilltellSASwhereyourWebserver softwareislocated. Physicalpathcorrespondingtohttp://<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

PhysicalpathforSAS/IntrNetCGIExecutables: IIS: C:\Inetpub\scripts

Apache(Windows): C:\program files\Apache Software Foundation\Apache2.2 \cgi-bin Apache(UNIX): /usr/local/apache2/cgi-bin

URLforCGIExecutables: IIS: http://<web_servername>/scripts Example:http://abcserver.comp.com/scripts

Apache(Windows): http:// <web_servername>/cgi-bin Apache(UNIX): Example:http://abcserver.comp.com/cgi-bin http://<web_servername>/cgi-bin Example:http://abcserver.comp.com/cgi-bin

27

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

Notethatyourentriesforthisdialogareaddedtothebroker.cfgfile.Thebroker.cfgfileisa textfilethatcanbeeditedaftertheinstallationiscomplete. NameoftheServiceAdministrator: (optional)Enterthenameoftheadministrator(forexample,JohnDoe). EmailAddressoftheServiceAdministrator: (optional)Entertheemailaddressoftheadministrator(forexample,NetAdmin@comp.com). DNSNameorIPAddressofApplicationServerHost: EntertheDNSnameorIPaddressoftheapplicationserverhostwhereSASFoundationis located. TCPPortNumberforApplicationServer: Thecustomarydefaultportnumberis5001,butyoucanuseanyvalidavailableportonyour systembetween25665535.

Installing CGI Tools and SAS Foundation on Machines with Different Operating Systems
YourSASFoundationsystemsoperatingsystemmightbedifferentthanyourCGIToolssystems operatingsystem.Forexample,yourSASFoundationmightbeinstalledonaWindowssystemand yourCGIToolsmightbeinstalledonaUNIXsystem.TheCGIToolsinstallationfromtheSAS DeploymentWizardwilldetectthedestinationoperatingsystemandinstalltheappropriate operatingsystemspecificsoftware. TherearetwomethodstomaketheSASSoftwareDepotavailabletotheinstalleronthedestination CGIToolssystem.Choosethemethodthatisappropriateforyoursitesavailablefacilities:

28

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

LaunchthesetupfromaSASSoftwareDepotthatresidesonaremotesystem.Youmight needtouseacrossplatformfileaccessmethodsuchasNFSorSAMBAtoconnectthetwo systems. CreatemediafromanexistingdepotusingtheSASDeploymentWizardandusethatmedia onthehostmachine.ThisprocessisdescribedmorethoroughlyintheSASDeployment WizardUsersGuide,availablefromInstallCenter (http://support.sas.com/documentation/installcenter/92/documents/index.html).

Note: SAS/IntrNetoperationrequiresTCP/IPconnectivitybetweentheSASFoundationsystemandthe CGIToolssystem,regardlessoftheoperatingsystemsonwhichthesecomponentsareinstalled.

Test the Web Server

TodetermineiftheWebserverisrunning,launchtheWebserversbrowserandenter http://localhost.ThiswillreturnaWebpageiftheWebserverisrunning. IfyoudonotreceiveaWebpage,youmustdebugorreinstallyourWebserverbeforecontinuing.

Internet Information Services (IIS) 6.0+ Post-Install Configuration for Broker

InIIS6.0andlater,youneedtotakemanualstepsinorderforIIStorecognizetheBrokerasan application.Formoreinformation,pleasevisithttp://support.sas.com/kb/10/496.html.

Test the Application Broker

ToverifythatCGIToolswasinstalledcorrectlyandcanaccessthebroker.cfgfile,pointyourWeb browsertothefollowingURL: Windows: IIS: http://<web_servername>/scripts/broker.exe

Apache: http://<web_servername>/cgi-bin/broker.exe Otherhosts: http://your_webserver/cgi-bin/broker Replaceyour_webserverwiththenameoftheWebserver.TheURLpathmightalsoneedto bechangedifyouinstalledCGIToolstoadifferentdirectory.YoushouldseeaWebpagesimilar tothefollowing: SAS/IntrNet Application Dispatcher Application Broker Version 9.2 (Build 1495) Application Dispatcher Administration SAS/IntrNet Samples SAS/IntrNet Documentation - requires Internet access Ifyoudonotreceivethispage,youmustdebugyourWebserverinstallationbeforecontinuing. VerifythatyourWebserverisenabledforCGIexecutioninthedirectorywhereyouinstalledthe ApplicationBroker(broker.exeandbroker.cfgfiles).Thisdirectorywasdeterminedbywhat wasenteredforPhysicalpathforSAS/IntrNetCGIExecutablesduringtheCGIToolsinstallation above.

29

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

Configure a Default Application Dispatcher Service

YoumustcreateadefaultApplicationDispatcherservicetorunanyofthesampleprogramssupplied withSAS/IntrNet.YoushouldcreatethedefaultservicewiththeSAS/IntrNetConfigurationUtility inetcfgServicescanbecreatedonWindowsplatformswithaconfigurationutilitythatisaccessible fromtheStartmenu. Performthefollowingstepstocreateandstartthedefaultservice: 1. 2. 3. 4. 5. FromtheStartmenu,selectPrograms SAS(orotherprogramgroupwhereSASis installed) IntrNet CreateaNewIntrNetService. TheIntrNetConfigUtilityWelcomewindowappears.ReadtheinformationintheWelcome window,andthenselectNexttocontinue. SelectCreateaSocketService,thenselectNexttocontinue. Typedefaultasthenameofthenewservice.SelectNexttocontinue. Specifythedirectorywhereyouwanttheconfigurationutilitytoplaceyourservicedirectory andcontrolfiles.Thedefaultlocation(underyourSASROOTdirectory)isrecommended. SelectNexttocontinue. TypetheTCP/IPportnumberthatyoureservedforthedefaultApplicationDispatcher service.SelectNexttocontinue. Apasswordisnotnecessaryforthedefaultservice.Youcanaddanadministratorpassword laterifyouusethisserviceforproductionapplications.SelectNexttocontinue. TheCreateServicewindowdisplaysalloftheinformationthatyouspecifiedforthisservice. VerifythattheinformationiscorrectandthenselectNexttocreatetheservice. SelectNextandthenFinishtocompletethesetupofthedefaultservice.

6. 7. 8. 9.

10. FromtheStartmenu,selectPrograms SAS(orotherprogramgroupwhereSASis installed) IntrNet defaultService StartInteractively.YourdefaultApplicationServer shouldnowberunning.

Starting and Stopping the Default Service

Asstatedabove,fromtheStartmenu,selectPrograms SAS(orotherprogramgroupwhereSASis installed) IntrNet defaultService StartInteractively.YourdefaultApplicationServershould nowberunning.

Testing the Socket Service

1. Tomakesurethattheservicewasinstalledandstartedcorrectly,pointyourWebbrowserto thisURL: Windows: IIS: http://<web_servername>/scripts/broker.exe

Apache: http://<web_servername>/cgi-bin/broker.exe Otherhosts: http://your_webserver/cgi-bin/broker

30

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

Replaceyour_webserverwiththenameoftheWebserver.TheURLpathmight alsoneedtobechangedifyouinstalledtheApplicationBrokertoadifferent directory.YoushouldseethefollowingWebpage:SAS/IntrNet Application Dispatcher Application Broker Version 9.2 (Build 1495) Application Dispatcher Administration SAS/IntrNet Samples SAS/IntrNet Documentation - requires Internet access 2. 3. ClickontheApplicationDispatcherAdministrationlinktoseeiftheApplicationBrokercan readthebroker.cfgfile.TheApplicationDispatcherServicesWebpageshouldopen. VerifyconnectivitybetweentheApplicationServerandtheWebserver.Clickonthe ApplicationDispatcherAdministrationlinkandthenclickonthepinglinkunder SocketServicedefaultheading.Ifthepingissuccessful,youshouldsee: Ping. The Application Server <hostname>:<port_number> is functioning properly. 4. Tocompleteinstallationtesting,typethisURLinyourbrowseraddressline: 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 Otherhosts: http://your_webserver/cgi-bin/broker?_service=default&_program= sample.webhello.sas YoushouldseethestringHelloWorld!inlargeboldtypeinyourbrowser.Ifyoudonot, addthedebugoptiontocreatealog: 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

Otherhosts:
http://yourWebserver/cgibin/broker?_service=default&_program=sample.webhello.sas&_debug=131

SavethelogscreenonthebrowserforSASTechnicalSupport.

31

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

Configure Additional Services

ThischapterdescribeshowtoconfigureonlyasimpledefaultApplicationDispatcherservice.There aremanyreasonsyoumaywanttoconfigureadditionalservices,includingsegregatingapplications bysecurityorperformancerequirementsandimplementingmorescalableservers.SeetheUsing ServicessectionoftheSAS/IntrNetApplicationDispatcherdocumentationat http://support.sas.com/documentation/onlinedoc/intrnet/index.htmlinformation onconfiguringadditionalservices,usingtheLoadManager,andaddingpoolservices.

32

Chapter 9: Installing SAS/SECURE Software Client Components

SAS/SECUREsoftwareincludesclientcomponentsthatnonSASSystemclientapplicationscanuseto communicatewithaSASserverinasecureenvironment.TouseencryptionbetweenanonSAS SystemclientandaSASserverwithSAS/SECUREsoftwarelicensed,youmustinstallthe SAS/SECUREclientcomponentsontheclientmachine.WhenSAS/SECUREsoftwareisincludedina customersorder,theseSAS/SECUREclientcomponentscanbeselectedforinstallationviatheSAS DeploymentWizard. Note: ThisinstallationisnotnecessaryiftheSASSystemisyourclient.TheSASSysteminstallsthe componentsthatitneedsaspartoftheSASSysteminstallationprocess.

SAS/SECURE for Windows Clients

TheSAS/SECUREcomponentsneededbyWindowsclientscanbeinstalledbyrunningtheSAS DeploymentWizardtoaccesstheSAS/SECUREWindowsClientComponents.

SAS/SECURE for Java Clients

TheSAS/SECUREcomponentsforJavaclientsprovideencryptionsupportforJavaapplications.You canincorporatethissupportintoapplicationsthatarewrittenusingthefollowingcomponents: SAS/SHAREdriverforJDBC SAS/CONNECTdriverforJava IOMBridgeforJava

IftheSAS/SECUREJavaComponentwaspartofyoursoftwareorder,theSAS/SECUREcomponents neededbyJavaclientswillbeinstalledautomaticallywhenyouruntheSASDeploymentWizard.

Page 33

Chapter 10: Post-Installation Setup for SAS/SHARE Software

ThischapterdiscussestheuseoftheTCP/IPaccessmethodswithSAS/SHAREsoftware.TCP/IPisthe accessmethodsupportedforSAS9.2onWindows.Forinformationabouttheaccessmethods supportedbyothersystems,pleasevisit http://support.sas.com/documentation/onlinedoc/andrefertoCommunicationsAccess MethodsforSAS/CONNECT9.2andSAS/SHARE9.2.

Using the TCP/IP Communications Access Method

CommunicationbetweenaSAS/SHAREserveranduserishandledbytheTCP/IPcommunications accessmethod,whichisapartofSAS9.2thatusesunderlyingcommunicationssoftwaretoexchange messagesanddata.TheTCP/IPaccessmethodrequiresMicrosoftsTCP/IPNetworkProtocol communicationssoftware. Note: TheAPPCaccessmethodisnolongersupportedfortheWindowsoperatingsystem. TousetheTCP/IPaccessmethod,youmusthavethesupportingsoftwareoneachworkstationon whichaSAS/SHAREserveroruserwillexecute.

System Configuration for the TCP/IP Access Method

SAS/SHAREsoftwaresupportsMicrosoftsTCP/IPNetworkProtocol,whichisprovidedwith Windows. TodefineservernamesintheTCP/IP SERVICESfile,completethefollowingsteps: 1. LocatetheSERVICESfile. Thisfileislocatedunderthe\windowsor\winntdirectorypathsdependingonthespecific Windowsoperatingsystemandupgrademethod.Forexample,underamachineconfiguredwith aWindows2000operatingsystem,thedirectorypathisnamed <drive letter>:\winnt\system32\drivers\etc 2. Specifytheservernamesandportassignments. EachSAS/SHAREserverthatrunsonanetworkmustbedefinedasaserviceintheSERVICES file.Eachentryinthisfileassociatesaservicenamewiththeportnumberandprotocolusedby thatservice.AnentryforaSAS/SHAREserverhastheform: <server name> <port number>/<protocol> # <comments>

Theservernamemustbe18charactersinlength.Thefirstcharactermustbealetteror underscore.Theremainingsevencharacterscanincludeletters,digits,underscores,thedollar($) sign,ortheat(@)sign.Theportnumbermustbeabove1024,asanyportnumberequaltoorless than1024isreserved.TheprotocolmustalwaysbeTCP. AnentryforaserverwiththenameMKTSERVmightlooklikethis: mktserv 5000/tcp # SAS server for Marketing and Sales

TheservernameisspecifiedwiththeSERVER=optioninthePROC SERVERstatementinthe serversSASsessionandinthePROC OPERATEandLIBNAMEstatementsinuserandserver

Page 34

Configuration Guide for SAS 9.2 Foundation for Microsoft Windows

administratorprograms.Iftheservernameisnotdefined,youmustuse __port#,forexample, server= __5012. FormoreinformationabouttheoptionsusedwithPROC SERVERandPROC OPERATE procedures,pleaserefertotheSAS/SHARE9.2UsersGuide.

Client-Side Components
SAS/SHAREsoftwareincludesclientcomponentsthatareusedoutsideofyourSASinstallation. ThesecomponentsareavailablefromtheSAS9.2SoftwareDownloadsiteandaredescribedbelow:

SAS/SHARE Data Provider

TheSAS/SHAREdataproviderenablesyoutoaccess,update,andmanipulateSASdatausingOLE DBandADOcompliantapplicationsonWindowsplatforms.

SAS ODBC Driver

TheSASODBCdriverenablesyoutoaccess,update,andmanipulateSASdatafromODBC compliantapplicationsonWindowsplatforms.

SAS/SHARE Driver for JDBC

TheSAS/SHAREdriverforJDBCenablesyoutowriteapplets,applications,andservletsthataccess andupdateSASdata.TheJavaToolspackagethatincludestheSAS/SHAREdriverforJDBCalso includestheSAS/CONNECTdriverforJava.IfyouarewritingJavaprogramsusingtheseinterfaces, youmayalsowanttousethetunnelfeature.ThisoptionalfeaturecanbeusedwiththeJavaapplets youwritetosolvesomecommonconfigurationproblems.

SAS/SHARE SQL Library for C

TheSASSQLLibraryforCprovidesanapplicationprogramminginterface(API)thatenablesyour applicationstosendSQLqueriesandstatementsthroughaSAS/SHAREservertodataonremote hosts.

NLS Information
SitesthatdeveloporsupportinternationalapplicationsthatuseSAS/SHAREsoftwareshouldreferto thechapterPostInstallationInstructionsforNationalLanguageSupport(NLS)onpage4.

35

Chapter 11: Windows Performance Monitor and Event Log Support

SupportforWindowsPerformanceMonitorallowsadvancedusersandadministratorstoobserve someinternalcharacteristicsofSAS9.2Foundation.Thisfacilitatesperformanceanalysisand tuningofSAS9.2. Also,supportfortheEventLogallowsthetrackingofcriticalerrorsinSAS9.2Foundationand SASSetup. TheuseraccountinstallingSAS9.2Foundationmusthaveadministratorprivilegestoinstall thesefeatures,sononadministratorswillnotgetthesefeaturesbydefault.Theycanbeadded laterbyinvokingsetup.exe(foundunderthesasfolderontheSetupDisk)withthefollowing commandlines: ToinstalltheWindowsPerformanceMonitorandEventLog: setup perfmon TouninstalltheWindowsPerformanceMonitorandEventLog: setup uperfmon

Page 37

38

support.sas.com
SAS is the world leader in providing software and services that enable customers to transform data from all areas of their business into intelligence. SAS solutions help organizations make better, more informed decisions and maximize customer, supplier, and organizational relationships. For more than 30 years, SAS has been giving customers around the world The Power to Know. Visit us at www.sas.com.