Sagent Data Flow Solution. Version 6.8 INSTALLATION GUIDE

Transcription

1 Sagent Data Flow Solution Version 6.8 INSTALLATION GUIDE

2

3 Information in this document is subject to change without notice and does not represent a commitment on the part of the vendor or its representatives. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, without the written permission of Pitney Bowes Software Inc., One Global View, Troy, New York Pitney Bowes Software Inc. All rights reserved. MapInfo, Group 1 Software, and Sagent Data Flow Solution are trademarks of Pitney Bowes Software Inc. Information Studio and Sagent are registered trademarks of Pitney Bowes Software, Inc. The Sagent Logo, Sagent Design Studio, Flashcube, Data Flow, and StarMart are trademarks of Pitney Bowes Software, Inc. All other trademarks are property of their respective companies. All other marks and trademarks are property of their respective holders. Any provisions of this license related to ICU that differ from the IBM Public License 1.0 are offered by Pitney Bowes Software, Inc. alone and not by any other party. The Source Code of the ICU program is available from Pitney Bowes Software, Inc. upon written request. Further information regarding the ICU Program may be found at: Portions Copyright 1996, Microsoft Corporation. All rights reserved. This software uses Xerces-J Copyright 1999 The Apache Software Foundation. All rights reserved. Contact information for all Pitney Bowes Software Inc. offices is located at: April 2012

4

5 Table of Contents Chapter 1: Introduction About Sagent Solution Installations About Sagent Solution Upgrades How to Proceed Downloading Sagent Solution from the Group 1 Website Chapter 2: System Requirements Server System Requirements for UNIX Server System Requirements for Windows DirectLink Server System Requirements Sagent Client System Requirements DirectLink Client System Requirements Supported Databases and Connectivity Software Databases Supported with Sagent on UNIX Databases Supported with Sagent on Windows Chapter 3: UNIX Server Installation Before Installing UNIX Server Software To Upgrade UNIX Server Software Running the Installation for a New Installation Finishing the Installation Process Updating the Data Flow Service License Key Upgrading a Patch on the UNIX Installation of Sagent Uninstalling Sagent from UNIX Servers Installation Command Parameters Chapter 4: Windows Installation Installation details for Version bit version Introduction Before Installing Sagent Solution Software for 64-bit Before Upgrading Sagent Solution Software for 64-bit Sagent Solution Setup for 64-bit Updating the Data Flow Server License Key for 64-bit Unattended Client Setup for 64-bit Installing Sagent Language Packs Installation details for Version bit version Introduction Before Installing Sagent Solution Software for 32-bit Before Upgrading Sagent Solution Software for 32-bit Sagent Data Flow Solution v6.8 5 Installation Guide

6 Sagent Solution Setup for 32-bit Updating the Data Flow Service License Key for 32-bit Unattended Client Setup for 32-bit Installing Sagent Language Packs Uninstalling Sagent from Windows Servers Uninstalling WebLink Client Controls Chapter 5: Configuration Instructions Configuration Details for 64-bit version Configuring Oracle on Windows 2003 (32/64-bit), XP Configuring Microsoft DB-Library Connections Configuring WebLink CAB File Update Options Configuring UNIX for the Data Flow Service Configuring Oracle on UNIX Configuring DB2 Clients Configuring UNIX Virtual X Server Configuring the WebLink Server for Solaris National Language Support Configuration Configuration Details for 32-bit versions Configuring Oracle on Windows 2003, XP Configuring the ODBC Driver for Microsoft SQL Server Configuring Microsoft DB-Library Connections Configuring Sybase CT-Lib Configuring WebLink CAB File Update Options Red Brick Configuration Enabling Scheduled Plans on Windows Chapter 6: Appendix Compatibility Matrix for Version Database Support Matrix Unsupported Transforms WebLink Support Matrix Platform, Hardware, and OS Recommendations DFS Tuning Parameters Index Sagent Data Flow Solution v6.8 6 Installation Guide

7 Introduction 1 This chapter includes the following topics: About Sagent Solution Installations About Sagent Solution Upgrades How to Proceed Downloading Sagent Solution from the Group 1 Website

8 Chapter 1: Introduction About Sagent Solution Installations About Sagent Solution Installations This manual describes how to install The Sagent Solution. It is intended for system administrators and professional services personnel who are responsible for installing Sagent. These instructions assume you are familiar with the Microsoft Windows and UNIX operating systems. The following summarizes the content of each section of this manual: Chapter 2, System Requirements, lists the system requirements for Sagent software including server, client, and databases. Chapter 3, UNIX Server Installation, describes the procedure for installing Sagent server software on UNIX. Chapter 4, Windows Installation, describes the procedure for installing Sagent software on Windows. Chapter 5, Configuration Instructions, describes the procedure for configuring servers and Sagent WebLink. Sagent Data Flow Solution v6.8 8 Installation Guide

9 Chapter 1: Introduction About Sagent Solution Upgrades About Sagent Solution Upgrades Sagent server, repository, and client software must pertain to the same version. You cannot upgrade one without upgrading the others. If you are upgrading from a previous version of Sagent Solution, you must upgrade server components before upgrading client components. Perform the following tasks to upgrade your Sagent Solution components: Upgrade all Sagent servers on UNIX or on Windows. Upgrade the Sagent repository (users of Sagent Data Flow version 6.0 or later can directly upgrade to Version 6.8). Upgrade the Add-on Transforms Upgrade all Sagent client software. Install the latest patch set from Group1 website. You must upgrade your repository from a Windows machine that has connections to all data sources. It is not possible to update or install the repository from a UNIX server. During the installation, you are asked whether to upgrade your current repository or build a new one. Building a new repository deletes all definitions stored in the current one, so only choose a new repository if you are installing for the first time or you are installing to a clean database. Upgrade your repository to retain existing definitions rather than build a new one. Alternatively, you can use the Sagent Repository utilities to copy data from your old repository to your new repository. For more information, see the Sagent Administrator s Guide and the Sagent Utilities Guide. For more information about upgrades, see To Upgrade UNIX Server Software on page 33 or Before Upgrading Sagent Solution Software for 64-bit on page 52. Sagent Data Flow Solution v6.8 9 Installation Guide

10 Chapter 1: Introduction How to Proceed How to Proceed Sagent Solution includes several server and client components. All components are supported on Windows. The Data Flow Service is supported on Solaris, AIX, HP-UX, and Windows. Sagent WebLink is supported on Solaris and Windows. Depending on your configuration, you can install all server software components on one server or on multiple servers. Use the following steps to install Sagent Solution: 1. Review the system requirements for UNIX servers, Windows servers, and Windows client systems. For more information, see Chapter 2, System Requirements, 2. Ensure that database servers, web servers, and other software required for the Sagent Solution have been installed and configured. For more information, see Chapter 2, Supported Databases and Connectivity Software. 3. If you are upgrading from a previous release of Sagent Solution and have customized your registry settings and repository, take a backup of your registry and repository. 4. If you are upgrading from versions prior to version 5.0.1, uninstall the previous release of Sagent Solution. See Before Upgrading Sagent Solution Software for 64-bit on page 52 for more upgrade information. 5. Install one or more of the following components on your UNIX or Windows servers. The Data Flow Service is supported on Solaris, AIX, HP-UX, and Windows. Sagent WebLink is supported on Solaris and Windows. Data Flow Service WebLink Server Build or Upgrade Repository Sagent Admin Design Studio Information Studio DirectLink Analytical Calculator Forecaster Transform Sagent Samples MetaLens Reports Transform SDK Centrus Transforms Sagent Language Pack Web Service WebService Data Sink 6. Configure the Sagent Solution and other server software. For more information, see Chapter 5, Configuration Instructions. 7. Apply the latest patches from the Group1 website. Sagent Data Flow Solution v Installation Guide

11 Chapter 1: Introduction How to Proceed 8. Install one or more of the following client components on Windows client machines: Design Studio Information Studio Sagent Admin Analytical Calculator Forecaster Transform Centrus Transforms DirectLink For more information, see Chapter 3, UNIX Server Installation and Chapter 4, Windows Installation. For more information, see Installing a Designer Workstation and Sagent Admin on page 79 and Installing an End-User Workstation on page 81. Table 1 provides a list of topics about installing each component in the Sagent Solution. Table 1:Sagent Solution List of Topics by Component Component Platform Sections Sagent Data Flow Service, WebLink Server and Repository Database Sagent WebLink Server Application UNIX Chapter 3, UNIX Server Installation Windows Chapter 4, Windows Installation Enabling Scheduled Plans on Windows on page 126 UNIX Configuring the WebLink Server for Solaris on page 109 Windows Configuring WebLink CAB File Update Options on page 124 Sagent Repository Database Windows/UN IX Sagent Repository Information on page 84 Sagent Samples Repository on page 85 Sagent MetaLens Reports Repository on page 62 Sagent Admin User s Guide Sagent Data Flow Solution v Installation Guide

12 Chapter 1: Introduction Downloading Sagent Solution from the Group 1 Website Downloading Sagent Solution from the Group 1 Website This section explains how to download your licensed Sagent Solution from the Group 1 website. All the installation activities that can be performed using the Sagent installation CD can also performed using the Group 1 website. To download Sagent Solution: 1. Enter the following URL in your browser window: Log in to the website to view the technical services offered. Figure 1: Group 1 Technical Services web page 2. Type your User ID and Password in the respective fields. The password is case-sensitive. After logging in, the Technical Services link gets enabled in the left pane of the Customer Services page. If you do not have a User ID and Password, click Do you need your User ID and password? in the USEFUL INFORMATION section. The Request Support ID/ Password page opens. Follow the instructions provided on the page to obtain your User ID and Password. 3. Click My Products under Technical Services. The My Products page displays. You can view the Sagent product licenses you own. Sagent Data Flow Solution v Installation Guide

13 Chapter 1: Introduction Downloading Sagent Solution from the Group 1 Website 4. Select the relevant product from the Available Products list. For example, Data Flow Premium, Data Flow Standard Bundle, and so on, depending on the product licenses you have purchased. You can also download the relevant Sagent Language Packages from this list. Figure 2: Customer Services - My Data Flow Standard Bundle Purchases 5. In the table, click View Available Downloads in the DETAILS column for the relevant product. This opens the page shown in Figure 3, which lists the products associated with the product licenses you have purchased. You can also view and download Products, Product Updates, Databases, Sub Components, and so on. 6. Navigate down to the Sub Components table on the page. This table lists the sub-components of the product you have purchased. Sagent Data Flow Solution v Installation Guide

