business intelligence user guide · this document provides support and setup information for using...

Business Intelligence User Guide v2.0

i

Copyright © 2016 Cirro, Inc. Confidential and Proprietary. All Rights Reserved.

Business Intelligence User Guide For use with v2.0

Document Version 2.0

Document Release: January 28, 2016



i


Table of Contents

1 Document Overview......................................................................................................................1

1.1 Audience................................................................................................................................1

1.2 Related Documents ................................................................................................................1

1.3 Usage Restrictions and Legal Statements ................................................................................1

1.3.1 Confidential and Proprietary Information....................................................................... 1

1.3.2 Trademarks ................................................................................................................ 1

1.4 Cirro Corporate Offices ...........................................................................................................2

1.5 Getting Help ...........................................................................................................................3

2 ODBC Driver Installation ...............................................................................................................4

2.1 Prerequisites ..........................................................................................................................4

2.1.1 Software Prerequisites ................................................................................................ 4

2.1.2 Other Prerequisites ..................................................................................................... 4

2.2 ODBC Driver Installation Steps ................................................................................................5

2.3 Creating the ODBC Data Source .............................................................................................6

2.3.1 Connection String Extra Properties .............................................................................. 9

2.3.1.1 tablenamepattern..................................................................................................9

2.3.1.2 schemanamepattern ........................................................................................... 10

2.3.2 Extra JVM args ......................................................................................................... 10

2.4 Modifying or Removing a Cirro Data Source ........................................................................... 10

2.5 Troubleshooting Cirro ODBC Driver Problems ........................................................................ 11

3 JDBC Driver Installation .............................................................................................................. 13

3.1 Prerequisites ........................................................................................................................ 13

3.1.1 Software Prerequisites .............................................................................................. 13

3.1.2 Other Prerequisites ................................................................................................... 13

3.2 JDBC Driver Installation Steps ............................................................................................... 13

3.3 JDBC Driver Connection String Values................................................................................... 13

3.4 Troubleshooting Cirro JDBC Driver Problems ......................................................................... 14

4 Using tablenamepattern Functionality........................................................................................... 15

5 Using SSL Client Connections ..................................................................................................... 16

6 Using BusinessObjects with Cirro ................................................................................................ 17

6.1 Supported BusinessObjects Versions and Other Requirements ............................................... 17

6.2 Prerequisites ........................................................................................................................ 17


ii


6.3 Installation Steps .................................................................................................................. 17

7 Using IBM Cognos with Cirro ....................................................................................................... 20

7.1 Supported IBM Cognos Versions and Other Requirements...................................................... 20

7.2 Prerequisites ........................................................................................................................ 20

7.3 Configuration Steps .............................................................................................................. 20

8 Using Google Analytics with Cirro ................................................................................................ 22

8.1 Prerequisites ........................................................................................................................ 22

8.2 Building Cirro Analyst for Excel Queries to Google Analytics.................................................... 22

8.3 Building SQL Queries for Google Analytics ............................................................................. 23

8.4 Removing Google Analytics Authorization .............................................................................. 24

9 Using TIBCO Spotfire with Cirro................................................................................................... 25

9.1 Supported Spotfire Versions and Other Requirements ............................................................ 25

9.2 Prerequisites ........................................................................................................................ 25

9.3 Spotfire Installation Instructions ............................................................................................. 25

10 Using Tableau with Cirro ............................................................................................................. 26

10.1 Supported Tableau Versions and Other Requirements ........................................................ 26

10.2 Prerequisites .................................................................................................................... 26

10.3 Tableau Installation Instructions ......................................................................................... 26

11 Document Change History........................................................................................................... 27


1


1 Document Overview

This document provides support and setup information for using business intelligence tools with Cirro, including instructions on installing and configuring the Cirro ODBC and JDBC drivers.

1.1 Audience

This document is for users of third party Business Intelligence (BI) tools (such as Business Objects and Tableau) for querying Cirro data sources, as well as users of Cirro Analyst for Excel.

