Progress DataDirect for ODBC for Apache Cassandra Driver

Transcription

1 Progress DataDirect for ODBC for Apache Cassandra Driver Quick Start for Windows Release 8.0.0

2

3 Copyright 2017 Progress Software Corporation and/or one of its subsidiaries or affiliates. All rights reserved. These materials and all Progress software products are copyrighted and all rights are reserved by Progress Software Corporation. The information in these materials is subject to change without notice, and Progress Software Corporation assumes no responsibility for any errors that may appear therein. The references in these materials to specific platforms supported are subject to change. Business Making Progress, Corticon, DataDirect (and design), DataDirect Cloud, DataDirect Connect, DataDirect Connect64, DataDirect XML Converters, DataDirect XQuery, Deliver More Than Expected, Icenium, Kendo UI, Making Software Work Together, NativeScript, OpenEdge, Powered by Progress, Progress, Progress Software Developers Network, Rollbase, SequeLink, Sitefinity (and Design), SpeedScript, Stylus Studio, TeamPulse, Telerik, Telerik (and Design), Test Studio, and WebSpeed are registered trademarks of Progress Software Corporation or one of its affiliates or subsidiaries in the U.S. and/or other countries. AccelEvent, Analytics360, AppsAlive, AppServer, Arcade, BravePoint, BusinessEdge, DataDirect Spy, DataDirect SupportLink, DevCraft, DigitalFactory, Fiddler, Future Proof, High Performance Integration, JustCode, JustDecompile, JustMock, JustTrace, OpenAccess, ProDataSet, Progress Arcade, Progress Profiles, Progress Results, Progress RFID, Progress Software, ProVision, PSE Pro, SectorAlliance, Sitefinity, SmartBrowser, SmartComponent, SmartDataBrowser, SmartDataObjects, SmartDataView, SmartDialog, SmartFolder, SmartFrame, SmartObjects, SmartPanel, SmartQuery, SmartViewer, SmartWindow, WebClient, and Who Makes Progress are trademarks or service marks of Progress Software Corporation and/or its subsidiaries or affiliates in the U.S. and other countries. Java is a registered trademark of Oracle and/or its affiliates. Any other marks contained herein may be trademarks of their respective owners. Please refer to the readme applicable to the particular Progress product release for any third-party acknowledgements required to be provided in the documentation associated with the Progress product. Updated: 2017/01/11 3

4 Copyright 4

5 Quick Start: Progress DataDirect for ODBC for Apache Cassandra Driver for Windows This quick start provides basic information that allows you to install, test connect, and access your data with some commonly used third-party applications. To take full advantage of the features and functionality available for your driver, refer to the Progress DataDirect for ODBC for Apache Cassandra Driver User's Guide and Reference. Note: OEM CUSTOMERS: Refer to the Progress DataDirect for ODBC Drivers Distribution Guide for information on installing, branding, unlocking, and distributing your branded drivers. This quick start covers the following topics: Before You Start on page 5 Requirements and Support on page 6 Downloading the Driver on page 6 Installing the ODBC Driver on Windows on page 7 Setting the Library Path Environment Variable on page 10 Configuring a Data Source on page 11 Testing the Connection on page 13 Tuning for Performance on page 14 Accessing Data With Third-Party Applications on page 17 Troubleshooting Setup/Connection Issues on page 24 Additional Resources on page 25 Before You Start Before you get started, you need the following: Appropriate user permissions to modify your environment and to read, write, and execute various files in the DataDirect for ODBC installation directory. Connection information: Host Name: The name or the IP address of the server to which you want to connect. Keyspace Name: The name of the Apache Cassandra keyspace to which you want to connect by default. The keyspace must exist, or the connection attempt will fail. Logon ID: The default user ID that is used to connect to your database. Port Number: The port number of the server listener. 5

