ProgressDataDirect for ODBC Drivers · install_dir isthepathtotheproductinstallationdirectory. driver_name istheabbreviatednameofyourdriver.Forexample,RedshiftisthisvaluefortheAmazonRedshift

Progress DataDirect for ODBCDriversInstallation Guide

March 2020

Copyright

© 2020 Progress Software Corporation and/or one of its subsidiaries or affiliates. Allrights reserved.These materials and all Progress® software products are copyrighted and all rights are reserved by ProgressSoftware Corporation. The information in these materials is subject to change without notice, and ProgressSoftware Corporation assumes no responsibility for any errors that may appear therein. The references inthese materials to specific platforms supported are subject to change.

Corticon, DataDirect (and design), DataDirect Cloud, DataDirect Connect, DataDirect Connect64, DataDirectXML Converters, DataDirect XQuery, DataRPM, Defrag This, Deliver More Than Expected, Icenium, Ipswitch,iMacros, Kendo UI, Kinvey, MessageWay, MOVEit, NativeChat, NativeScript, OpenEdge, Powered by Progress,Progress, Progress Software Developers Network, SequeLink, Sitefinity (and Design), Sitefinity, SpeedScript,Stylus Studio, TeamPulse, Telerik, Telerik (and Design), Test Studio, WebSpeed, WhatsConfigured,WhatsConnected, WhatsUp, and WS_FTP are registered trademarks of Progress Software Corporation or oneof its affiliates or subsidiaries in the U.S. and/or other countries. Analytics360, AppServer, BusinessEdge,DataDirect Autonomous REST Connector, DataDirect Spy, SupportLink, DevCraft, Fiddler, iMail, JustAssembly,JustDecompile, JustMock, NativeScript Sidekick, OpenAccess, ProDataSet, Progress Results, ProgressSoftware, ProVision, PSE Pro, SmartBrowser, SmartComponent, SmartDataBrowser, SmartDataObjects,SmartDataView, SmartDialog, SmartFolder, SmartFrame, SmartObjects, SmartPanel, SmartQuery, SmartViewer,SmartWindow, and WebClient are trademarks or service marks of Progress Software Corporation and/or itssubsidiaries or affiliates in the U.S. and other countries. Java is a registered trademark of Oracle and/or itsaffiliates. Any other marks contained herein may be trademarks of their respective owners.

Updated: 2020/03/06

3Progress DataDirect for ODBC Drivers: Installation Guide: Version March 2020

Progress DataDirect for ODBC Drivers: Installation Guide: Version March 20204

Copyright

Table of Contents

Preface............................................................................................................7Welcome to the Progress DataDirect for ODBC Drivers Installation Guide............................................7

About the Product Documentation...............................................................................................8

Product Platforms........................................................................................................................9

Conventions Used in This Guide................................................................................................11

Contacting Technical Support....................................................................................................12

Requirements and Support.........................................................................13Installer Requirements..........................................................................................................................14

Driver Requirements.............................................................................................................................14

Supported Databases...........................................................................................................................16

Supported Operating Systems.............................................................................................................16

Installation on Windows..............................................................................17Before You Install (Windows)................................................................................................................17

System Requirements...............................................................................................................18

Default Installation Directory......................................................................................................18

Installing from Downloaded Files..........................................................................................................19

Installing Using a GUI................................................................................................................19

Log Files Created During Installation.........................................................................................24

Unlocking and Distributing Branded ODBC Drivers...................................................................25

Installing from a Network Directory............................................................................................25

Silent Installations of Licensed Drivers......................................................................................25

Testing Your Driver Installation..............................................................................................................31

Configuring Drivers and Data Sources.................................................................................................32

Processor Information Utility.................................................................................................................32

Installing to a Different Location...........................................................................................................32

Uninstalling the Product on Windows...................................................................................................32

Uninstalling the 7.1 Product.......................................................................................................32

Uninstalling the 8.0 Product ......................................................................................................32

Upgrading an Evaluation Installation....................................................................................................33

Adding Drivers to Your Installation........................................................................................................34

For More Information............................................................................................................................34

Installation on UNIX and Linux...................................................................35Before You Install (UNIX/Linux).............................................................................................................35



Contents



Installing Using a GUI................................................................................................................37

Installing Using a Command-Line..............................................................................................40


Silent Installations of Licensed Drivers......................................................................................43


Processor Information Utility.................................................................................................................50


Upgrading an Evaluation Installation....................................................................................................51


Uninstalling the Product on UNIX and Linux........................................................................................51

Uninstalling the 7.1 Product on UNIX and Linux........................................................................51

Uninstalling the 8.0 Product on UNIX and Linux........................................................................51


Installation on Mac OS X.............................................................................55Before You Install (Mac OS X)..............................................................................................................55








Uninstalling the Product on Mac OS X.................................................................................................61


Index..............................................................................................................63


Contents

Preface

For details, see the following topics:

• Welcome to the Progress DataDirect for ODBC Drivers Installation Guide

Welcome to the Progress DataDirect for ODBC DriversInstallation Guide

This book is your installation guide to Progress DataDirect® for ODBC drivers, which includes the following products:

• Progress DataDirect® Autonomous REST Connector® for ODBC

• Progress DataDirect® for ODBC for Amazon Redshift™ Wire Protocol

• Progress DataDirect® for ODBC for Apache Hive™ Wire Protocol

• Progress DataDirect® for ODBC for Apache Cassandra™ Wire Protocol

• Progress DataDirect® for ODBC for Apache Spark SQL™ Wire Protocol

• Progress DataDirect® for ODBC for Google BigQuery™

• Progress DataDirect® for ODBC for MongoDB™

• Progress DataDirect® for ODBC for Oracle Service Cloud™

• Progress DataDirect® for ODBC for Oracle™ Wire Protocol

• Progress DataDirect® for ODBC for Salesforce™

• Progress DataDirect® for ODBC for Snowflake™

• Progress DataDirect® for ODBC for SQL Server™ Wire Protocol


The drivers are available in both 32- and 64-bit versions.

Note: If your driver is not listed, refer to the DataDirect Connect Series for ODBC Installation Guide forinformation about installing your drivers. The DataDirect documentation library is available at:https://www.progress.com/documentation/datadirect-connectors

The content of this book assumes that you are familiar with your operating system and its commands. It containsthe following information:

• Requirements and Support on page 13 lists driver requirements and supported databases.

• Installation on Windows on page 17 explains how to install the product on a local or network drive onWindows platforms.

• Installation on UNIX and Linux on page 35 explains how to install the product on UNIX and Linux platforms.

• Installation on Mac OS X on page 55 explains how to install the product on Mac OS X platforms.

Database drivers are continually being added to each operating environment. For the latest information aboutthe specific drivers available for your platform, refer to the Progress DataDirect supported configurations Webpage at:

https://www.progress.com/matrices/supported-configurations

Note: This book refers the reader to Web pages using URLs for more information about specific topics, includingWeb URLs not maintained by Progress DataDirect. Because it is the nature of Web content to change frequently,Progress DataDirect can guarantee only that the URLs referenced in this book were correct at the time ofpublishing.

About the Product Documentation

In addition to this installation guide, the product documentation library for each driver includes a standaloneuser’s guide and reference book that contains information specific to that driver. Each driver’s user’s guide andreference provides information about configuring and using the product, detailed reference information, and atroubleshooting guide. An HTML-based copy of your driver’s user’s guide and reference is placed in yourdriver’s directory during installation. The books are also available on the Progress DataDirect Web site at:

https://www.progress.com/documentation/datadirect-connectors

HTML VersionYour driver's user's guide and reference is placed on your system as HTML-based online help during a normalinstallation of the product. It is located in the help subdirectory of the product installation directory.

On Windows, you can access the entire Help system by selecting the help icon that appears in theDataDirect program group.

On all platforms, you can access the entire Help system by opening the following file from within your browser:

install_dir/help/driver_nameHelp/index.html

