ibi open visualizations release 8207...preface this document describes how to install, configure,...

ibi Open VisualizationsRelease 8207

September 04, 2020

Active Technologies, EDA, EDA/SQL, FIDEL, FOCUS, Information Builders, the Information Builders logo, iWay, iWaySoftware, Parlay, PC/FOCUS, RStat, Table Talk, Web390, WebFOCUS, WebFOCUS Active Technologies, and WebFOCUSMagnify are registered trademarks, and DataMigrator and Hyperstage are trademarks of Information Builders, Inc.

Adobe, the Adobe logo, Acrobat, Adobe Reader, Flash, Adobe Flash Builder, Flex, and PostScript are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Due to the nature of this material, this document refers to numerous hardware and software products by theirtrademarks. In most, if not all cases, these designations are claimed as trademarks or registered trademarks by theirrespective companies. It is not this publisher's intent to use any of these names generically. The reader is thereforecautioned to investigate all claimed trademark rights before using any of these names other than to refer to the productdescribed.

Copyright © 2020, by Information Builders, Inc. and iWay Software. All rights reserved. Patent Pending. This manual, orparts thereof, may not be reproduced in any form without the written permission of Information Builders, Inc.

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Information You Should Have . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

User Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Information Builders Consulting and Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1. Introducing ibi Open Visualizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

ibi Open Visualizations Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

ibi Open Visualizations Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

ibi Open Visualizations Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2. Introducing the ibi ODBC Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

What Is Open Database Connectivity? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

What Is an ODBC Driver? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

ODBC Application Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

ibi ODBC Connector Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Supported Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3. Installing the ibi Client on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Installing and Configuring ibi Open Visualizations on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4. Installing the ibi Client on Linux or UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Installing and Configuring ibi Open Visualizations on Linux or UNIX . . . . . . . . . . . . . . . . . . . . . . . . . 37

5. Using Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Using the ODBC Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Using ODBC Escape Clauses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Issuing Your Own SQL Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

6. Introducing the ibi JDBC Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Using the JDBC Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

7. Using Python With the ODBC and JDBC Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Using Python From Jupyter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

ibi Open Visualizations 3

Contents

4 Information Builders

Preface

This document describes how to install, configure, and use ibi Open Visualizations, a datavirtualization solution that easily connects your BI platform to virtually any database, fileformat, or web service in your Enterprise.

How This Manual Is Organized

This manual includes the following chapters:

Chapter/Appendix Contents

1 Introducing ibi OpenVisualizations

Introduces the ibi Open Visualizations datavirtualization solution that easily connects yourexisting BI platform to virtually any database, fileformat, application, or web service in yourEnterprise.

2 Introducing the ibi ODBCConnector

Introduces the ibi ODBC Connector.

3 Installing the ibi Client onWindows

Describes how to install and configure the ibi Clienton Windows platforms.

4 Installing the ibi Client onLinux or UNIX

Describes how to install and configure the ibi Clienton Linux or UNIX platforms.

5 Using Applications Describes how to use the ibi ODBC Connector fromMicrosoft Access®, Microsoft Excel®, MicrosoftPower BI®, and Tableau® to create visualizations.

6 Introducing the ibi JDBCConnector

Introduces the ibi JDBC Connector.

7 Using Python With the ODBCand JDBC Connectors

Describes how to use Python from Jupyter with theODBC and JDBC Connectors.

Conventions

The following table lists and describes the conventions that apply in this manual.


Convention Description

THIS TYPEFACE

or

this typeface

Denotes syntax that you must enter exactly as shown.

this typeface Represents a placeholder (or variable), a cross-reference, or animportant term.

underscore Indicates a default setting.

this typeface Highlights a file name or command. It may also indicate a button,menu item, or dialog box option you can click or select.

Key + Key Indicates keys that you must press simultaneously.

{ } Indicates two or three choices; type one of them, not the braces.

[ ] Indicates a group of optional parameters. None is required, but youmay select one of them. Type only the parameter in the brackets,not the brackets.

| Separates mutually exclusive choices in syntax. Type one of them,not the symbol.

... Indicates that you can enter a parameter multiple times. Type onlythe parameter, not the ellipsis points (...).

.

.

.

Indicates that there are (or could be) intervening or additionalcommands.

Related Publications

To view a current listing of our publications and to place an order, visit our Technical ContentLibrary, http://documentation.informationbuilders.com. You can also contact the PublicationsOrder Department at (800) 969-4636.

Customer Support

Do you have any questions about this product?

Related Publications


http://documentation.informationbuilders.com

Join the Focal Point community. Focal Point is our online developer center and more than amessage board. It is an interactive network of more than 3,000 developers from almost everyprofession and industry, collaborating on solutions and sharing tips and techniques. AccessFocal Point at http://forums.informationbuilders.com/eve/forums.

You can also access support services electronically, 24 hours a day, with InfoResponseOnline. InfoResponse Online is accessible through our website, http://www.informationbuilders.com. It connects you to the tracking system and known-problemdatabase at the Information Builders support center. Registered users can open, update, andview the status of cases in the tracking system and read descriptions of reported softwareissues. New users can register immediately for this service. The technical support section of www.informationbuilders.com also provides usage techniques, diagnostic tips, and answers tofrequently asked questions.

Call Information Builders Customer Support Services (CSS) at (800) 736-6130 or (212)736-6130. Customer Support Consultants are available Monday through Friday between 8:00a.m. and 8:00 p.m. EST to address all your questions. Information Builders consultants canalso give you general guidance regarding product capabilities. Please be ready to provide yoursix-digit site code number (xxxx.xx) when you call.

To learn about the full range of available support services, ask your Information Buildersrepresentative about InfoResponse Online, or call (800) 969-INFO.

Information You Should Have

To help our consultants answer your questions effectively, be prepared to provide the followinginformation when you call:

Your six-digit site code (xxxx.xx).

Your Open Visualizations configuration:

The front-end you are using, including vendor and release. For example, Microsoft Excel2019.

The connector you are using, for example, ODBC or JDBC.

The ibi Client software version. You can find this information on Windows from theODBC Data Sources application on the Drivers tab.

The ibi Server version and release. You can find this information using the Versionoption in the Web Console.

The Master and Access Files, if available from the ibi Server.

Preface


http://forums.informationbuilders.com/eve/forums

http://www.informationbuilders.com