6 Chapter 1: Quick Start: Progress DataDirect for ODBC for Apache Cassandra Driver for Windows For licensed installations, you will also need the following information that was provided by Progress DataDirect: IPE Key (control number) Serial Number Requirements and Support Driver Requirements: The driver requires a Java Virtual Machine (JVM): Java SE 6 or higher. Supported Data Sources: Apache Cassandra 3.0 and higher Apache Cassandra 2.0 and higher DataStax Enterprise 5.0 and higher DataStax Enterprise 4.7 and higher For more information on supported data sources, visit the Progress DataDirect Supported Configurations Web page. Downloading the Driver To download the ODBC Apache Cassandra driver: 1. Visit the Progress DataDirect Connectors Download Web page. 2. Enter Apache Cassandra in the search field. 3. Select ODBC for the interface. 4. Select the OS and architecture your application runs on: Windows 32-bit Windows 64-bit 5. Enter your contact information, and click Download. The installer program is downloaded to your system. See "Installing the ODBC Driver on Windows" for instructions on installing the driver. See also Installing the ODBC Driver on Windows on page 7 6

7 Installing the ODBC Driver on Windows Installing the ODBC Driver on Windows Note: OEM CUSTOMERS: Refer to the Progress DataDirect for ODBC Drivers Distribution Guide for information on installing, branding, unlocking, and distributing your branded drivers. This section provides instructions for installing the driver using a GUI. For complete installation instructions, refer to the Progress DataDirect for ODBC Drivers Installation Guide. To install the drivers from downloaded files: 1. Unzip the files, maintaining the directory structure in the zip file, to a temporary directory, for example, c:\temp. After extracting the files, the temporary directory should contain the following files: PROGRESS_DATADIRECT_ODBC_n.n_WIN_xx_INSTALL.exe PROGRESS_DATADIRECT_ODBC_COMMON_n.n.n_WIN_xx_INSTALL.iam.zip PROGRESS_DATADIRECT_ODBC_DOCUMENTATION_n.n.n_INSTALL.iam.zip PROGRESS_DATADIRECT_ODBC_CASSANDRA_n.n.n_WIN_xx_INSTALL.iam.zip 2. From Windows Explorer, navigate to the temporary directory that contains the unzipped installer files; then, double-click the installer program: For 32-bit drivers, the installer program is named: PROGRESS_DATADIRECT_ODBC_nn_WIN_32_INSTALL.exe For 64-bit drivers, the installer program is named: PROGRESS_DATADIRECT_ODBC_nn_WIN_64_INSTALL.exe where: nn is the product version number. For example, this value is 8.0 for the 8.0.x version of the product. 3. The Introduction window for the product installation appears. Click Next to continue. 4. The License Agreement window appears. Make sure that you read and understand the license agreement. To continue with the installation, select the I accept the terms of the License Agreement option; then, click Next. Note: You can exit the installer program at any time by clicking Cancel or return to the previous window by clicking Previous. 5. The Install Directory window appears. In the Where Would You Like to Install? field, type the path, including the drive letter, of the product installation directory or click the Choose... button to browse to and select an installation directory. If you are running the 32-bit installer on 64-bit Windows, the default value for the installation directory is C:\Program Files (x86)\progress\datadirect\odbc_nn. For all other installations, the default value for the installation directory is C:\Program Files\Progress\DataDirect\ODBC_nn Verify that you have entered (or selected) the correct installation directory. Then, click Next to continue. 7

8 Chapter 1: Quick Start: Progress DataDirect for ODBC for Apache Cassandra Driver for Windows To restore the installation directory to its default setting, click Restore Default. 6. Choose the type of installation to perform. Select one of the following options: Evaluation Installation (will expire in 15 days). Select this option to install an evaluation version of the driver. Click Next to continue with the installation. Skip to Step 10 on page 9. OEM/Licensed Installation. Select this option if you purchased a licensed version of one or multiple drivers. Click Next. Proceed to the next step. Note: OEM CUSTOMERS: Refer to the Progress DataDirect for ODBC Drivers Distribution Guide for information on installing, branding, unlocking, and distributing your branded drivers. 7. The Product Registration window appears. Type the IPE key (control number) that was provided by Progress DataDirect in the IPE Key field, and click the Validate button. A tree menu of drivers with valid licenses appears in the selection box. You can add one or multiple keys, one at a time. 8. From the tree menu, select the drivers that you want to install. Drivers that are already installed are listed in the Drivers (Installed) tree and cannot be deselected. To remove installed drivers, you must uninstall the product. Click Next to continue. Note: If you are installing a different version of a currently installed driver, the installer will overwrite the existing driver files with the version that you are installing. 9. The Product Registration window appears. 8