14 Chapter 1: Introduction Downloading Sagent Solution from the Group 1 Website Figure 3: Customer Services - Products and Sub Components details page 7. Under the Sub Components table, click View Available Downloads in the DETAILS column for the relevant sub-component. The download of the selected sub-component begins. Sagent Data Flow Solution v Installation Guide

15 System Requirements 2 This chapter includes the following topics: Server System Requirements for UNIX Server System Requirements for Windows Sagent Client System Requirements Supported Databases and Connectivity Software

16 Chapter 2: System Requirements Server System Requirements for UNIX Server System Requirements for UNIX Before installing the Sagent Solution on a UNIX server, confirm that your server systems meet the minimum requirements listed in: Table 2: Server System Requirements for Solaris Table 3: Server System Requirements for AIX Table 4: Server System Requirements for HP-UX Itanium Version 10 of Solaris SPARC, UltraSPARC Table 2:Server System Requirements for Solaris 300 MHz SPARC processor 1 GB of available disk space to host the Data Flow Service server applications on a single server 500 MB of temporary disk space during the installation 2 GB of RAM 40 MB of disk space, 100 MB recommended, allocated for the Repository database 20 MB of disk space, 50 MB recommended, allocated for the Repository database log X server environment (or virtual X server) with the DISPLAY environment variable set Write-access to the cron table for scheduling On the Sagent Server machine, database client libraries to connect to any database used as sources or targets Sun Java System Web Server 7.0 (for WebLink only) Download the Web server from the Oracle website at HTTP 1.1 or later (for WebLink only) If you are using iplanet Web Server 7, install the JDK bundled with iplanet 7 and see Configuring the WebLink Server for Solaris on page 109 for instructions about configuring iplanet Web Server to operate with WebLink. To run the Sagent WebLink sample application, your server must support JSP files. The number of transactions, amount of data, and the type of analyses that you plan to do affect the required amount of disk space, memory, and processing power. Take your planned use of the Sagent Solution into consideration when evaluating your minimum server system requirements. In the absence of any generic guidelines, please consult your professional services. Table 3:Server System Requirements for AIX AIX 5.3 AIX 6.1 os level MHz PowerPC processor Sagent Data Flow Solution v Installation Guide

17 Chapter 2: System Requirements Server System Requirements for UNIX 1 GB of available disk space to host the Data Flow Service server applications on a single server 500 MB of temporary disk space during the installation 2 GB of RAM 40 MB of disk space, 100 MB recommended, allocated for the Repository database 20 MB of disk space, 50 MB recommended, allocated for the Repository database log X server environment (or virtual X server) with the DISPLAY environment variable set Write-access to the cron table for scheduling On the Sagent Server machine, database client libraries to connect to any database used as sources or targets Table 4:Server System Requirements for HP-UX Itanium HP-UX Itanium 11i version 2.0 or higher Gold Applications Patches for HP-UX 11i, December 2002 or higher Gold Base Patches for HP-UX 11i, December 2002 or higher We no longer support HP-UX PA-RISC 750 MHz PA 8700 on PA-RISC processor or higher 1 GB of available disk space to host the Data Flow Service server applications on a single server 500 MB of temporary disk space during the installation 2 GB of RAM Table 3:Server System Requirements for AIX (continued) 40 MB of disk space, 100 MB recommended, allocated for the Repository database 20 MB of disk space, 50 MB recommended, allocated for the Repository database log X server environment (or virtual X server) with the DISPLAY environment variable set Write-access to the cron table for scheduling On the Sagent Server machine, database client libraries to connect to any database used as sources or targets Sagent Data Flow Solution v Installation Guide

18 Server System Requirements for Windows Chapter 2: System Requirements Server System Requirements for Windows Before installing Sagent Data Flow Service or WebLink on a Windows server, confirm that your system meets the minimum requirements listed in Table 5 (for a 32-bit server) and Table 6 (for a 64- bit server). Table 5:Server System Requirements for Windows (32-bit server) Microsoft Windows 2003 with Service Pack 1, Service Pack 2 or Release 2 (R2). Microsoft Windows Server 2008 (x86) SP2 Enterprise Edition for Sagent Server. Note: Windows 2003 Web Edition is not supported as a Data Flow Service platform. Pentium processor 2 GB of RAM 500 MB of available disk space 100 MB of disk space allocated for the Repository database 20 MB of disk space, 50 MB recommended, allocated for the Repository database log TCP/IP or Named Pipes network protocol software. Sagent recommends TCP/IP On the Sagent Server machine, database client libraries to connect to any database used as sources or targets One of the following Web servers installed: Microsoft Internet Information Server (IIS) 6.0 or 7.0 Contact Microsoft support for additional Web Server settings, if you are migrating from IIS 5.x to 6.0. If you will be installing WebLink, Microsoft Internet Explorer 6.0, 7.0 and 8.0, or Netscape 8.x must be installed before installing WebLink. Table 6:Server System Requirements for Windows (64-bit server) Microsoft Windows 2003 Release 2 (R2) Enterprise x64 (64-Bit) Microsoft Windows Server 2008 (x64) SP2 Standard Edition Microsoft Windows Server 2008 (x64) Enterprise Edition Microsoft Windows Server 2008 R2 with SP1 Intel Processor 8 GB of RAM(Recommended) 12 GB Swap Space(Min) 500 MB of available disk space 100 MB of disk space allocated for the Repository database 20 MB of disk space, 50 MB recommended, allocated for the Repository database log TCP/IP or Named Pipes network protocol software. Sagent recommends TCP/IP Sagent Data Flow Solution v Installation Guide

19 Chapter 2: System Requirements Server System Requirements for Windows On the Sagent Server machine, database client libraries to connect to any database used as sources or targets Microsoft Internet Information Server (IIS) 6.0, 7.0 or 7.5: The Web Server can be on the same machine or on a different Windows Server. The Web Server is required only if you are installing Weblink. The number of transactions, amount of data, and the type of analyses that you plan to do affect the required amount of disk space, memory, and processing power. Take your planned use of the Sagent Solution into consideration when evaluating your minimum server system requirements. In order for the date, time, currency, and number internationalization display features to work correctly, make sure that all WebLink servers, Data Flow Services and Sagent clients are set to use the same locale. The locale settings are set by selecting a language from Standards and formats and by clicking Apply in Regional Options after selecting the Regional and Language option from the Control Panel. Sagent Data Flow Solution v Installation Guide

20 DirectLink Server System Requirements Chapter 2: System Requirements DirectLink Server System Requirements DirectLink server requirements depend on the number of transactions, amount of data, and type of analyses affect the requirements for disk space, memory, and processing power. The minimum system configuration is listed in Table 7. Table 7:DirectLink Server Requirements Microsoft Windows 2003 Release 2 (R2) Pentium processor 1 GB of RAM 40 MB of available disk space At least 150 MB of additional disk space allocated for the repository database in addition to your original allocation for the Sagent Repository. At least 50 MB of additional disk space allocated for the Repository database logs On the Sagent server machine, database client libraries to connect to any database accessible from Information Studio or Design Studio The appropriate client connectivity software for connection to the SAP database, such as SQL Net for Oracle You must install the Sagent Load Server or the Premium Data Flow Server. Sagent Data Flow Solution v Installation Guide

21 Chapter 2: System Requirements Sagent Client System Requirements Sagent Client System Requirements This section provides the system requirements for Sagent clients. Before installing the Sagent Solution, confirm that your client system meets the minimum requirements in Table 8. Table 8:Sagent Client System Requirements Microsoft Windows XP SP2, SP3 or Windows 2003 SP1, SP2 or Release 2 (R2) Microsoft Windows Vista. Microsoft Windows 7 Pentium processor 1 GB of RAM 500 MB of available disk space TCP/IP or Named Pipes client software to connect to the Sagent Server. Sagent recommends TCP/IP. Database client libraries for the Repository database. Design Studio also requires the client libraries for each source and target database. Client systems must be able to connect to the database server before you install Sagent software. Therefore, you must install the client libraries for your vendor s database software on each client system. (Optional) Microsoft Office XP, 2003, 2007 or 2010 for using Excel Transforms. (Optional) One of the following web browsers: If you are using Sagent WebLink, you need Microsoft Internet Explorer 6.0, 7.0 or 8.0 for Windows to display ActiveX objects, such as the Grid, Crosstab, and Reports. You can use other browsers, but in all other browsers, Plan and Snap results display in an HTML table format. In order for the date, time, currency, and number internationalization display features to work correctly, make sure that all WebLink servers, Data Flow Services and Sagent clients are set to use the same locale. The locale settings are set by selecting a language from Standards and formats and by clicking Apply in Regional Options after selecting the Regional and Language option from the Control Panel. Sagent Data Flow Solution v Installation Guide

22 Chapter 2: System Requirements DirectLink Client System Requirements DirectLink Client System Requirements Install the client libraries for your vendor s database software on each client system before you install Sagent software to connect to the database server. The minimum client configuration is listed in Table 9. Table 9:DirectLink Client Requirements Microsoft Windows XP SP2 or Windows 2003 SP1, SP2 or Release 2 (R2) Microsoft Windows Vista. Microsoft Windows 7 Pentium processor 512 MB of RAM 30 MB of available disk space Database client libraries for the Repository database and for each SAP database accessed by Design Studio. You must install Sagent Design Studio on the same machine as the DirectLink client. Sagent Data Flow Solution v Installation Guide

23 Supported Databases and Connectivity Software Chapter 2: System Requirements Supported Databases and Connectivity Software In addition to the software on your Sagent installation media, you need compatible database server and connectivity software. Sagent supports a variety of database vendors for the Sagent Repository and for source and target databases. See the following sections for tables of supported vendors: Databases Supported with Sagent on UNIX Databases Supported with Sagent on Windows These tables contain product versions and required client library packages. Client libraries must provide 32-bit support. For information about version compatibility between client libraries and RDBMS server software, see your database vendor documentation. Sagent Data Flow Solution v Installation Guide