1.2 Related Documents

Cirro provides this documentation suite. Contact your Cirro representative to obtain additional documents.

Cirro Admin Guide: Provides instructions for system administrators who will install, configure, and maintain the Cirro solution.

Cirro SQL Specification: Defines the Cirro SQL language.

Cirro Analyst User Guide: Provides instructions on advanced and ad hoc querying, including using Cirro Analyst for Excel.

Cirro Business Intelligence User Guide: Provides instructions for using third-party business intelligence tools such as Business Objects and Tableau to work with Cirro, as well as installation instructions for the Cirro ODBC and JDBC drivers.

Cirro Functions Guide: Provides definitions for the Cirro pre-defined function library and information on creating custom functions.

1.3 Usage Restrictions and Legal Statements

1.3.1 Confidential and Proprietary Information

This document contains the confidential and proprietary information of Cirro, Inc. This document is submitted on a confidential basis and parties accessing this presentation are required to maintain the

confidentiality of all confidential information contained herein. This document may not be distributed or reproduced in whole or in part or shown to any person without the prior consent of Cirro. The information contained herein is believed to be reliable, but no warranty is made as to the accuracy of any such

information. Circumstances could change since the date this information was supplied.

1.3.2 Trademarks

The following terms are trademarks of Cirro, Inc.:

Cirro Data Hub, Cirro Analyst for Excel

The following terms are trademarks or registered trademarks of their respective owners and no claims to rights to such marks are made by Cirro, Inc.:


2


Microsoft, Windows, Windows NT, Excel, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Apache, Apache Hadoop, Hadoop, HDFS, Avro, Cassandra, Chukwa, HBase, Hive, Mahout, Pig, Zookeeper are trademarks of the Apache Software Foundation.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be

trademarks of their respective owners.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crys tal

Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Tableau is a trademark of Tableau Software in the United States, other countries, or both.

EMC2, EMC, Greenplum, Greenplum Chorus, and where information lives are registered trademarks or trademarks of EMC Corporation in the United States and other countries.

Teradata is a trademark or registered trademark of Teradata Corporation in the United States and other countries.

InfiniDB is a trademark or registered trademark of Calpont in the United States, other countries,

or both.

VMWare and SQLFire are a trademark or registered trademark of VMware, Inc. in the United States and/or other jurisdictions.

Hortonworks is a trademark or registered trademark of Hortonworks Inc in the United States, other countries, or both.

Twitter is a trademark of Twitter Inc. in the United States, other countries, or both.

TIBCO and TIBCO Spotfire are trademarks or registered trademarks of TIBCO Software Inc.

Additional marks may be included in this document that are the trademarks, trade names, logos, and service marks of their respective owners and no rights to such marks are made by Cirro, Inc.

1.4 Cirro Corporate Offices

Address all questions or comments regarding this documentation to Cirro at:

Cirro, Inc.

120 Vantis, Suite 500 Aliso Viejo, CA 92656 Phone: (949) 373-9600


3


1.5 Getting Help

For assistance using Cirro products, contact Cirro Support at [email protected].

mailto:[email protected]


4


2 ODBC Driver Installation

This section describes the pre-requisites and installation instructions for the Cirro ODBC driver. Obtain the driver from your Cirro representative.

The Cirro ODBC driver is distributed in a 64-bit package and a 32-bit package. The two packages cannot

be installed simultaneously on the same system.

Only one version of the ODBC driver can be installed at a time. You do not need to manually uninstall older versions (of the same driver) before installing a new one.

2.1 Prerequisites

Before proceeding, determine whether your Windows environment is 32-bit or 64-bit. Go to the Windows start menu, right click “Computer” and select “Properties”. If the “System type” is “64-bit Operating

System” you need to install the 64-bit package. Otherwise, install the 32-bit package.

2.1.1 Software Prerequisites

This driver requires the following software to be present on the system prior to the start of driver

installation.