9 Installing the ODBC Driver on Windows Provide the following information: a) Type your name and company name in the corresponding fields. b) Type the serial number that was provided by Progress DataDirect. Click Next to continue. Skip to Step 11 on page The Driver Evaluation Selection window appears. From the Drivers To Be Evaluated tree, select the Apache Cassandra driver. Drivers that are already installed are listed in the Drivers (Installed) tree and cannot be deselected. 9

10 Chapter 1: Quick Start: Progress DataDirect for ODBC for Apache Cassandra Driver for Windows 11. The Create Default Default Data Source window appears. Select the Create Default Data Source box to define a user data source in HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI for each DataDirect driver that you install. Warning: If you select Create Default Data Sources, existing data sources in your registry with the same DataDirect default name will be overwritten. To maintain your current DataDirect default data sources, rename them before you continue. Then, click Next to continue. 12. The Pre-Installation Summary window provides the opportunity to review the information you have entered. When you are satisfied with your installation or branding option selections, click Install to begin the installation. 13. When the installation finishes, the Install Complete window appears. You may be prompted to restart your system, but it is not required to use the product. Select one of the following options: Yes, restart my system. Select this option if you are ready to restart your system. The installer will restart your system when you exit the program. No, I will restart my system myself. Select this option if you prefer to use the product without restarting the system, or if you are not ready to restart the system. Click Done to exit the installer program. This completes the installation. A Progress DataDirect program group is created as part of the installation. This program group provides the following shortcuts: ODBC Administrator ODBC Driver Help ODBC Performance Tuning Wizard ODBC Readme Processor Information Utility Uninstall Progress DataDirect for ODBC bit [32-bit only] Uninstall Progress DataDirect for ODBC bit [64-bit only] XML Persistence Demo [32-bit only] Before you begin using your driver, see "Setting the Library Path Environment Variable." See also Setting the Library Path Environment Variable on page 10 Setting the Library Path Environment Variable Before you can use your driver, you must set the PATH environment variable to include the path of the jvm.dll file of your Java Virtual Machine (JVM). 10

11 Configuring a Data Source Configuring a Data Source To configure a basic data source to test your connection: 1. Start the ODBC Administrator by selecting its icon from the Progress DataDirect for ODBC program group. 2. Click either the User DSN, System DSN, or File DSN tab to display a list of data sources. User DSN: If you installed an Apache Cassandra data source as part of the installation, select Apache Cassandra from the list of data sources and click Configure to display the driver Setup dialog box. If you did not install an Apache Cassandra data source during installation, click Add to display a list of installed drivers. Select the Apache Cassandra driver and click Finish to display the driver Setup dialog box. System DSN: To configure a new system data source, click Add to display a list of installed drivers. Select the Apache Cassandra driver and click Finish to display the driver Setup dialog box. File DSN: To configure a new file data source, click Add to display a list of installed drivers. Select the Apache Cassandra driver and click Advanced to specify attributes; otherwise, click Next to proceed. Specify a name for the data source and click Next. Verify the data source information; then, click Finish to display the driver Setup dialog box. 3. The General tab of the Setup dialog box appears by default. 11

12 Chapter 1: Quick Start: Progress DataDirect for ODBC for Apache Cassandra Driver for Windows Note: The General tab displays only fields that are required for creating a data source. The fields on all other tabs are optional. On the General tab, provide the following information; then, click Schema Map tab. Data Source Name: Type a string that identifies this data source configuration, such as Accounting. Description: Type an optional long description of a data source name, such as My Accounting Database. Host Name: Type the name or IP address of the server to which you want to connect. Port Number: Type the port number of the server listener. Keyspace Name: Type the name of the keyspace to which you want to connect. 4. The Schema Map tab appears. 12