24 Databases Supported with Sagent on UNIX Chapter 2: System Requirements Supported Databases and Connectivity Software Sagent supports the databases listed in Table 10. Some databases are not supported for all Sagent functions. Table 10 indicates which database vendors and products are compatible for Repository, source, and target databases. Save to Table and Batch Loaders are used to load target databases. Table 10: Database Clients Supported with Sagent on UNIX also includes support for StarViews and Snap databases. Data Flow Service access to the repository is only for plan tracking. Table 10:Database Clients Supported with Sagent on UNIX RDBMS Vendor Versions Microsoft SQL Server with database version (All via DataDirect Connect ODBC 3.60) Oracle 1 Sybase 2 Red Brick (Informix Red Brick Decision Server) IBM DB2 Universal Database Native Connection for 10g for 10g R g Oracle Database client is used for connecting to Oracle Database server as Oracle client is specific to Windows Server Native Connection System ASE Sybase ASE v6.3.0 via ODBC driver or later with DataDirect Connect ODBC 3.60 Native Connection DB DB Source Save to Table Batch Loader Repository StarView Snap X X X X X X X X X X X X X X X X X X X X X X X Sagent Data Flow Solution v Installation Guide

25 Chapter 2: System Requirements Supported Databases and Connectivity Software Table 10:Database Clients Supported with Sagent on UNIX(continued) Netezza Netezza v4.6 Netezza v5.0 Netezza v Text Files RDBMS Vendor Versions Native Connection Flat File and Delimited Text File Transforms Source Save to Table Batch Loader Repository StarView Snap X X X 1 Depending on your version of Oracle, you may need fixes from Oracle or other workarounds in order to run the Oracle Batch Loader. See Configuring Oracle on UNIX on page 101 for more information.for HP-UX, the Oracle Release 2 Patch Set 4 Version for HP-UX is required for Oracle 9i. 2. For DB2 Server and Sybase ASE, you must change the code page size to 16MB. 3. Sagent will not support any database versions that are no longer supported by the database vendor. Sagent Data Flow Solution v Installation Guide

26 Databases Supported with Sagent on Windows Chapter 2: System Requirements Supported Databases and Connectivity Software Table 11: Database Clients Supported with Sagent on Windows (32-bit) provides the database clients supported by 32-bit version of Sagent.Table 12: Database Clients Supported with Sagent on Windows (64-bit) gives the database clients supported by 64-bit version of Sagent. Data Flow Service access to the repository is only for plan tracking.. Table 11:Database Clients Supported with Sagent on Windows (32-bit) RDBMS Vendor Microsoft SQL Server Versions Native Connection with database version SQL Server 2005 Standard Edition SQL Server 2008 SP1 Enterprise Edition SQL Server 2008 R2 ODBC Connection with database version SQL Server 2005 Standard Edition SQL Server 2008 SP1 Enterprise Edition SQL Server 2008 R2 Source Save to Table Batch Loader Repository StarView Snap Client Library Package X X X X X X The Batch Loader is supported on versions of MS SQL Server that support the older BCP API. X X Sagent Data Flow Solution v Installation Guide

27 Chapter 2: System Requirements Supported Databases and Connectivity Software Table 11:Database Clients Supported with Sagent on Windows (32-bit)(continued) RDBMS Vendor Oracle 1 Versions Native Connection for 10g for 10g R g 11g R2 Oracle Database client is used for connecting to Oracle Database server as Oracle client is specific to Windows Server Source Save to Table Batch Loader Repository StarView Snap X X X X X X Client Library Package Sybase 2 Informix IBM DB2 Universal Database - Workgroup, Enterprise, and Enterprise Extended Editions Red Brick (Informix Red Brick Decision Server) Native Connection System ASE Sybase 15 ASE Native Connection 9.x 10.0 Dynamic Server ODBC Connection 7.x using Intersolv ODBC v2.12+ Native Connection ODBC Connection IBM DB2 ODBC driver Native Connection 6.30 TC6 ODBC Connection Red Brick ODBC Driver v X X X X X X OpenClient for Windows X X X X X X X X X X X X X X X X X X X X X Red Brick provides an ODBC connection as the native connection type, starting with Sagent Data Flow Solution v Installation Guide

28 Chapter 2: System Requirements Supported Databases and Connectivity Software Table 11:Database Clients Supported with Sagent on Windows (32-bit)(continued) RDBMS Vendor Microsoft Access ODBC Connection Office 2003, 2007 and 2010 using Microsoft Access Driver Netezza Netezza v4.6 Netezza v5.0 Netezza v Oh-Pa 1/3 Oh-Pa 1/3 IE X Text Files Versions Native Connection Flat File and Delimited Text File Transforms ODBC Connection Available using Microsoft ODBC drivers Source Save to Table Batch Loader Repository StarView Snap X X X X X Client Library Package 1 The Oracle SQL*Loader is not capable of doing Fast Loads against databases running on a different operating system than the Sagent Server. 2. For DB2 Server and Sybase ASE, you must change the code page size to 16MB. Sagent will not support any database versions that are no longer supported by the database vendor. Sagent Data Flow Solution v Installation Guide

29 Chapter 2: System Requirements Supported Databases and Connectivity Software Table 12:Database Clients Supported with Sagent on Windows (64-bit) RDBMS Vendor Microsoft SQL Server Oracle 1 IBM DB2 Universal Database - Workgroup, Enterprise, and Enterprise Extended Editions Sybase Versions Native Connection: 2000 SP4 (32- Bit) 2005 with SP2 or SP3 SQL Server 2008 SP1 Enterprise Edition SQL Server 2008 R2 ODBC Connection bit 2005 with database version bit and 64-bit Native Connection 9i (32/ 64-Bit) 10g (32/ 64-Bit) 11g R2 Source Save to Table Batch Loader Repository StarView Snap Client Library Package X X X X X X The Batch Loader is supported on versions of MS SQL Server that support the older BCP API. X X X X X X X X 9.1 (32/ 64-Bit) X X X X X X ODBC Connection IBM DB2 ODBC driver Native Connection: System 12.5 ASE (32-Bit) Sybase 15 ASE (32/ 64-Bit) Netezza Netezza v4.6 Netezza v5.0 Netezza v X X X X X X X X OpenClient for Windows. X Sagent Data Flow Solution v Installation Guide

30 Chapter 2: System Requirements Supported Databases and Connectivity Software RDBMS Vendor Versions Source Save to Table Batch Loader Repository StarView Snap Client Library Package Text Files Native Connection Flat File and Delimited Text File Transforms X X ODBC Connection Available using Microsoft ODBC drivers X 1 The Oracle SQL*Loader is not capable of doing Fast Loads against databases running on a different operating system other than the Sagent Server. Sagent will not support any database versions that are no longer supported by the database vendor. Sagent Data Flow Solution v Installation Guide

31 UNIX Server Installation 3 This chapter describes how to install the Sagent server software on UNIX systems. This chapter includes the following topics: Before Installing UNIX Server Software To Upgrade UNIX Server Software Running the Installation for a New Installation Finishing the Installation Process Updating the Data Flow Service License Key Upgrading a Patch on the UNIX Installation of Sagent Uninstalling Sagent from UNIX Servers Installation Command Parameters

32 Chapter 3: UNIX Server Installation Before Installing UNIX Server Software Before Installing UNIX Server Software These prerequisites apply to a first-time installation of the Sagent Solution. If you are upgrading the Sagent Solution, see To Upgrade UNIX Server Software on page 33. Before installing server software, complete the following prerequisites: 1. Note your Sagent license key, which is printed on the Sagent Solution packing list. 2. If you are installing WebLink, confirm that you have the root password so that you can run the Sagent installation program. The root password is required for WebLink installations. Installing Sagent software over NFS mounts is not recommended. NFS installations may restrict root access, so installations to an NFS-mounted directory may not succeed. 3. Confirm that your system meets the requirements listed in Chapter 2, System Requirements 4. Create a UNIX user ID for Sagent Solution that uses Korn or Bourne shell as the default shell. The suggested user ID is sagent. If you are installing WebLink, create a group for your WebLink administrators. 5. If you are installing WebLink on Solaris, create a Web server instance within iplanet Web Server 7 to host WebLink, using the user ID that you created in step 4. Specify the following: Server Name Server Port Server Identifier Server User ID Docroot Location The server user ID must match the Data Flow Service user ID if WebLink is installed on the same machine. Never run Regedit or other Sagent processes as root. Running a Sagent process as root can cause your installation to become unusable. Sagent Data Flow Solution v Installation Guide

33 Chapter 3: UNIX Server Installation To Upgrade UNIX Server Software To Upgrade UNIX Server Software If you are upgrading to Version 6.8 from an older version, you must first uninstall the older version and then do a fresh installation of Version Uninsntall the existing version as described in Uninstalling Sagent from UNIX Servers on page Install the new version as described in Running the Installation for a New Installation on page 34. Sagent Data Flow Solution v Installation Guide

34 Running the Installation for a New Installation Chapter 3: UNIX Server Installation Running the Installation for a New Installation The installation installs or upgrades the server components for the Sagent Solution. You can install the Data Flow Service and WebLink server applications on different servers by running the installation application on each server. To exit the installation at any time, press Ctrl + c. For information on the optional installation script parameters, see Installation Command Parameters on page 42. To install Sagent server applications on a UNIX system: 1. If you are installing WebLink server, log in with the root password. Root privileges are required for any installation that includes WebLink. For all other installations, you can log in as the sagent user. 2. Insert the Sagent CD into a network-accessible CD-ROM drive. UNIX will auto-mount the CD once it is inserted in the drive. 3. Type /cdrom/install. If you are not logged in with the root password, a message displays that states that root is required for WebLink installation. Type Y to continue with the installation or type N to stop the installation so that you can log in as root. The installation displays a welcome message and prompts you to review the license agreement. 4. Press Enter to review the Sagent license agreement. The installation program prompts you to agree to the terms of the license agreement. 5. Type Y and press Enter to accept the terms of the Sagent license agreement. The installation program prompts you for the target directory. 6. Type the target directory and press Enter. The installation program unpacks mw.tar to the target directory. If you are logged in as root, the installation program prompts for the owner and group of the installed files. If not, skip to step Type the owner for the files and press Enter. The default value is sagent. 8. Type the group or accept the default and then press Enter. The installation program prompts you for the license key. 9. Type the license key and press Enter. The installation program displays the license key information, including product permission and expiration date. The installation program prompts for the server components to install. 10. Type the number for each server component to install and press Enter. 11. When you have selected all the server components that you want to install, type the number that appears next to Exit, and press Enter to exit the text menu when you finish selecting components. Depending on the product series that you are installing, the installation program prompts you for the database type. Sagent Data Flow Solution v Installation Guide

