User Guide for PowerCenter

Transcription

1 User Guide for PowerCenter Informatica PowerExchange for SAS (Version 9.6.1)

2 Informatica PowerExchange for SAS User Guide Version June 2014 Copyright Informatica Corporation. All rights reserved. This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S. and/or international Patents and other Patents Pending. Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS (a) and (a) (1995), DFARS (1)(ii) (OCT 1988), FAR (a) (1995), FAR , or FAR (ALT III), as applicable. The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing. Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica On Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and Informatica Master Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners. Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights reserved. Copyright Sun Microsystems. All rights reserved. Copyright RSA Security Inc. All Rights Reserved. Copyright Ordinal Technology Corp. All rights reserved.copyright Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright Meta Integration Technology, Inc. All rights reserved. Copyright Intalio. All rights reserved. Copyright Oracle. All rights reserved. Copyright Adobe Systems Incorporated. All rights reserved. Copyright DataArt, Inc. All rights reserved. Copyright ComponentSource. All rights reserved. Copyright Microsoft Corporation. All rights reserved. Copyright Rogue Wave Software, Inc. All rights reserved. Copyright Teradata Corporation. All rights reserved. Copyright Yahoo! Inc. All rights reserved. Copyright Glyph & Cog, LLC. All rights reserved. Copyright Thinkmap, Inc. All rights reserved. Copyright Clearpace Software Limited. All rights reserved. Copyright Information Builders, Inc. All rights reserved. Copyright OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo Communications, Inc. All rights reserved. Copyright International Organization for Standardization All rights reserved. Copyright ej-technologies GmbH. All rights reserved. Copyright Jaspersoft Corporation. All rights reserved. Copyright is International Business Machines Corporation. All rights reserved. Copyright yworks GmbH. All rights reserved. Copyright Lucent Technologies. All rights reserved. Copyright (c) University of Toronto. All rights reserved. Copyright Daniel Veillard. All rights reserved. Copyright Unicode, Inc. Copyright IBM Corp. All rights reserved. Copyright MicroQuill Software Publishing, Inc. All rights reserved. Copyright PassMark Software Pty Ltd. All rights reserved. Copyright LogiXML, Inc. All rights reserved. Copyright Lorenzi Davide, All rights reserved. Copyright Red Hat, Inc. All rights reserved. Copyright The Board of Trustees of the Leland Stanford Junior University. All rights reserved. Copyright EMC Corporation. All rights reserved. Copyright Flexera Software. All rights reserved. Copyright Jinfonet Software. All rights reserved. Copyright Apple Inc. All rights reserved. Copyright Telerik Inc. All rights reserved. Copyright BEA Systems. All rights reserved. Copyright PDFlib GmbH. All rights reserved. Copyright Orientation in Objects GmbH. All rights reserved. Copyright Tanuki Software, Ltd. All rights reserved. Copyright Ricebridge. All rights reserved. Copyright Sencha, Inc. All rights reserved. This product includes software developed by the Apache Software Foundation ( and/or other software which is licensed under various versions of the Apache License (the "License"). You may obtain a copy of these Licenses at Unless required by applicable law or agreed to in writing, software distributed under these Licenses is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the Licenses for the specific language governing permissions and limitations under the Licenses. This product includes software which was developed by Mozilla ( software copyright The JBoss Group, LLC, all rights reserved; software copyright by Bruno Lowagie and Paulo Soares and other software which is licensed under various versions of the GNU Lesser General Public License Agreement, which may be found at lgpl.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine, and Vanderbilt University, Copyright ( ) , all rights reserved. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and redistribution of this software is subject to terms available at and This product includes Curl software which is Copyright , Daniel Stenberg, <daniel@haxx.se>. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies. The product includes software copyright ( ) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at license.html. The product includes software copyright , The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at dojotoolkit.org/license. This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software are subject to terms available at This product includes software copyright Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at kawa/software-license.html. This product includes OSSP UUID software which is Copyright 2002 Ralf S. Engelschall, Copyright 2002 The OSSP Project Copyright 2002 Cable & Wireless Deutschland. Permissions and limitations regarding this software are subject to terms available at This product includes software developed by Boost ( or under the Boost software license. Permissions and limitations regarding this software are subject to terms available at / This product includes software copyright University of Cambridge. Permissions and limitations regarding this software are subject to terms available at This product includes software copyright 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at and at This product includes software licensed under the terms at license.html, asm.ow2.org/license.html, license.html, license.html, license-agreement; nanoxml.sourceforge.net/orig/copyright.html; copyright.html, iodbc/wiki/iodbc/license;

3 html/license.html#summary; /github.com/rantav/hector/blob/master/license; and This product includes software licensed under the Academic Free License ( the Common Development and Distribution License ( the Common Public License ( the Sun Binary Code License Agreement Supplemental License Terms, the BSD License ( the new BSD License ( the MIT License ( the Artistic License ( and the Initial Developer s Public License Version 1.0 ( This product includes software copyright Joe WaInes, XStream Committers. All rights reserved. Permissions and limitations regarding this software are subject to terms available at This product includes software developed by the Indiana University Extreme! Lab. For further information please visit This product includes software Copyright (c) 2013 Frank Balluffi and Markus Moeller. All rights reserved. Permissions and limitations regarding this software are subject to terms of the MIT license. This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775; 6,640,226; 6,789,096; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,243,110; 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422; 7,676,516; 7,720,842; 7,721,270; 7,774,791; 8,065,266; 8,150,803; 8,166,048; 8,166,071; 8,200,622; 8,224,873; 8,271,477; 8,327,419; 8,386,435; 8,392,460; 8,453,159; 8,458,230; and RE44,478, International Patents and other Patents Pending. DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice. NOTICES This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress Software Corporation ("DataDirect") which are subject to the following terms and conditions:1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS. Part Number: PWX-SSU

4

5 Table of Contents Preface ix Informatica Resources ix Informatica My Support Portal ix Informatica Documentation ix Informatica Web Site ix Informatica How-To Library ix Informatica Knowledge Base x Informatica Support YouTube Channel x Informatica Marketplace x Informatica Velocity x Informatica Global Customer Support x Chapter 1: Understanding PowerExchange for SAS Understanding PowerExchange for SAS Overview PowerExchange for SAS Architecture User Authentication Users User Administration Chapter 2: Installation and Configuration Installation and Configuration Overview Prerequisites Installing and Configuring PowerExchange for SAS Upgrading PowerExchange for SAS Installing PowerExchange for SAS Installing the Client Component Installing the Server Component Installing the Communication Component Configuring the Communication Component Configuring the Communication Component on Windows Configuring the Communication Component on UNIX Configuring the SAS Autoexec File Starting the Communication Component on Windows Starting the Communication Component on UNIX Registering the Plug-in Uninstalling PowerExchange for SAS Uninstalling from Windows Cleaning Up the SAS Environment Release Information New Features Table of Contents v

6 Chapter 3: Working with SAS Sources Creating a SAS Source Definition Creating a SAS Source Definition Manually Importing a SAS Source Definition Editing a SAS Source Definition Table Attributes Column Attributes Editing Source Qualifier Attributes Source Qualifier Attributes Joining tables in SAS Chapter 4: Working with SAS Targets Creating a SAS Target Definition Creating a SAS Target Definition Manually Importing a SAS Target Definition Editing a SAS Target Definition Table Attributes Column Attributes Configuring Indexes and Keys Configuring Indexes Configuring a Key Index Working with Field Attributes Configuring Load Types Full Load Append Load Update Else Insert Load Chapter 5: Working with SAS Sessions Configuring a SAS Relational Database Connection Editing a SAS Session Appendix A: SAS Datatype Reference SAS Datatypes and Formats Character Data Numeric Data Date, Time, and Datetime Data Appendix B: SPI Server Configuration Parameters Configuration Parameters Appendix C: Error Messages PowerCenter Client Messages Integration Service Messages Communication Component Messages vi Table of Contents

7 Index Table of Contents vii

8 viii Table of Contents

9 Preface This book describes the installation, configuration and use of PowerExchange for SAS. It is intended as reference for those maintaining the installation and those working with SAS sources and targets in PowerCenter as a developer of mappings and workflows. Informatica Resources Informatica My Support Portal As an Informatica customer, you can access the Informatica My Support Portal at The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica How-To Library, the Informatica Knowledge Base, Informatica Product Documentation, and access to the Informatica user community. Informatica Documentation The Informatica Documentation team takes every effort to create accurate, usable documentation. If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through at infa_documentation@informatica.com. We will use your feedback to improve our documentation. Let us know if we can contact you regarding your comments. The Documentation team updates documentation as needed. To get the latest documentation for your product, navigate to Product Documentation from Informatica Web Site You can access the Informatica corporate web site at The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services. Informatica How-To Library As an Informatica customer, you can access the Informatica How-To Library at The How-To Library is a collection of resources to help you learn more about Informatica products and features. It includes articles and interactive demonstrations that provide ix

10 solutions to common problems, compare features and behaviors, and guide you through performing specific real-world tasks. Informatica Knowledge Base As an Informatica customer, you can access the Informatica Knowledge Base at Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team through at Informatica Support YouTube Channel You can access the Informatica Support YouTube channel at The Informatica Support YouTube channel includes videos about solutions that guide you through performing specific tasks. If you have questions, comments, or ideas about the Informatica Support YouTube channel, contact the Support YouTube team through at or send a tweet Informatica Marketplace The Informatica Marketplace is a forum where developers and partners can share solutions that augment, extend, or enhance data integration implementations. By leveraging any of the hundreds of solutions available on the Marketplace, you can improve your productivity and speed up time to implementation on your projects. You can access Informatica Marketplace at Informatica Velocity You can access Informatica Velocity at Developed from the real-world experience of hundreds of data management projects, Informatica Velocity represents the collective knowledge of our consultants who have worked with organizations from around the world to plan, develop, deploy, and maintain successful data management solutions. If you have questions, comments, or ideas about Informatica Velocity, contact Informatica Professional Services at ips@informatica.com. Informatica Global Customer Support You can contact a Customer Support Center by telephone or through the Online Support. Online Support requires a user name and password. You can request a user name and password at The telephone numbers for Informatica Global Customer Support are available from the Informatica web site at x Preface

11 C HAPTER 1 Understanding PowerExchange for SAS This chapter includes the following topics: Understanding PowerExchange for SAS Overview, 1 PowerExchange for SAS Architecture, 1 User Authentication, 2 Understanding PowerExchange for SAS Overview PowerExchange for SAS is an extension of PowerCenter that facilitates the use of SAS Data Objects in your data integration processes. It integrates with the PowerCenter Client and the Integration Service. PowerExchange for SAS consists of the following components: Client component. Extends the PowerCenter Client capabilities to facilitate the registration and use of SAS Data Objects. Integration Service component. Extends the Integration Service so it can read from and write to SAS. Repository Service component. Extends the Repository Service so it can store SAS metadata. Communication component (SPI Server). Completes all the tasks requested from the machine that hosts the SAS Data Objects. PowerExchange for SAS Architecture The central component of the architecture for PowerExchange for SAS is the Communication component, also known as the SPI Server. The SPI Server is a multithreaded TCP/IP listener service. It handles requests from the PowerCenter Designer and from sessions started from the Integration Service. When you use the Designer to import a SAS source or a SAS target definition, the Client component requests the metadata from the SPI Server. The SPI Server starts an SPI session to retrieve the information from SAS, then passes this information to the Client component. When you save the SAS source or target, the Repository Service component saves it to the PowerCenter repository. 1

12 When you run a workflow that includes a SAS source or target, the Integration Service uses the Integration Service component to start a session with the SPI Server. The SPI Server accesses SAS data and passes it back to the Integration Service component for processing. The following figure shows the PowerCenter integration with SAS: User Authentication To connect to an SPI Server, user authentication is required. RELATED TOPICS: Configuring the Communication Component, 7 Users PowerExchange for SAS users include normal users and administrators. Normal user. Has permission to connect to the SPI Server to get table metadata when importing sources or targets with the Designer and to request to read or write SAS data. Administrator. Same as a normal user, but with permission to remotely stop the SPI Server. User Administration You can administer users locally. Use the SPI Server Configuration tool to add or remove a user, change a password, or change the type of a user. After installation, two users are defined with default passwords being equal to the user names. 2 Chapter 1: Understanding PowerExchange for SAS

13 C HAPTER 2 Installation and Configuration This chapter includes the following topics: Installation and Configuration Overview, 3 Installing PowerExchange for SAS, 4 Configuring the Communication Component, 7 Registering the Plug-in, 9 Uninstalling PowerExchange for SAS, 10 Release Information, 10 Installation and Configuration Overview This chapter provides information about upgrading, installing, and configuring PowerExchange for SAS. Prerequisites Before you upgrade or install PowerExchange for SAS, install or upgrade PowerCenter. Installing and Configuring PowerExchange for SAS To install and configure PowerExchange for SAS, complete the following steps: 1. Install PowerExchange for SAS. For more information, see Installing PowerExchange for SAS on page Configure the Communication component. For more information, see Configuring the Communication Component on page Register the plug-in. For more information, see Registering the Plug-in on page 9. Upgrading PowerExchange for SAS When you upgrade PowerExchange for SAS, complete the following tasks: 1. Uninstall the previous versions of PowerExchange for SAS. On Windows, make sure that the previous versions of PowerExchange for SAS are uninstalled. For more information about uninstalling 3

14 PowerExchange for SAS, see Uninstalling PowerExchange for SAS on page 10. On UNIX, you do not need to uninstall the previous version. 2. Install PowerExchange for SAS. For more information about installing PowerExchange for SAS, see Installing PowerExchange for SAS on page Configure the Communication component. For more information, see Configuring the Communication Component on page Upgrade the plug-in registration. For more information, see Registering the Plug-in on page 9. Installing PowerExchange for SAS When you install PowerExchange for SAS, you install the following components that allow PowerCenter to access SAS: Client component. Allows you to import definitions, create mappings, and create connection objects using the PowerCenter Client. Server component. Allows the Integration Service to run SAS sessions. SPI Server component. Allows the Designer and Integration Service to access the SAS host. You can use the Full Installation option to install all components at one time. Installing the Client Component Install the Client component on each PowerCenter Client machine where you want to create or access SAS metadata. To install the Client component on Windows: 1. Run install from the following location: <InstallerLocation>\install.bat 2. Follow the instructions in the installation wizard. The Client component is installed. Updating PowerCenter Online Help Files When you install the Client component, the following online help files are extracted to the PowerExchange for SAS installation directory: powercenterhelp.chm. The PowerCenter master help file that contains links to PowerExchange for SAS help. sas.chm. The online help file for PowerExchange for SAS. To complete the Client component installation, copy the PowerExchange for SAS online help files to the PowerCenter help directory. To update PowerCenter online help files: 1. On the PowerCenter Client machine, back up powercenterhelp.chm in the help directory in the following location: <PowerCenter Installation Directory>\clients\PowerCenterClient\client\bin\Help\en To back up the file, rename it to Original_powercenterhelp.chm. 2. Copy powercenterhelp.chm and sas.chm from the PowerExchange for SAS installation directory to the help directory on the PowerCenter Client machine. 4 Chapter 2: Installation and Configuration

15 Installing the Server Component If the Integration Service is configured to run on primary and backup nodes, install the Integration Service component on each node configured to run the Integration Service process. To install the Integration Service component on Windows: 1. Run setup.exe from one of the following locations: <DownloadLocation>\install.bat <DownloadLocation>\install.bat 2. Click Yes to install PowerExchange for SAS. The Welcome window introduces the PowerExchange for SAS installation. 3. Click Next. 4. Choose a directory to install the Integration Service component. Click Browse to find a directory or use the default directory. 5. Click Next. 6. Select Server Component and click Next. 7. Select a Start menu folder for program shortcuts and click Next. A confirmation page appears. 8. Click Install. The Integration Service Component Setup Wizard launches. 9. Click Next. 10. Review the license agreement and click Yes. The Integration Service component is installed. 11. Click Finish to exit the installer. The Integration Service component is installed. To install the Integration Service component on UNIX: Run the installation script from the installation CD and choose Install Server Plugin. Use the same login that you used to install the Integration Service. The Integration Service component is installed. Installing the Communication Component Install the Communication component, also known as the SPI Server, on the machine that runs the SAS environment that you want to connect to. The Communication component does not connect to the PowerCenter repository. The configuration is stored locally. Installing the Communication Component on Windows On Windows, the Communication component runs as a Windows service. To install the Communication component on Windows: 1. Run setup.exe from the following location: <DownloadLocation>\install.bat 2. Click Yes to install PowerExchange for SAS. Installing PowerExchange for SAS 5

16 The Welcome window introduces the PowerExchange for SAS installation. 3. Click Next. 4. Choose a directory to install the Communication component. Click Browse to find a directory or use the default directory. 5. Click Next. 6. Select SAS Communication Component and click Next. 7. Select a Start menu folder for program shortcuts and click Next. A confirmation page appears. 8. Click Install. The Communication Component Setup Wizard launches. 9. Click Next. 10. On the SPI Server Configuration page, enter the following information and click OK: Setting Port Number Log File Path SAS Pre Post Code. Application Path Working Directory Path Autoexec Name Description TCP/IP port number for the SPI Server listener process. Absolute path to the log file. Default is C:\PowerExchange for SAS Allow SAS exits: Yes or No. Default is No. Absolute path to the SAS executables. Default is C:\Program Files\SAS\sas.exe. SAS Working Environment directory path. Default is C:\testdata. Name of the autoexec file. Default is autoexec.sas. Click the Users button to add, edit, or delete users or to change user attributes. 11. Click OK. 12. Review the license agreement and click Yes. The Communication component is installed. Installing the Communication Component on UNIX Install the Communication component with a user account that has authorization to start SAS and to access the SAS data you want to read or write. PowerExchange for SAS uses this user account to access the SAS data. To install the Communication component on UNIX: 1. Run the installation script from the installation CD. 2. Choose a directory where you want to install the Communication component. 3. Follow the instructions and choose Install SAS Communication Component. The Communication component is installed. Post-install step for the Communication component on UNIX: The following libraries are installed with the spiserver binary: 6 Chapter 2: Installation and Configuration

17 libicuuc.<ext>.34 libicui18n.<ext>.34 libicudata.<ext>.34 where <ext> must be replaced by the shared library extension for the UNIX platform in question, for example libicuuc.so.34 for Linux. Bring these libraries in the system library path in one of the two following ways. 1. Add the SPI Server installation directory to the library search path: for example: export LD_LIBRARY_PATH=/home/PowerExchange ForSAS:$LD_LIBRARY_PATH 2. Move the library files to a directory already in the library search path, for example /usr/local/lib Configuring the Communication Component To configure the Communication component, use the configuration tool to maintain the configuration files. The configuration file is located in the Communication component installation directory. Configuring the Communication Component on Windows To start the configuration tool on Windows, use the SPI Server Configuration in the Start menu. Use SPI Server Configuration to configure the TCP/IP port where the SPI Server listens, the location of the SPI Server log file, and the SPI Server users and passwords. You must also configure the SAS environment. Working Directory Path: Enter the directory from which SAS runs. Autoexec Name: Enter the file name that SAS uses as its initialization file. You can use the initialization file to assign SAS Library Names or SAS Libnames that must be accessible by both the Designer and the PowerCenter sessions accessing SAS data. The following is an example of a SAS autoexec file: /* Sample SAS autoexec file */ LIBNAME whdata 'W:\data\saswhdata' ; LIBNAME oltp 'W:\data\sales\2008Q1' ; For a valid LIBNAME syntax and options, see the SAS documentation. User Administration on Windows You can add or remove users and change the user password or the user administrator property. To perform user administration on Windows: 1. In the configuration dialog, click Users. 2. In the user administration dialog, enter changes and click Close. Configuring the Communication Component 7

18 Configuring the Communication Component on UNIX To start the configuration tool on UNIX: 1. Enter./spiconfig on the shell prompt in the SPI Server installation directory. 2. Choose an option you want to change. The configuration tool prompts you for a new value. 3. Select Users to enter the user administration. Configuring the SAS Autoexec File Use the SAS autoexec file named autoexec.sas to configure the SAS environment. Session and User Identification The following PowerCenter session properties are passed to the environment where SAS runs: Name of the PowerCenter Integration Service that runs the corresponding workflow. Name of the PowerCenter connection used to access the SAS machine. Name of the SPI Server user who accesses the SAS environment. The values of these properties can thus be used for conditional initialization logic in the SAS autoexec script. The following system variables provide PowerCenter session property information to the SAS process: System Variable Available Description TBPC_PMSERVER_NAME server Name of the active Integration Service. TBPC_CONNECTION_NAME server Name of the Integration Service connection. TBPC_USER_NAME client/server Name of the connected SPI Server user. You can use the SAS function sysget() to retrieve system variables. For example: /* Store system variables into SAS macro variables: */ srvname = sysget("tbpc_pmserver_name"); conname = sysget("tbpc_connection_name"); /* Use the SAS macro variables to code logic: */ /* End of logic */ When the PowerCenter Designer initiates a connection to the SAS machine, the system variables unavailable for client connections contain no meaningful information. The system variable values default to _NONE_. Reading SAS Character Columns with Binary Zeros SAS allows binary zero bytes inside character columns. In PowerCenter, characters with binary zeros are not allowed. You can replace binary zeros with NULL characters before passing data to PowerCenter. To enable binary zeros to be replaced by NULL characters, assign the macro variable CHCKNLLS in the SAS autoexec file. Add the following line in the SAS autoexec file: %let CHCKNLLS=YES; 8 Chapter 2: Installation and Configuration

19 Removing Leading Spaces in Text Fields In PowerCenter Connect for SAS and earlier, leading spaces in text fields in a SAS source were removed. Also when writing to a SAS target, leading spaces were trimmed. You can add the following statement to the SAS autoexec file to remove leading spaces: %let TRMLDSPC=YES ; Starting the Communication Component on Windows On Windows, the SPI Server runs as a Windows service called Informatica SPI Server. You can start and stop this service in the following ways: Set Startup type to manual. Start and stop the service using the Windows Service Manager. Set Startup type to automatic. The service starts automatically when booting the Windows system. Use a Windows command line or script file. To start, enter the following command: net start Informatica SPI Server To stop, enter the following command: net stop Informatica SPI Server Starting the Communication Component on UNIX On UNIX, the SPI Server is an executable that runs as a daemon process. To start, go to the directory in which the SPI Server is installed and enter the following command: spiserver Check the SPI Server log file to make sure that the server started successfully. For more information about the location of the log file, see Configuring the Communication Component on page 7. To stop, enter the following command: spiserver stop <host> <portnumber> <administrator name> <password> You can build an initialization script to start the SPI Server automatically when the system boots. For more information, see your system documentation. Note: If the SPI Server does not shut down normally, it might not restart. If this occurs, remove the SPI Server lock file in the SPI Server working directory, then restart the SPI Server. Registering the Plug-in After you install PowerExchange for SAS, register the plug-in with the repository. If you are upgrading from a previous version, update the plug-in registration when you register the plug-in. A plug-in is an XML file that defines the functionality of PowerExchange for SAS. To register the plug-in, the repository must be running in exclusive mode. Use the Administration Console or the pmrep RegisterPlugin command to register the plug-in. The plug-in file for PowerExchange for SAS is pmsaspi.xml. When you install the Repository component, the installer copies pmsaspi.xml to the following directory: <PowerCenter Installation Directory>/server/bin/Plugin For more information about using the Administrator Tool to register a plug-in, see the Informatica Administrator Guide. For more information about the pmrep RegisterPlugin command, see the Informatica Command Reference. Registering the Plug-in 9

20 Note: If you do not have the correct privileges to register the plug-in, contact the user who manages the PowerCenter Repository Service. Uninstalling PowerExchange for SAS To uninstall PowerExchange for SAS, uninstall it from each machine where you installed the Client, Repository, or Integration Service components. Uninstalling from Windows To uninstall PowerExchange for SAS on Windows, uninstall the main files and each component of PowerExchange for SAS. To uninstall PowerExchange for SAS from Windows: From the Start menu, locate the PowerExchange for SAS program group and click the component you want to uninstall. Cleaning Up the SAS Environment When you uninstall PowerExchange for SAS, you may want to remove PowerExchange for SAS files from the SAS environment, such as SAS log files and the SAS autoexec file. Release Information New Features Reading from physical SAS file. It is now possible to read data directly from a SAS data file. 10 Chapter 2: Installation and Configuration

21 C HAPTER 3 Working with SAS Sources This chapter includes the following topics: Creating a SAS Source Definition, 11 Importing a SAS Source Definition, 11 Editing a SAS Source Definition, 12 Editing Source Qualifier Attributes, 13 Creating a SAS Source Definition You can use the Designer to create SAS source definitions. You can manually create the source definition or import a SAS data object as a source definition. Creating a SAS Source Definition Manually Use the following procedure to manually create a SAS source definition. To create a SAS source definition: 1. In the Source Analyzer, click Sources > Create. 2. Enter SAS as the Database Type. 3. Enter a name for the SAS source. 4. Click Create. A new SAS source definition appears in the Source Analyzer. Importing a SAS Source Definition When you import a SAS data object, the PowerCenter Client imports metadata from the SAS data dictionary that describes the data object. This metadata is used to register the data object as a source definition in the repository. 11

22 To import a SAS source definition: 1. In the Source Analyzer, click Sources > Import SAS Source. The Import SAS Source dialog appears. 2. Select the SAS Server you want to use and enter the user name and password. 3. Click Connect. You can add or change SAS server definitions by clicking Reconnect. 4. Expand the Library nodes to access tables and views, and select the table or view you want to import. 5. Click OK. To import a SAS source definition from a SAS file: 1. In the Source Analyzer, click Sources > Import SAS Source from file. The Import SAS Source from file dialog appears. 2. Navigate to the physical SAS file whose definition you want to import. 3. Click OK. Editing a SAS Source Definition You can edit a SAS source definition by using the source properties dialog. Table Attributes Most table attributes are accessed through the Rename button on the Table tab: Table name. Corresponds with the name of the table to read from SAS. Database name. Constitutes a logical grouping of data objects in the Designer. After importing a SAS table, the value of this attribute will be the name of the SAS Library you imported the table from. Business name. Corresponds with the SAS Label assigned to the table. The following attribute can be accessed through the Metadata Extensions tab: LibraryName. Holds the actual Library Name from which PowerCenter reads the SAS table. The LibraryName can be overruled in the session properties. Mapping parameters and variables can be used in the LibraryName attribute. Column Attributes You can access the following column attributes on the Columns tab: Column name. Corresponds with the name of the column in the SAS table. Precision and scale. Determines how the data is represented in the mapping and how it is transported from SAS. Datatype. Indicates how the Integration Service processes data in the mapping. 12 Chapter 3: Working with SAS Sources

23 Editing Source Qualifier Attributes You can edit source related attributes in the source qualifier by entering the properties dialog. Source Qualifier Attributes The following attributes can be accessed through the Metadata Extensions tab: WhereClause. Lets you enter a selection of rows from the SAS source. This where clause will result in a WHERE statement in SAS. For more information about where clauses in SAS, see the SAS documentation. PreSASCode and PostSASCode exits. Facilitates the invocation of a SAS Macro or a SAS %include statement to be executed just before or just after the reading of the SAS Source object. SPI Server must be configured to allow the execution of SAS exits. The SAS Macro to be invoked must be defined from the autoexec.sas file that is part of the SPI Server configuration. Mapping parameters and variables can be used in the WhereClause attribute, PreSASCode exit and PostSASCode exit. Joining tables in SAS You can join tables in SAS by connecting these tables to one source qualifier. The SAS System will perform the join. The attributes related to the table join are accessed through the Join tab in the source qualifier properties dialog: Join Type. Supported join types are the inner join, the full outer join, the left outer join and the right outer join. Note that only in the case of an inner join more than two tables can be joined. Join Condition. Lets you define the condition that defines the join to be executed. The join condition is entered using the join condition builder dialog that you can access by clicking the button next to the join condition field. For a full description of valid join conditions in SAS, see the SAS documentation. If no join condition is specified a join condition will be generated based on the existing primary key- foreign key relations between the sources as defined in the source analyzer. Left table. When Left Outer Join or Right Outer Join is selected as Join Type, this option lets you define which of the two participating tables is to be considered the Left table. Editing Source Qualifier Attributes 13

24 14 Chapter 3: Working with SAS Sources

25 C HAPTER 4 Working with SAS Targets This chapter includes the following topics: Creating a SAS Target Definition, 15 Editing a SAS Target Definition, 16 Configuring Indexes and Keys, 16 Working with Field Attributes, 17 Configuring Load Types, 17 Creating a SAS Target Definition You can manually create a SAS target definition or import a SAS Data Object as a target definition. Creating a SAS Target Definition Manually Use the following procedure to manually create a SAS target definition. To create a SAS target definition: 1. In the Target Designer, click Targets > Create. 2. Enter SAS as the database type. 3. Enter a name for the SAS target. 4. Click Create. A new SAS target definition appears in the Target Designer. Importing a SAS Target Definition When you import a SAS data object, the PowerCenter Client imports metadata from the SAS data dictionary that describes the data object. This metadata is used to register the data object as a target definition in the repository. To import a SAS target definition: 1. In the Target Designer, click Targets > Import SAS Target. The Import SAS Target dialog appears. 2. Select the SAS Server you want to use and enter the user name and password. 15

26 3. Click Connect. To add or change SAS server definitions, click Reconnect. 4. Expand the library nodes to access tables and views, and select the table or view you want to import. 5. Click OK. Editing a SAS Target Definition You can edit a SAS target by using the target properties dialog. Table Attributes Use the Rename button on the Table tab to access the following table attributes: Table name. Corresponds with the name of the table to read from SAS. Database name. Constitutes a logical grouping of data objects in the Designer. After importing a SAS table, the value of this attribute will be the name of the SAS Library you imported the table from. Business name. Corresponds with the SAS label assigned to the table. Use the Metadata Extensions tab to access the following attributes: LibraryName. Holds the actual library name in which PowerCenter writes the SAS table. SASCode and PostSASCode exits. Defines a SAS macro or a SAS %include statement to be run just before or just after the processing of the SAS source object. SPI Server must be configured to allow the execution of SAS exits. The macro to be invoked must be defined from the autoexec.sas file that is part of the SPI Server configuration. Mapping parameters and variables can be used in the LibraryName and Whereclause attributes as well as PreSASCode and PostSASCode exits. Column Attributes You can access the following column attributes on the Columns tab: Column name. Corresponds with the name of the column in the SAS table. Precision and scale. Determine how the data is represented in the mapping, and also how the data is transported from SAS. Datatype. Indicates how the Integration Service processes data in the mapping. Configuring Indexes and Keys You can create and configure indexes and key indexes for SAS target definitions. 16 Chapter 4: Working with SAS Targets