Operating systems and architectures: The Cirro ODBC driver can be used on 32-bit and 64-bit (x64) Microsoft Windows environments. IA64 is not currently supported.

Oracle Java 6 jre or jdk. The ODBC driver works well with Java 6 update 31, which can be

downloaded here: http://www.oracle.com/technetwork/java/javase/downloads/jre -6u31-download-1501637.html

There are three options for Java for windows: 32bit (x86) 64bit x64 AKA AMD64 or EMT64

64bit IA64 or Itanium The file you need is determined by the type of client you're using.

If you will use Cirro Analyst for Excel, this file must match the version (32-bit or 64-bit) or your Microsoft Excel 2010 installation. To check your Excel 2010 version, load Excel and click File,

then “Help”. The version is shown under the header “About Microsoft Excel” in the right column. If you are not sure whether you need the 64-bit or 32-bit version, contact Cirro Support.

2.1.2 Other Prerequisites

In order to install the ODBC driver, you will need a login with administrator access for the installation machine.

In order to create the ODBC data source, you will need a user account for the Cirro Data Hub, plus the IP address or host name for the server. Obtain that information now.

http://www.oracle.com/technetwork/java/javase/downloads/jre-6u31-download-1501637.html

http://www.oracle.com/technetwork/java/javase/downloads/jre-6u31-download-1501637.html


5


2.2 ODBC Driver Installation Steps

To install the ODBC driver:

1. Download the correct package (either 32-bit or 64-bit) for your system. (Contact your Cirro representative to obtain this file.)

2. Unzip the file and run the installer package.

3. Follow the prompts in the installation process to install the driver.


6


4. Once the installation is complete, you will see a confirmation message and will be prompted to

click “Close” to close the install Window. The ODBC driver has been installed. Proceed to “Creating the ODBC Data Source”.

2.3 Creating the ODBC Data Source

Once the ODBC driver has been installed, create an ODBC data source.

In the Windows Control Panel under System and Security > Administrative Tools, double-click the “Data Sources (ODBC)” item. This item can also be accessed by typing “odbc” in the Start menu search box.


7


In the “ODBC Data Source Administrator” window, select the “User DSN” tab, and then click the “Add” button.

In the “Create New Data Source” window, select the Cirro driver, and then click “Finish”.


8


When the new dialog titled “Cirro ODBC” is displayed, enter the datasource name (for example, “MyCirroServer”) and the IP address or host name of the Cirro server. Enter your username and

password.

Once all connection values have been set, click “OK” to save your connection.


9


2.3.1 Connection String Extra Properties

The “Connection String Extra Properties” field allows you to define other driver behaviors.

2.3.1.1 tablenamepattern

The “tablenamepattern” option is used to manage two-part table and view name mappings and is required for some BI tools.

The syntax for the option is

tablenamepattern=true


10


or

tablenamepattern=false

“false” is the default value for tablenamepattern.

When set to “true”, tablenamepattern modifies the object mapping behavior of the Cirro Data Hub to allow two-part object names in source queries. See 4 “Using tablenamepattern Functionality” on page 15 for more information on how to use this functionality.

2.3.1.2 schemanamepattern

Please contact Cirro Support for assistance using schemanamepattern.

2.3.2 Extra JVM args

The “Extra JVM args” field allows you to provide instructions on how to start a JVM. This feature allows passing extra arguments when the ODBC driver creates a JVM in order to connect to the Cirro Hub using JDBC.

Do not use this feature unless instructed to do so by Cirro Support.

When provided, the string should be formatted similar to the syntax used when launching a Java program on the shell.

Example:

-Xmx80m –Djavax.net.ssl.keyStore="c:\Users\user1\mykeystore"

-Djavax.net.ssl.keyStorePassword="secret"

2.4 Modifying or Removing a Cirro Data Source

Remove a data source by selecting it in the User DSN tab, then clicking “Remove”.


11


To review or change the configuration settings for an existing data source, click the “Configure” option for that data source. Make any needed changes, and save the data source.

