in 910hf1 jodbcconnectionguide en

Informatica Data Services (Version 9.1.0 HotFix 1)

JDBC/ODBC Connection Guide

Informatica Data Services JDBC/ODBC Connection Guide

Version 9.1.0 HotFix 1June 2011

Copyright (c) 2011 Informatica. All rights reserved.

This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use anddisclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form,by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S. and/or internationalPatents and other Patents Pending.

Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided inDFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013 © (1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), asapplicable.

The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us inwriting.

Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange,PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica OnDemand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and InformaticaMaster Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other companyand product names may be trade names or trademarks of their respective owners.

Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rightsreserved. Copyright © Sun Microsystems. All rights reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All rightsreserved.Copyright © Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright © MetaIntegration Technology, Inc. All rights reserved. Copyright © Intalio. All rights reserved. Copyright © Oracle. All rights reserved. Copyright © Adobe Systems Incorporated. Allrights reserved. Copyright © DataArt, Inc. All rights reserved. Copyright © ComponentSource. All rights reserved. Copyright © Microsoft Corporation. All rights reserved.Copyright © Rogue Wave Software, Inc. All rights reserved. Copyright © Teradata Corporation. All rights reserved. Copyright © Yahoo! Inc. All rights reserved. Copyright ©Glyph & Cog, LLC. All rights reserved. Copyright © Thinkmap, Inc. All rights reserved. Copyright © Clearpace Software Limited. All rights reserved. Copyright © InformationBuilders, Inc. All rights reserved. Copyright © OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo Communications, Inc. All rightsreserved. Copyright © International Organization for Standardization 1986. All rights reserved. Copyright © ej-technologies GmbH . All rights reserved. Copyright © JaspersoftCorporation. All rights reserved.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and other software which is licensed under the Apache License,Version 2.0 (the "License"). You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing,software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See theLicense for the specific language governing permissions and limitations under the License.

This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software copyright ©1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under the GNU Lesser General Public License Agreement, which may be found at http://www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but notlimited to the implied warranties of merchantability and fitness for a particular purpose.

The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine,and Vanderbilt University, Copyright ( © ) 1993-2006, all rights reserved.

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and redistribution ofthis software is subject to terms available at http://www.openssl.org and http://www.openssl.org/source/license.html.

This product includes Curl software which is Copyright 1996-2007, Daniel Stenberg, <[email protected]>. All Rights Reserved. Permissions and limitations regarding thissoftware are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to use, copy, modify, and distribute this software for any purpose with or withoutfee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

The product includes software copyright 2001-2005 ( © ) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms availableat http://www.dom4j.org/ license.html.

The product includes software copyright © 2004-2007, The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to termsavailable at http://dojotoolkit.org/license.

This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding thissoftware are subject to terms available at http://source.icu-project.org/repos/icu/icu/trunk/license.html .

This product includes software copyright © 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at http://www.gnu.org/software/ kawa/Software-License.html.

This product includes OSSP UUID software which is Copyright © 2002 Ralf S. Engelschall, Copyright © 2002 The OSSP Project Copyright © 2002 Cable & WirelessDeutschland. Permissions and limitations regarding this software are subject to terms available at http://www.opensource.org/licenses/mit-license.php .