Or, from a command-line environment, at a command prompt, enter:

browser_exe install_dir/help/driver_nameHelp/index.html

where:


Preface




install_dir

is the path to the product installation directory.

driver_name

is the abbreviated name of your driver. For example, Redshift is this value for the Amazon RedshiftWire Protocol driver.

browser_exe

is the name of your browser executable.

After the browser opens, the left pane displays the Table of Contents, Index, and Search tabs for the entiredocumentation library. When you have opened the main screen of the Help system in your browser, you canbookmark it in the browser for quick access later.

Note: Security features set in your browser can prevent the Help system from launching. A security warningmessage is displayed. Often, the warning message provides instructions for unblocking the Help system forthe current session. To allow the Help system to launch without encountering a security warning message, thesecurity settings in your browser can be modified. Check with your system administrator before disabling anysecurity features.

Help is also available from the setup dialog box for each driver. When you click Help, your browser opens tothe correct topic without opening the help Table of Contents. A grey toolbar appears at the top of the browserwindow.

This tool bar contains previous and next navigation buttons. If, after viewing the help topic, you want to seethe entire library, click:

on the left side of the toolbar, which opens the left pane and displays the Table of Contents, Index, and Searchtabs.

PDF VersionThe product documentation is also provided in PDF format.You can view or print the documentation, andperform text searches in the files. The PDF documentation is available on the Progress DataDirect Web siteat:


Product Platforms

The Progress DataDirect for ODBC drivers allow you to connect to a variety of databases from these platforms:

Windows (32-bit)


Preface


• Windows Server 2016



• Windows 10

• Windows 8.1

• Windows 7

Windows (64-bit)




• Windows 10

• Windows 8.1

• Windows 7

UNIX and Linux (32-bit)

• AIX

• HP-UX aCC Enabled

• Linux

• Oracle Solaris

UNIX and Linux (64-bit)

• AIX

• HP-UX aCC Enabled

• Linux

• Oracle Solaris

macOS (32-bit)

• macOS v10.12.x (Sierra)

• Mac OS X v10.11.x (El Capitan)

• Mac OS X v10.10.x (Yosemite)

• Mac OS X v10.9.x (Mavericks)

macOS (64-bit)






Preface

Conventions Used in This Guide

The following sections describe the conventions used to highlight information that applies to specific operatingsystems and typographical conventions.

Operating System Symbols

The drivers are supported in the Windows, UNIX, Linux, and macOS environments. When the informationprovided is not applicable to all supported environments, the following symbols are used to identify thatinformation:

The Windows symbol signifies text that is applicable only to Windows.

The UNIX symbol signifies text that is applicable only to UNIX and Linux.

The macOS symbol signifies text that is applicable only to macOS.

Typography

This guide uses the following typographical conventions:

ExplanationConvention

Introduces new terms with which you may not be familiar, and is used occasionallyfor emphasis.

italics

Emphasizes important information. Also indicates button, menu, and icon names onwhich you can act. For example, click Next.

bold

Indicates keys or key combinations that you can use. For example, press the ENTERkey.

BOLD UPPERCASE

Indicates SQL reserved words.UPPERCASE

Indicates syntax examples, values that you specify, or results that you receive.monospace

Indicates names that are placeholders for values that you specify. For example,filename.

monospaceditalics

Separates menus and their associated commands. For example, Select File > Copymeans that you should select Copy from the File menu.

>

The slash also separates directory levels when specifying locations under UNIX, Linuxor macOS.

/

Indicates an "OR" separator used to delineate items.vertical rule |


Preface

ExplanationConvention

Indicates optional items. For example, in the following statement: SELECT[DISTINCT], DISTINCT is an optional keyword.

Also indicates sections of the Windows Registry.

brackets [ ]

Indicates that you must select one item. For example, {yes | no} means that you mustspecify either yes or no.

braces { }

Indicates that the immediately preceding item can be repeated any number of timesin succession. An ellipsis following a closing bracket indicates that all information inthat unit can be repeated.

ellipsis . . .

Contacting Technical Support

Progress DataDirect offers a variety of options to meet your support needs. Please visit our Web site for moredetails and for contact information:

https://www.progress.com/support

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 bulletinsand other information.

When you contact us for assistance, please provide the following information:

• Your number or the serial number that corresponds to the product for which you are seeking support, or acase number if you have been provided one for your issue. If you do not have a SupportLink contract, theSupportLink representative assisting you will connect you with our Sales team.

• Your name, phone number, email address, and organization. For a first-time call, you may be asked for fullinformation, 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 understandthe problem.

• A brief description of the problem, including, but not limited to, any error messages you have received, whatsteps you followed prior to the initial occurrence of the problem, any trace logs capturing the issue, and soon. Depending on the complexity of the problem, you may be asked to submit an example or reproducibleapplication 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 Websearch engines, our Knowledgebase, or have tested additional configurations, applications, or other vendorproducts, 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.


Preface

https://www.progress.com/support

1Requirements and Support

Before you install the product, you need to verify that you have a supported version of the database, a supportedversion of the operating system, and, if necessary, the correct database client software on your system.


• Installer Requirements

• Driver Requirements

• Supported Databases

• Supported Operating Systems


Installer RequirementsThe installer requires a Java Virtual Machine (JVM):

• For version 7.1, Java SE 7 or higher

• For version 8.0, Java SE 8 or higher.

• For the Autonomous REST Connector GoogleBigQuery, Snowflake, and Salesforce drivers, the installeruses and deploys the following Java versions:

• Windows: OpenJDK 11

• Linux x32: Oracle JDK 8

• Linux x64: OpenJDK 11

For other platforms, a JRE version 8 or higher is required; however, the installer does not deploy a copy ofthe JVM for these operating systems.

For UNIX users, the Java Virtual Machine (JVM) must be defined on your path.

Driver RequirementsThe following section describes requirements for Progress DataDirect for ODBC drivers.

The Autonomous REST ConnectorThe driver requires a Java Virtual Machine (JVM): Java SE 8 or higher, including Oracle JDK, OpenJDK, andIBM SDK (Java) distributions.

The Amazon Redshift Wire Protocol DriverThe driver has no client requirements.

The Apache Cassandra DriverThe driver requires one of the following Java Virtual Machines (JVM):

• Oracle JDK 6 or higher (LTS version)

• OpenJDK 8 or higher (LTS version)

• IBM SDK (Java) 6 or higher (LTS version)

The Apache Hive Wire Protocol DriverThe driver has no client requirements.

The Apache Spark SQL Wire Protocol DriverThe driver has no client requirements.


Chapter 1: Requirements and Support

The Google BigQuery DriverThe driver requires a Java Virtual Machine (JVM): Java SE 8 or higher, including Oracle JDK, OpenJDK, andIBM SDK (Java) distributions.

The MongoDB DriverThe driver requires one of the following Java Virtual Machines (JVM):




The Oracle Service Cloud DriverThe driver requires one of the following Java Virtual Machines (JVM):




The Oracle Wire Protocol DriverThe driver has no client requirements.

On Mac platforms, an iODBC Driver Manager, version 3.52.7 or higher, is required.

The Salesforce DriverThe driver requires one of the following Java Virtual Machines (JVM):




The Snowflake DriverThe driver requires one of the following Java Virtual Machines (JVM):




The SQL Server Wire Protocol DriverThe driver has no client requirements.


Driver Requirements

Supported DatabasesDatabase drivers are continually being added to each operating environment. For the latest information aboutthe specific drivers available for your platform, refer to the Progress DataDirect supported configurations Webpage at:


Supported Operating SystemsFor supported operating systems and other requirements, refer to the Progress DataDirect supportedconfigurations Web page at:



Chapter 1: Requirements and Support



2Installation on Windows

The product includes an installer program that enables you to install from downloaded files or a networkdirectory. If you purchased a license for redistributing the product, the installation provides a way to do that.


• Before You Install (Windows)

• Installing from Downloaded Files