2.5 Troubleshooting Cirro ODBC Driver Problems

This section lists some problems you may encounter when installing, configuring, and using the Cirro ODBC driver, and their solutions.

I Cannot Find the Cirro Driver in the ODBC Data Source Configuration Application

This problem usually means that you installed the wrong driver architecture (e.g. 32-bit instead of 64-bit), or installed the driver on an unsupported platform.

When I Try to Connect to a Data Source, the Connection Fails Immediately

This problem most often occurs in one of these situations:

1. The wrong driver is installed for your platform (e.g. a 32-bit driver on a 64-bit operating system).

2. The driver was installed on an unsupported platform.

3. The wrong Java version was installed for your Excel version (e.g. a 64-bit Java Runtime with a 32-bit Excel installation).

4. You have specified the wrong username and password to connect to Cirro.


12


When I Try to Connect to a Data Source, the Application Appears to Hang or Pause before Failing

Most likely, the wrong Cirro server IP address or hostname was specified in the data source configuration,

or the Cirro server is currently down or otherwise inaccessible from your system.

Other Problems

Please check with Cirro support if you run into other problems that you cannot resolve.


13


3 JDBC Driver Installation

The Cirro JDBC driver is a generic JDBC driver which is placed on the local system, rather than installed.

3.1 Prerequisites

The section lists prerequisites for using the Cirro JDBC driver.

3.1.1 Software Prerequisites

This driver requires Oracle Java 6 on the local system.

3.1.2 Other Prerequisites

You may want to obtain the address or host name of your Cirro server, plus a username and password, now. This information will be required before a connection can be established.

3.2 JDBC Driver Installation Steps

To install the Cirro JDBC driver:

1. Obtain the JDBC driver from Cirro.

2. Extract the compressed file to a folder on your local system.

3. Copy the cirrojdbc.jar file (class name com.cirro.jdbc.Driver) to a directory on the local system. See the installation instructions for the BI tool you are using with the Cirro JDBC driver for any special instructions regarding the location to place this file.

3.3 JDBC Driver Connection String Values

Once installed, use this JDBC connection string:

jdbc:derby://<connectionName>:<port(1527)>/cirro;create=true;user=<username>;

password=<password>;tablenamepattern=false;ssl=

where

connectionName is the name of the connection or server.

port is the connection port. This value is generally 1527.

username is a username on the Cirro Data Hub.

password is the password for username.

tablenamepattern is used to manage two-part table and view name mappings, and is required for some BI tools. The syntax for the option is tablenamepattern=true or tablenamepattern=false (default).

When set to “true”, tablenamepattern modifies the object mapping behavior of the Cirro Data Hub to allow two-part object names in source queries. See 4 “Using tablenamepattern Functionality”

on page 15 for more information on how to use this functionality.

ssl specifies whether an SSL connection is enabled for the client.


14


3.4 Troubleshooting Cirro JDBC Driver Problems

JDBC connections that fail are most likely caused by one of these problems:

The Cirro JDBC driver .jar was not placed in the directory needed for or referenced by the BI tool .

The Cirro Data Hub username and password specified in the BI tool are not correct .

The Cirro Data Hub is not accessible from the BI tool software or otherwise is not accessible on your network.

You are trying to connect to Cirro using an unsupported BI tool or an unsupported BI tool version.


15


4 Using tablenamepattern Functionality

Both the ODBC and JDBC drivers support the tablenamepattern option. With this functionality, users of tools such as Tableau which do not show the complete table tree structure can still access Cirro data sources, which use four-part object names.

To use the functionality, follow these steps:

1. Make sure your Cirro administrator has created multi-part name mappings for your data sources. Instructions for creating these mappings are provided in the Cirro Admin Guide and the Cirro

SQL Reference Guide.

2. Set the tablenamepattern value for the driver to “true”.

3. When displaying the object tree, your BI tool will show the object name using a pattern similar to

“db-catalog-schema-table”. Be aware of this difference, in case you are accustomed to seeing the object references in the form “db.catalog.schema.table” or “catalog.schema.table”.