This product includes software developed by Boost (http://www.boost.org/) or under the Boost software license. Permissions and limitations regarding this software are subjectto terms available at http:/ /www.boost.org/LICENSE_1_0.txt. This product includes software copyright © 1997-2007 University of Cambridge. Permissions and limitationsregarding this software are subject to terms available at http://www.pcre.org/license.txt.

This product includes software copyright © 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to termsavailable at http://www.eclipse.org/org/documents/epl-v10.php.

This product includes software licensed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/overlib/?License, http://www.stlport.org/doc/ license.html, http://www.asm.ow2.org/license.html, http://www.cryptix.org/LICENSE.TXT, http://hsqldb.org/web/hsqlLicense.html, http://httpunit.sourceforge.net/doc/license.html, http://jung.sourceforge.net/license.txt, http://www.gzip.org/zlib/zlib_license.html, http://www.openldap.org/software/release/license.html, http://www.libssh2.org,http://slf4j.org/license.html, http://www.sente.ch/software/OpenSourceLicense.html, http://fusesource.com/downloads/license-agreements/fuse-message-broker-v-5-3- license-agreement; http://antlr.org/license.html; http://aopalliance.sourceforge.net/; http://www.bouncycastle.org/licence.html; http://www.jgraph.com/jgraphdownload.html; http://www.jcraft.com/jsch/LICENSE.txt. http://jotm.objectweb.org/bsd_license.html; http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231; http://www.slf4j.org/license.html; http://developer.apple.com/library/mac/#samplecode/HelpHook/Listings/HelpHook_java.html; http://www.jcraft.com/jsch/LICENSE.txt;http://nanoxml.sourceforge.net/orig/copyright.html; http://www.json.org/license.html; and http://forge.ow2.org/projects/javaservice/.

This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and DistributionLicense (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php), the Sun Binary Code LicenseAgreement Supplemental License Terms, the BSD License (http://www.opensource.org/licenses/bsd-license.php) and the MIT License (http://www.opensource.org/licenses/mit-license.php).

This product includes software copyright © 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this softwareare subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab. For furtherinformation please visit http://www.extreme.indiana.edu/.

This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775;6,640,226; 6,789,096; 6,820,077; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422, 7,720,842;7,721,270; and 7,774,791 , international Patents and other Patents Pending.

DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the impliedwarranties of oninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. Theinformation provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation issubject to change at any time without notice.

NOTICES

This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress SoftwareCorporation ("DataDirect") which are subject to the following terms and conditions:

1.THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OFTHE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACHOF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

Part Number: IN-JOC-91000-HF1-0001

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iiiInformatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Informatica Customer Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Informatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Informatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Informatica Multimedia Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Chapter 1: SQL Data Service Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1SQL Data Service Connections Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 2: Client Machine Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Client Machine Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Client Machine Configuration Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Result Set Caching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

JDBC Client Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Installing the Informatica JDBC Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Updating the CLASSPATH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Connecting to the SQL Data Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

ODBC Client Connections on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Installing the Informatica ODBC Driver on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Configuring the Informatica ODBC Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4


ODBC Client Connections on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Installing the Informatica ODBC Driver on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Updating the Shared Library Environment Variable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Updating odbc.ini. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6


Chapter 3: Third-Party Client Tool Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Third-Party Client Tool Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

BusinessObjects Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Step 1. Update the BusinessObjects Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Step 2. Create the ODBC Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

IBM Cognos Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Step 1. Update the IBM Cognos Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Table of Contents i

Step 2. Create the ODBC Connection and Import Metadata. . . . . . . . . . . . . . . . . . . . . . . . . . . 10

MicroStrategy Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Step 1. Create the Database Instance and Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Step 2. Configure the SQL Generation Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

QlikView Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

SQuirreL SQL Client Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Step 1. Copy the Driver File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Step 2. Create the Driver and Alias. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

WinSQL Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Appendix A: Troubleshooting Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Troubleshooting JDBC Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Troubleshooting ODBC Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

ii Table of Contents

PrefaceThe Informatica Data Services JDBC/ODBC Connection Guide explains how to connect to an SQL data service sothat you can run SQL queries against virtual tables and run virtual stored procedures. This guide is written for endusers that need to configure client machines and third-party JDBC or ODBC client tools. End users connect toSQL data services through third-party tools to run SQL queries against virtual tables and run virtual storedprocedures.

Informatica Resources

Informatica Customer PortalAs an Informatica customer, you can access the Informatica Customer Portal site at http://mysupport.informatica.com. The site contains product information, user group information, newsletters,access to the Informatica customer support case management system (ATLAS), the Informatica How-To Library,the Informatica Knowledge Base, the Informatica Multimedia Knowledge Base, Informatica ProductDocumentation, and access to the Informatica user community.

Informatica DocumentationThe Informatica Documentation team takes every effort to create accurate, usable documentation. If you havequestions, comments, or ideas about this documentation, contact the Informatica Documentation team throughemail at [email protected]. We will use your feedback to improve our documentation. Let usknow if we can contact you regarding your comments.

The Documentation team updates documentation as needed. To get the latest documentation for your product,navigate to Product Documentation from http://mysupport.informatica.com.

Informatica Web SiteYou can access the Informatica corporate web site at http://www.informatica.com. The site contains informationabout Informatica, its background, upcoming events, and sales offices. You will also find product and partnerinformation. The services area of the site includes important information about technical support, training andeducation, and implementation services.

Informatica How-To LibraryAs an Informatica customer, you can access the Informatica How-To Library at http://mysupport.informatica.com.The How-To Library is a collection of resources to help you learn more about Informatica products and features. It

iii

http://mysupport.informatica.com

mailto:[email protected]


http://www.informatica.com


includes articles and interactive demonstrations that provide solutions to common problems, compare features andbehaviors, and guide you through performing specific real-world tasks.

Informatica Knowledge BaseAs an Informatica customer, you can access the Informatica Knowledge Base at http://mysupport.informatica.com.Use the Knowledge Base to search for documented solutions to known technical issues about Informaticaproducts. You can also find answers to frequently asked questions, technical white papers, and technical tips. Ifyou have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Baseteam through email at [email protected].

Informatica Multimedia Knowledge BaseAs an Informatica customer, you can access the Informatica Multimedia Knowledge Base at http://mysupport.informatica.com. The Multimedia Knowledge Base is a collection of instructional multimedia filesthat help you learn about common concepts and guide you through performing specific tasks. If you havequestions, comments, or ideas about the Multimedia Knowledge Base, contact the Informatica Knowledge Baseteam through email at [email protected].

Informatica Global Customer SupportYou can contact a Customer Support Center by telephone or through the Online Support. Online Support requiresa user name and password. You can request a user name and password at http://mysupport.informatica.com.

Use the following telephone numbers to contact Informatica Global Customer Support:

North America / South America Europe / Middle East / Africa Asia / Australia

Toll FreeBrazil: 0800 891 0202Mexico: 001 888 209 8853North America: +1 877 463 2435 Standard RateNorth America: +1 650 653 6332

Toll FreeFrance: 00800 4632 4357Germany: 00800 4632 4357Israel: 00800 4632 4357Italy: 800 915 985Netherlands: 00800 4632 4357Portugal: 800 208 360Spain: 900 813 166Switzerland: 00800 4632 4357 or 0800 463200United Kingdom: 00800 4632 4357 or 0800023 4632 Standard RateFrance: 0805 804632Germany: 01805 702702Netherlands: 030 6022 797

Toll FreeAustralia: 1 800 151 830New Zealand: 1 800 151 830Singapore: 001 800 4632 4357 Standard RateIndia: +91 80 4112 5738

iv Preface






C H A P T E R 1

SQL Data Service ConnectionsThis chapter includes the following topic:

¨ SQL Data Service Connections Overview, 1

SQL Data Service Connections OverviewAn SQL data service is a virtual database that you can query. It provides a uniform view of data that might bescattered among disparate, heterogeneous data sources. You can use a third-party JDBC or ODBC client tool torun SQL queries against the virtual tables in an SQL data service and to run virtual stored procedures.

An SQL data service can contain the following objects:

¨ Virtual schemas that define the database structure

¨ Virtual tables

¨ Virtual table mappings that define the flow of data between sources and a virtual table

¨ Virtual stored procedures that take optional inputs through parameters, transform the data, and optionallyreturn output through parameters

To make the virtual tables and virtual stored procedures available to you, a developer creates and deploys anapplication that contains the SQL data service. The developer deploys the application to a Data IntegrationService and an administrator runs the application. When the application is running, you can query the virtual tablesand run the virtual stored procedures in the SQL data service.

When you query a virtual table or run a virtual stored procedure, the JDBC or ODBC driver sends the request tothe Data Integration Service. By default, the driver uses HTTP to communicate with the Data Integration Service. Ifan administrator enables Transport Layer Security (TLS) for the domain, the driver uses TLS to communicate withthe Data Integration Service.

Before you can run SQL queries or virtual stored procedures for the first time, you must configure the machinefrom which you want to access the SQL data service. You must also configure the client tool so that it can connectto the SQL data service.

1

C H A P T E R 2

Client Machine ConfigurationThis chapter includes the following topics:

¨ Client Machine Configuration Overview, 2

¨ JDBC Client Connections, 3

¨ ODBC Client Connections on Windows, 4

¨ ODBC Client Connections on UNIX, 5

Client Machine Configuration OverviewBefore you can connect to an SQL data service through a third-party client tool, you must configure the machinethat you want to connect from. You configure the machine differently based on whether you connect through aJDBC or ODBC client tool.

Before you can configure the JDBC or ODBC client machine, you must get domain information from theInformatica administrator. If the Informatica administrator enables result set caching for the SQL data service, youmust also decide if you want the ability to cache the results or retrieve results from the cache.

Client Machine Configuration RequirementsThe domain information is required to construct the JDBC URL or ODBC connection string for the client tool.

The following table describes the domain information required to configure the JDBC or ODBC connection on theclient machine:

Required Information Description

Data Integration Service name Data Integration Service where the application that contains the SQL data service runs.

Domain host name Machine that hosts the Informatica domain.

Domain HTTP port Informatica domain HTTP port number.

Runtime SQL data service name SQL data service that contains the virtual tables you want to query or the virtual storedprocedures you want to run.By default, the runtime SQL data service name is:<application name>.<SQL data service name>where <application name> is the name of the application that contains the SQL dataservice.

2

Required Information Description

Security domain name Informatica security domain name. Required if the security domain is not native.

User name Informatica domain user name. Required if you cannot enter this information in the JDBCor ODBC client tool.

User password Informatica domain user password. Required if you cannot enter this information in theJDBC or ODBC client tool.

Result Set CachingResult set caching enables the Data Integration Service to use cached results for SQL data service queries andweb service requests. You can disable result set caching for an SQL data service query when the SQL dataservice is configured to cache the result set.

Users that run identical queries in a short period of time may want to use result set caching to decrease theruntime of identical queries.

When you disable result set caching, the Data Integration Service does not cache the results of the query and itwill not use the result set cache to return the query results. To disable result set caching for all SQL queries,append the following to the end of the JDBC URL or ODBC connection string:&SQLDataServiceOptions.disableResultSetCache=true

JDBC Client ConnectionsYou can connect to an SQL data service through a JDBC client tool such as the SQL SQuirreL Client.

Before you can connect to an SQL data service through a JDBC client tool, you must perform the following tasks:

1. Install the Informatica JDBC driver.

2. Update the CLASSPATH environment variable.

Note: The Informatica JDBC driver does not support the setBigInt method. If you use setBigInt in a parameterizedquery, the Java client code fails at compilation. If you need to bind data to a bigint column, use the setLongmethod.

Installing the Informatica JDBC DriverInstall the Informatica JDBC driver on the machine you connect to the SQL data service from. To install the driver,run the Informatica JDBC/ODBC driver installation program.

The Informatica JDBC driver version must match the Data Integration Service version. For example, version 9.1.0of the Informatica JDBC driver is not compatible with version 9.0.1 of the Data Integration Service. Similarly,version 9.0.1 of the Informatica JDBC driver is not compatible with version 9.1.0 of the Data Integration Service.

Updating the CLASSPATHUpdate the CLASSPATH environment variable to include the JDBC driver. The JDBC driver is compiled with Java6.

JDBC Client Connections 3

The JDBC driver is installed in the following location:

<Informatica Installation Directory>\jdbcdrv\infadsjdbc.jar

Connecting to the SQL Data ServiceYou can connect to an SQL data service through a JDBC client tool.

To connect through a JDBC client tool, the CLASSPATH environment variable on the machine where the clienttool runs must include the JDBC driver.

1. Open the JDBC client tool.

2. Enter the following information:

Option Value

Class name com.informatica.ds.sql.jdbcdrv.INFADriver

JDBC URL jdbc:informatica:sqlds/<optional security domain\><optional user name>/<optional user password>@<domain host name>:<domain HTTP port>?dis=<Data Integration Service name>&sqlds=<runtime SQL data service name>

ODBC Client Connections on WindowsYou can connect to an SQL data service through an ODBC client tool such as QlikView or WinSQL.

Before you can connect to an SQL data service through an ODBC client tool on Windows, you must perform thefollowing tasks:

1. Install the Informatica ODBC driver.

2. Configure the Informatica ODBC driver.

Installing the Informatica ODBC Driver on WindowsInstall the Informatica ODBC driver on the machine you connect to the SQL data service from. To install the driver,run the Informatica JDBC/ODBC driver installation program.

The Informatica JDBC/ODBC driver installation program updates the system path to include the Java VirtualMachine (jvm.dll) directory. If you install the ODBC driver on a machine with a Windows 64-bit operating system,you must restart the machine after you run the Informatica JDBC/ODBC driver installation program.

Configuring the Informatica ODBC DriverBefore you can connect to an SQL data service through an ODBC client tool on Windows, you must configure theInformatica ODBC driver.

1. Open the Administrative Tools from the Windows Control Panel.

2. Open the Data Sources (ODBC) shortcut.

The ODBC Data Source Administrator appears.

3. Click Add.

4. Select the Informatica Data Services ODBC Driver.

4 Chapter 2: Client Machine Configuration

5. Click Finish.

6. Configure the driver with the following options:

Option Value

DSN name Any valid data source name.

Connect string jdbc:informatica:sqlds/<optional security domain\><optional user name>/<optional user password>@<domain host name>:<domain HTTP port>?dis=<Data Integration Service name>&sqlds=<runtime SQL data service name>

JDBC Jar <Informatica Installation Directory>\jdbcdrv\infadsjdbc.jar

Treat Length as Characters (DeferredParameters) *

Enabled

Multi-threaded application Enabled

. *Enable this option only for MicroStrategy.

Connecting to the SQL Data ServiceYou can connect to an SQL data service through an ODBC client tool on Windows.

To connect to an SQL data service through an ODBC client tool on Windows, the PATH environment variable onthe Windows machine must include the Java Virtual Machine (jvm.dll) directory. The Informatica Data ServicesODBC Driver must also be configured on the machine.

1. Open the ODBC client tool.

2. Enter the connect string and JDBC Jar file location.

ODBC Client Connections on UNIXYou can connect to an SQL data service through an ODBC client tool such as IBM Cognos.

Before you can connect to an SQL data service through an ODBC client tool on UNIX, you must perform thefollowing tasks:

1. Install the Informatica ODBC driver.

2. Update the shared library environment variable.

3. Update odbc.ini.

Installing the Informatica ODBC Driver on UNIXInstall the Informatica ODBC driver on the machine you connect to the SQL data service from. To install the driver,run the Informatica JDBC/ODBC driver installation program.

Updating the Shared Library Environment VariableSet the shared library environment variable based on the operating system.

ODBC Client Connections on UNIX 5

Update the shared library environment variable to include the directories where the Java Virtual Machine andDriver Manager library files exist.

The following table describes the shared library environment variable for each operating system:

Operating System Shared Library Environment Variable

AIX LIBPATH

HP-UX SHLIB_PATH or LD_LIBRARY_PATH

Linux LD_LIBRARY_PATH

Solaris LD_LIBRARY_PATH

Update the shared library environment variable to include the following directories:

¨ The directory where the platform libjvm or j9vm library resides.

¨ The directory where the libodbc and libodbcinst libraries reside. This is usually the Driver Manager lib directory.

Updating odbc.iniBefore you can connect to an SQL data service through an ODBC client tool on UNIX, you must update odbc.ini.

1. Edit odbc.ini or copy odbc.ini to the home directory and edit it. This file exists in the $ODBCHOME directory.$ cp $ODBCHOME/odbc.ini $HOME/.odbc.ini

2. Add an entry for the ODBC user under the section [<user name>_odbc]. For example:[<user name>_odbc]ConnectionString=jdbc:informatica:sqlds/<optional security domain\><optional user name>/<optional user password>@<domain host name>:<domain HTTP port>?dis=<Data Integration Service name>&sqlds=<runtime SQL data service name>Driver=$ODBC_DRIVER_INSTALL_LOCATION/bin/$OS/libinfadsodbc.soIsMultiThreaded=trueJDBCDriverLocation=<Informatica Installation Directory>/jdbcdrv/infadsjdbc.jarUseDetach=falseWCHARLengthInChars=true

Configure WCHARLengthInChars only for MicroStrategy.

Connecting to the SQL Data ServiceYou can connect to an SQL data service through an ODBC client tool on UNIX.

To connect to an SQL data service through an ODBC client tool on UNIX, the shared library environment variableon the UNIX machine must include the correct directories. The odbc.ini file must also be configured on themachine.

1. Open the ODBC client tool.

2. Enter the connection string and JDBC driver location.

6 Chapter 2: Client Machine Configuration

C H A P T E R 3

Third-Party Client ToolConfiguration

This chapter includes the following topics:

¨ Third-Party Client Tool Configuration Overview, 7

¨ BusinessObjects Configuration, 7

¨ IBM Cognos Configuration, 9

¨ MicroStrategy Configuration, 11

¨ QlikView Configuration, 12

¨ SQuirreL SQL Client Configuration, 13

¨ WinSQL Configuration, 14

Third-Party Client Tool Configuration OverviewBefore you can connect to an SQL data service, you must configure the JDBC or ODBC third-party client tool thatyou want to connect from.

You can connect to an SQL data service through the following third-party client tools:

¨ BusinessObjects

¨ IBM Cognos

¨ MicroStrategy

¨ QlikView

¨ SQuirreL SQL Client

¨ WinSQL

BusinessObjects ConfigurationYou can access the virtual data in an SQL data service through a BusinessObjects universe. Import metadata fromthe SQL data service into the universe. Use a BusinessObjects application to query the data or generate reports.

7

To configure BusinessObjects to access an SQL data service, complete the following tasks:

1. Update the BusinessObjects Connection Server configuration file to include Informatica Java Virtual Machine(JVM) information.

2. Create an ODBC connection to the SQL data service in the BusinessObjects universe.

After you perform these tasks, you can import metadata from an SQL data service into the universe and generatereports based on the data.

Step 1. Update the BusinessObjects Configuration FileBusinessObjects Connection Server is the data access software that manages the connection between aBusinessObjects application and a data source. To use an SQL data service as a data source, you must updatethe BusinessObjects Connection Server configuration file, cs.cfg. Update the configuration file to replace theBusinessObjects JVM with the Informatica JVM, version 1.6.

The BusinessObjects XI 3.1 configuration file, cs.cfg, is in the following directory:

<BusinessObjects Installation Directory>\BusinessObjects Enterprise 12.0\win32_x86\dataAccess\connectionServer\

1. Open cs.cfg in a text editor.

2. Find the JavaVM element.

3. In the LibraryName element, replace the JVM directory with the Informatica JVM directory and replace theJNIVersion with the Informatica JVM version.For example, change the following lines:

<JavaVM> <LibraryName JNIVersion="JNI_VERSION_1_4"> C:\Program Files\Business Objects\javasdk\jre6\bin\client\jvm.dll </LibraryName></JavaVM>

To:<JavaVM> <LibraryName JNIVersion="JNI_VERSION_1_6"> C:\Informatica\9.0\java\jre\bin\server\jvm.dll </LibraryName></JavaVM>

Note: You must specify an absolute path for the Informatica JVM directory.

4. Save and close cs.cfg.

Step 2. Create the ODBC ConnectionCreate the ODBC connection through a BusinessObjects application such as BusinessObjects Designer. To createthe ODBC connection, use the application New Connection wizard.

1. Open the Business Objects application New Connection wizard.

2. Click Add to create a connection.

The Define a new connection dialog box, Database Middleware Selection page appears.

3. Enter a connection name and select a generic ODBC or ODBC3 data source driver.

4. Click Next.

The Login Parameters page appears.

8 Chapter 3: Third-Party Client Tool Configuration


Option Description

Authentication Mode Select Use specified username and password.

User name Informatica domain user name.

Password Informatica domain user password.

Data source name ODBC data source name for the SQL data service.

6. Click Test Connection to test the connection.

The BusinessObjects application displays a message saying that the server is responding.

7. Click OK.

IBM Cognos ConfigurationIBM Cognos Framework Manager is a modeling tool that allows you to create and manage business-relatedmetadata for use in all Cognos 8 BI applications. Use Framework Manager to create a project. Within a project,you can create data source connections and import data source metadata.

When you define a data source in Framework Manager, you create an ODBC connection to the SQL data service.Cognos uses the information in the connection to connect to the SQL data service. After you create the ODBCconnection and import the SQL data service metadata, you can create a Cognos model based on the SQL dataservice. Use the model to run queries and generate reports in Cognos BI applications.

To run queries that include aggregations, the Cognos configuration file must include Informatica ODBC driverinformation.

To configure IBM Cognos to access an SQL data service, complete the following tasks:

1. Update the IBM Cognos configuration file to include the Informatica ODBC driver information.

2. Create an ODBC connection to the SQL data service, and import SQL data service metadata in a Cognosproject.

Step 1. Update the IBM Cognos Configuration FileUpdate the IBM Cognos configuration file to include Informatica ODBC driver information. The ODBC driverinformation in the configuration file enables the Data Integration Service to handle SQL queries that includeaggregations. If you do not update the configuration file and you query an SQL data service from an IBM Cognosapplication, the query might fail if it includes aggregations.

The IBM Cognos configuration file, cogdmod.ini, is in the following directories:

¨ C:\Program Files\cognos\tools\c8\bin\¨ C:\Program Files\cognos\c8\bin\You must update both copies of the configuration file.

1. Stop the Cognos service.

2. Back up both copies of cogdmod.ini.

IBM Cognos Configuration 9

3. Add the following entry to both copies of cogdmod.ini:[Exceptions Set Operators DRIVER:INFADSODBC.DLL]Distinct="distinct"Except="except"Except_All=TIntersect="intersect"Intersect_All=TUnion="union"Union_All=T[Exceptions Tables DRIVER:INFADSODBC.DLL]Derived=TJoined=TSimple=TUniqueName_Prefix="coguda"[Exceptions OLAP Functions DRIVER:INFADSODBC.DLL]Olap_Max="max"Olap_Min="min"Olap_Sum="sum"Olap_Avg="avg"Olap_Count="count"Olap_Count_Star="count(*)"Olap_Distinct="distinct"

4. Restart the Cognos service.

Step 2. Create the ODBC Connection and Import MetadataCreate the ODBC connection and import SQL data service metadata into a project. Use Cognos FrameworkManager to create the project. Run the Framework Manager Run Metadata wizard to create the connection andimport metadata.

1. Start Cognos Framework Manager.

2. Create a project.

3. Start the Run Metadata wizard.

4. In the Select Metadata Source window, click Data Sources.

5. Click Next.

The Select Data Source window appears.

6. Click New.

The New Data Source wizard appears.

7. In the name and description page, enter a name and optional description for the data source.

8. Click Next.

9. In the connection page, select the ODBC database type, select an isolation level, and click Next.

10. In the connection string page, enter the SQL data service ODBC data source name in the ODBC data sourceand ODBC connect string fields. Enter timeouts or sign-on information, if required. Enter the user ID andpassword if they are not part of the Informatica ODBC driver connect string.

11. Click Test the connection to test the connection to the Informatica ODBC driver.

12. In the Run Metadata wizard, select the data source.

13. Click Next.

14. In the Select Objects page, select the objects you want to import and specify how the import handlesduplicate object names.

15. Specify the criteria to use to create relationships and click Import.

Framework Manager displays the number of imported objects and a list of objects that it could not import.

16. Click Finish.


MicroStrategy ConfigurationMicroStrategy is a business intelligence platform that allows you to analyze, distribute, and customize businessinformation. MicroStrategy Desktop allows you to create projects and reports. Within a project, you can create datasource connections and import data source metadata.

To configure MicroStrategy to access an SQL data service, complete the following tasks:

1. Create the database instance and connection.

2. Configure the SQL generation options.

Step 1. Create the Database Instance and ConnectionUse MicroStrategy Desktop to create the database instance and database connection. MicroStrategy retrievesSQL data service metadata through the database instance.

1. Open MicroStrategy Desktop.

2. Create a project.

3. Select Schema > Warehouse Catalog to open the project Warehouse Catalog.

The Warehouse Database Instance dialog box appears.

4. Click New.

The Database Instance Wizard opens.

5. Click Next.

6. In the Database Instance General Information page, enter a name for the database instance and selectGeneric DBMS as the database type.

7. Click Next.

8. In the ODBC Data Source Information page, select the ODBC data source name for the SQL data serviceand enter the Informatica domain user name and password.

9. Click Finish.

10. Click OK to close the Warehouse Database Instance dialog box.

11. Select Schema > Warehouse Catalog to open the Warehouse Catalog.

12. Click Options.

13. Select Warehouse Connection.

14. In the Warehouse Connection settings, select the database instance and click Edit.

The Database Instances dialog box opens.

15. Click New to create a database connection.

The Database Connections dialog box opens.

16. On the General tab, enter a database connection name and select the ODBC data source name for the SQLdata service.

17. Click the Advanced tab.

18. Set the following options:

¨ Select the Multi-threaded database driver mode.

¨ Select the Use parameterized queries option.

¨ Set the character set encoding option for Windows and UNIX drivers to UTF-8.

19. Click OK to close the Database Connections dialog box.

MicroStrategy Configuration 11

20. Click OK to close the Database Instances dialog box.

21. In the Warehouse Catalog, select Read Settings.

22. In the Read Settings, select Use standard ODBC calls to obtain the database catalog.

23. Click OK.

24. In the Warehouse Catalog, click Save and Close to save the changes.

Step 2. Configure the SQL Generation OptionsThe virtual tables in an SQL data service are read-only tables. Configure the SQL generation options to preventMicroStrategy Desktop users from trying to write data to the virtual database.

1. Select Schema > SQL Generation Options to open the SQL generation options.

2. In the SQL Data Warehouses settings, select the database instance you use to connect to the SQL dataservice.

3. Click VLDB Properties to edit the VLDB properties for the database instance.

4. Open the Tables settings.

5. In the Drop Temp Tables Method settings, set the drop temp table method to Do nothing.

6. In the Intermediate Table Type settings, set the intermediate table type to Derived table.

7. In the Table Creation Type settings, set the table creation type to Implicit Table.

8. In the CREATE and INSERT Support settings, select the Create and insert are not supported option.

9. Save and close the SQL generation options.

QlikView ConfigurationYou can access the virtual data in an SQL data service through QlikView. To read data from an SQL data serviceinto your QlikView document, use the Script Editor. The script that you create uses an ODBC connection toconnect to and retrieve data from the SQL data service.

1. Create a QlikView document.

2. Select File > Edit Script.

The Edit Script dialog box appears.

3. In the Data view, select ODBC as the database and click Connect.

The Connect to Data Source dialog box appears.

4. Select the ODBC data source name for the SQL data service and enter the user name and password for theInformatica domain user.

5. Click Test Connection to test the connection.

6. Click OK to close the connection results.

7. Click OK to close the Connect to Data Source dialog box.

8. In the Data view of the Edit Script dialog box, click Select to create an SQL SELECT statement that retrievesinformation from the SQL data service.

9. Click OK.

10. Run the script to retrieve data from the SQL data service.


SQuirreL SQL Client ConfigurationYou can access the virtual data in an SQL data service through SQuirreL SQL Client. SQuirreL SQL Client allowsyou to view the structure of a database and browse and query the data.

To configure SQuirreL SQL Client to access an SQL data service, complete the following tasks:

1. Copy the Informatica JDBC driver to the SQuirreL SQL Client library directory.

2. Create the Informatica JDBC driver and the database alias in SQuirreL SQL Client.

After you perform these tasks, you can import data from an SQL data service into SQuirreL SQL Client.

Step 1. Copy the Driver FileCopy the Informatica JDBC driver to the SQuirreL SQL Client library directory.

u Copy the Informatica JDBC driver, infadsjdbc.jar, from the following directory:

<Informatica Installation Directory>\jdbcdrv\To the following directory:

<SQuirreL SQL Client Installation Directory>\lib\

Step 2. Create the Driver and AliasTo read data from an SQL data service into SQuirreL SQL Client, create a driver definition and a database alias.SQuirreL SQL Client uses the driver definition and the database alias to enable you to view the SQL data servicestructure, browse the data in virtual tables, and enter SQL queries.

1. Open the Drivers list window.

2. Select Drivers > New Driver.

The Add Driver dialog box appears.


Option Description

Name Informatica JDBC Driver

Example URL jdbc:informatica:sqlds/<optional security domain\><optional user name>/<optionaluser password>@<domain host name>:<domain HTTP port>?dis=<Data IntegrationService name>&sqlds=<runtime SQL data servicename>

Website URL jdbc:informatica:sqlds/<optional security domain\><optional user name>/<optionaluser password>@<domain host name>:<domain HTTP port>?dis=<Data IntegrationService name>&sqlds=<runtime SQL data servicename>

Extra Class Path <Informatica Installation Directory>\jdbcdrv\infadsjdbc.jar

Class Name com.informatica.ds.sql.jdbcdrv.INFADriver

4. Click OK.

SQuirreL SQL Client displays a message saying that driver registration is successful.

5. Open the Aliases list window.

SQuirreL SQL Client Configuration 13

6. Select Aliases > New Alias.

The Add Alias dialog box appears.


Option Description

Name Alias name.

Driver Select the new driver.

URL jdbc:informatica:sqlds/<optional security domain\><optional user name>/<optionaluser password>@<domain host name>:<domain HTTP port>?dis=<Data IntegrationService name>&sqlds=<runtime SQL data servicename>

User Name Informatica domain user name.


8. Click Test.

SQuirreL SQL Client displays a message saying that the connection is successful.

9. Click OK.

WinSQL ConfigurationYou can access the virtual data in an SQL data service through WinSQL. To read data from an SQL data serviceinto WinSQL, create a new connection. WinSQL imports data from the SQL data service based on the connectioninformation.

1. Create a query.

2. Select File > New Connection.

The ODBC Data Source dialog box appears.


Option Description

Data Source Name Select the ODBC data source name for the SQL data service.

User ID Informatica domain user name.


Database Type (WinSQL Plugin) Select Generic ODBC.

4. Click OK.


A P P E N D I X A

Troubleshooting ConnectionsThis appendix includes the following topics:

¨ Troubleshooting JDBC Connections, 15

¨ Troubleshooting ODBC Connections, 15

Troubleshooting JDBC Connections

I am connecting to an SQL data service through a JDBC client tool. I get an error when I try to bind data to abigint column through a parameterized query.The Informatica JDBC driver does not support the setBigInt method. If you use setBigInt in a parameterized query,the Java client code fails at compilation.

If you need to bind data to a bigint column, use the setLong method instead of the setBigInt method. For example,the following code does not cause a JDBC driver error:

String sql = "select * from VT where COL_BIGINT = ?";PreparedStatement stmt = connection.prepareStatement(sql);stmt.setLong (1,new Long("9223372036854775807"));

Troubleshooting ODBC Connections

The ODBC application consumes large amounts of data.Increase the maximum amount of memory available to the Java Virtual Machine (the -Xmx value).

To increase the -Xmx value, set the environment variable INFA_ODBCJVM to -Xmx??m, where ?? is the numberof megabytes. For example, to set the -Xmx value to 64 MB, set INFA_ODBCJVM to -Xmx 64m. If you set the -Xmx value to a very large value, for example >500 MB, the Memory Manager may not be able to allocate thememory.

I am connecting to an SQL data service through the BusinessObjects Designer but I get the error, "The serveris not responding! (SBO0001). CS: Error on Connect."The Java Virtual Machine in BusinessObjects versions 11 and 12 does not load the Informatica JDBC driver. TheJVM also uses version 5 of the Java Runtime Environment (JRE), while Informatica requires JRE version 6.

15

To work around this issue, update the CLASSPATH on the machine that runs the BusinessObjects Designer sothat it includes the JDBC driver directory. By default, the JDBC driver is installed in the following directory:

<Informatica Installation Directory>\jdbcdrv\

After you update the CLASSPATH, configure the BusinessObjects JVM to use JRE version 6.

1. Stop all BusinessObjects services on the machine.

2. Back up the contents of the default JRE directory:

<BusinessObjects Installation Directory>\javasdk\jre\3. Go to the JRE version 6 directory:

<BusinessObjects Installation Directory>\javasdk\jre6\4. Copy the contents of the JRE version 6 directory to the default JRE directory.

5. Go to the JRE bin directory:

<BusinessObjects Installation Directory>\javasdk\jre\bin\6. Create a server subdirectory in the JRE bin directory.

7. Go to the JRE client directory:

<BusinessObjects Installation Directory>\javasdk\jre\bin\client\8. Copy the contents of the JRE client directory to the server subdirectory:

<BusinessObjects Installation Directory>\javasdk\jre\bin\server\9. Restart BusinessObjects services.

16 Appendix A: Troubleshooting Connections

I N D E X

BBusinessObjects

configuration 8connection error 15creating the ODBC connection 8updating the configuration file 8

CCLASSPATH

updating 4configuration

BusinessObjects 8client machine configuration 2client tool configuration 7disable result set caching 3IBM Cognos 9MicroStrategy 11QlikView 12SQuirreL SQL Client 13WinSQL 14

connectionsoverview 1protocol 1

IIBM Cognos

configuration 9creating the ODBC connection 10updating the configuration file 9

Informatica JDBC driverinstalling 3

Informatica ODBC driverconfiguring 4installing on UNIX 5installing on Windows 4

JJDBC client connections

connecting to an SQL data service 4installing the driver 3overview 3troubleshooting 15updating the CLASSPATH 4

JVMincreasing memory available 15

LLD_LIBRARY_PATH

updating 6LIBPATH

updating 6

MMicroStrategy

configuration 11configuring SQL generation options 12creating the database instance 11

OODBC client connections on UNIX

connecting to an SQL data service 6installing the driver 5overview 5troubleshooting 15updating odbc.ini 6updating the shared library 6

ODBC client connections on Windowsconfiguring the driver 4connecting to an SQL data service 5installing the driver 4overview 4troubleshooting 15

odbc.iniupdating 6

Pparameterized queries

troubleshooting 15

QQlikView

configuration 12

Rresult set caching

disabling 3

17

Sshared library environment variable

updating 6SHLIB_PATH

updating 6SQL data service connections

overview 1SQL data services

connecting through JDBC 4connecting through ODBC on UNIX 6connecting through ODBC on Windows 5JDBC client connections 3ODBC client connections on UNIX 5ODBC client connections on Windows 4

SQuirreL SQL Clientconfiguration 13copying the driver file 13creating the driver and alias 13

Tthird-party client tools

supported third-party tools 7

WWinSQL

configuration 14

18 Index

in 910hf1 jodbcconnectionguide en

Documents