13 Testing the Connection On the Schema Map tab, provide the following information; then, click Apply: Schema Map: Type the name and location of the configuration file where the relational map of native data is written. The driver looks for this file when connecting to a server. If the file does not exist, the driver creates the following file: application_data_folder\local\progress\datadirect\cassandra_schema\host_name.config. 5. Your driver is now configured with the basic settings necessary to connect your driver. Choose from the following: If you would like to test the connection, proceed to Testing the Connection on page 13. If you would like to tune your driver for performance, proceed to Tuning for Performance on page 14. If you would like to save the values you have specified and close the setup dialog, click OK. These values will be used as the default settings when you connect to a data source. Testing the Connection To test the connection: 13

14 Chapter 1: Quick Start: Progress DataDirect for ODBC for Apache Cassandra Driver for Windows 1. After you have configured the Apache Cassandra data source, you can click Test Connect on the Setup dialog box to attempt to connect to the data source using the connection options specified in the dialog box. 2. The logon dialog box appears. The fields have been populated with the values you supplied in "Configuring a Data Source." If Authentication Method is set to 0 - User ID/Password, type your Apache Cassandra password in the corresponding field. Click OK to test connect. Note that the information you enter in the logon dialog box during a test connect is not saved. If the driver can connect, it releases the connection and displays a Connection Established message. Click OK. If the driver cannot connect because of an incorrect environment or connection value, it displays an appropriate error message. Click OK. 3. On the driver Setup dialog box, click OK. The values you have specified are saved and are the defaults used when you connect to the data source. You can change these defaults by using the previously described procedure to modify your data source, or you can override these defaults by connecting to the data source using a connection string with alternate values. Refer to the Progress DataDirect for ODBC for Apache Cassandra Driver User's Guide and Reference for additional information. See also Configuring a Data Source on page 11 Tuning for Performance The connection options described in this section directly affect the performance of your driver. To tune for performance, configure your driver according to the recommended settings and your environment. Application Using Threads Purpose: Determines whether the driver works with applications using multiple ODBC threads. Performance Impact: 14

15 Tuning for Performance The driver coordinates concurrent database operations (operations from different threads) by acquiring locks. Although locking prevents errors in the driver, it also decreases performance. If your application does not make ODBC calls from different threads, the driver has no reason to coordinate operations. Recommended Settings: If your application is multi-threaded, enable (default) this option. If your application is not multi-threaded, disable this option for improved performance. GUI Tab: Advanced Fetch Size Purpose: Specifies the number of rows that the driver processes before returning data to the application when executing a Select. This value provides a suggestion to the driver as to the number of rows it should internally process before returning control to the application. The driver may fetch fewer rows to conserve memory when processing exceptionally wide rows. Performance Impact: Fetch Size and Native Fetch Size can be used to adjust the trade-off between throughput and response time. In general, setting larger values for Fetch Size and Native Fetch Size will improve throughput, but can reduce response time. Recommended Settings: Set Fetch Size to suit your environment. Smaller fetch sizes can improve the initial response time of the query. Larger fetch sizes improve overall fetch times at the cost of additional memory. GUI Tab: Advanced JVM Arguments Purpose: Contains the arguments that are passed to the JVM that the driver is starting. The JVM Arguments connection option can be used to adjust the heap size of the JVM. Performance Impact: Increasing the maximum Java heap size with JVM Arguments increases the amount of data the driver accumulates in memory and reduces the need to write to disk. JVM Arguments can be used in conjunction with Result Memory Size to ensure that result sets fit easily within the JVM's free heap space. When result sets fit easily within the JVM's free heap space, performance can be improved and out of memory errors can be avoided. Recommended Settings: By default, the maximum size of an intermediate result set that the driver holds in memory is determined by a percentage of the maximum Java heap size. Testing has shown that the default behavior works in most scenarios. However, you may choose to make the following adjustments to suit your requirements. Use JVM Arguments to increase the maximum Java heap size and avoid the need to page to disk. In conjunction with the Result Memory Size connection option, use JVM Arguments to adjust the maximum Java heap size such that your result sets fit easily within the JVM's free heap space. GUI Tab: SQL Engine 15