4. If you need to submit manual SQL queries when tablenamepattern is set to true, make sure to

use the object name shown by your BI tool, not the period-delimited name.


16


5 Using SSL Client Connections

Cirro supports SSL for client connections to the Cirro Data Hub, through the extra parameters options for both ODBC and JDBC drivers.

The SSL options are:

ssl=off (default). Specifies that SSL is not used in client connections.

ssl=basic. The "basic" setting specifies server-side SSL authentication.

ssl=pureauthentication. The "pureauthentication" setting specifies mutual SSL authentication. Enabling "pureauthentication" requires additional steps (including client and server public key set

up) which are not covered in this document. Contact Cirro Support for assistance if mutual SSL authentication is required for your installation.

If either "basic" or "pureauthentication" is specified, this value must match the HUB_SSL_MODE setting

for the server, set in the cirro_env.local file. (Contact your Cirro system administrator for information determining the HUB_SSL_MODE setting for your installation).

17


6 Using BusinessObjects with Cirro

This section describes the requirements for, and the configuration process to, connect to a Cirro Data Hub using BusinessObjects.

6.1 Supported BusinessObjects Versions and Other Requirements

Cirro supports BusinessObjects 4.0. Other versions of BusinessObjects have not been certified by Cirro.

6.2 Prerequisites

You will need the Cirro JDBC driver in order to connect to a Cirro Data Hub from BusinessObjects .

Contact your Cirro representative to obtain this file.

Before starting configuration, make sure that the Cirro Data Hub you will connect to is accessible on your network, and that you have a username and password to access the DH.

6.3 Installation Steps

Follow these instructions for setting up BusinessObjects to access Cirro data. These instructions assume a supported BusinessObjects version has already been installed on your network.

1. Create a directory on the Business Objects Connection Server and place the derbyclient.jar file in

the directory. The path to this directory is not significant, but remember the location for future

reference.

2. Modify the BusinessObjects jdbc.sbo file for the “Generic JDBC datasource” and add the path of

Cirro JDBC Driver to the classpath of the JDBCDriver. If the Connection Server runs in Windows,

this file is located in “C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects

Enterprise XI 4.0\dataAccess\connectionServer\jdbc. The relevant code block from the jdbc.sbo

file is shown here:

<DataBases>

<DataBase Active="Yes" Name="Generic JDBC datasource">

<JDBCDriver>



<ClassPath>

<Path>C:\CirroJDBCDriver\derbyclient.jar</Path>

</ClassPath>

</JDBCDriver>

...

</DataBase>

...

</DataBases>


18


3. Open a BusinessObjects 4.0 application, such as the Information Design Tool, and create a new

connection.

a. Choose Generic -> Generic JDBC datasource -> JDBC Drivers and click next.

b. Use the following properties to configure the Cirro Data Hub connection:

1) User name: database login name.

2) Password: password for the user.

3) Database URL: jdbc:derby://{host name}:{port}/{database name};[create=true].

4) JDBC Class: org.apache.derby.jdbc.ClientDriver.


19


4. Click “Test Connection” and make sure that you can connect successfully.

If the connection fails, double-check the Cirro JDBC driver path and that you are using a valid

username and password.


20


7 Using IBM Cognos with Cirro

This section describes the requirements for, and the configuration process to, connect to a Cirro Data Hub using IBM Cognos.

7.1 Supported IBM Cognos Versions and Other Requirements

Cirro supports IBM Cognos 10. Other versions of Cognos have not been certified by Cirro.

7.2 Prerequisites

You will need the Cirro JDBC driver in order to connect to a Cirro Data Hub from IBM Cognos. Contact

your Cirro representative to obtain this driver.

Before starting configuration, make sure that the Cirro Data Hub you will connect to is accessible on your network, and that you have a username and password to access the DH.

7.3 Configuration Steps

Follow these instructions for setting up IBM Cognos to access Cirro data. These instructions assume a supported IBM Cognos version has already been installed on your network .