• Testing Your Driver Installation

• Configuring Drivers and Data Sources

• Processor Information Utility

• Installing to a Different Location

• Uninstalling the Product on Windows

• Upgrading an Evaluation Installation

• Adding Drivers to Your Installation

• For More Information

Before You Install (Windows)Before you begin the installation:


• Exit or close all applications to prevent file-locking conflicts.

• Verify that your system meets the driver’s requirements for a database before you install the driver. Thedriver will not work if these requirements are not met. See "Requirements and Support" for a list of driverrequirements.

• You must be a system administrator or have update privileges for the Registry key [HKEY_LOCAL_MACHINE].These privileges are required to update the Registry with the new drivers being installed. See your systemadministrator if you are unsure.

• If the files are on a network, verify that you have write privileges. See your network administrator if you areunsure.

Important: You must have Microsoft Data Access Components (MDAC) installed. For 32-bit drivers, you musthave version 2.6 or higher. For 64-bit drivers, you must have version 2.8 (64-bit) or higher. Depending on theversion of your Windows operating system, these components may already be installed.You can download autility that determines whether MDAC is installed and its version from the following Microsoft site:https://msdn.microsoft.com/en-us/data/aa937730.aspx

You can also download MDAC from the same site.

See alsoRequirements and Support on page 13

System Requirements

System requirements for drivers on Windows operating systems are documented in the “Support for MultipleEnvironments” section of the user’s guide for each driver. The complete documentation set for each driver canbe found on the DataDirect Documentation page.

See alsoDriver Requirements on page 14

Default Installation Directory

The installer program lets you specify the directory into which the drivers will be installed. By default, the installerprogram installs the drivers in the following directories:

For 32-bit drivers on 64-bit machines:

C:\Program Files(x86)\Progress\DataDirect\ODBC_nn

For all other installations:

C:\Program Files\Progress\DataDirect\ODBC_nn

where

nn

is the product version number. For example, this value is 80 for the 8.0 version of the product.


Chapter 2: Installation on Windows

https://msdn.microsoft.com/en-us/data/aa937730.aspx

https://www.progress.com/resources/documentation/datadirect-documentation

Installing from Downloaded Files

Note: OEM CUSTOMERS: Refer to the Progress DataDirect for ODBC Drivers Distribution Guide for informationon installing, branding, unlocking, and distributing your branded drivers.

This section provides instructions for installing your downloaded files.

To install the drivers from downloaded files:

1. Download the product zip file.

2. Unzip the files, maintaining the directory structure in the zip file, to a temporary directory, for example:C:\TEMP.

3. Perform the installation:

• If you prefer to use a Graphical User Interface (GUI), see Installing Using a GUI on page 19 forinstructions.

• If you prefer to use a silent installation, see Silent Installations of Licensed Drivers on page 25 forinstructions.

Installing Using a GUI


This section provides instructions for installing your downloaded files using a GUI.

To install the drivers using a GUI:

1. 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 version of the product.

2. The Introduction window for the product installation appears. Click Next to continue.

3. 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 windowby clicking Previous.

4. The Install Directory window appears. In the Where Would You Like to Install? field, type the path, includingthe drive letter, of the product installation directory or click the Choose... button to browse to and select aninstallation directory.

• If you are running the 32-bit installer on 64-bit Windows, the default value for the installation directory isC:\Program Files (x86)\Progress\DataDirect\ODBC_nn.

• For all other installations, the default value for the installation directory isC:\Program Files\Progress\DataDirect\ODBC_nn

where:

nn


Verify that you have entered (or selected) the correct installation directory. Then, click Next to continue.

To restore the installation directory to its default setting, click Restore Default.

5. 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 ofthe driver. Click Next to continue with the installation. Skip to Step 9 on page 22.

• OEM/Licensed Installation. Select this option if you purchased a licensed version of one or multipledrivers. Click Next. Proceed to the next step.

Note: OEM CUSTOMERS: Refer to the Progress DataDirect for ODBC Drivers Distribution Guide forinformation on installing, branding, unlocking, and distributing your branded drivers.

6. The Product Registration window appears.



Type the control number, including the dashes, that was provided by Progress DataDirect in the Control #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.

7. From the tree menu, select the drivers that you want to install. Drivers that are already installed are listedin the Drivers (Installed) tree and cannot be deselected. To remove installed drivers, you must uninstall theproduct. See "Uninstalling the Product on Windows" for details. Click Next to continue.

Note: If you are installing a different version of a currently installed driver, the installer will overwrite theexisting driver files with the version that you are installing.




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 10 on page 23

9. The Driver Evaluation Selection window appears.



From the Drivers To Be Evaluated tree, select the drivers that you want to install. Drivers that are alreadyinstalled are listed in the Drivers (Installed) tree and cannot be deselected. To remove installed drivers, youmust uninstall the product. See "Uninstalling the Product on Windows" for details. Click Next to continuewith the installation.

10. The Create Default Default Data Source window appears. Select the Create Default Data Source box todefine a user data source in HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI for each DataDirectdriver that you install.

Warning: If you select Create Default Data Sources, existing data sources in your registry with thesame DataDirect default name will be overwritten. To maintain your current DataDirect default datasources, rename them before you continue.

Then, click Next to continue.

11. 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.

12. When the installation finishes, the Install Complete window appears.You may be prompted to restart yoursystem, 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 willrestart 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 restartingthe 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 thefollowing shortcuts:

• ODBC Administrator

• ODBC Driver Help

• ODBC Performance Tuning Wizard

• ODBC Readme


• Uninstall Progress DataDirect for ODBC nn- 32 bit [32-bit only]

• Uninstall Progress DataDirect for ODBC nn- 64 bit [64-bit only]

• XML Persistence Demo [32-bit only]

After installation, you must configure drivers and data sources; see "Configuring Drivers and Data Sources"for details.

See alsoUninstalling the Product on Windows on page 32Configuring Drivers and Data Sources on page 32

Log Files Created During Installation

Installation Log FilesIf the installer successfully creates the product installation directory, the installer writes a set of log files in theproduct installation directory. Each log file is an installation record for a different component of the product.Examine these log files for a record of any problems that may have occurred during the installation. Theinstallation log files use the following naming formats:

For the log for components specific to a driver:

driver_name_Install_timestamp.log

For the log for components common to all drivers:

odbc_common_platform_Install_timestamp.log

For the log for documentation components:

odbc_doc_Install_timestamp.log

For the log for user interactions with the installer program:

DataDirect_for_ODBC_nn_-_version_bit_Install_timestamp.log

where

driver_name

is an abbreviated name of your driver. For example, Mongodb is used for the MongoDB driver.

timestamp

is the date and time the product was installed.



version

is the platform of your product. This value is 32 for 32-bit installations or 64 for 64-bit installations.

nn

is the product version number.

If the installation fails completely, the installer does not create the installation directory and writes file namedProgress_DataDirect_for_ODBC_nn_InstallFailed.txt in the machine’s default temporary directory(%TEMP%).

If you need help interpreting the contents of these files, contact Progress DataDirect Technical Support.

Installer Console LogThe installer records standard errors and standard output generated during installation todd_odbc_console_install.log, which is created in the user profile directory. Progress DataDirect TechnicalSupport might ask for this log file to troubleshoot some installer problems.

Unlocking and Distributing Branded ODBC Drivers

Refer to the Progress DataDirect for ODBC Drivers Distribution Guide for information on unlocking the brandeddrivers from the applications you develop, and for the files that you must distribute with your Windows application.

Installing from a Network Directory

The installer program can be copied to a network directory from the directory containing downloaded files.Youcan then install the drivers from this directory.

Copy all of the downloaded files from their temporary directory to a network directory; then, map the networkdirectory as a local drive. Navigate to the network directory and double-click the installer program. TheIntroduction window for the product installer appears. To complete the installation, follow Steps 2 on page 19through 12 on page 23 in "Installing from Downloaded Files."