35 12. Type the number for the database type you are using and press Enter. Chapter 3: UNIX Server Installation Running the Installation for a New Installation 13. Type the name of the computer that will host the Data Flow Server and press Enter. The default is the host name of the computer. The installation program prompts for the TCIP/IP port number to use for the Manager (saad_dmn). 14. Type the TCP/IP port number to use for the Manager and press Enter. The valid range is 1025 to The default value is The installation program prompts for the TCIP/IP port number to use for the Data Flow Server. 15. Type the TCP/IP port number to use for the Data Flow Server and press Enter. The valid range is 1025 to The default TCP/IP port number for the server is If you are installing WebLink, the installation program prompts for location of the iplanet or Sun One installation directory. If you are not installing WebLink, skip to step Type the location of the iplanet or Sun One installation directory and press Enter. The installation program detects available web servers in the directory and prompts for the name of the web server to use as the WebLink web server instance. 17. Type the name of the web server to use as the WebLink web server instance and press Enter. The installation program prompts for the TCIP/IP port number to use for the WebLink Server. 18. Type the TCP/IP port number to use for the WebLink Server and press Enter. The valid range is 1025 to The default TCP/IP port number for the server is The installation program displays the configuration information that you have entered. The installation program displays the Is this configuration correct message. 19. Type Y and press Enter. The installation program displays the Do you want to install with these settings message. 20. Type Y and press Enter. If you type N, the installation program returns to the license key prompt so that you can change any incorrect information. The installation program begins the installation and displays progress messages as the installation continues. The installation program displays the You have successfully installed Sagent Version 6.8 message when the installation is finished. 21. Follow the procedures in Finishing the Installation Process to finish installing Sagent server applications on UNIX. If you are upgrading, all of your pre-upgrade configuration files are saved in $SAGENT_HOME/log/.dfsconfig, where $SAGENT_HOME is the installation directory, so that you can reapply any customizations after upgrading. Configurable server Sagent Data Flow Solution v Installation Guide

36 Chapter 3: UNIX Server Installation Running the Installation for a New Installation tuning data is preserved and reapplied after upgrading by applying your database environmental variables to the new.sagentrc located in $SAGENT_HOME root. Do not copy the old.sagentrc. Sagent Data Flow Solution v Installation Guide

37 Chapter 3: UNIX Server Installation Finishing the Installation Process Finishing the Installation Process To finish installing the Sagent Solution on UNIX, you must configure your UNIX environment, start the admin daemon, and install Windows components. To complete your UNIX installation: 1. Change to the installation directory, such as /opt/sagent. 2. Add your database-specific environment variables to the end of the.sagentrc file located in the installation directory. Variables must be set in Bourne compatible format. Do not use CSH syntax. The following sample lists the variables to add: # DB2 settings for 7.2 LD_LIBRARY_PATH=/opt/IBMdb2/V7.1/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH. /export/home/db2inst3/sqllib/db2profile # oracle settings # ORACLE_SID=sagent9i export ORACLE_SID ORACLE_HOME=/opt/oracle/OraHome1 export ORACLE_HOME ORACLE_OWNER=oracle export ORACLE_OWNER PATH=$PATH:$ORACLE_HOME/bin export PATH LIBPATH=${LIBPATH}:${ORACLE_HOME}/lib export LIBPATH LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${ORACLE_HOME}/lib export LD_LIBRARY_PATH # sybase settings # SYBASE=/opt/sybase export SYBASE PATH=/opt/sybase/OCS-12_0/bin:$PATH export PATH SYBASE_OCS=OCS-12_0 export SYBASE_OCS LM_LICENSE_FILE=/opt/sybase/SYSAM- 1_0/licenses/license.dat:$LM_LICENSE_FILE export LM_LICENSE_FILE LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/sybase/OCS- 12_0/lib:/usr/local/openwin/lib:/usr/lib:/opt/sybase/SQLRemote/lib export LD_LIBRARY_PATH SYBASE_SYSAM=SYSAM-1_0 export SYBASE_SYSAM Sagent Data Flow Solution v Installation Guide

38 Chapter 3: UNIX Server Installation Finishing the Installation Process # Merant ODBC settings ODBC_HOME=/opt/odbc export ODBC_HOME LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${ODBC_HOME}/lib export LD_LIBRARY_PATH ODBCINI=/opt/odbc/sa_odbc.ini export ODBCINI # Netezza settings LD_LIBRARY_PATH=/export/home/sagent/odbc64v51/lib:$LD_LIBRARY_PATH ODBCINI=/export/home/sagent/odbc64v51/odbc.ini NZ_ODBC_INI_PATH=/export/home/sagent/odbc64v51 export LD_LIBRARY_PATH export ODBCINI export NZ_ODBC_INI_PATH In AIX UNIX, use LIBPATH environment variable to configure the DB2 library path setting. For example, LIBPATH=INSTHOME/sqllib/lib:${SAGENT_HOME}/lib:${MWCURRENT_LIBPAT H}:${LIBPATH}export LIBPATH 3. If you installed the Data Flow Service Access server or Sagent WebLink, add the DISPLAY variable to the.sagentrc file. 4. Start Sagent: a. Change to the bin directory, such as /opt/sagent/bin b. Type the follwing command: /sagent start Running this command starts the Sagent admin daemon and Data Flow Service. This allows you to start and monitor the Data Flow Service on UNIX from Sagent Admin. If a WebLink Server is installed, it is started automatically as well. 5. Install the Sagent Repository and Sagent Admin. You must install these components from a Windows system. For instructions, see Chapter 4, Windows Installation 6. Use Sagent Admin from a Windows client to start and monitor the Data Flow Service. See the Sagent Administrator s Guide for more information about running the Data Flow Service. 7. Install the client components. For instructions, see Installing a Designer Workstation and Sagent Admin on page 79 and Installing an End-User Workstation on page 81. Sagent client components must be installed on Windows systems only. 8. If WebLink is installed on a different UNIX server than the Data Flow Server, type the following command:./weblink start 9. See Automatically Starting the Data Flow Service on page 99 for information about automating Sagent Solution start scripts. Sagent Data Flow Solution v Installation Guide

39 Updating the Data Flow Service License Key Chapter 3: UNIX Server Installation Updating the Data Flow Service License Key Access to Data Flow Service capabilities is controlled through license keys. You can use the installation program to do the following without installing any additional software: Upgrade a system with an evaluation license to a full software license. Enable one or more of the following Data Flow Service capabilities on an existing licensed system: Sagent Data Flow Server Sagent Load Server Sagent Access Server You need your Sagent CD to update the license keys using the following instructions. The -u option updates the license key without installing any new software. To update a license key on UNIX, the Sagent user s default shell must be ksh or sh, not csh. To update the Sagent license key on a UNIX system: 1. Log in with the root password or the Sagent installation owner. 2. Insert the Sagent CD into a network-accessible CD-ROM drive. UNIX auto-mounts the CD after it is inserted in the drive. 3. Type cd /cdrom. 4. Type./install -u and press Enter. 5. Type Y to accept the Sagent License Agreement. 6. Type the target installation directory and press Enter. 7. Type the new license key and press Enter. If you are not logged in as root, the installer prompts you for the password of the Sagent installation owner. The new license key is now installed. The install program displays license key status and information. Sagent Data Flow Solution v Installation Guide

40 Chapter 3: UNIX Server Installation Upgrading a Patch on the UNIX Installation of Sagent Upgrading a Patch on the UNIX Installation of Sagent Use the following steps to add a particular patch on the existing Sagent installations on UNIX systems: 1. Download the patch from the PTS server using your login credentials. 2. Unzip the files using the tar or unzip command utilities. 3. Use the chmod R 777 <patch_file_dir> to give the permissions to all files in the patch installer. 4. Log in with the Sagent user. 5. Stop all Sagent Services using the./sagent stop command. 6. Browse to the patch installer directory and run the command:./update. The installation displays a welcome message and prompts the user to review the license agreement. 7. Press Enter to review the Sagent license agreement. The installation program prompts the user to agree to the terms of the license agreement. 8. Type Y and press Enter to accept the terms of the Sagent license agreement. The installation program prompts the user for the target directory. The target directory is the directory where Sagent is currently installed. 9. Type the target directory and press Enter. The installer copies the license agreement to a specified folder as per the installation directory and retrieves the DFS Tuning information like the Installation directory, port numbers, system name, and owner name. The installation displays a message for the user to review the settings. 10. Type Y and Enter to continue with the installation if the settings are correct. Otherwise, press N and restart the installation. Enter the correct information. Go to step 6. The installer unpacks the necessary files and installs the files under the Sagent installation folder. 11. After finishing the installation a message is displayed for a successful installation. 12. Run the.sagentrc file. 13. Restart all the Sagent services. 14. Check the files under the.log directory of the Sagent installation directory. This should contain a new file with the name and date of the upgrade. The file contains information on all components that were upgraded during the patch installation process. Sagent Data Flow Solution v Installation Guide

41 Chapter 3: UNIX Server Installation Uninstalling Sagent from UNIX Servers Uninstalling Sagent from UNIX Servers When you uninstall Sagent from a UNIX server, you must remove all files in the directory. To uninstall Sagent from a UNIX server: 1. Log in as root or the Sagent installation owner. 2. Carefully type the following command to delete all Sagent files and subdirectories: rm -rf <sagent dir> where <sagent dir> is the directory where you installed Sagent, such as /opt/sagent. Be sure to include the Sagent installation directory in the rm -rf command. If you type rm -rf /, you will erase the entire server. 3. If you want to uninstall WebLink, delete the Web server instance that hosts WebLink. All the necessary files will be deleted. Sagent Data Flow Solution v Installation Guide