1. Add the Cirro JDBC driver and configuration files to the IBM Cognos class paths, in these locations in the IBM Cognos library folder on your system:

On Linux, this could be /opt/ibm/cognos/c10_64/webapps/p2pd/WEB-INF/lib On Windows, this could be C:\Program Files\IBM\<your IBM Cognos product name>\webapps\p2pd\WEB-INF\lib

Pleace the cirroclient.jar file in this folder. For IBM Cognos versions 10.2.1 or older, put the configuration file (DriverCirroAdaptorFactory.xml) in the same folder.

For IBM Cognos versions 10.2.2 or higher, put the JDBC Adaptor SDK jar (CirroJDBCAdaptor.jar) in the same folder.

2. Restart your IBM Cognos server program.

3. Use the IBM Cognos Framework manager or IBM Cognos Administration console to add the Cirro Data Hub as a new data source. a. In the New Data Source wizard, specify a name for the Cirro Data Hub connection, then click

"Next". b. Pull down the “Type” menu and select “JDBC”, then click "Next". This will take you to the

JDBC configuration menu.

c. In the JDBC configuration menu, pull down on the Type menu and select MySQL. IBM Cognos pre-fills the next fields with MySQL connection parameters which you are now going to override.


21


JDBC URL: jdbc:cirro://<host>:1527/cirro;create=true;tablenamepattern=true (don’t forget to replace the <host> token with your hostname / ip address for the Cirro Data Hub)

Driver class name: com.cirro.jdbc.Driver\

Provide the Signon information required.

d. Test the connection.

4. Proceed with configuring and exporting of the data source as you would with any other data source for IBM Cognos.


22


8 Using Google Analytics with Cirro

This section describes the requirements for, and the configuration process to, connect to Google Analytics from Cirro.

8.1 Prerequisites

In order to use Google Analytics as a data source, you will need to authorize Cirro to connect to your Google Analytics account from your local machine. Follow these steps for each client machine which requires access to Google Analytics:

1. Make sure you have the latest version of Cirro Analyst for Excel. Older versions of Cirro Analyst for Excel do not support Google Analytics.

2. Make sure you have the log in username and password for your Google Analytics account on

hand before starting the next step.

3. Use the Cirro Analyst for Excel Cirro_SQL() function or another Cirro-connected SQL client to submit these commands:

a. CREATE SYSTEM <userSpecifiedName> OF TYPE “GOOGLEANALYTICS” ; for example, CREATE SYSTEM ga OF TYPE “GOOGLEANALYTICS” ;

b. VALUES oauth_token(<userSpecifiedName>) ;

The response to this command will provide you with a code. Follow the instructions provided to enter this code on the Google Analytics website. For example, the response might read: “Go to http://www.google.com/device from a web browser and enter code

vbdd733v to authorize Cirro to access your data.” c. ADD AUTHORIZATION TO <userSpecifiedName> ;

This command turns on access to Google Analytics as a data source for your Cirro

installation and from your local machine and should only be performed after step b is complete.

4. You should now be able to see Google Analytics in your Cirro Analyst for Excel Data Explorer. (You may need to refresh your Data Explorer.)

8.2 Building Cirro Analyst for Excel Queries to Google Analytics

To query Google Analytics from Cirro Analyst for Excel, follow these steps:


23


1. From the function list, select the “Google” category and then “Cirro_GoogleAnalytics_Report”.

2. The argument selection for the function works the same way as other Cirro functions . You should

see your Google Analytics account as the data source when clicking the browse button for that row. See the Cirro Functions Guide for more information on using functions in Cirro Analyst for Excel.

8.3 Building SQL Queries for Google Analytics

To submit queries to Google Analytics using a SQL client, follow these guidelines:

1. The table name for the query is GOOGLEANALYTICS.Cirro.Cirro.Cirro. 2. The column names are the selection values available through the Google Analytics web

interface. See the Google Analytics documentation for more information.