See alsoConfiguring Drivers and Data Sources on page 32

Silent Installations of Licensed Drivers

The installer program provides a command-line option for silent installations of licensed drivers. The silentinstallation is useful for system administrators who want to create a batch file to execute multiple identicalinstallations of the drivers.

Note: NOTE TO OEM CUSTOMERS: Refer to the Progress DataDirect for ODBC Drivers Distribution Guidefor information on branding, unlocking, and distributing your branded drivers.

A silent installation requires performing the following steps:

• Creating the response file:



Using the installer. See Creating a Response File Using the GUI Installer on page 26 for instructions.•

• Using a text editor. See Creating a Response File Using a Text Editor on page 29 for instructions.

• Performing the silent installation. See Performing the Silent Installation on page 30 for instructions.

Important: Your product license may limit the number of CPUs that can exist on the machine on which theproduct is installed. This limit also is imposed on any machine on which the silent installation is performed. Ifyou need to upgrade your product license, contact your Progress DataDirect sales representative.

Creating a Response File Using the GUI InstallerTo create the response file:

1. At a command prompt, switch to the directory containing the unzipped installer files; then, type the command:

installer_filename.exe -r response_file

where:

installer_filename

is the full name of the installer's executable file you unzipped in Step 2 on page 19 of "Installingfrom Downloaded Files."

response_file

is the absolute path and file name of the response file you want to create.

For example, the following command creates a response file named installer.properties in theC:\temp directory:

PROGRESS_DATADIRECT_ODBC_8.0_WIN_64_INSTALL.exe -r C:\temp\installer.properties




4. The Install Directory window appears. In the Where Would You Like to Install? field, type the location ofthe 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 isC:\Program Files (x86)\Progress\DataDirect\ODBC_nn.

• For all other installations, the default value for the installation directory isC:\Program Files\Progress\DataDirect\ODBC_nn

where

nn






5. When prompted to choose the type of installation to perform, select OEM/Licensed Installation. Click Nextand proceed to the next step.


Note: The silent installation method is supported only for OEM/Licensed installations.


In the Control # field, type the control number, including the dashes, that was provided by Progress DataDirect;then, click the Validate button. A tree menu of drivers with valid licenses appears in the selection box.Youcan add one or multiple keys, one at a time.

7. From the tree menu, select the drivers that you want to install. Drivers that are already installed are listedin the Drivers (Installed) tree and cannot be deselected. To remove installed drivers, you must uninstall theproduct. See "Uninstalling the Product on Windows" for details. Click Next to continue.

Note: If you are installing a new version of a currently installed driver, the installer will overwrite the installeddriver files with the newer version.







Click Next to continue.

9. The Create Default Default Data Source window appears. Select the Create Default Data Source box todefine a user data source in HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI for each DataDirectdriver that you install.

Warning: If you select Create Default Data Sources, existing data sources in your registry with thesame DataDirect default name will be overwritten. To maintain your current DataDirect default datasources, rename them before you continue.

Then, click Next to continue.




• No, I will restart my system myself. Select this option if you prefer to use the product without restartingthe system, or if you are not ready to restart the system.

12. Click Done to exit the installer. The response file is created in the directory you specified in Step 1 on page26.



See Performing the Silent Installation on page 30 for instructions on running the response file.

Creating a Response File Using a Text EditorA silent installation configuration file is a text file that you create, for example, silent.properties. This file mustcontain the following arguments:

## Use the hash mark for comments in the file

USER_INSTALL_DIR=install_dir EVAL=0LICENSED=1USERNAME=user_nameCOMPANYNAME=company_nameSERIALNUMBER=xxxxxxxxINSTALL_OPTIONS_CREATE=(0 | 1)KEYLIST=yyyyyyyyyy

## Optionally, overwrite a specific file-fileOverwrite_filename=(Yes | No)

The following table describes the keyword-value pairs used when creating a response file.

Table 1: Response File Keywords

DescriptionKeyword

specifies the product installation directory. Notice that the colon(:) and backslash (\) special characters must be escaped witha backslash. For example:

C:\\Program Files\\Progress\\DataDirect\\ODBC_80

USER_INSTALL_DIR

Specifies whether this is an evaluation install. Type 0 to specifya licensed installation. Note that the silent installation methoddoes not support evaluation installs.

EVAL

Specifies whether this is a licensed install. Type 1 to specify alicensed installation. Note that the silent installation methoddoes not support evaluation installs.

LICENSED

Specifies the user name that will be written to the license file.For example, type Sales Team as the user name.

USERNAME

Specifies the company name that will be written to the licensefile. For example, type MyCompany.

COMPANYNAME

specifies the product serial number that will be written to thelicense file.

SERIALNUMBER

is your product license key, including dashes. If specifyingmultiple keys, separate them using a space. For example:123-456-7890 234-567-8901 345-678-9012.

KEYLIST



DescriptionKeyword

specifies whether to create default data sources. Type 1 if youwant to create default data sources or 0 if you do not want tocreate default data sources.

INSTALL_OPTIONS_CREATE

indicates whether the silent installer should overwite a specificfile (optional). For example, if you are overwriting an existingODBC installation and do not want to update the ProgressDataDirect ODBC tracing library(C:\Windows\system32\ivtrc28.dll), then include thefollowing line in the response file:

-fileOverwrite_C\:\\Windows\\system32\\ivtrc28.dll=No

Notice that the colon (:) and backslash (\) special charactersmust be delimited with a backslash.

-fileOverwrite_filename

See Performing the Silent Installation on page 30 for instructions on running the response file.

Performing the Silent InstallationTo perform a silent installation:

1. Download the product zip file from the location provided by Progress DataDirect when you purchased thesoftware.

2. Unzip the file to a temporary directory, for example:

C:\TEMP

3. At a command prompt, change to the temporary directory containing the installer program. For example,PROGRESS_DATADIRECT_ODBC_8.0_WIN_32_INSTALL.exe is the installer program for the 8.0 versionof the product for 32-bit platforms.

4. Type the command:

installer_filename.exe –f response_file -i silent

where:

installer_filename

is the name of the installer program.

response_file

is the path and file name of the response file created in "Creating a Response File Using the GUI"or Creating a Response File Using a Text Editor." You must specify an absolute path.

The following example performs a silent installation by running a response file namedinstaller.properties, which is located in the C:\temp directory:

PROGRESS_DATADIRECT_ODBC_8.0_WIN_64_INSTALL.exe -f C:\temp\installer.properties–i silent

The installation proceeds without any further user intervention or notification.



Refer to the installation log file for a record of any problems that may have occurred during the installation.See The Silent Installation Log File for details.

See alsoCreating a Response File Using the GUI Installer on page 26Creating a Response File Using a Text Editor on page 29The Silent Installation Log File on page 31

The Silent Installation Log FileIf the installer successfully creates the product installation directory, the installer writes the following log filesin the product installation directory:

• DataDirect_for_ODBC_nn_-_version_bit_Install_timestamp.log

• driver_name_Install_timestamp.log

Examine the log file for a record of any problems that may have occurred during the installation.

If the installation fails completely, the installer does not create the installation directory and writes the followingfile in the machine’s default temporary directory named %TEMP%:

• Progress_DataDirect_for_ODBC_nn_SilentInstallFailed.txt

where:

driver_name


version

is the platform and version number of your product. This value is 32 for 32-bit installations, or 64 for64-bit installations.

timestamp


nn


If you need help interpreting the contents of these files, contact Progress DataDirect Customer Support.

Testing Your Driver InstallationFor basic information about connecting and testing your drivers immediately after installation, refer to "GettingStarted" in your driver's user's guide and reference.


Testing Your Driver Installation

Configuring Drivers and Data SourcesBefore you can use a driver, you must configure a data source for it. A data source consists of a data sourcename, driver location, and optional driver information in the Registry. Use the ODBC Administrator to selectan installed driver and then configure a data source for it. Configuration instructions are provided in your driver'suser's guide and reference. See "About the Product Documentation" for details.