The exact nature of the problem:

The error message and return code, if applicable.

Is this related to any other problem?

Has the procedure or query ever worked in its present form? Has it been changed recently?How often does the problem occur?

What release of the operating system are you using? Has it, your security system,communications protocol, or front-end software changed?

Is this problem reproducible? If so, how?

Have you tried to reproduce your problem in the simplest form possible? For example, if youare having problems joining two data sources, have you tried executing a query containingjust the code to access the data source?

Do you have a trace file?

How is the problem affecting your business? Is it halting development or production? Doyou just have questions about functionality or documentation?

User Feedback

In an effort to produce effective documentation, the Technical Content Management staffwelcomes your opinions regarding this document. You can contact us through our website, http://documentation.informationbuilders.com/connections.asp.

Thank you, in advance, for your comments.

Information Builders Consulting and Training

Interested in training? Information Builders Education Department offers a wide variety oftraining courses for this and other Information Builders products.

For information on course descriptions, locations, and dates, or to register for classes, visitour World Wide Web site (http://www.informationbuilders.com) or call (800) 969-INFO to speakto an Education Representative.

User Feedback


http://documentation.informationbuilders.com/connections.asp

Chapter1Introducing ibi Open Visualizations

ibi Open Visualizations is a data virtualization solution that easily connects your existingBI platform to virtually any database, file format, application, or web service in yourEnterprise. In addition, these connections are made in a curated, secure, real-time,trusted manner.

The ibi Open Visualizations environment is shown in the image below.

In this chapter:

ibi Open Visualizations Benefits

ibi Open Visualizations Components

ibi Open Visualizations Users



The benefits of ibi Open Visualizations include the following:

Install once and configure at scale. Install and configure multiple data connections on onecentral server with little data preparation effort.

Ability to install the server on any platform. Supported platforms are Windows, Linux,UNIX, IBM i, and z/OS.

Access to almost any data source. Our data adapters use native database APIs,whenever possible, and ODBC and JDBC when required, as well as providing access toflat, delimited files, XML or JSON documents, and RESTful Web Services.

Easily establish secure data management and architecture standards. Take control ofyour data without undertaking a large data mastering project.

Robust metadata. Create a single, robust metadata layer for database tables and filesources.

Folder functionality. Classify metadata into folders to group related sources together.

User authorization for security. Categorize users with permission levels for dataaccess.

Control data access. Administrator can control access to individual columns by user ordata values.

Usage reports. Access reports that show what data assets are being used and who isusing them.

Power up your dashboards with integrated data. Cross-database joins allow you to queryand treat multiple data sources as one.

Data federation. Make all data sources, regardless of source, appear as one. Theserver queries the underlying data sources and returns a single answer set.

Virtualization abilities. Gain access to virtually any database, column store, file format,or web service, without the requirement to copy or prepare the data.

Data preparation features. Simplify or augment data, all built into the product.

Resource usage reports. See which users accessed which data sources.



Make it easy for end users. Provide a native and single connection to trusted data withreal-time access.

One ODBC Connector. Single connector installed on each user machine can connect toan ibi Server natively within your BI platform.

Direct pipes. Direct connection to enterprise data sources ensures real-time access andno latency for users.

Ready made and trusted data. Since all data is curated within ibi Open Visualizations,users can use the data as-is within their BI tool.

ibi Open Visualizations Components

The following are the components of ibi Open Visualizations:

ODBC and JDBC Connectors to provide access to data from any visualization tool.

ibi Server to provide web configuration for data virtualization, data preparation, scheduler,usage reporting, and optimized SQL generation.

Adapters to data sources to provide access to almost any database, column store, file, andweb service.

The ibi Open Visualizations architecture is shown in the following image.

1. Introducing ibi Open Visualizations



The following are user types for ibi Open Visualizations:

Business Analyst. Uses an analytics or visualization tool (Tableau, Microsoft Excel,Microsoft Power BI, and so on). The ODBC Connector provides access to additional,curated data sources.

Data Administrator. Uses the ibi Web Console to configure Adapters and connections todata sources. Creates metadata for tables and other data so they can be used by theBusiness Analyst. May also classify, augment, and secure data.



Chapter2Introducing the ibi ODBC Connector

The ibi ODBC Connector provides ODBC-enabled applications with transparent access tolocal and remote data sources.

In this chapter:

What Is Open Database Connectivity?

What Is an ODBC Driver?

ODBC Application Components

ibi ODBC Connector Components

Supported Environments

What Is Open Database Connectivity?

Open Database Connectivity (ODBC) is the database access component of the Windows OpenSystem Architecture (WOSA). It is a remote database specification based on the SequelAccess Group (SAG) and the X/Open Call Level Interface specification.

The specification attempts to define all calls required for application interaction with a datasource. The format of the call and expected data return for connect, query, define, and datamanipulation are standardized. This enables front-end applications to access multiple,heterogeneous relational and non-relational DBMSs, while eliminating the need to develop aspecific interface for each one.

What Is an ODBC Driver?

An ODBC driver represents the layer of software that maps the ODBC specification to theDBMS's proprietary API specification. These drivers are recognized and managed by the ODBCDriver Manager. Applications make database access calls to the Driver Manager, and theDriver Manager calls the appropriate ODBC driver.

To call the Driver Manager and to use the ODBC calls for the connection and retrieval of data,an application must be ODBC-compliant. Also, the ODBC drivers must conform to these calls.The drivers must return data and messages to the application, according to the ODBCspecification.



The following components are used when an ODBC application queries a data source:

ODBC API. An open API designed to provide a standard set of calls that multipleapplications can use to access remote data sources.

ODBC-enabled application. An application that uses the ODBC API to access remote data.For example, Microsoft applications, such as Access and Excel, or visualization tools, suchas Tableau.

ODBC Driver Manager. Stores information on the installed ODBC drivers and theassociated data source names. An ODBC-enabled application can request a list of driversand available data sources from the Driver Manager. Once a connect request is made for adata source, the Driver Manager loads the relevant driver and passes the ODBC requestsfrom the application to that driver. The ODBC Administration utilities are used to recordinformation about drivers, data sources, and data source configurations. These utilities arealso used to add new data sources.

Note: While Windows includes an ODBC Driver Manager, other operating systems requirethat you install one.

ibi ODBC Connector Components

The ibi ODBC Connector is installed with the ibi Client. The ibi ODBC Connector is an ODBCdriver that provides access to a server. This driver receives incoming ODBC calls (requests)from an ODBC application through the Driver Manager. It converts the calls into the appropriateAPI commands. The SQL statement is sent to the server in the form passed from theapplication.

Supported Environments

The ibi ODBC Connector is supported in the following environments:

Windows. Supports any ODBC application running in a Windows environment.

Linux/UNIX. Supports any ODBC application running in a Linux or UNIX environment.



Chapter3Installing the ibi Client on Windows

The following procedures describe how to install and configure the ibi Client on Windowsplatforms.

In this chapter:

Installing and Configuring ibi Open Visualizations on Windows


The following procedures describe how to install, configure, test, and enable traces for ibiOpen Visualizations.

Procedure: How to Install and Configure ibi Open Visualizations on Windows

1. Exit all programs before continuing.

2. Execute the following executable from the location in which you extracted the software(isetup.zip):

setup.exe

Note: If a User Access Control (UAC) security prompt appears, click yes.

The Choose Setup Language dialog box opens.

3. Select the language to be used during installation and click Next.

If you have no prior 82 installation, the License Registration dialog box opens.


If a prior installation was found, the Prior Installs Found: Choose an Action dialog boxopens, as shown in the following image.

If you choose to upgrade, the upgrade starts immediately, with no furtherinformation needed from you.

If you choose to create a new installation/configuration, the License Registrationdialog box opens prompting for the license key (similar to when there is no priorsoftware).



However, when there is a prior installation, the Prior Installation Found: SelectOption dialog box opens after the license key prompt asking you to choose betweenadding a new installation or creating an additional configuration. If you select Createadditional configuration, software is not installed, but the highlighted entry from theprior screen is used as a base for adding an additional configuration. If you selectInstall and Create configuration, a separate complete new installation and initialconfiguration is created. In this instance, when adding a new configuration, it isrecommended to not use the default installation paths and server name to avoidoverwriting a prior installation or configuration location. The Prior Installation Found:Select Option dialog box is shown in the following image.

4. On the License Registration dialog box, type your license key and click Next.

The license key should be saved for future reference. You must include the hyphens.

The License Key determines which product you are installing.

Your license key is checked and, if it is valid, an informational Registration Confirmationdialog box opens. Click OK.

If you typed an invalid License Key, the setup program displays a warning.

Click OK to correct the key.

3. Installing the ibi Client on Windows


5. On the License Agreement dialog box, click Yes to accept the terms of the licenseagreement.

The Select Initial Settings dialog box opens, as shown in the following image.

6. You can accept the default values or edit the following settings.

Program Folder. By default, this is named IBI 82 Client.

Installation Root. By default, this is C:\. You can browse to or type another location.

Customize default directory locations. Select this check box if you want to customizethe directory locations. For example, if you are configuring an additional instance of theserver, some of the locations, such as EDAHOME and EDACONF, must be customized.One way to customize the directories is to just use a different installation root andkeep the default location names under that root.

7. Click Next.



If you selected this check box to customize the default directories, the Select Directoriesdialog box opens, as shown in the following image.

8. Specify the following locations, or accept the default values:

a. Product installation directory. This contains the executable files. This location isreferred to as EDAHOME. It must conform to the pattern:

C:\ibi\client82\home

If you are performing a new installation, accept the default directory, or specify adifferent directory. The new software will be placed in this directory.

If you are configuring an additional instance, using your existing software, accept thedefault EDAHOME directory. If several 82 installation directories exist, select the onethat corresponds to the software home directory for which you are configuring a newinstance.

b. Product configuration directory. This contains configuration information for theinstance. This location is referred to as EDACONF.

If you changed the EDAHOME value, the default EDACONF value changes to conformto EDAHOME.

For example:

C:\ibi\client82\cln



Accept the default value, or click Browse, or type a name to specify a differentdirectory.

c. Click Next.

9. Click Next.

The Review Selected Product Parameters dialog box opens showing all of the selectionsyou have made, as shown in the following image.

On the Review Selected Product Parameters dialog box, ensure that the Register ODBCDriver parameter is set to Yes.

10. Click Continue.

11. When the setup is complete, click Finish.



12. To confirm that this works, from the Windows Start menu, type ODBC in the search field,select ODBC Data Sources (64-bit), and then click the System DSN tab. You should see theIBI 82 Client ODBC Driver, as shown in the following image.



13. To see the version of the ODBC Connector that is installed, click the Drivers tab, as shownin the following image.

Procedure: How to Add Data Sources on Windows

You can add data sources from the Connector after installation is completed.

1. From the Start menu, type ODBC in the search box.

2. Select ODBC Data Sources (64-bit).

The ODBC Data Source Administrator (64-bit) dialog box opens.

3. Select the System DSN tab.



4. From the System DSN tab, click Add, as shown in the following image.



The Create New Data Source dialog box opens, as shown in the following image.

5. Select IBI 82 Client ODBC Driver and click Finish.



The ibi ODBC Driver Configuration dialog box opens, as shown in the following image.

6. Enter the following information:

Data Source Name. Type a name for the server. The default value is IBISERVE.

Description. Type a description for the server.

TCP/IP Server. Type the host name for the Open Visualizations Server. This can be aname on your system, a fully-qualified domain name, or an IPv4 address.

Port. Type the TCP Port Number. This number is one less than the port number used toconnect to the server from a web browser. The default value is 8120, other commonvalues are 8100 and 8116. It must be the port number that the Open VisualizationsServer is listening on. Contact your server administrator if you do not know this number.

User and Password. Optionally, type a user ID and Password to connect to the server.Some ODBC Client tools may use these credentials to connect to the server.

Note: The ODBC Driver Manager stores credentials in the Windows Registry in plain text,so do not enter information if your PC is not secured.

7. Optionally, you can test your connection by clicking Test. You should receive a "ConnectionSucceeded" message. If not, correct your entries and try again.



8. Click OK to save your connection.

Procedure: How to Remove Data Sources on Windows

You can remove data sources from the Connector after installation is completed.





4. From the System DSN tab, select the System data source to which you want to add a datasource and click Remove, as shown in the following image.

Procedure: How to Configure Data Sources on Windows

You can configure data sources from the Connector, if you need to change any of theparameters.







4. From the System DSN tab, select the System data source to which you want to add a datasource and click Configure, as shown in the following image.



The ibi ODBC Driver Configuration dialog box opens, as shown in the following image.

5. Make any necessary changes or add new information as needed, and then click OK. Formore information, see How to Add Data Sources on Windows on page 22.

Procedure: How to Test the ODBC Driver Using the RDAAPP Tool

You can use the RDAAPP interactive test tool to test and troubleshoot connector applicationsthat connect to servers.

1. From the Windows Start menu, select Information Builders and then select IBI 82 Client.



2. Select Diagnostic Functions, and then double-click Test ODBC Connector through Rdaapp,as shown in the following image.

The Command prompt opens and displays the following. User entries are displayed inbold.

RDAAPP: invoked from shell

Allocating environment handle...

List of available servers: 1 - IBISERVE

Enter corresponding server entry number or name(default=1): 1

Enter User Name: srvadminEnter Password: ********

Allocating connection handle...Attempting connect to the datasource: IBISERVE ...Connect status = 0

New ODBC Extender Test.

RDAAPP Command Options: S <SELECT SQL Statement to Execute> ; Q Quit/Disconnect ? Help



Enter Command:s select country from car ;

Alloc stmt ...Return code from alloc stmt is 0Issuing SQLPrepare call for select country from car ; Return code from SQLPrepare call is 0Executing select country from car ; stmt...Issuing SQLNumResultCols call for select country from car ;

Number of resultset columns is 1

Printing select item descriptions:

Issuing SQLDescribeCol call for colNum=1

item #1colname = COUNTRYcoltype = 1precision = 10scale = 0nullable = 0

Binding columns...Fetching report data...

ENGLANDFRANCEITALYJAPANW GERMANY

<<< 5 record(s) processed. >>>

New ODBC Extender Test.



Procedure: How to Test the ODBC Driver With Microsoft Excel 2019

If you have Microsoft Excel installed on your Windows PC, you can also test the ODBC Driverusing the following procedure.

1. Create a text file with a .dqy extension. Include your DATASOURCE, USER, and PASSvalues, in addition to your SQL request, as shown in the following image.

Note: Replace the SELECT COUNTRY FROM CAR statement with a SELECT statement for atable that exists on your server.

2. Save the file.

3. Double-click the file to run.

4. On the Security Notice dialog box, click Enable, as shown in the following image.



5. If the server has security enabled, type the user ID and password to connect and click OK,as shown in the following image.

The values from the SQL request display, as shown in the following image.

Procedure: How to Configure Additional Nodes

You can configure additional nodes (servers) or change the configuration of an existing node.



Procedure: How to Update Your Client Configuration

If you have previously installed and configured the ibi Client prior to release 8207.14, youshould follow these steps before proceeding.

1. From the Windows Start menu, select Information Builders and then select IBI 82 Client.

2. Select Configure Functions, and then select Remove IBI ODBC Driver, as shown in thefollowing image.

3. Right-click Register IBI ODBC Driver and select Run as administrator. The IBI 82 ClientODBC Driver is registered, as shown in the following image.



Procedure: How to Configure the ODBC Connector Environment

The ODBC Connector environment can be configured by setting environment variables. Whilethese can be set from a batch file that subsequently calls the program that uses the ODBCConnector, they are most commonly set from the Windows Control Panel from SystemProperties on the Advanced tab.

Environment variables can be either System Variables, which affect all users of the PC, or UserVariables, which affect only the current user. For an example of how to set a variable, see Howto Enable ODBC Tracing on page 43.

The following variables are used:

EODTRACE = {ON|OFF}. Enables or disables tracing. When enabled, trace files are written tothe user's %TEMP% directory.

EOD2PARTNAME = {ON|OFF}. Controls how the server obtains the ODBC schema name. Thissetting is provided for compatibility with prior versions of the ODBC Connector.

where:

ON

ON indicates that the application folder names on the server should be used.

OFF

OFF indicates the name EDADBA should be used.

Note: By default, for Microsoft Excel 2019, Microsoft Power BI, and Tableau, the defaultapplication folder names on the server are used. For other applications, the name EDADBA isused.

Procedure: How to Enable Tracing

The following steps describe how to enable tracing by setting an environment variable from theControl Panel. When enabled, trace files are created in your %TEMP% directory.

1. From the Windows Start menu, type env in the search field and select Edit the Systemenvironment variables.

The System Properties dialog box opens.

2. On the Advanced tab, select Environment Variables.

The Environment Variables dialog box opens.

3. Under User variables, click New.



The New User Variable dialog box opens, as shown in the following image.

4. In the Variable name field, type EODTRACE.

5. In the Variable value field, type ON.

6. Click OK to close the New User Variable dialog box.

7. Click OK to close the Environment Variables dialog box and then click OK to close theSystem Properties dialog box.

8. Run your test.

You can view traces in the user temp directory, as shown in the following image.



Chapter4Installing the ibi Client on Linux or UNIX

The following procedures describe how to install and configure the ibi Client on Linux orUNIX platforms.

In this chapter:

Installing and Configuring ibi Open Visualizations on Linux or UNIX


Note: ODBC on Linux or UNIX requires an ODBC Driver Manager, which you can download fromthe unixodbc.org website, as shown in the following image.


Many Linux distributions include unixODBC, and so that you can install the unixODBC DriverManager using one of the following commands:

$ sudo yum install unixODBC$ sudo apt-get install unixodbc$ sudo dnf install unixODBC

The following procedures describe how to install, configure, set environment variables, andenable traces for ibi Open Visualizations.

Procedure: How to Install and Configure ibi Open Visualizations on Linux or UNIX

1. Exit all programs before continuing.

2. Execute the following executable from the location in which you extracted the software(isetup.zip):

$ ./isetup

The following isetup screen displays.

--------------------------------------------------------------------- Welcome to the Product Set Up Facility Please respond to the prompts or enter Q to quit at any prompt.---------------------------------------------------------------------Select an option: 1. Install and Configure 2. Add Additional Configuration Instance 3. Refresh Installation (Reinstall, Keep Configurations) 4. Install Debuggables to the Installation Directory 5. View Installation NotesEnter a selection (Default=1) :

3. Type 1 for the Install and Configure option.

You are prompted for the location of the installation file, iserver.tar.

Please enter the full path name of the media for the product(Default=/home/user/iserver.tar)Please supply media or <Enter> :

4. Type the full path name of the iserver.tar file, or press Enter to accept the default.

You are prompted for your license key.

Enter your License Key (Current number of CPUs = n)(Format 999-999-9999-99) : xxx-xxx-xxxx-xx

5. Type your license key.

Your license attributes are displayed, and the license key is confirmed.

License Key has been checkedProduct: Client



You are now shown the default values of the environment variables and port numbers, andgiven an opportunity to change them. For example, if you were logged in with the user IDiadmin:

Please review the default settings.

EDAHOME = /home/iadmin/ibi/client82/homeEDACONF = /home/iadmin/ibi/client82/cln

Proceed with defaults? (Y/N Default=Y) :

6. If you want to accept the default values, type Y. Otherwise, select N and change anyproperties that you wish.

7. Press Enter to continue.

You are prompted to supply the location on disk in which to install the software.

Supply the location on disk in which to install the software.This location is also known as EDAHOME.

(Default=/home/iadmin/ibi/client82/home)

Please supply location or <Enter>:

8. Type the location or press Enter to accept the default.

You are prompted to supply the location on disk in which to configure the software.

Supply the location on disk in which to configure the software.This location is also known as EDACONF.

(Default=/home/iadmin/ibi/client82/cln)

Please supply location or <Enter>:

9. Type the location or press Enter to accept the default.

The installation and configuration steps begin and the completion status displays.

ISETUP: Installation Step completedPlease wait while we are configuring the product ...

ISETUP: Configuration Step completed

Procedure: How to Configure the Client and ODBC Driver Manager

Configuring the ODBC driver includes configuring environment variables and setting up theODBC configuration file.

By default, this file is located in the user home directory and is called:

.odbc.ini

4. Installing the ibi Client on Linux or UNIX


A centralized system information file can also be used. By default, it is:

/etc/odbc.ini

Additionally, the location can be specified by setting the ODBCINI environment variable beforestarting the client program or in your profile.

For example:

export ODBCINI=/ibi/odbc.ini

Note: When this variable is set, it overrides the default values.

If you are configuring the driver for the current user, issue the following command:

$ nano .odbc.ini

If you are configuring the driver for all users, issue the following command:

$ sudo nano /etc/odbc.ini

Note that the node name in the .odbc.ini file (EDASERVE in this example) must match a nodename in the server configuration file odin.cfg.

The following is an example:

[ODBC Data Sources]ibiserve=IBI 82 Client ODBC Driver[ibiserve]Driver=/ibi/client82/home/bin/libedaod3x.soDescription=Open Visualizations ServerServer=hostnamePort=8120user=userpwd=password

Make sure the paths to the driver are correct.

Procedure: How to Set Environment Variables

The connector requires several environment variables. These variables can be set andexported in the .profile file.

Note: Before configuring the environment for the ODBC Connector ODBC, make sure the clientsoftware is installed and configured.



Set and export the following environment variables before configuring ODBC parameters. Youcan add them to the iadmin ID .profile or .bash_profile file.

1. Determine the shared library search path variable for your platform, and addEDAHOME/bin to it. For most UNIX platforms, the variable is LD_LIBRARY_PATH.Applications that use the ODBC Connector must have this set in their environment toensure that ODBC components can be located at the time of execution.

Note: Some UNIX distributions use an OS-specific environment variable for shared librariesand commands to set the value. For example:

For AIX, variable name is LIBPATH.

For HP-UX, variable name is SHLIB_PATH.

For all other UNIX platforms, variable name is LD_LIBRARY_PATH.

For example, if the client was installed in /home/iadmin/ibi/client82, issue the command:

export LD_LIBRARY_PATH=/home/iadmin/ibi/client82/home/bin:$LD_LIBRARY_PATH

2. If you modified the profile, log off and then log back on or re-execute the profile as follows:

. $HOME/.profile

3. Configure additional environment variables.

For an example of how to set a variable, see How to Enable ODBC Tracing on page 43.

The following variables are used:

export EODTRACE = {ON|OFF}. Enables or disables tracing. When enabled, trace files arewritten to the current directory.

export EOD2PARTNAME = {ON|OFF}. Controls how the server obtains the ODBC schemaname. This setting is provided for compatibility with prior versions of the ODBC Connector.

where:

ON

ON indicates that the application folder names on the server should be used.

OFF

OFF indicates the name EDADBA should be used.



Procedure: How to Test the ODBC Connection Using isql

Once you have configured communications, issue the following command to start the ODBCtest tool in order to verify the communication configuration:

$ isql -v server [userid [password]]

where:

server

Is the node name from the odbc.ini file.

userid

Is the user ID for the user.

password

Is the password for the user ID.

Note: The user ID and password are optional, if there is no security on your server.

For example, the following is a sample session, where the server name is ibiserve, the user IDis ibi, and the password is ibi:

$ isql -v ibiserve ibi ibi

The test tool opens with the following window:

+---------------------------------------+| Connected! || || sql-statement || help [tablename] || quit || |+---------------------------------------+

The tool opens the SQL environment, identified by the SQL prompt, SQL>.

Issue a SELECT statement for a table on your server, for example as shown in the followingstatement, and press Enter:

SQL> select country from car ;



If the following output displays, the communications configuration is verified:

+-----------+| COUNTRY |+-----------+| ENGLAND || FRANCE || ITALY || JAPAN || W GERMANY |+-----------+SQLRowCount returns 05 rows fetchedSQL>

Enter the following command to exit the SQL environment.

quit

Procedure: How to Troubleshoot ODBC

Log File

In addition to the messages returned to the calling application, more detailed messages arewritten to the client log file. For example:

$ cat edaprint.log

Sample Output

11:18:55.546 E error: <NGXX> xxodin_con:client with nodename edaserve not found/valid 15:03:21.050 E error: <NGXX> xxcrt_client:could not find or parse odin communication file

Procedure: How to Enable ODBC Tracing

1. To enable tracing, issue the following command:

$ export EODTRACE=ON

2. Run your test.

Trace files are written to the user home directory with an extension of trc.



Chapter5Using Applications

The ODBC Connector is compliant with the ODBC 3.5 specification.

In this chapter:

Using the ODBC Connector

Using ODBC Escape Clauses

Issuing Your Own SQL Statement


The following procedures describe how to use the ibi ODBC Connector from Microsoft Access,Microsoft Excel, Microsoft Power BI, and Tableau.

Procedure: How to Use the ibi ODBC Connector from Microsoft Access

The following procedure describes how to use the ibi ODBC Connector from Microsoft Accessand create a visualization.

1. From Microsoft Office 2019, open Microsoft Access, as shown in the following image.


2. From the External Data tab on the ribbon, select New Data Source, and then select FromOther Sources, as shown in the following image.

3. Select ODBC Database from the menu, as shown in the following image.

The Select the source and destination of the data dialog box opens.



4. Select how and where you want to store the data in the current database, as shown in thefollowing image.

5. Click OK.

5. Using Applications


6. From the Select Data Source dialog box, select the data source name, for exampleCENTRE, as shown in the following image.

7. Click OK.

The Import Object dialog box opens.



8. Select the table name, as shown in the following image.

Note: Application folder names are shown when the EOD2PARTNAME environment variableis set to ON. For compatibility with prior releases of the ODBC Connector, when set to OFFinstead of the application folder, the name EDADBA is shown for all tables.

9. Click OK.



The data values for the imported table display, as shown in the following image.

Procedure: How to Use the ibi ODBC Connector from Microsoft Excel

The following procedure describes how to use the ibi ODBC Connector from Microsoft Exceland create a visualization.

1. From Microsoft Office 2016 or 2019, open Microsoft Excel.

2. From the Data tab, select Get Data.

3. From the Get Data drop-down list, select From Other Sources, and then select From ODBC,as shown in the following image.

The From ODBC dialog box opens.



4. Select the Data Source Name, for example, EDASERVE, as shown in the following image.

5. Click OK.

The Application Directory Navigator dialog box opens, as shown in the following image.



6. Select the application directory name. You can also search for a data source name, asshown in the following image.

7. Select a data source name.

8. Select Load to load the data and return to Power BI or select Transform Data to edit thedata before loading.



The Power Query Editor opens, as shown in the following image.

9. Using the Queries and Connections option, create a query against the data, as shown inthe following image.



Note:

If you are using a previous version of Microsoft Excel, for example Excel 2013, selectFrom Other Sources, then select From Microsoft Query, and then select the data sourcefrom the Choose Data Source dialog box, as shown in the following image.

In Microsoft Excel 2013, if EOD2PARTNAME IS set to ON, you must select a foldername from the Owner drop-down menu, for example, ibisamp, as shown in thefollowing image. Otherwise, you get all the synonym names in one list.



Procedure: How to Use the ibi ODBC Connector from Microsoft Power BI

The following procedure describes how to use the ibi ODBC Connector from Microsoft Power BIand create a visualization.

1. Open Microsoft Power BI, as shown in the following image.

2. Select Get data.

The Get Data dialog box opens.

3. Select Other and then select ODBC, as shown in the following image.



4. Click Connect.

The ODBC driver dialog box opens, as shown in the following image.

5. Type your user name and password and click Connect.

The Application Directory Navigator dialog box opens.

Note: Power BI caches your user ID and password. After the first time you enter yourcredentials, you will not be prompted again.



6. Select the application directory name and table or tables, as shown in the following image.

7. Click Load.

8. Create a visualization with Power BI, as shown in the following image.



Procedure: How to Use the ibi ODBC Connector from Tableau

The following procedure describes how to use the ibi ODBC Connector from Tableau and createa visualization.

1. Start Tableau Desktop, as shown in the following image.



2. Under Connect To a Server, select More, and then select Other Databases (ODBC), asshown in the following image.

3. Select the Data Source Name, for example, DATA, and click Sign In.

The iWay ODBC dialog box opens.

4. Type your User ID and password, as shown in the following image.

5. Click OK.

6. On the Connections screen, select EDADB for Database (it is your only choice).



7. Type a schema name or % to see all the schemas, as shown in the following image.

8. Type a full table name, or a partial table name, for example dm, as shown in the followingimage.



9. Select a table from the list and drag it to the work area to start, as shown in the followingimage.

10. Create a visualization using Tableau Desktop, as shown in the following image.




Use the ODBC Escape Clause to run remote procedures. ODBC uses similar escape clauses todefine various extensions to ANSI standard SQL.

Reference: Using ODBC Escape Clauses to Run Remote Procedures

--(*vendor(Microsoft),product(ODBC) call proc_name[(parm1,parm2...)]*)--

where:

proc_name

Specifies the name of the procedure stored on the server.

parm1,parm2...

Specifies the name of one or more optional parameters.

Reference: Invoking Remote Procedures Using Shorthand Syntax

{call proc_name[(parm1,parm2...)]}

The Connector driver supports the shorthand syntax.

Note: Some ODBC applications use their own syntax for calling remote procedures. Theseapplications also convert the syntax into the ODBC Escape Clause syntax internally.

Reference: Using ODBC Escape Clauses for Dates, Times, and Timestamps

{d 'date_value'}{t 'time_value'}{ts 'timestamp_value'}

The Connector modifies the ODBC syntax to match the appropriate ANSI SQL form. Forexample, the Connector changes the ODBC escape clause {d 'date_value'} to the ANSI SQLequivalent 'date_value'. The date value is not modified and must be entered in the appropriateform from the ODBC application.


You can issue your own SQL statement for Excel or Power BI. For either one, you can click onAdvanced Options and then use the data source in an SQL statement.



For example, in Excel, click Advanced Options, as shown in the following image.

Type the SQL statement in the SQL statement input box.



Chapter6Introducing the ibi JDBC Connector

The ibi JDBC Connector is installed with the ibi Client. The ibi JDBC Connector providesaccess to a server. It receives incoming JDBC calls (requests) from a JDBC applicationand converts the calls into the appropriate API commands. The SQL statement is sent tothe server in the form passed from the application.

In this chapter:

Using the JDBC Connector


After installing the ibi Client, the JDBC Connector consists of a single self-contained .jar filethat comprises the JDBC Driver.

The .jar file name is jlink_standalone.jar, located in the \home\etc\java\srvr directory.

Procedure: How to Use the JDBC Connector With sqlline

You can test the JDBC Connector using the open source program sqlline.

1. Download sqlline from the following website:

https://search.maven.org/search?q=sqlline

2. Click the download button for sqlline and select jar-with-dependencies.jar.

This will download the sqlline-1.9.0-jar-with-dependencies.jar file.

3. Extract the two .jar files to the same directory.

jlink-standalone.jar

sqlline-1.9.0-jar-with-dependencies.jar

4. For Windows, create a batch file called sqlline, with the following code:

java -cp "%~dp0\*" sqlline.SqlLine %* --color=true

For Linux, create a shell script called sqlline, with the following code, and make itexecutable:

export CP=for file in *.jar ; do CP=$file:$CP ; donejava -cp $CP sqlline.SqlLine $* --color=true


https://search.maven.org/search?q=sqlline

5. Test the Connector using sqlline, as shown in the sample (for Linux) below:

$ ./sqllinesqlline version 1.9.0sqlline> !scanscan complete in 241ms1 driver classes foundCompliant Version Driver Classno 8.2 ibi.jlink.EdaDriversqlline> !connect jdbc:jlink://server:8110 user password Transaction isolation level TRANSACTION_REPEATABLE_READ is not supported. Default (TRANSACTION_READ_UNCOMMITTED) will be used instead.0: jdbc:jlink://server:8110> select country from car;+------------+| COUNTRY |+------------+| ENGLAND || FRANCE || ITALY || JAPAN || W GERMANY |Error: HY010 (state=attempted to next() after eos,code=0)0: jdbc:jlink://server:8110> !quit

Procedure: How to Connect to a Server Using a URL

The Connector uses a standard JDBC URL to locate a server. You can include all the necessaryinformation to connect to a server in a URL, using the following syntax:

jdbc:jlink://host:port;keyword1=value1;keyword2=value2

where:

jdbc:jlink

Identifies the interface you are using. This indicates that the Connector should be loaded.

host

Is the IP address or Domain Name Service (DNS) of the server.

port

Is the TCP/IP port number on which the server listens.

keywords

You can pass all the required communications properties in the URL. Properties arespecified as keyword=value pairs and must be separated by a semicolon (;). Possiblevalues are:

user or userid

Is the user identification for access to the server.



password or pswd

Is the user password for access to the server.

trace

Identifies the active trace level. A trace setting can be any combination of the numbers1, 2, 3, and 4. You can use one or more of the trace levels for tracing and debuggingapplications. The following table provides detailed information about each trace level.The numbers for each trace level represent the numbers as they appear on the trace.

Level Description

1 Displays each entry and exit to and from a Connector function,along with the parameter values processed.

2 Displays data transmission and internal logic. Key decisions madein JLINK are traced.

3 Displays internal logic. Input and output are traced.

4 Displays internal debugging information.

Procedure: How to Use the JDBC Connector With SQuirrel SQL

You can use the JDBC Connector with the SQuirrel SQL Client open source program onWindows, Linux, and other platforms.

1. Download the SQuirrel SQL Client from the following website and follow the installationinstructions:

http://www.squirrelsql.org/#installation

2. Open the SQuirrel SQL Client.

6. Introducing the ibi JDBC Connector


http://www.squirrelsql.org/#installation

3. Click the Drivers tab, and then click the plus (+) button to add a new driver, as shown inthe following image.



The Add Driver dialog box opens, as shown in the following image.



4. In the Name field, type a name for the driver, for example, IBI Client, and in the ExampleURL field, type the URL for your server, for example, jdbc:jlink://server:8120;, as shown inthe following image.



5. Click the Extra Class Path tab and then click Add, as shown in the following image.

6. Navigate to the directory where you installed the ibi Client, and then to the /home/etc/java/srvr directory. For example, on Windows, the default directory is:

C:\ibi\client82\home\etc\java\srvr



7. Select the jlink_standalone.jar file in that directory, as shown in the following image.

8. Click Open.



The jlink_standalone.jar file is successfully added, as shown in the following image.

9. Click List Drivers.

The ibi.jdbc.EdaDriver class name will be populated in the Class Name field.

10. Click OK.

Procedure: How to Create an Alias

1. Click the Aliases tab, as shown in the following image.



Note: An Alias is what SQuirrel calls a connection to a server.

2. On the Aliases tab, click the plus (+) button to add a new alias, as shown in the followingimage.



The Add Alias dialog box opens, as shown in the following image.



3. In the Name field, type a name for the alias, for Driver, select IBI Client, and for URL, typethe connection information for your server, as shown in the following image. Optionally,you can type a User Name and Password.

4. Click Test.

The Connect to data dialog box opens.

Note: If you did not enter a user and password on the previous Add Alias dialog box, typea user and password on the Connect to data dialog box, as shown in the following image.



5. Click Connect.

You should see a Connection successful message, as shown in the following image.

6. Click OK and then click Close.

7. You can now click Connect to connect to your configured server. The first screen shows theproperties of the JDBC Connection, as shown in the following image.

8. Click the SQL tab.



You can now type a select statement for a table on your server. Click the running man torun the select statement and view the results, as shown in the following image.



Chapter7 Using Python With the ODBC and JDBCConnectors

You can use Python with the ODBC and JDBC Connectors using the Jupyter Notebook(single user) or JupyterHub (multi-user) on Linux and Windows.

In this chapter:

Using Python From Jupyter


The following procedures describe how to install Jupyter software and how to connect to Pythonusing the ODBC and JDBC Connectors.

Procedure: How to Install Jupyter Software

1. Download the Jupyter Notebook or JupyterHub from the following website and follow theinstructions to install Anaconda on Jupyter.

https://jupyter.org/install

2. Using conda or pip, install the following packages:

To use ODBC, install pyodbc.

To use JDBC, install JayDeBeApi.

For enhanced reports, install pandas.

3. Start the Jupyter Notebook or JupyterHub.

4. If you are running Jupyter on Linux and want to use ODBC, see How to Set Up the LinuxODBC Environment for Jupyter on page 79. If you are using JDBC, no additional setup isrequired.

Procedure: How to Set Up the Linux ODBC Environment for Jupyter

The LD_LIBRARY_PATH environment variable indicates to the ODBC Driver Manager where tofind files needed by the ODBC Connector. It must be established before starting JupyterNotebook.

Jupyter Notebook is designed for a single user, so you can install and configure it as neededfor your own use. This variable can be set as an environment variable for starting thenotebook.


https://jupyter.org/install

JupyterHub is designed for use by multiple users and is usually installed by a systemadministrator. For JupyterHub, this variable must be set in the kernel. You can modify thedefault kernel or create an alternate kernel.

1. Find the kernels directory for Jupyter. This directory has a subdirectory for each kernel. Forexample, if you installed using miniconda, the directory is:

/usr/miniconda3/share/jupyter/kernels

2. Optionally, you can make a copy of the default python3 directory if you do not want to alterit. For example:

# cd /usr/miniconda3/share/jupyter/kernels# cp -r python3 python3_ibi

3. In the kernel directory, edit the kernel.json file.

4. If you made a copy, change the value of "display name" to a new name.

5. Add a comma (,) and a new "env" dictionary, with a name "LD_LIBRARY_PATH". Include avalue of the bin directory in the location where you installed the ODBC Connector and anyother directories, as shown in the following example.

{ "argv": [ "/usr/miniconda3/bin/python", "-m", "ipykernel_launcher", "-f", "{connection_file}" ], "display_name": "Python 3 ibi", "language": "python", "env": {"LD_LIBRARY_PATH":"/ibi/client82/home/bin:/usr/lib:/lib"}}

Procedure: How to Connect From the Jupyter Notebook Using ODBC

1. From a web browser, connect to the Jupyter Notebook.

2. Click New to create a new notebook. If you created a new kernel, then select it from thepull-down list.

3. Type import pyodbc into a cell and run it. There should be no output. For example:

4. Connect to the server. The DSN is the name that appears in your odbc.ini file, UID is auser ID, and PWD is the password. For example:



There should be no output if the configuration is successful.

Now, you can fetch or read the data.

Procedure: How to Connect From the Jupyter Notebook Using JDBC

1. From a web browser, connect to the Jupyter Notebook.

2. Type import jaydebeapi into a cell and run it. There should be no output. For example:

3. Connect to the server using the jaydebeapi connect method. The method takes thefollowing parameters. There should be no output.

Parameter Value

Driver Name ibi.jlink.EdaDriver

URL jdbc:jlink://server:port

User/Password ["user","password"]

JDBC Driver /install/ibi/client82/home/etc/java/srvr/jlink_standaone.jar

where:server

Is the name or IP address of your ibi Server.port

Is the TCP port the server is listening on.user

Is a valid user ID on the ibi Server.password

Is the corresponding password for the user ID.install

Is the directory where you installed the ibi Client.

For example:

7. Using Python With the ODBC and JDBC Connectors


Now, you can fetch or read the data from the table.

Procedure: How to Fetch a Table

Once you have established a connection to a data source using either ODBC or JDBC, you canretrieve the data in the same way.

1. Get a cursor for the connection. For example:

2. Assign a variable, such as sql, to a select statement for a table on your server. Thereshould be no output. For example:

sql = "select COUNTRY, STATE, CITY, SUM(REVENUE) FROM retail_sales GROUP BY COUNTRY, STATE, CITY"

3. Execute the select statement. For example:

4. Now, you can fetch the data. For example:



Procedure: How to Read a Table

Pandas provides an alternative way of viewing a table. Once you have established a connectionto a data source using either ODBC or JDBC, you can also use this method.

1. Type import pandas into a cell and run it. There should be no output. For example:

2. Assign a variable, such as sql, to a select statement for a table on your server. Thereshould be no output. For example:

sql = "select COUNTRY, STATE, CITY, SUM(REVENUE)FROM retail_sales GROUP BY COUNTRY, STATE, CITY"

3. Read the data using the pandas.read_sql method. For example:

4. Use the head method to display the formatted output. For example:

7. Using Python With the ODBC and JDBC Connectors


Index

A

adding data sources 22

B

benefits 10

C

components 11

configuring additional nodes 32

configuring data sources 26

configuring ODBC Connector environment 34

E

environment 9

EOD2PARTNAME 34

EODTRACE 34

I

ibi Client

installation on Linux or UNIX 37

installing on Windows 15

ibi JDBC Connector

introducing 65

ibi ODBC Connector

components 14

introducing 13

supported environments 14

installing ibi Cient on Linux or UNIX 37

installing ibi Client on Windows 15

introducing ibi JDBC Connector 65

introducing ibi ODBC Connector 13

introducing Open Visualizations 9

isql test tool 42

issuing SQL statement 62

J

JDBC Connector

Jupyter 81

sqlline 65

SQuirrel 67

Jupyter 79

Jupyter Notebook 79

JupyterHub 79

M

Microsoft Access 45

Microsoft Excel 50

Microsoft Power BI 55

O

ODBC Connector

configuring 34

from Jupyter 80

from Microsoft Access 45

from Microsoft Excel 50

from Microsoft Power BI 55


ODBC Connector

from Tableau 58

ODBC driver 13

testing with Excel 2019 31

testing with RDAAPP 28

ODBC escape clauses 62

dates, times, and timestamps 62

running remote procedures 62

using shorthand syntax 62

ODBCINI environment variable 40

Open Visualizations

benefits 10

components 11

environment 9

introducing 9

P

Python 79

R

RDAAPP interactive tool 28

removing data sources 26

S

setting environment variables

on Linux and UNIX 40

sqlline 65

SQuirrel 67

T

Tableau 58

tracing

on Linux and UNIX 43

on Windows 34

U

using applications 45

using the ODBC Connector 45

V

variables 34

EOD2PARTNAME 34

EODTRACE 34

Index


FeedbackCustomer success is our top priority. Connect with us today!

Information Builders Technical Content Management team is comprised of many talentedindividuals who work together to design and deliver quality technical documentation products.Your feedback supports our ongoing efforts!

You can also preview new innovations to get an early look at new content products andservices. Your participation helps us create great experiences for every customer.

To send us feedback or make a connection, contact Sarah Buccellato, Technical Editor,Technical Content Management at [email protected].

To request permission to repurpose copyrighted material, please contact Frances Gambino,Vice President, Technical Content Management at [email protected].

Information Builders, Inc.Two Penn PlazaNew York, NY 10121-2898

ibi Open VisualizationsRelease 8207

DN4501769.0920

ibi open visualizations release 8207...preface this document describes how to install, configure,...

Documents