3. All queries to Google Analytics must include startdate and enddate values in the WHERE clause. These values must be in the form ‘yyyy-MM-dd’.

4. Note that data types in returned values are of type “string”, even when the returned value is

numeric.

For example,


24


SELECT visits, source, keyword FROM GOOGLEANALYTICS.Cirro.Cirro.Cirro WHERE

startdate='2016-01-01' AND enddate = '2016-02-02' ORDER BY visits,source;

8.4 Removing Google Analytics Authorization

To remove a previously-authorized Google Analytics association from your system, submit this SQL command:

DROP AUTHORIZATION TO GOOGLEANALYTICS;

This command removes the ability to submit queries to Google Analytics, and removes the Google

Analytics Data Explorer tree item in Cirro Analyst for Excel.


25


9 Using TIBCO Spotfire with Cirro

This section describes the requirements for, and the configuration process to, connect to a Cirro Data Hub using TIBCO Spotfire.

9.1 Supported Spotfire Versions and Other Requirements

Cirro has verified this version of Spotfire for use when connecting to Cirro:

Tibco Spotfire 6.0

9.2 Prerequisites

You will need these components from Cirro in order to connect to a Cirro Data Hub from Spotfire. Contact your Cirro representative to obtain these files.

The Cirro ODBC driver.

Before starting configuration, make sure that the Cirro Data Hub you will connect to is access ible on your

network, and that you have a username and password to access the DH.

9.3 Spotfire Installation Instructions

Follow these instructions for using Spotfire to access Cirro data.

1. Install a supported version of Tibco Spotfire on your local system. Do not start Spotfire yet. 2. Install the Cirro ODBC driver. See “2 ODBC Driver Installation” on page 4.

3. Create the ODBC data source to the Cirro Data Hub. See “2.3 Creating the ODBC Data Source” on page 6. Add a schemanamepattern for this connection, using the instructions in that section.

4. Start Spotfire, log in to your Spotfire Server and click “Add Data Connection”.

5. Click “Add” and select “Database” from the “Other” section of the pull down list. 6. Select “Odbc Data Provider” and click “Configure”. 7. Use the pull down list of “System or user data source” items to select the DSN/data source you

configured previously.

You should now be able to access data that is available through the Cirro Data Hub.


26


10 Using Tableau with Cirro

This section describes the requirements for, and the configuration process to, connect to a Cirro Data Hub using Tableau.

10.1 Supported Tableau Versions and Other Requirements

Cirro has verified these versions of Tableau for use when connecting to Cirro:

Tableau Desktop 6.1 and 7.0

Tableau Server 7.0

10.2 Prerequisites

You will need these components from Cirro in order to connect to a Cirro Data Hub from Tableau. Contact your Cirro representative to obtain these files.

The Cirro ODBC driver.

The Cirro ODBC Customization .tdc file (cirro_odbc-customization.tdc).

Before starting configuration, make sure that the Cirro Data Hub you will connect to is ac cessible on your network, and that you have a username and password to access the DH.

10.3 Tableau Installation Instructions

Follow these instructions for using Tableau to access Cirro data.

1. Install a supported version of Tableau on your local system. Do not start Tableau yet.

2. Install the Cirro ODBC driver. See “2 ODBC Driver Installation” on page 4.

3. Create the ODBC data source to the Cirro Data Hub. See “2.3 Creating the ODBC Data Source” on page 6.

4. Save the .tdc file to this directory on your local system: C:\Users\<your user name>\Documents\My Tableau Repository\Datasources.

5. Start Tableau, select “Connect to Data”, then “Other Databases (ODBC)”.

6. In the “Generic ODBC Connection” dialog box, check the “DSN” button, and use the pull down list to select the DSN/data source you configured previously.

You should now be able to access data that is available through the Cirro Data Hub.


27


11 Document Change History

This section lists recent changes to this document.

Document Version Release Date Description of Change(s)

2.0 January 28, 2016 Version 2.0 document release.