See alsoAbout the Product Documentation on page 8

Processor Information UtilityProgress DataDirect Technical Support may, on occasion, ask that you use the Processor Information Utilityto identify the type of license you need.

From the DataDirect program group, select Processor Information Utility.The utility automatically determinesthe number and type of processors in your machine and displays a hexadecimal number that identifies yourProgress DataDirect product installation. Provide this number to your Progress DataDirect sales representativeor to Technical Support when requested.

Installing to a Different LocationIf you have the product installed and want to install it in a different location, you must first uninstall it. Then,reinstall the product in the new location.

Uninstalling the Product on WindowsThe following sections describe how to uninstall the product on Windows according to version.

Uninstalling the 7.1 Product

You can uninstall the 7.1 version of the product through the Uninstall DataDirect for ODBC 7.1 - xx option in theDataDirect program group or through the Add/Remove Programs feature in the Control Panel.

Uninstalling the 8.0 Product

This section describes how to uninstall the 8.0 version of the product. Depending on your preference, you canuninstall individual drivers or the entire product.

To uninstall:



1. From the Progress DataDirect for ODBC 8.0 - xx bit program group, select the Uninstall DataDirect forODBC 8.0 - xx bit option.

2. The Uninstall Progress DataDirect for ODBC 8.0 window appears. Click Next to continue.

3. A tree menu of installed drivers is displayed.

Choose one of the following:

• If you want to uninstall only specific drivers, select the drivers you want to remove from the menu; then,click Uninstall.

• If you want to uninstall the entire product, select all the installed drivers from the menu; then, clickUninstall. In addition to the components specific to the selected drivers, common files, directories andshortcuts are removed.

4. When the program completes uninstalling the selected components, a confirmation message appears. ClickDone to exit the program.

This completes uninstalling the 8.0 product.

Upgrading an Evaluation InstallationAfter an evaluation installation, you may want to upgrade to a licensed installation. To upgrade, reinstall theproduct using the serial number and key provided to you by Progress DataDirect.


Upgrading an Evaluation Installation

Adding Drivers to Your InstallationIf you want to install additional drivers, start the installer (see "Installing from Downloaded Files"). Follow thesame procedure as for a licensed installation. Be sure to have the serial numbers and keys available for theadditional drivers that you want to install.You must install the additional drivers into the same installationdirectory.

See alsoInstalling from Downloaded Files on page 19

For More InformationWe recommend that you read the readme text file that accompanies the product for current information regardingthe release.You can find the latest readme text file at:





3Installation on UNIX and Linux

The product includes a installer program that enables you to install from downloaded files.This chapter describesthe procedure for installation of the drivers on AIX, HP-UX, Linux, and Oracle Solaris.


• Before You Install (UNIX/Linux)





• Upgrading an Evaluation Installation


• Uninstalling the Product on UNIX and Linux


Before You Install (UNIX/Linux)Before you begin the installation:

• Verify that you have write privileges for the installation directory.



Note: The installer requires a Java Virtual Machine (JVM):



The Java Virtual Machine (JVM) must be defined on your path.


System Requirements

System requirements for drivers on UNIX and Linux operating systems are documented in the “Support forMultiple Environments” section of the user’s guide for each driver. The complete documentation set for eachdriver can be found on the DataDirect Documentation page.


The installer program lets you specify the directory into which the drivers are installed. By default, the installerprogram installs the drivers in this directory:

For 32-bit installations:

/opt/Progress/DataDirect/ODBC_nn_32bit



If you do not have /opt directory permissions, the installer program installs the drivers to your home directoryby default. For example, the directory for 32-bit installation would be:

/home_directory/Progress/DataDirect/ODBC_nn_32bit

where

home_directory

is the home directory for the user who is installing the product.

nn


Installing from Downloaded FilesThis section provides instructions for installing your downloaded files.


Chapter 3: Installation on UNIX and Linux

https://www.progress.com/resources/documentation/datadirect-documentation

Note: The following steps reflect the messages displayed when installing on Solaris. If you are installing ona different UNIX or Linux platform version, the name of that platform is substituted.



1. Download the appropriate product file from the Web site into a temporary directory, for example, /tmp.

• If you are installing an evaluation copy, download the product file from the Progress DataDirect Website.

• If you are installing a licensed copy, download the product file from the location provided by ProgressDataDirect when you purchased the software.

Important: Do not download the file to the installation directory that you will specify during the installation.

2. Switch the temporary directory; then, choose one of the following:

• If your product file uses the tar.Z format, proceed to the next step.

• If your product file uses the .tgz format, skip to Step 4 on page 37.

3. Uncompress the contents of this file. Enter:

uncompress compressed_filename.tar.Z

where compressed_filename is the name of the file you downloaded.

A tar file is extracted from the compressed file.

4. Extract the contents of the product file. Enter:

tar -xvzf product_filename.tgz

where product_filename is the name of the tarred product file name.

The untarred files appear in the temporary directory.

5. Perform the installation:

• If you prefer to use a Graphical User Interface (GUI), go to Installing Using a GUI on page 37 forinstructions.

• If you prefer to use a command line, go to Installing Using a Command-Line on page 40 for instructions.

• If you prefer to use a silent installation, go to Silent Installations of Licensed Drivers on page 43 forinstructions.

Installing Using a GUI

This section provides instructions for installing your downloaded files using a GUI.

1. From the temporary directory containing the installer files, open the installer's binary file to start the installer.






4. The Install Directory window appears. In the Where Would You Like to Install? field, type the full path ofthe product installation directory or click the Choose... button to browse to and select an installation directory.The default value for the installation directory is:







where

nn


home_directory





• Evaluation Installation (will expire in 15 days). Select this option to install an evaluation version ofthe driver. Click Next to continue with the installation. Skip to Step 9 on page 40.

• OEM/Licensed Installation. Select this option if you purchased a licensed version of one or multipledrivers. Click Next. Proceed to the next step.





Type the control number, including dashes, that was provided by Progress DataDirect in the Control # field,and click the Validate button. A tree menu of drivers with valid licenses appears in the selection box.Youcan add one or multiple keys, one at a time.

7. From the tree menu, select the drivers that you want to install. Drivers that are already installed are listedin the Drivers (Installed) tree and cannot be deselected. To remove installed drivers, you must uninstall theproduct. See "Uninstalling the Product on UNIX and Linux" for information on uninstalling drivers. Click Nextto continue.

Note: If you are installing a different version of a currently installed driver, the installer will overwrite theexisting driver files with the version that you are installing.







Click Next to continue. Skip to Step 10 on page 40.

9. The Driver Evaluation Selection window appears.

From the Drivers To Be Evaluated tree, select the drivers that you want to install. Drivers that are alreadyinstalled are listed in the Drivers (Installed) tree and cannot be deselected. To remove installed drivers, youmust uninstall the product. See "Uninstalling the Product on UNIX and Linux" for information on uninstallingdrivers. Click Next to continue with the installation.


11. When the installation finishes, the Install Complete window appears. Click Done to exit the installer program.



See alsoUninstalling the Product on UNIX and Linux on page 51Configuring Drivers and Data Sources on page 50

Installing Using a Command-Line

This section provides instructions for installing your downloaded files from a command-line interface.

1. To run the installer program, switch to the temporary directory that contains the untarred installer files andenter:

./installer_filename.bin –i console

where:



installer_filename

is the full name of the installer's binary file you untarred in Step 4 on page 37 of "Installing fromDownloaded Files."

2. The Introduction step appears. Press ENTER.

3. The product license agreement appears. Press SPACEBAR to page to the end of the agreement. At theend, you are asked to accept the agreement:

• Enter Y to accept the license agreement and continue with the installation.

• Enter N to abort the installation.

Note: You can exit the installer program at any time by typing quit or return to the previous step by typingprevious.

4. You are prompted to enter the absolute path to the installation directory. The default is:


opt/Progress/DataDirect/ODBC_nn_32bit