42 Chapter 3: UNIX Server Installation Installation Command Parameters Installation Command Parameters The installation command includes several parameters as listed in the following syntax example. The table that follows explains each parameter. install [ -v ] [ -s ] [ -C ] [ -u ] [ -c CfgFil ] [ -l LogFile ] [ -i InstDir ] [ -L lang ] Command Name Description -v Verbose Output Mode Normally, the installation script writes a "." for every file written to indicate activity. With verbose mode, the actual filenames are printed. Generates several thousand lines of output. -s Silent Install Mode. Use to place the installation script in your own scripts. The installation script returns status 0 on success. Used with the configuration files to automate installations. -C Prompt to Save Configurations in files for later use. As the installation script executes, it prompts you for the installation options. When -C is set, it prompts you for a filename to save all of the responses in so they can be used later. -u Set new license key in registry Used for updating the license key on an existing installation. Can be used any time after an initial installation. -c Config_File Specify an installation configuration file to use. -l Log_File Specify a log file to report messages to. (default "/tmp/sagent_install.3972.log") Config_File is a configuration file produced with a previous install -C. The installation will use the contents of the file for default values when prompting the user. If the script is invoked in unattended mode, the configuration file values will be used instead of prompting the user. Allows the user to save the installation log to a specified file. Sagent Data Flow Solution v Installation Guide

43 Chapter 3: UNIX Server Installation Installation Command Parameters Command Name Description -i Specify a default installation directory. (default "/opt/sagent") Not really needed any more, but provides another mechanism to specify the default installation directory. Redundant to the value in the configuration file. The configuration file takes precedence. -L Install non-english version Supported languages are: JA > Japanese KO > Korean ZH > Chinese Sagent Data Flow Solution v Installation Guide

44 Windows Installation 4 This chapter describes how to install or upgrade the Sagent Solution software on supported Microsoft Windows systems. This chapter also describes how to install or upgrade the Sagent Repository. This chapter includes the following topics: Installation details for Version bit version Installation details for Version bit version Uninstalling Sagent from Windows Servers Uninstalling WebLink Client Controls

45 Installation details for Version bit version This section includes the following topics: Introduction Before Installing Sagent Solution Software for 64-bit Before Upgrading Sagent Solution Software for 64-bit Sagent Solution Setup for 64-bit Updating the Data Flow Server License Key for 64-bit Unattended Client Setup for 64-bit Chapter 4: Windows Installation Installation details for Version bit version Introduction Topics in this section include: Sagent Solution Installation Workflow Server Components Designer, End-User, and Administrator Components Repository and Other Components Sagent Solution Setup for Windows includes all the components for installing and upgrading all Sagent Solution server software, repository, and end-user applications. There are five types of system installations you can perform: Server - This software is installed on IT systems and provides the load and access services that designers and end users use to create and use plans in their business intelligence activities. Repository - This metadata is loaded into your DBMS system. Design Studio - This software is installed on designer workstations for people who create extraction, transformation, load Plans, report Plans, and Plans for others to use in their business intelligence activities. Admin - This software is installed on IT systems for people who administer the Sagent Solution. If a Sagent designer is also designated as the Sagent Administrator, then this software should be loaded on the designer workstation as well. Information Studio - This software is installed on end-user workstations for people using plans in their business intelligence activities. Sagent Solution Installation Workflow Figure 4 shows the workflow to refer when you install the Sagent Solution. The Server components are installed first, following which the Client and the Repository components are installed. The exceptions are when: Server components run on separate Windows systems. You do not have access to the database server where the repository will be stored and you need the assistance of the DBA. After you install and configure the server components, install the designer workstations, end-user workstations and the Repository components. The Sagent Solution includes one license for Sagent Admin. Sagent Admin should be installed at the Sagent administrator s workstation only. Sagent Data Flow Solution v Installation Guide

46 Chapter 4: Windows Installation Installation details for Version bit version Sagent Data Flow Server - Configures the Sagent server with server product components included in your product license. Sagent WebLink Server - Select this option to install Sagent WebLink. Sagent WebLink provides access from a Web browser to Plans and Snaps stored in the Repository. Web Service - Select this option to install Sagent Web Service, which exposes custom Application Programming Interfaces (API s) that can be called from any web service client. For information about upgrading from a previous version of the Sagent Solution or about adding new components to an existing installation, see Before Upgrading Sagent Solution Software for 64-bit on page 52. Figure 4: Sagent Solution Installation Workflow Sagent Data Flow Solution v Installation Guide

47 Chapter 4: Windows Installation Installation details for Version bit version Table 13 lists the components to select for each Sagent Solution system type. The list of components you see during installation depends on your product license. Use this table to choose the server and end-user installation components to install for each system. Table 13:Sagent Solution Component Matrix Data Flow Server WebLink Server Component Repository Server X Server WebLink Server X SampleWebPagesOnly X Web Service X Designer/Administrator/End User Design Studio Information Studio Admin Tool 1 X X Admin Developer/ Designer Repository, Add-ons, and other components Repository - Build or Upgrade X Analytical Calculator, Forecaster X X X WebService DataSink X X X Help Files X X X X Samples MetaLens Reports X General Samples X X X End User Transform SDK X 1 Sagent Admin should only be installed on a designer workstation designated as the Sagent Administrator. Server Components This section describes each of the server components. Sagent Data Flow Server - Configures the Sagent server with server product components included in your product license. Weblink Server - Select this option to install Sagent Weblink. Sagent Weblink provides access from a Web browser to Plans and Snaps stored in the Repository. Sagent Data Flow Solution v Installation Guide

48 Chapter 4: Windows Installation Installation details for Version bit version Web Service - Select this option to install Sagent Web Service, which exposes custom Application Programming Interfaces (API s) that can be called from any web service client. Designer, End-User, and Administrator Components This section describes the user applications that the Client Setup installs. Design Studio - Select this option to install Design Studio. If you install Design Studio, you cannot install Information Studio. Design Studio should be installed on the machine of a user who needs to design plans. Information Studio - Select this option to install Information Studio. If you install Information Studio, you cannot install Design Studio. Admin Tool - Select this option to install Sagent Admin, where you can manage both client and server activities for one or more Sagent installations, including configuring servers or Repositories, defining security and creating new users, and other tasks All the Repository build/upgrade can be made only during Client installation. The Client installation can be done on supported 32-Bit Windows platforms. It can also be installed on supported 64-Bit Windows Server platforms where it will operate as a 32-Bit legacy application. The Sagent Client includes one license for Sagent Admin. Sagent Admin should be installed at the Sagent administrator s workstation only. You can upgrade v6.0, v6.5, v6.6, v6.7 or v6.7.1 client to Version 6.8 client. During Sagent Installation, Microsoft Visual C redistributable may prompt an error: There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. In the msiexec log, you may see an error: Error There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action SxsInstallCA, entry: CustomAction_SxsMsmInstall, library: C:\WINDOWS\Installer\MSIA.tmp". To overcome this, Install Windows Installer 3 or later before installing the VC++ Redistributable MSI. For information about upgrading from a previous version of the Sagent Solution or about adding new components to an existing installation, see Before Upgrading Sagent Solution Software for 64-bit on page 52. Sagent Data Flow Solution v Installation Guide

49 Chapter 4: Windows Installation Installation details for Version bit version Repository and Other Components This section describes the Repository installation options, add-on products, and other components. When you install add-on products there are components that need to be added to the repository and components that need to be installed on the Sagent Solution workstations. Repository - Build or Upgrade - Select this option to create or upgrade a repository for your Sagent Solution. Forecaster Transform - Select this option to install Forecaster, which is a data trend forecasting application add-on product. This option also adds Forecaster to the repository. Analytical Calculator - Select this option to install the Analytical Calculator, a statistical analysis application add-on product. This option also adds Analytical Calculator to the repository. WebService DataSink - A Web Service Data Returning Sink Transform is now available for use in your plans. You can output your plan results to a web service sink using Sagent Web Service. Help Files - Select this option to install the online help. Samples - Select this option to install sample databases, a sample repository, or MetaLens reports. Transform SDK - Select this option to install the Sagent Transform Software Developer s Kit (SDK). Sagent Transform SDK is a set of sample code and library files for developing Transforms in C++. This release supports custom Transforms, using Sagent Transform SDK and Microsoft Visual Studio Before Installing Sagent Solution Software for 64-bit For a list of system requirements, see System Requirements on page 15. Before installing Sagent Solution software, complete the following prerequisites: 1. The following minimum system preferences must be set: a. UAC (User Account Control) must be disabled. b. You must have installation privileges to install the software, if not the admin privileges. c. To run WebLink, IIS must be installed. d. Active X content must be enabled. e. Firewall settings or any local network policy must be disabled as it blocks ActiveX contents. 2. Note your Sagent license keys, which are printed on the Sagent Solution packing list. You will find two Sagent License keys: one specified for the Client and the other for the Server. Use the appropriate license key for your type of installation. 3. Verify that the date/time format is set correctly in the Regional Settings of the Control Panel. Design Studio, Information Studio, and DFS servers should be set to the same date/time format to avoid potential date and time incompatibilities. 4. Confirm that the database server for your repository is running. 5. Create a database for the Sagent Repository with the following characteristics: At least 100 MB in size A transaction log space of at least 20 MB Grant all database logins used by Sagent users the permissions to select, insert, update, and delete on the repository database. Sagent Data Flow Solution v Installation Guide

50 Chapter 4: Windows Installation Installation details for Version bit version 6. If you are installing the Sagent Samples Repository or MetaLens Reports Repository, see Sagent Samples Repository on page 60 or Sagent MetaLens Reports Repository on page 62 for database prerequisite information. 7. Confirm that your database login has create, update, and drop table permissions. 8. Note the following information about your Sagent Repository, Samples, and MetaLens Reports databases: The name of the database. The name of the server where the database is located. The login and password you used to create the database. 9. To use the IBM DB2 Extended Enterprise Edition (DB2 EEE) with the Sagent Solution you must create a special nodegroup and tablespace before installing Sagent. DB2 EEE is a partitioned database (the data is spread across multiple partitions). When you want to create tables for the database, you must first create the nodegroup (a set of one or more database partitions) where the tablespaces are stored. A nodegroup that contains only one database partition is known as a single-partition nodegroup. Sagent requires the repository to be created on a single-partition nodegroup. Please consult your Database Administrator before creating DB2 EEE. Tasks to complete with DB2 EEE before installing Sagent: a. Create a single-partitioned nodegroup. b. Create a tablespace on that single-partitioned nodegroup. c. Add the tablespace name to the Sagent registry setting (for example, HKEY_LOCAL_MACHINE\SOFTWARE\Sagent\DataMart\RW\TableSpaceInfo) in the following format: DB2=TABLESPACE1:DATABASEALIAS1 where TABLESPACE1 is the name of the tablespace on which Sagent will create tables, and DATABASEALIAS1 is the database alias for the DB2 database. To define more than one server type, tablespace, and database alias, separate each item with a semicolon. For example: DB2=REPO_TABLESPACE:REPO_DB_ALIAS; DB2=METALENS_TABLESPACE:METALENS_DB_ALIAS For Windows 2008 users: To Install Sagent Data Flow Server on Windows 2008: 1. Login to Windows 2008 as an Administrator or User having administrator privilege. 2. Disable UAC (User Account Control). 3. Install Sagent Data FlowVersion 6.8 Server and other components. Refer to Sagent Solution Setup for 64-bit on page Reboot and login as the same user again. 5. Open Sagent Admin, register Data Flow Server and start it. 6. Open Design Studio and login as sa. Sagent Data Flow Solution v Installation Guide