16 Chapter 1: Quick Start: Progress DataDirect for ODBC for Apache Cassandra Driver for Windows Native Fetch Size Purpose: Specifies the number of rows of data the driver attempts to fetch from the native data source on each request submitted to the server. Performance Impact: Fetch Size and Native Fetch Size can be used to adjust the trade-off between throughput and response time. In general, setting larger values for Fetch Size and Native Fetch Size will improve throughput, but can reduce response time. Recommended Settings: Set Native Fetch Size to suit your environment. Smaller fetch sizes can improve the initial response time of the query. Larger fetch sizes improve overall fetch times at the cost of additional memory. GUI Tab: Advanced Read Consistency Purpose: Specifies how many replica servers (replicas) must respond to a read request before returning data to the client application. Performance Impact: The Read Consistency connection option manages the trade-off between the consistency and availability of your data. Higher consistency requires more processing and therefore can slow response time. Recommended Settings: By default, Read Consistency is set to quorum and data is returned after a quorum of replicas has responded from any data center. If your application requires higher consistency than the default, consider setting Read Consistency to all so that all replicas must respond before data is returned to the application. If consistency is not a great concern and you want to increase the speed with which data is returned to an application, consider setting Read Consistency to one. This setting returns data from the closest replica set. GUI Tab: Advanced Result Memory Size Purpose: Specifies the maximum size, in megabytes, of an intermediate result set that the driver holds in memory. When this threshold is reached, the driver writes a portion of the result set to disk in temporary files. Performance Impact: Increasing the value of Result Memory Size can improve performance by avoiding the need to page to disk. Result Memory Size can be used in conjunction with JVM Arguments to ensure that result sets fit easily within the JVM's free heap space. When result sets fit easily within the JVM's free heap space, performance can be improved and out of memory errors can be avoided. Recommended Settings: 16

17 Accessing Data With Third-Party Applications Testing has shown that the default setting of -1 works in most scenarios. When set to -1, the maximum size of an intermediate result set that the driver holds in memory is determined by a percentage of the maximum Java heap size. When this threshold is reached, the driver writes a portion of the result set to disk. However, you may choose to make the following adjustments to suit your requirements. Increase the value of Result Memory Size to avoid the need to page to disk. Adjust the value of Result Memory Size and JVM Arguments such that your result sets fit easily within the JVM's free heap space. GUI Tab: Advanced Write Consistency Purpose: Determines the number of replica servers (replicas) on which the write must succeed before returning an acknowledgment to the client application. Performance Impact: Higher consistency requires more processing, since the write must succeed on a greater number of replicas. Therefore, higher write consistency can slow response time. Recommended Settings: By default, Write Consistency is set to quorum. After the write succeeds on a quorum of replicas, an acknowledgment is returned to the client application. If your application requires higher consistency than the default, consider setting Write Consistency to all so that the write must succeed across all replicas in the cluster. If consistency is not a great concern and you want to decrease your applications response time, consider setting Write Consistency to one. With this setting, the write must succeed on at least one node. GUI Tab: Advanced Accessing Data With Third-Party Applications The following sections guide you through using the driver to access your data with some common third-party applications: Accessing Data in Tableau on page 17 Accessing Data in Microsoft Excel from the Data Connection Wizard on page 20 Accessing Data in Microsoft Excel from the Query Wizard on page 22 Accessing Data in Tableau After you have configured your data source, you can use the driver to access your Cassandra data with Tableau. Tableau is a business intelligence software program that allows you to easily create reports and visualized representations of your data. By using the driver with Tableau, you can improve performance when retrieving data while leveraging the driver's relational mapping tools. 17