where

nn


home_directory


5. You are prompted for the type of installation:

• If you are installing an evaluation copy of the product (expires in 15 days), enter 1. Then, press Enterto confirm the evaluation information. Skip to Step 8 on page 41.

• If you are installing a OEM or licensed copy of the product, enter 2. Proceed to the next step.

Note: If you were issued multiple product keys, you can type them sequentially, separating the keys witha space. For example: xxxxkey1 xxxxkey2 xxxxkey3

6. You are prompted to enter the control number that was provided by Progress DataDirect. Type the controlnumber, including dashes, and then press ENTER. Proceed to the next step.

7. The installer prompts you for product registration information. Enter your name, your company name, andthe serial number provided by Progress DataDirect; then, press ENTER.

8. The Pre-Installation Summary step provides the opportunity for you to review the information you haveentered, and you are prompted to accept or change the information:



• Press ENTER to accept the information and begin the installation.

• To change the information, type back and then press ENTER.You are prompted for the informationagain.

• If you are installing with a licensed OEM control number, you are prompted for branding information.Please refer to the Progress DataDirect for ODBC Drivers Distribution Guide.

9. After completion of the installation, a message appears indicating that you have installed the softwaresuccessfully. Press ENTER to close the installer.



See alsoConfiguring Drivers and Data Sources on page 50




driver_name_Install_timestamp.log






DataDirect_for_ODBC_nn_-_version_bit_Install_timestamp.log

where

driver_name


timestamp




platform

is the platform and version of your product. For example, this value would be solarisx32 for a32-bit Solaris installation.

nn





Silent Installations of Licensed Drivers

The installer program provides an option for silent installations of licensed drivers. The silent installation isuseful for system administrators who want to create a configuration file to execute multiple identical installationsof the drivers. The installation is silent in the sense that it requires no user interaction, but it sends outputmessages to the display as the installation proceeds.

A silent installation requires performing the following steps:

• Creating the configuration file.You can create the configuration file in either of the following ways:

• Using the GUI installer. See Creating the Configuration File Using the GUI Installer on page 43 forinstructions.

• Using the command-line installer. See Creating the Configuration File Using the Command-Line Installeron page 46 for instructions.

• Using a text editor. See Creating a Configuration File Using a Text Editor on page 48 for instructions.

• Performing the silent installation. See Performing a Silent Installation on page 48 for instructions.

Important: Your product license may limit the number of CPUs that can exist on the machine on which theproduct is installed. This limit also is imposed on any machine on which the silent installation is performed. Ifyou need to upgrade your product license, contact your Progress DataDirect sales representative.

Creating the Configuration File Using the GUI InstallerTo create the response file:

1. At a command prompt, switch the to directory containing the installer files; then, type the command:

./installer_filename -r configuration_file

where



installer_filename


configuration_file

is the absolute path and file name of the configuration file you want to create.

The following example creates a configuration file named silent.config in the /opt/tmp directory:

PROGRESS_DATADIRECT_ODBC_8.0_LINUX_64_INSTALL.bin -r /opt/tmp/silent.config

2. The Introduction window for the product installation appears window appears. Click Next.

3. 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 in the License Agreement option; then,click Next.

4. The Install Directory window appears. In the Where Would You Like to Install? field, type the path, includingthe drive letter, of the product installation directory or click the Choose... button to browse to and select aninstallation directory.

• For 32-bit installations, the default value for the installation directory is:


• For 64-bit installations, the default value for the installation directory for a is:




where

nn


home_directory




5. When prompted to choose the type of installation to perform, select OEM/Licensed Installation. Click Nextand proceed to the next step.


Note: The silent installation method is supported only for OEM/licensed installs.




Type the control number that was provided by Progress DataDirect in the Control # field, and click theValidate button. A tree menu of drivers with valid licenses appears in the selection box.You can add oneor multiple keys, one at a time.

7. From the tree menu, select the drivers that you want to install. Drivers that are already installed are listedin the Drivers (Installed) tree and cannot be deselected. To remove installed drivers, you must uninstall theproduct. For information on uninstalling drivers, see Uninstalling the Product on UNIX and Linux on page51 Click Next to continue.

Note: If you are installing a new version of a currently installed driver, the installer will overwrite the installeddriver files with the newer version.







Click Next to continue.

9. The Pre-Installation Summary window provides the opportunity to review the information you have entered.When you are satisfied with your installation option selections, click Install to begin the installation.



• No, I will restart my system myself. Select this option if you are not ready to restart your system.Youwill need to restart your system manually before using the product.

11. Click Done to exit the installer. The configuration file is created in the directory you specified in Step 1 onpage 43.

See Performing a Silent Installation on page 48 for instructions on running the configuration file.

Creating the Configuration File Using the Command-Line InstallerTo create a response file:

1. At a command prompt, switch the directory containing the installer files; then, type the command:

./installer_filename -r configuration_file - i console

Where:

installer_filename


configuration_file

is the absolute path and file name of the configuration file you want to create.

For example:

This example creates a configuration file named silent.config in the /opt/tmp directory.

PROGRESS_DATADIRECT_ODBC_8.0_LINUX_64_INSTALL.bin -r /opt/tmp/silent.config -iconsole

2. The Introduction step appears. Press ENTER.

3. The product license agreement appears. Press ENTER to page to the end of the agreement. At the end,you are asked to accept the agreement:


• Enter anything other than N to abort the installation.



Note: You can exit the installer at any time by typing quit or return to the previous step by typing quit.








where

nn


home_directory


5. You are prompted for the type of installation. Enter 2 for an OEM or licensed copy of the product.You areprompted to enter the control number that was provided by Progress DataDirect. Type the control numberand then press ENTER. Proceed to the next step.

Note: The silent install method is not supported for evaluation installations.





• To change the information, type back; then, press ENTER.You are prompted for the information again.


8. Press ENTER to close the installer. The configuration file is created in the directory you specified in Step1 on page 46.

See Performing a Silent Installation on page 48 for instructions on running the configuration file.



Creating a Configuration File Using a Text EditorA silent installation configuration file is a text file that you create, for example, silent.cfg. This file mustcontain the following arguments:

USER_INSTALL_DIR=installation directoryEVAL=0LICENSED=1KEYLIST=key_valueUSERNAME=user_nameCOMPANYNAME=company_nameSERIALNUMBER=serial_number_value

## Optionally, overwrite a specific file-fileOverwrite_filename=(Yes | No)

The following table describes the keyword-value pairs used when creating a configuration file.

Table 2: Configuration File Keywords

DescriptionKeyword

Specifies the full path to the directory where you want to install the drivers.This cannot be the same directory as the temporary installation directory.

USER_INSTALL_DIR

Specifies whether this is an evaluation install. Type 0 to specify a licensedinstallation. Note that the silent installation method does not supportevaluation installs.

EVAL

Specifies whether this is a licensed install. Type 1 to specify a licensedinstallation. Note that the silent installation method does not supportevaluation installs.

LICENSED

Specifies your product license key, including dashes. If specifying multiplekeys, separate them using a space. For example: 123-456-7890234-567-8901 345-678-9012.

KEYLIST

Specifies your name.USERNAME

Specifies your company name. The company name can include spaces.COMPANYNAME

Specifies the serial number provided for your purchased product.SERIALNUMBER

Indicates whether the silent installer should overwite a specific file (optional).For example, if you are overwriting an existing ODBC installation and wantto update the Progress DataDirect for ODBC uninstaller(/home/john/Progress/uninstall_ODBC_80.lax), then include thefollowing line in the response file:

-fileOverwrite_/home/john/Progress/uninstall_ODBC_80.lax=Yes

-fileOverwrite_filename

Performing a Silent InstallationTo perform a silent installation:



1. From a command-line prompt, navigate to the directory that contains the installer's binary file.

2. Execute a silent installation:

installer_filename -f configuration_file

where

installer_filename


configuration_file

is the location and name of the configuration file that you have created.