51 Chapter 4: Windows Installation Installation details for Version bit version 7. Enable UAC and reboot OS. If Sagent Admin and Data Flow Server are installed on different machines (with the Data Flow server on Windows 2008), the Error 5 error message is displayed while trying to register the Data Flow Server in Sagent Admin. Workaround: Access the Data Flow server machine once from the machine on which Sagent Admin is installed. Once you are authenticated, the Data Flow server will be successfully registered in Sagent Admin. For WebLink Users: If you are installing WebLink on IIS 7, please install the ASP Components and IIS 6 Management Compatibility Components. You must have write permissions on HTML root directory (C:\inetpub\wwwroot folder) To install the IIS 6.0 Management Compatibility Components in Windows Server 2008 R2 or in Windows Server by using the Server Manager tool 1. Click Start, click Administrative Tools, and then click Server Manager. 2. In the navigation pane, expand Roles, right-click Web Server (IIS), and then click Add Role Services. 3. In the Select Role Services pane, scroll down to IIS 6 Management Compatibility. 4. Click to select the IIS 6 Metabase Compatibility and IIS 6 Management Console check boxes. 5. In the Select Role Services pane, click Next, and then click Install at the Confirm Installations Selections pane. 6. Click Close to exit the Add Role Services wizard. To install the IIS 6.0 Management Compatibility Components in Windows 7 or in Windows Vista from Control Panel 1. Click Start, click Control Panel, click Programs and Features, and then click Turn Windows features on or off. 2. Open Internet Information Services. 3. Open Web Management Tools. 4. Open IIS 6.0 Management Compatibility. 5. Select the check boxes for IIS 6 Metabase and IIS 6 configuration compatibility and IIS 6 Management Console. 6. Click OK. For more information, refer to Sagent Data Flow Solution v Installation Guide

52 Chapter 4: Windows Installation Installation details for Version bit version IIS 7 on Windows 2008 Server For IIS 7 on Windows 2008 Server, ASP component and Management Tools should be installed on the client machine as these are not installed by default in IIS 7. Before Upgrading Sagent Solution Software for 64-bit If you are upgrading the client components and repository to Version 6.8 from version 6.0 or later, you can upgrade directly. To upgrade a Sagent Repository: 1. Use Sagent Admin to clean up each Sagent Repository. 2. If you are upgrading your repository, make sure that the system you are upgrading from has connections to all data sources. 3. Use your database tools to create a database backup of each Sagent Repository. 4. Shut down all client applications. 5. If you are upgrading the Client from versions earlier than 6.0, then uninstall the Sagent programs from the Add/Remove Programs in the Control Panel. Version 6.0 or later Clients can upgrade to Version 6.8 directly. For more information, see Uninstalling Sagent from Windows Servers on page 93. Reboot the system before beginning to install the new software. 6. Install the new version as described in Sagent Solution Setup for 64-bit. If you have created custom registry settings and Data Flow Server settings, record your customizations before uninstalling Sagent. After you upgrade your Client components/fresh installation of DFS, reapply your customizations. Sagent Solution Setup for 64-bit Topics in this section include: Installing a Sagent Solution Server Installing a Designer Workstation, Sagent Admin and Repository Installing an End-User Workstation Installing WebLink Client Sagent Repository Information Sagent Samples Repository Sagent MetaLens Reports Repository Updating the Data Flow Server License Key for 64-bit Installing a Sagent Solution Server Setup installs the Sagent Solution servers. To install Sagent applications: Sagent Data Flow Solution v Installation Guide

53 Chapter 4: Windows Installation Installation details for Version bit version 1. Log into the computer. The account you use to install the Sagent Solution must have administrator privileges. 2. Exit all applications currently running. See Before Upgrading Sagent Solution Software for 64- bit on page 52 before continuing. 3. Insert the Sagent Solution media. 4. Autorun starts Setup automatically. If Setup does not automatically start, double-click Setup.exe at the root of the Sagent media. The Sagent Setup screen displays. If you are using a installation archive downloaded from the PBBI website as detailed in Downloading Sagent Solution from the Group 1 Website on page 12, double-click Setup.exe at the root of the archive. 5. Click Install Products and then click Sagent 64-Bit Windows. 6. The Welcome Dialog displays. 7. Click Next. 8. Click Yes to accept the Software License Agreement. The Customer Information dialog displays. 9. Type the following information in the Customer Information dialog text fields: User Name - Type the user s name. Company Name - Type the name of your company. Installation Key - Type the entire license key. The license key is printed on the Sagent Solution packing list. If you are only installing a new license key, click Update key only. For more information about installing license keys, see Updating the Data Flow Server License Key for 64-bit on page 63. The Confirm Information dialog displays. 10. Click Yes to confirm your information. Click No to change any incorrect information. The Choose Destination Location dialog for the Sagent Solution displays. 11. Click Browse to change the location and then click Next. The default is c:\program Files\Sagent The Select Components dialog displays. 12. In the Select Components dialog, click the check boxes for the Sagent Solution components to install. Select server components. For more information, see Server Components on page Click Next. If you selected Transform SDK, the Choose Destination Location dialog for Transform SDK displays. 14. To change the installation location, click Browse and select a directory location. The default is c:\program Files\Sagent\Sagent64\TransformSDK. Sagent Data Flow Solution v Installation Guide

54 Chapter 4: Windows Installation Installation details for Version bit version 15. Click Next. The DFS Information dialog displays. 16. In the text fields of the DFS Information dialog, type the port number for the Data Flow Server and the name of the machine where you want the Data Flow Server to run. 17. Select a communication protocol for connections between the clients and the Data Flow Service. You have the following choices: TCP/IP (default) Named Pipes If you selected to install WebLink, the WebLink Server Information dialog displays 18. Type the following information in the text boxes: HTML Root directory Type the directory path. The default is c:\inetpub\wwwroot. Web Server Host Name Type the machine name of the web server. 19. Click Next. The WebLink Configuration Information dialog displays. 20. Type the following information in the text boxes: Physical Sagent HTML directory Type the directory path. The default is c:\inetpub\wwwroot\sagentweb. Virtual Path for Sagent HTML Type the virtual path. The default is sagent/. Physical Extension File directory Type the directory path. The default is c:\inetpub\scripts. Virtual Path for extension files Type the virtual path. The default is scripts/. 21. Click Next. The Confirm Product Selections dialog displays. 22. Click Next. Setup begins installing the components you specified in Step 12 on page Select a restart option: Yes, I want to restart my computer now. No, I want to restart my computer later. Make sure that you log into the system after you restart it so that Setup can finalize any system file updates and Sagent file registration tasks. 24. Click Finish. Sagent Solution Server is now installed. Refer to the Sagent Administrator s Guide for information about starting your Sagent Solution services. Sagent Data Flow Solution v Installation Guide

55 Chapter 4: Windows Installation Installation details for Version bit version Installing a Designer Workstation, Sagent Admin and Repository Sagent 32-bit Windows refers to the 32-bit Client Installer suite available with 64-bit Version 6.8 Installer. Setup installs Sagent Design Studio and optional components. To install Sagent applications: 1. Log into the computer. The account you use to install the Sagent Solution must have administrator privileges. 2. Exit all applications currently running. If you are upgrading the Sagent Solution and server applications that run on this designer workstation, use the Control Panel to stop all Sagent services: Data Flow Server Web Server (if installing WebLink) Web Service 3. Insert the Sagent Solution CD. 4. Autorun starts Setup automatically. If Setup does not automatically start, double-click Setup.exe at the root of the Sagent CD. The Sagent Setup screen displays. If you are using a installation archive downloaded from the PBBI website as detailed in Downloading Sagent Solution from the Group 1 Website on page 12, double-click Setup.exe at the root of the archive. 5. Click Install Products and then click Sagent 32-Bit Windows. If this is a new installation, the Choose Setup Language dialog displays. 6. Select a language and then click Next. The Welcome dialog displays. 7. Click Next to confirm that you have exited all applications and stopped all services. 8. Click Yes to accept the Software License Agreement. The Customer Information dialog displays. 9. Type the following information in the Customer Information dialog text fields: User Name - Type the user name for this workstation. Company Name - Type the name of your company. Installation Key - Type the entire license key. The license key is printed on the Sagent Solution packing list. 10. Click Next. The Confirm Information dialog displays. Sagent Data Flow Solution v Installation Guide

56 Chapter 4: Windows Installation Installation details for Version bit version 11. Click Yes to confirm your information. The Choose Destination Location dialog for the Sagent Solution displays. 12. Click Browse to change the location and then click Next. The default is c:\program Files\Sagent. The Select Components dialog displays. 13. In the Select Components dialog, click the check boxes for the Sagent Solution components to install. Select Design Studio. If this Sagent designer workstation will be used to administer the Sagent Solution, select Sagent Admin. If this Sagent designer workstation will be used to create custom Transforms, select Transform SDK. If your system locale is set to Japanese,German, or French, Localized Components and Files is selected by default. Setup prompts you for the applicable Sagent Language Pack after the installation of Sagent Solution completes. For more information about installing Sagent Language Packs, see Installing Sagent Language Packs on page 67. If you want to install English, deselect Localized Components and Files. 14. Click Next. If you selected TransformSDK, the Choose Destination Location dialog for Transform SDK displays. 15. To change the installation location, click Browse and select a directory location. The default is c:\programfiles\sagent\transformsdk. 16. Click Next. The DFS Information dialog displays. 17. In the text fields of the DFS Information dialog, type the port number for the Data Flow Server and the name of the machine where Data Flow Server runs. 18. Select a communication protocol for connecting with the Data Flow Service. You have the following choices: TCP/IP (default) Named Pipes 19. Click Next. The Repository Information dialog displays. 20. In the text fields of the Repository Information dialog, select the appropriate database and type the login information for this designer workstation. See Table 14 on page Click Next. The Confirm Product Selections dialog displays. 22. Click Next. Setup begins installing the components you specified in Step 13 on page 56. The Install Wizard Complete dialog displays when Setup completes. Sagent Data Flow Solution v Installation Guide