18 Chapter 1: Quick Start: Progress DataDirect for ODBC for Apache Cassandra Driver for Windows To use the driver to access data with Tableau: 1. Navigate to the \Tableau subdirectory of the Progress DataDirect installation directory; then, locate the Tableau data source file, DataDirect Apache Cassandra.tdc. 2. Copy the DataDirect Apache Cassandra.tdc into the following directory: C:\Users\user_name\Documents\My Tableau Repository\Datasources 3. Open Tableau. If the Connect menu does not open by default, select Data > New Data Source or the Add New Data Source button to open the menu. 4. From the Connect menu, select Other Databases (ODBC). 5. The Server Connection dialog appears. 18

19 Accessing Data With Third-Party Applications In the DSN field, select the data source you want to use from the drop down menu. For example, My DSN. Then, click Connect. The Logon to Cassandra dialog appears pre-populated with the connection information you provided in your data source. 6. If required, type your user name and password; then, click OK. The Logon dialog closes. Then, click OK on the Server Connection dialog. 7. The Data Source window appears. 19

20 Chapter 1: Quick Start: Progress DataDirect for ODBC for Apache Cassandra Driver for Windows By default, Tableau connects live, or directly, to your data. We recommend that you use the default settings to avoid extracting all of your data. However, if you prefer, you can import your data by selecting the Extract option at the top of the dialog. 8. In the Schema field, select the database you want to use. The tables stored in this database are now available for selection in the Table field. You have successfully accessed your data and are now ready to create reports with Tableau. For more information, refer to the Tableau product documentation at: Accessing Data in Microsoft Excel from the Data Connection Wizard After you have configured your data source, you can use the driver to access your data with Microsoft Excel from the Query Wizard. Using the driver with Excel provides improved performance when retrieving data, while leveraging the driver's relational-mapping tools. To use the driver to access data with Excel from the Query Wizard: 1. Open your workbook in Excel. 2. From the Data menu, select From Other Sources>From Microsoft Query. 3. The Choose Data Source dialog appears. 20

21 Accessing Data With Third-Party Applications From the Databases list, select your data source. For example, MyDSN. Click Next. 4. The logon dialog appears pre-populated with the connection information you provided in your data source. If required, type your password. Click OK to proceed. Note: The logon dialog may reappear if Excel needs to access additional information from the data source. If this occurs, re-enter your password; then, click OK to proceed to the next step. 5. The Query Wizard - Choose Columns window appears. Choose the columns you want to import into your workbook. To add a column, select the column name in Available tables and columns pane; then, click the > button. After you add the columns you want to include, click Next to continue. 6. Optionally, filter your data using the drop down menus; then, click Next. 7. Optionally, sort your data using the drop down menus; then, click Next. 8. Select "Return Data to Microsoft Excel"; then, click Finish. 9. The Import Data window appears. 21

22 Chapter 1: Quick Start: Progress DataDirect for ODBC for Apache Cassandra Driver for Windows Select the desired view and insertion point for your data. Click OK. You have successfully accessed your data in Excel using the Query Wizard. For more information, refer to the Microsoft Excel product documentation at: Accessing Data in Microsoft Excel from the Query Wizard After you have configured your data source, you can use the driver to access your data with Microsoft Excel from the Data Connection Wizard. Using the driver with Excel provides improved performance when retrieving data, while leveraging the driver's relational-mapping tools. To use the driver to access data with Excel from the Data Connection Wizard: 1. Open your workbook in Excel. 2. From the Data menu, select From Other Sources>From Data Connection Wizard. 3. The Welcome to Data Connection Wizard dialog appears. Select ODBC DSN from the data source list; then, click Next. 22

23 Accessing Data With Third-Party Applications 4. From the ODBC data sources list, select your data source. Click Next. 5. The logon dialog app pre-populated with the connection information you provided in your data source. If required, type your password. Click OK to proceed. Note: The logon dialog may reappear if Excel needs to access additional information from the data source. If this occurs, re-enter your password; then, click OK to proceed to the next step. 6. The Select Database and Table window appears. To access data from multiple tables, uncheck the Connect to a specific table box; then, click Next. To access data from a specific table, select the table you want to import from the list; then, click Next. 7. Enter the file name, description, and, optionally, the friendly name and search keywords for your Data Connection file in the corresponding fields. Click Finish. If you chose to access data from multiple tables in Step 6 on page 23, proceed to the next step. If you chose to access data from a specific table in Step 6 on page 23, skip to Step 9 on page The Select Table window appears. 23