If the configuration file is named silent.cfg and resides in the current working directory, you would enterthe following for a 64-bit Linux installation of the 8.0 version of the product:

PROGRESS_DATADIRECT_ODBC_8.0_LINUX_64_INSTALL.bin -f silent.cfg -i silent

You may also specify an absolute or relative path, for example:

PROGRESS_DATADIRECT_ODBC_8.0_LINUX_64_INSTALL.bin -f/home/users/johndoe/silent.cfg -i silent

or

PROGRESS_DATADIRECT_ODBC_8.0_LINUX_64_INSTALL.bin -f ./install/silent.cfg

3. The installation proceeds without any further user intervention unless you enter an incorrect value on thecommand line or in the configuration file, in which case an error is displayed and the installer aborts. Tocomplete the installation, you must correct the command line or silent installation configuration file andexecute it again.

The Silent Installation Log FileIf the installer successfully creates the product installation directory, the installer writes the following log filesin the /install/logs folder of the product installation directory:

• Progress_DataDirect_for_ODBC_nn_-_version_bit_Install_timestamp.log

• driver_name_Install_timestamp.log

Examine the log file for a record of any problems that may have occurred during the installation.

If the installation fails completely, the installer does not create the installation directory and writes the followingfile in the machine’s default temporary directory, named $TEMP:

• Progress_DataDirect_for_ODBC_nn_SilentInstallFailed.txt

where:

driver_name




version

is the platform and version number of your product. This value is 32 for 32-bit installations, or 64 for64-bit installations.

timestamp


nn


If you need help interpreting the contents of these files, contact Progress DataDirect Customer Support.


Processor Information UtilityProgress DataDirect Technical Support may, on occasion, ask that you use the Processor Information Utilityto identify the type of license you need.

From a command shell, change to the following directory:

install_dir/tools

where install_dir is the path to the product installation directory. Then, enter:

ddprocinfo

The utility automatically determines the number and type of processors in your machine and displays ainformation in a command shell window. The message also includes the hexadecimal number that identifiesyour Progress DataDirect product installation. Provide this number to your Progress DataDirect salesrepresentative or to Technical Support when requested.

Configuring Drivers and Data SourcesBefore you can use an installed driver, you must configure a data source for the driver. A data source consistsof a data source name, driver location, and optional driver information in the system information file (odbc.ini).Configuration instructions are provided in your driver's user's guide and reference. See "About the ProductDocumentation" for details.




Upgrading an Evaluation InstallationAfter an evaluation installation, you may want to upgrade to a licensed installation. To upgrade, reinstall theproduct using the serial number and key provided to you by Progress DataDirect.



Uninstalling the Product on UNIX and LinuxThe following sections describe how to uninstall the product on UNIX and Linux according to version.

Uninstalling the 7.1 Product on UNIX and Linux

Delete the ODBC driver installation directory.

Uninstalling the 8.0 Product on UNIX and Linux

This section describes how to uninstall the 8.0 version of the product on UNIX and Linux.You can use thefollowing methods to uninstall the product:

• Graphical User Interface (GUI): If you prefer to use a GUI, see Uninstalling Using a GUI on page 51 forinstructions.

• Command Line: If you prefer to use a command line, see Uninstalling Using a Command-Line on page52 for instructions.

Uninstalling Using a GUIThis section describes how to uninstall the 8.0 version of the product. Depending on your preference, you canuninstall individual drivers or the entire product.

To uninstall:

1. Navigate to the uninstall folder of the installation directory; then, open the uninstall_ODBC_80 file.

2. The Uninstall Progress DataDirect for ODBC 8.0 window appears. Click Next to continue.

3. A tree menu of installed drivers is displayed.


Upgrading an Evaluation Installation


• If you want to uninstall only specific drivers, select the drivers you want to remove from the menu; then,click Uninstall.

• If you want to uninstall the entire product, select all the installed drivers from the menu; then, clickUninstall. In addition to the components specific to the selected drivers, common files, directories andshortcuts are removed.

4. When the program completes uninstalling the selected components, a confirmation message appears. ClickDone to exit the program.


Uninstalling Using a Command-LineThis section describes how to uninstall the 8.0 version of the UNIX and Linux product using a command line.Depending on your preference, you can uninstall individual drivers or the entire product.

To uninstall:

1. At a command prompt, navigate to the uninstall folder in the product installation directory; then, enterthe following command:

./uninstall_ODBC_80 -i console

2. The Uninstall Progress DataDirect for ODBC 8.0 program opens. Press ENTER to continue.

Note: You can exit the installer program at any time by typing quit.

3. A list of installed drivers is displayed.


• If you want to uninstall only specific drivers, type the number(s) that corresponds to the driver(s) youwant to uninstall. For multiple drivers, separate the numbers entered with a comma. Press ENTER.



• If you want to uninstall the entire product, type the number that corresponds to the All drivers option;then, press ENTER. This option will remove all product components, directories and shortcuts.

4. The program provides you with an opportunity to review the drivers you have selected to uninstall, and youare prompted to accept or change your selection:

• To uninstall the selected drivers, type Y; then, press ENTER. Proceed to the next step.

• To change your selection, type N; then, press ENTER. Follow the instructions in 3 on page 52 to reselectthe drivers you want to uninstall.

5. Press ENTER to uninstall.

6. When the program completes uninstalling the selected drivers, a confirmation message appears. PressENTER to exit the program.





For More Information




4Installation on Mac OS X

The product includes an installer program that enables you to install from downloaded files or a networkdirectory. This section describes the procedure for installation of the drivers on Mac OS X.


• Before You Install (Mac OS X)





• Uninstalling the Product on Mac OS X


Before You Install (Mac OS X)Before you begin the installation:

• Verify that you have write privileges for the installation directory.



• An iODBC Driver Manager, version 3.52.7 or higher, must be installed. For information on downloading theiODBC Driver Manager, refer to http://www.iodbc.org/.

Note:

The installer requires a Java Virtual Machine (JVM), Java SE 6 or higher. The Java Virtual Machine (JVM)must be defined on your path.


System Requirements

The following are requirements for the drivers on Mac operating systems:

32-bit Drivers

• All required network software that is supplied by your database system vendors must be 64-bit compliant.

• An iODBC Driver Manager, version 3.52.7 or higher, is required.

• The following processors are supported:

• Intel

• The following operating systems are supported for your 32-bit driver. All editions are supported unlessotherwise noted.





• Only the Oracle Wire Protocol driver is currently supported on macOS platforms.


Chapter 4: Installation on Mac OS X

http://www.iodbc.org/

64-bit Drivers

• All required network software that is supplied by your database system vendors must be 64-bit compliant.

• An iODBC Driver Manager, version 3.52.7 or higher, is required.

• The following processors are supported:

• Intel

• The following operating systems are supported for your 64-bit driver. All editions are supported unlessotherwise noted.





• Only the Oracle Wire Protocol driver is currently supported on macOS platforms.


The installer program lets you specify the directory into which the drivers are installed. By default, the installerprogram installs the drivers in the following directory:

/Users/home_directory/Progress/DataDirect/ODBC_nn_xxbit

where

home_directory


nn

is the product version number. For example, this value is 80 for the 8.0.x version of the product.

xx

bitness of the product. For example, this value is 64 for the 64-bit version of the product.


Note: On Mac OS X, the installer program currently supports only a command-line interface.


This section provides instructions for installing your downloaded files.




1. Download the product disk image file.

2. Double-click on the file to mount the disk image.

3. Double-click on the install.command script to launch the installer.

4. You are prompted for the type of installation:

• Enter S for a system installation (the default). System installations allow the drivers to be accessed byall applications on the system, including signed applications. This type of installation complies with thebest security practices for Mac OS X platforms.

• Enter U for a user installation. Select this option if you do not have administrator privileges. Note thatsome third-party applications may not be able to access the drivers.

5. The Introduction step for the product installation appears. Press ENTER to continue.