57 Chapter 4: Windows Installation Installation details for Version bit version 23. Select a restart option: Yes, I want to restart my computer now. No, I want to restart my computer later. Make sure that you log into the system after you restart it so that Setup can finalize any system file updates and Sagent file registration tasks. 24. Click Finish. Sagent Solution software is now installed. Installing an End-User Workstation Setup installs Sagent Information Studio and optional components. To install Sagent applications: 1. Log into the computer. The account you use to install the Sagent Solution must have administrator privileges. 2. Exit all applications currently running. 3. Insert the Sagent Solution CD. 4. Autorun starts Setup automatically. If Setup does not automatically start, double-click Setup.exe at the root of the Sagent CD. The Sagent Setup screen displays. If you are using a installation archive downloaded from the PBBI website as detailed in Downloading Sagent Solution from the Group 1 Website on page 12, double-click Setup.exe at the root of the archive. 5. Click Install Products and then click Sagent 32-Bit Windows. If this is a new installation, the Choose Setup Language dialog displays. 6. Select a language and then click Next. The Welcome dialog displays. 7. Click Next to confirm that you have exited all applications and stopped all services. 8. Click Yes to accept the Software License Agreement. The Customer Information dialog displays. 9. Type the following information in the Customer Information dialog text fields: User Name Type the user name for this workstation. Company Name Type the name of your company. Installation Key Type the first 22 digits of the license key. The licence key is printed on the back of the Sagent Solution packing list. Sagent Data Flow Solution v Installation Guide

58 Chapter 4: Windows Installation Installation details for Version bit version 10. Click Next. The Confirm Information dialog displays. 11. Click Yes to confirm your information. The Choose Destination Location dialog for the Sagent Solution displays. 12. Click Browse to change the location and then click Next. The default is c:\program Files\Sagent. The Select Components dialog displays. 13. In the Select Components dialog, click the check boxes for the Sagent Solution components to install. Select Information Studio. Select Help Files if you want to install online help. If your system locale is set to Japanese, German, or French, Localized Components and Files is selected by default. Setup prompts you for the applicable Sagent Language Pack after the installation of Sagent Solution completes. For more information about installing Sagent Language Packs, see Installing Sagent Language Packs on page 67. If you want to install English, deselect Localized Components and Files. The DFS Information dialog displays. 14. In the text fields of the DFS Information dialog, type the port number for the Data Flow Server and the name of the machine where Data Flow Server runs. 15. Select a communication protocol for connecting with the Data Flow Service. You have the following choices: TCP/IP (default) Named Pipes 16. Click Next. The Repository Information dialog displays. 17. In the text fields of the Repository Information dialog, select the appropriate database and type the login information for this designer workstation. See Table 14 on page 59. The Confirm Product Selections dialog displays. 18. Click Next. Setup begins installing the components you selected. The Install Wizard Complete dialog displays when Setup completes. 19. Select a restart option: Yes, I want to restart my computer now. No, I want to restart my computer later. Make sure that you log into the system after you restart it so that Setup can finalize any system file updates and Sagent file registration tasks. 20. Click Finish. Sagent Solution software is now installed. Sagent Data Flow Solution v Installation Guide

59 Chapter 4: Windows Installation Installation details for Version bit version Installing WebLink Client When you install WebLink server, Sagent Setup puts the WebLink Client Setup program in the webroot folder (C:\Inetpub\wwwroot\Sagent WebLink Client, by default). You can provide a link to the client install for your WebLink users to install the WebLink Client on their computers. WebLink CAB files are automatically downloaded to WebLink browsers when you access the WebLink server. If you don t want users to download the WebLink CAB files through the web server, you can use the Sagent WebLink Client Setup. Some examples for using the client setup are: WebLink users must be in the Windows Administrators group to download ActiveX controls. Corporate policies restricting the download of programs from web servers. Corporate policies restricting the size of files downloaded from web servers. To install WebLink Client: 1. Double-click Setup.exe. The Welcome dialog displays. 2. Click Next. The License Agreement dialog displays. 3. Click the accept checkbox and then click Next. The Select Components dialog displays. 4. Select the components to install and then click Next. If you do not use Netscape, deselect the Sagent Netscape Plugin checkbox. 5. Click Install. Sagent WebLink Client Setup installs the selected components. 6. Click Finish. Sagent Repository Information Table 14 shows the information you need to enter for each Database type supported by the Sagent Solution repository. Table 14:Sagent Repository Information Dialog Fields Database Type Fields Required Information Microsoft SQL Server Repository Database Server Name Login Name Password Type the name of the database for your repository. Type the name of the server where the repository is located. Type a login name for the repository database. Type the password for the login name or leave this field blank. Sagent Data Flow Solution v Installation Guide

60 Chapter 4: Windows Installation Installation details for Version bit version Table 14:Sagent Repository Information Dialog Fields (continued) Database Type Fields Required Information Oracle Host String Type the host string for the server where the repository is located. User Name Type a user name for the repository database. Password Type the password for the user name or leave this field blank. IBM DB2 Database Alias Type the name of the server where the repository is located. User Name Password Type a user name for the repository database. Type the password for the user name or leave this field blank. Sagent Samples Repository This section includes the following topics: Preparing Oracle for Sagent Samples Preparing Microsoft SQL Server for Sagent Samples Preparing IBM DB2 for Sagent Samples Sagent Samples are sample databases with a sample repository and sample data. You can use these samples with Sagent documentation to learn about the functions of the Sagent Solution. The Sagent Samples installation loads this sample data into Microsoft SQL Server, Oracle, or IBM DB2 databases. Sagent Samples include sample data sources and a sample Sagent Repository. The Information Studio tutorial uses the samples_gourmet_food database, which is a star schema data mart. The population example in the Sagent Data Mart Population Guide uses the samples_creditcard_oltp database, which is an OLTP data source, and samples_creditcard_star. The sample repository includes BaseViews, MetaViews, the Sagent users, and sample Plans. The Sagent Samples installation creates all the necessary tables and loads sample data. You must create a database and tablespace. Follow the steps that correspond to your database type to create and configure your sample environment. Preparing Oracle for Sagent Samples Use your Oracle tools or modeling tools to create tablespace for storing sample data and repository definitions. 1. Create an account using the Oracle Enterprise Manager or SQLPlus. Ensure that the account has CONNECT and RESOURCE role rights and have at least 40MB of tablespace allocated. Sagent Data Flow Solution v Installation Guide

61 Chapter 4: Windows Installation Installation details for Version bit version 2. Use a reasonable naming of the account as not to confuse users. For example: Account for Samples Data and Repository: SAMPLES Preparing Microsoft SQL Server for Sagent Samples To prepare Microsoft SQL Server: 1. Use your database tools or modeling tools to create the databases listed in Table 15 for storing sample data and repository definitions on SQL Server databases. 2. Create one or more database logins for Sagent users to access the sample databases. 3. Use the database names and sizes to grant the user permissions listed in Table 15. Table 15:Microsoft SQL Server Samples Requirements Database Name Database Size Login Permissions samples_gourmet_food 5 MB select samples_creditcard_oltp 5 MB select samples_creditcard_star 5 MB select, create table samples_snaps 5 MB per 12 users select, create table samples_repository 30 MB select, insert, update, delete, create, drop, and alter table 1. Activate the Truncate Log on Checkpoint option. See your Microsoft SQL Server manual for more information. Preparing IBM DB2 for Sagent Samples To prepare IBM DB2: 1. Use your database tools or modeling tools to create the databases (aliases) listed in Table 16 for storing sample data and repository definitions on IBM DB2 databases. 2. Create one or more database logins for Sagent users to access the sample databases. Use the database names and sizes to grant the user permissions listed in Table 16. Table 16:IBM DB2 Samples Requirements Database Name Database Size Login Permissions SAGTFOOD 5 MB select SACCOLTP 5 MB select SACCSTAR 5 MB select, create table Sagent Data Flow Solution v Installation Guide

62 Chapter 4: Windows Installation Installation details for Version bit version Table 16:IBM DB2 Samples Requirements Database Name Database Size Login Permissions SASNAPS 5 MB per 12 users select, create table SAMPREPO 30 MB select, insert, update, delete, create, drop, and alter table See your preferred IBM DB2 manual for more information. Sagent MetaLens Reports Repository In this section, you install Sagent MetaLens Reports in your repository. This section includes the following topics: Preparing Oracle for Sagent MetaLens Reports Preparing Microsoft SQL Server for Sagent Samples Preparing IBM DB2 for Sagent MetaLens Reports The MetaLens Reports Repository becomes your default repository upon installation. You can use Sagent Admin to select another repository as your default. For more information, see the Sagent Administrator s Guide. Sagent MetaLens Reports are supported for Windows systems only. You need a separate database for Sagent MetaLens Repository. Follow the steps that correspond to your database type to configure your MetaLens environment. Preparing Oracle for Sagent MetaLens Reports Use your Oracle tools or modeling tools to create a database for the Sagent MetaLens Reports Repository. Use the following information: User name: METALENS or any user-defined name Table space size: 40 MB Permissions: connect and resource role rights See your preferred Oracle manual for more information. Preparing Microsoft SQL Server for Sagent MetaLens Reports Use your database tools or modeling tools to create a database for the Sagent MetaLens Reports Repository. Use the following information: Database name: repository_reports Database size: 40 MB Permissions: select, insert, update, delete, create, drop, and alter tables See your Microsoft SQL Server manual for more information. Sagent Data Flow Solution v Installation Guide