24 Chapter 1: Quick Start: Progress DataDirect for ODBC for Apache Cassandra Driver for Windows Select the tables that you want to import into your workbook; then, click OK. 9. The Import Data window appears. Select the desired view and insertion point for the data. Click OK. You have successfully accessed your data in Excel using the Data Connection Wizard. For more information, refer to the Microsoft Excel product documentation at: Troubleshooting Setup/Connection Issues This section describes common setup/connection issues you may encounter while trying to establish a database connection with the driver as well as some potential reasons for these issues. If you are experiencing a problem not described in this section, comprehensive troubleshooting resources are available in the "Troubleshooting" section of the User's Guide and Reference for your driver. In addition, Progress DataDirect offers a variety of options to meet your technical support needs. See Contacting Technical Support on page 25 for details. Common Setup/Connection Issues You are experiencing a setup/connection issue if you are encountering an error or hang while you are trying to make a database connection with the ODBC driver or are trying to configure the ODBC driver. Some common errors that are returned by the ODBC driver if you are experiencing a setup/connection issue include: Specified driver could not be loaded. Data source name not found and no default driver specified. Unable to connect to destination. Invalid username/password; logon denied. 24

25 Additional Resources Troubleshooting the Issue Some common reasons that setup/connection issues occur are: The library path environment variable is not set correctly. Before you can use the driver, you must set the PATH environment variable to the path of the jvm.dll file of your Java Virtual Machine (JVM). For Windows platforms, the library path environment variable is PATH. The database and/or listener are not started. The ODBC driver s connection options are not set correctly when configuring the driver. For example, the host name or port number are not correctly configured. See "Configuring a Data Source" for a list of connection options that are required for the driver to connect properly to the underlying database. See also Configuring a Data Source on page 11 Additional Resources In addition to this quick start, the following resources enable you to take full advantage of the features and support offered for your driver. Product Documentation Library contains a comprehensive set of product documentation, including the following guides: Progress DataDirect for ODBC Drivers Installation Guide details requirements and procedures for installing the product. Progress DataDirect for ODBC for Apache Cassandra Driver User's Guide and Reference guides you through using and configuring the driver, provides detailed reference information, and explains the tools used to troubleshoot common problems. Progress Support Knowledgebase provides answers to questions, access to technical documentation, release notes, product alerts and other support information. Progress Community allows you to contribute, share, and network with other Progress users and employees. Technical Support provides technical support services, including maintenance services and opening a support case. Contacting Technical Support Progress DataDirect offers a variety of options to meet your support needs. Please visit our Web site for more details and for contact information: The Progress DataDirect Web site provides the latest support information through our global service network. The SupportLink program provides access to support contact details, tools, patches, and valuable information, including a list of FAQs for each product. In addition, you can search our Knowledgebase for technical bulletins and other information. When you contact us for assistance, please provide the following information: 25

26 Chapter 1: Quick Start: Progress DataDirect for ODBC for Apache Cassandra Driver for Windows Your number or the serial number that corresponds to the product for which you are seeking support, or a case number if you have been provided one for your issue. If you do not have a SupportLink contract, the SupportLink representative assisting you will connect you with our Sales team. Your name, phone number, address, and organization. For a first-time call, you may be asked for full information, including location. The Progress DataDirect product and the version that you are using. The type and version of the operating system where you have installed your product. Any database, database version, third-party software, or other environment information required to understand the problem. A brief description of the problem, including, but not limited to, any error messages you have received, what steps you followed prior to the initial occurrence of the problem, any trace logs capturing the issue, and so on. Depending on the complexity of the problem, you may be asked to submit an example or reproducible application so that the issue can be re-created. A description of what you have attempted to resolve the issue. If you have researched your issue on Web search engines, our Knowledgebase, or have tested additional configurations, applications, or other vendor products, you will want to carefully note everything you have already attempted. A simple assessment of how the severity of the issue is impacting your organization. 26