Note: You can exit the installer program at any time by entering quit or return to the previous step byentering back.

6. The License Agreement step appears. Press ENTER to page through the agreement. At the end, you areasked to accept the agreement.


• Enter anything other than Y to abort the installation.


For 32-bit system installations:

/Library/Progress/DataDirect/ODBC_80_32bit

For 64-bit system installations:

/Library/Progress/DataDirect/ODBC_80_64bit

For user installations, the installer program installs the drivers to your Users directory by default. Forexample, the directory for 32-bit installation would be:

/Users/user_name/Library/Progress/DataDirect/ODBC_80_32bit


• If you are installing an evaluation copy of the product (will expire in 15 days), enter 1. Skip to Step 11on page 58.

• If you are installing a OEM or licensed copy of the product, enter 2. Proceed to the next step.

9. You are prompted to enter the control number that was provided by Progress DataDirect. Type the controlnumber, including dashes, and then press ENTER. Proceed to the next step.







• To change the information, type back and then press ENTER.You are prompted for the informationagain.


12. After completion of the installation, a message appears indicating that you have installed the softwaresuccessfully. Press ENTER to close the installer.



See alsoUninstalling the Product on Mac OS X on page 61Configuring Drivers and Data Sources on page 60




data_source_Install_timestamp.log






Progress_DataDirect_for_ODBC_nn_-_64_bit_Install_timestamp.log

where

data_source

is the name of the data source you are connecting to. For example, oracle is used for Oracledatabases.

timestamp




platform

is the platform and version of your product. For example, this value would be mac32 for a 32-bitinstallation.

nn






Configuring Drivers and Data SourcesBefore you can use an installed driver, you must configure a data source for the driver. A data source consistsof a data source name, driver location, and optional driver information in the system information file (odbc.ini).Configuration instructions are provided in your driver's user's guide and reference. See "About the ProductDocumentation" for details.






Uninstalling the Product on Mac OS XThis section describes how to uninstall the product on Mac OS X. Depending on your preference, you canuninstall individual drivers or the entire product.

Note: On Mac OS X, the uninstaller program is currently only supported in a command-line interface.

To uninstall:

1. From the Terminal, navigate to the uninstall folder in the product installation directory; then, enter thefollowing command that corresponds to your installation:

For system installations:

sudo ./uninstall_ODBC_80.app -i console

For user installations:

./uninstall_ODBC_80.app -i console

2. The Uninstall Progress DataDirect for ODBC 8.0 program opens. Press ENTER to continue.

Note: You can exit the installer program at any time by typing quit.

3. A list of installed drivers is displayed.


• If you want to uninstall only specific drivers, type the number(s) that corresponds to the driver(s) youwant to uninstall. For multiple drivers, separate the numbers entered with a comma. Press ENTER.

• If you want to uninstall the entire product, type the number that corresponds to the All drivers option;then, press ENTER. This option will remove all product components, directories and shortcuts.

4. The program provides you with an opportunity to review the drivers you have selected to uninstall, and youare prompted to accept or change your selection:

• To uninstall the selected drivers, type Y; then, press ENTER. Proceed to the next step.

• To change your selection, type N; then, press ENTER. Follow the instructions in 3 on page 61 to reselectthe drivers you want to uninstall.

5. Press ENTER to uninstall.

6. When the program completes uninstalling the selected drivers, a confirmation message appears. PressENTER to exit the program.





Uninstalling the Product on Mac OS X




Index

Aadding drivers

Mac 60UNIX and Linux 51Windows 34

AIX, See UNIX and LinuxAmazon Redshift Wire Protocol driver

driver requirements 14Apache Cassandra driver

driver requirements 14Apache Hive Wire Protocol driver

driver requirements 14Apache Spark SQL Wire Protocol driver

driver requirements 14Autonomous REST Connector

driver requirements 14

Bbefore you install

on Mac 55on UNIX and Linux 35on Windows 17

branding driversSee also Progress DataDirect for ODBC Drivers Distribution

GuideWindows 25See also Progress DataDirect for ODBC DriversDistribution Guide

Ccommand-line installation

UNIX and Linux 40configuration file for UNIX/Linux silent installation

creating using the GUI installer 43configuring drivers and data sources

on Mac 60on UNIX and Linux 50on Windows 32

contacting Technical Support 12creating

configuration file using the GUI installer 43response file using a text editor 29response file using the installer 26

Ddefault installation directory

on Mac 57

default installation directory (continued)on UNIX and Linux 36on Windows 18

distributing driversWindows 25

documentation, about 8downloaded files, installing from

Mac 57UNIX and Linux

command-line, using 40GUI, using a 37

Windows 19driver requirements

Amazon Redshift Wire Protocol driver 14Apache Cassandra driver 14Apache Hive Wire Protocol driver 14Apache Spark SQL Wire Protocol driver 14Autonomous REST Connector 14Google BigQuery driver 14MongoDB driver 14Oracle Service Cloud driver 14Oracle Wire Protocol driver 14Salesforce driver 14Snowflake driver 14SQL Server Wire Protocol driver 14

drivers, addingMac 60UNIX and Linux 51Windows 34

Eevaluation installation, upgrading to licensed

UNIX and Linux 51Windows 33

GGoogle BigQuery driver

driver requirements 14GUI Installation

UNIX and Linux 37

HHP-UX, See UNIX and Linux

Iinstaller

requirements 14


Index

installing the driversfrom a network directory 25from downloaded files

on Mac 57on UNIX and Linux 36–37, 40, 46on Windows 19

in a different location on Windows 32

LLinux, See UNIX and Linuxlog files for installation

Mac 59UNIX and Linux 42Windows 24

MMac

before you install 55default installation directories 57installing from downloaded files 57

MongoDB driverdriver requirements 14

Nnetwork directory, installing from 25

OOEM customers, See Progress DataDirect for ODBCDrivers Distribution GuideOracle Service Cloud driver

driver requirements 14Oracle Wire Protocol driver

driver requirements 14

Pperforming a silent installation 30Processor Information Utility

UNIX 50Windows 32

Rremoving the product

Mac OS X 61UNIX and Linux

using a command line. 52using a GUI 51

UNIX/Linuxversion 7.1 51version 8.0 51

removing the product (continued)Windows

version 7.1 32removing the product on Windows

version 8.0using a GUI 32

requirementsinstaller 14

response file for silent installationcreating using a text editor 29creating using the installer 26

SSalesforce driver

driver requirements 14silent installation

creating a configuration fileusing the GUI installer 43

creating a response fileusing a text editor 29using the installer 26

performing 30UNIX

arguments 48command-line syntax 48overview 43

UNIX/Linuxlog file for silent installation 49

Windowslog file for silent installation 31overview 25

Snowflake driverdriver requirements 14

Solaris, See UNIX and LinuxSQL Server Wire Protocol driver

driver requirements 14system requirements

for UNIX and Linux 36, 56for Windows 18

TTechnical Support, contacting 12

Uuninstalling the product

Mac OS X 61UNIX and Linux

using a command line 52using a GUI 51

UNIX/Linuxversion 7.1 51version 8.0 51


Index

uninstalling the product (continued)Windows

version 7.1 32uninstalling the product on Windows

version 8.0using a GUI 32

UNIX and Linuxbefore you install 35default installation directories 36driver requirements 14installing from downloaded files

command-line, using 40GUI, using a 37

system requirements 36, 56upgrading an evaluation installation

UNIX and Linux 51

upgrading an evaluation installation (continued)Windows 33

WWeb install

Mac 57UNIX and Linux 36, 46Windows 19

Windowsbefore you install 17default installation directory 18driver requirements 14installing from a network directory 25installing from downloaded files 19system requirements 18


Index


Index

Documents

ProgressDataDirect for ODBC Drivers · install_dir isthepathtotheproductinstallationdirectory. driver_name istheabbreviatednameofyourdriver.Forexample,RedshiftisthisvaluefortheAmazonRedshift