63 Preparing IBM DB2 for Sagent MetaLens Reports Chapter 4: Windows Installation Installation details for Version bit version Use your database tools or modeling tools to create a database alias for the Sagent MetaLens Reports Repository. Use the following information: Database alias: METALENS Database size: 40 MB Permissions: select, insert, update, delete, create, drop, and alter tables See your preferred IBM DB2 manual for more information. Updating the Data Flow Server License Key for 64-bit Access to Data Flow Server capabilities is controlled through license keys. You can use the installation program to do the following without installing any additional software: Upgrade a system with an evaluation license to a full software license. Updating the license key allows access to Transforms that may have been previously restricted by a license key. Running the complete installation is required for certain add-on Transforms, such as the Forecaster Transform or Analytical Calculator. You need your Sagent media to update the license keys using the following instructions. You need to upgrade the Server and Client licenses seperately. To update the Sagent license on a Windows system: 1. Insert the Sagent media and double-click Setup.exe. The Welcome dialog displays. 2. Click Next to confirm that you have exited all applications and stopped all services. 3. Click Yes to accept the Software License Agreement. The User Information dialog displays. 4. Type the new license key and click Next. The Set DFS Capabilities dialog displays. 5. Select one or more of the server or package types. 6. Select Update License Key and click Next. The Setup Complete dialog displays. The new license key is now installed. 7. Click Finish. Unattended Client Setup for 64-bit This section includes the following topics Creating an Unattended Setup Unattended Setup Example Sagent Data Flow Solution v Installation Guide

64 Chapter 4: Windows Installation Installation details for Version bit version Advanced Settings Tips for Unattended Setup Unattended Setup Log File Creating an Unattended Setup An unattended installation program executes without displaying any dialog boxes, prompting the user for input, or displaying an icon in the system taskbar. Unattended installations are useful for system administrators to install software without users being able to cancel the installation or enter incorrect information. An unattended installation works by reading response values to be used in place of direct user feedback from a text file called a response file. You can create a response file for installing Sagent Solution by running Sagent Setup in response mode. To do this, type setup.exe -r at a command prompt by navigating to the Platform folder at the root of the Sagent Solution CD. Let E: be the CD drive of the machine. You need to enter the following command: E:\>cd platform If you view the directory listing at this location by issuing the dir command, you will find files like data1.cab, data1.hdr, data2.cab, engine32.cab etc. along with other folders. To run installation in record mode, enter the command: E:\>setup.exe -r The response file, a text file called setup.iss, records the choices you make when prompted for information during the install and is then saved in the Windows directory. Once you have a response file, you can execute the installation program in unattended mode. Copy the contents of the Sagent Solution CD to your local hard drive, and place a copy of the setup.iss in that directory. Run setup.exe -s to start the setup in unattended mode using the response file you created earlier. The installation executes based on the information in the response file. A setup.log file records whether an installation was successful and logs any error codes returned. The default location of the log file is the same location as the setup.exe. A setup program running unattended does not display any dialog boxes, even if an error occurs. An unsuccessful unattended installation will have a negative value in the ResultCode=n line in the setup.log file. Two command line options for setup.exe can be used for unattended installation if it is not in the same location as setup.exe: -f1"<path>\setup.iss" specifies a path to the response file being read or created. -f2"<path>\setup.log" specifies the directory where the unattended install log file should be placed. Do not place spaces after the -f1 or -f2 options. Also, make sure to place double quotes around paths that contain spaces. Sagent Data Flow Solution v Installation Guide

65 Chapter 4: Windows Installation Installation details for Version bit version For unattended installation of Weblink Client, response file of the Weblink Client installer needs to be created instead of the response file of the main installer. $><Full Path of Weblink Client Installer>\WebLink Client Setup.exe r The setup.iss file will created. This can be used in the same way as the main installer. $><Full Path of Weblink Client Installer>\WebLink Client Setup.exe s f1<full Path of setup.iss file> -f2<full Path of Log File> Unattended Setup Example For an unattended installation to use a response file located at the root level of the C: drive and place the resulting log file in the Temp directory of the target system, the following command should be used: Setup -s -f1"c:\setup.iss" -f2"c:\temp\setup.log" You can specify alternate names for the setup.iss and setup.log files when you use these command line options. This is useful for creating response files for each operating system that your end users may have. For example, if end users run Windows XP, create the response file by running the setup program in response mode on a Windows XP machine as well. This ensures successful unattended installations. You may want to call the response file WinXPSetup.iss or something similar and have users point to this response file with the -f1 parameter as above. Advanced Settings Table 17 shows the configuration parameters in custom.ini that are applicable to unattended setups, which is located in the Platform\Custom folder. Sagent Setup ignores any line that begins with a semi-colon, which disables that setting. Table 17:Custom.ini Usage [Section] Parameter RmSaConfig RmSaAdmin RmSaISD RmSaRpEXEs SetSaNoAdvKey Valid Value(s) (Default Value) YES or NO (NO) YES or NO (NO) YES or NO (NO) YES or NO (NO) YES or NO (NO) Notes Removes saconfig.exe utility if found on the target computer. Removes Admin (saad.exe), and ldap.exe utility if found on the target computer Removes Design Studio saisd.exe if found on the target computer. Removes the repository utilities if found. This controls the Advanced button behavior in the IS and DS login dialog boxes. Sagent Data Flow Solution v Installation Guide

66 Table 17:Custom.ini Usage Chapter 4: Windows Installation Installation details for Version bit version [Section] Parameter Valid Value(s) (Default Value) Notes SaAdvKeyValue 0 or 1 (Advanced key enabled) SetSaDB2FetchOnly 0 or 1 (0) The value for the Advanced key setting. For end users: 0 = don t allow Advanced Login 1= hide the button and always run in Advanced mode. No key or other value = default behavior For IBM DB2 EEE customers. 0 = default 1 = append FOR READ ONLY to SQL Tips for Unattended Setup If MDAC 2.1 or greater is not installed on the target computer, the Microsoft MDAC install launches and a system reboot will be necessary. This occurs before the remainder of the Sagent install can run. If you do not want this installation behavior, initiate the MDAC install using your own installation program. The MDAC setup program is located on the Sagent Solution CD in the Platform\MDAC folder. Create a separate response file for each operating system. Select No at the reboot prompt at the end of the setup. If you select Yes, your response file will contain a Yes response to this dialog and all end user systems will be rebooted after the unattended setup. After an unattended installation the computer should be restarted to activate any new settings. Unattended Setup Log File The setup.log file contains three sections. The [InstallShield Silent] section identifies the version of InstallShield Silent used in the unattended setup. It also identifies the file as a log file. The [Application] section identifies the name and version of the installed application and the company name. The [ResponseResult] section contains the result code indicating whether or not the unattended setup succeeded. An integer value is assigned to the ResultCode keyname in [ResponseResult]. InstallShield places one of the following return values after the ResultCode keyname: 0 Success. -1 General error. -2 Invalid mode. -3 Required data not found in the setup.iss file. -4 Not enough memory available. -5 File does not exist. Sagent Data Flow Solution v Installation Guide

67 Chapter 4: Windows Installation Installation details for Version bit version -6 Cannot write to the response file. -7 Unable to write to the log file. -8 Invalid path to the InstallShield Silent response file. -9 Not a valid list type (string or number). -10 Data type is invalid. -11 Unknown error during setup. -12 Dialog boxes are out of order. -51 Cannot create the specified folder. -52 Cannot access the specified file or folder. -53 Invalid option selected. Installing Sagent Language Packs Language packs can be applied only on the top of a GA installation. Sagent 32-bit Windows refers to the 32-Bit Client Installer Suite of Version 6.8. Sagent 32-bit Windows Solution is available in several languages. The installation media is constructed so that there is a core installation package, plus installation packs for supported languages. The core package is installed first, followed by the language pack, which installs the necessary localized components. Language packs available from Sagent 32-bit Windows Solution include: French FRA German DEU Japanese JPN To install a language pack: 1. Double-click Setup.exe on the Sagent 32-bit Windows Solution Language Pack installation media. The Sagent 32-bit Windows Solution Language Pack Selected Components dialog is displayed. Sagent Data Flow Solution v Installation Guide

68 2. Click Next. The localized components and files are installed. Chapter 4: Windows Installation Installation details for Version bit version Sagent Language Packs must be installed at the following location even if Sagent Data Flow is installed at a different location: C:\Program Files\Sagent If Sagent Language Pack is installed (for Non-English users) you must install Sagent Version 6.8 language pack packaged with the Sagent Version 6.8 Installer after upgrading to Version 6.8. If Sagent Language Pack is installed (for Non-English users) and you choose to uninstall the existing version of Sagent, you must also uninstall the existing Sagent language pack before installing Sagent Version 6.8 GA and the corresponding language pack (packaged with the Sagent Version 6.8 Installer). Sagent Data Flow Solution v Installation Guide

69 Installation details for Version bit version This section includes the following topics: Introduction Before Installing Sagent Solution Software for 32-bit Before Upgrading Sagent Solution Software for 32-bit Sagent Solution Setup for 32-bit Updating the Data Flow Service License Key for 32-bit Unattended Client Setup for 32-bit Chapter 4: Windows Installation Installation details for Version bit version Introduction Topics in this section include: Sagent Solution Installation Workflow Server Components Designer, End-User, and Administrator Components Repository and Other Components Sagent Solution Setup for Windows includes all of the components for installing and upgrading all Sagent Solution server software, repository, and end-user applications. There are five types of system installations you can perform: Server This software is installed on IT systems and provides the load and access services that designers and end users use to create and use plans in their business intelligence activities. Repository This metadata is loaded into your DBMS system. Design Studio This software is installed on designer workstations for people who create extraction, transformation, load Plans, report Plans, and Plans for others to use in their business intelligence activities. Admin This software is installed on IT systems for people who administer the Sagent Solution. If a Sagent designer is also designated as the Sagent Administrator, then this software should be loaded on the designer workstation as well. Information Studio This software is installed on end-user workstations for people who use Plans in their business intelligence activities. Sagent Solution Installation Workflow Figure 5 shows the workflow to follow when you install the Sagent Solution. The server and repository components are installed first, generally at the same time during initial installation. The exceptions are when: Server components run on separate Windows systems. One or more Sagent servers run on a UNIX system. For more information about UNIX server installations, see UNIX Server Installation on page 31. You do not have access to the database server where the repository will be stored and you need the assistance of the DBA. Sagent Data Flow Solution v Installation Guide

70 Chapter 4: Windows Installation Installation details for Version bit version After you install and configure the server and repository components, then install the designer workstations and end-user workstations. The Sagent Solution includes one license for Sagent Admin. Sagent Admin should be installed at the Sagent administrator s workstation only. For information about upgrading from a previous version of the Sagent Solution or about adding new components to an existing installation, see Before Upgrading Sagent Solution Software for 32-bit on page 75. Figure 5: Sagent Solution Installation Workflow Sagent Data Flow Solution v Installation Guide