Openlink lite odbc drivers for progress 11

Prompt to access their registries. Licensing What Do I Do If My Existing License Key Is Expired? Users may obtain additional, temporary license keys from the OpenLink web site. Users proceed through the downloads matrix and stop, when they are presented with the product download links. Licenses are mailed to users, before they click the actual links to obtain the software. Licensing What Do I Tell Users Who Want New Temporary Licenses? Users may repeat the downloads process—up to three times—to obtain new, temporary licenses. However, this option is inconvenient for many persons. Consequently, consultants may generate licenses with the license generators. Alternatively, consultants may ask the Account Manager to generate a temporary key. Licensing What Is A Concurrent Connection? A concurrent session is an open database session. Users often confuse database connections with perceived application connections. For example, Microsoft Access may appear to open one connection against the target database. However, Access really spawns 2 or more database sessions. This causes an unexpected number of licenses to be consumed. Users must understand that Access and other connections are coded to behave in this manner. Licensing What Is A Concurrent User? A concurrent user is a distinct ip address. Licensing What Is ASNPRINT.exe? ASNPRINT.exe is a diagnostic utility. It reads OpenLink 4.x and 5.x licenses, and displays the terms associated with those licenses. ASNPRINT.exe cannot read corrupt licenses. ASNPRINT.exe cannot read 1.x or 3.x licenses. Licensing What Licenses are provided? OpenLink provided non-expiring, evaluation licenses with 1.x and 3.x Multi-Tier software. Inform 1.x and 3.x users that OpenLink's latest components use a new licensing model. Then, send these users to Account Management for additional information. Licensing What are the UDA Licensing Model based on? Both Single-Tier and Multi-Tier license models are based on concurrent "users" and concurrent "connections." Open Database Connectivity (ODBC) What is Generic ODBC? OpenLink's ODBC Lite and Generic ODBC drivers perform a special function. These drivers enable users to establish ODBC connections to databases, for which OpenLink does not provide an agent. To proceed, users must possess native or 3rd party ODBC drivers that connect to their databases. Then, users must install OpenLink's ODBC Lite drivers on the machine, which contains these drivers. Multi-Tier users must install the Request Broker and Generic ODBC Agent on the machine, which contains these drivers. Multi-Tier users may install the Multi-Tier client on any supported operating system. Finally, OpenLink's ODBC Lite and Generic ODBC drivers proxy SQL requests from the application-through the 3rd party Data Source Name-to the actual database. Performance How can I bench-test OpenLink drivers? You can download OpenLink ODBC Bench to run TPC-A like and TPC-C like bench tests against OpenLink and non-OpenLink ODBC drivers. OpenLink Software also provide a OpenLink JDBC Bench to run TPC-A like bench tests against OpenLink and non-OpenLink JDBC drivers. Please feel free to contribute your results to the OpenLink Product Support team Performance How can I detect bottlenecks caused by OpenLink drivers? Download ODBC Scan to detect bottlenecks caused by OpenLink drivers.

3rd party data source, which connects to the user's database. Users must install Virtuoso Universal Server client and server components on one or more supported operating systems. Users must install the iODBC Driver Manager, OpenLink ODBC Bench, and ODBC Scan on a supported client operating system. Some users may require a compiler and library linker, if they intend to develop ODBC compliant applications or re-link OpenLink's agents or Driver Manager. Compatibility What Is The Compatibility with A Newer DB? Users who possess newer builds of popular databases. For example, OpenLink may provide software for Sybase 11 systems. However, users have Sybase 12. In most instances, consultants should encourage users to download the closest match to their database version. OpenLink's software is upwards compatible and should function with the newer product. Be advised - Progress databases and OpenLink's Progress software are compatible, as long as both products share the same major number. For instance, OpenLink's Progress 8 database agents will connect to most Progress 8 databases. However Progress 7 database agents will not connect to Progress 8 databases. Compatibility What JDBC Connection Formats Do Multi-Tier Drivers Support? OpenLink's Multi-Tier drivers support Type 3 (DSN-Less) JDBC connections. Multi-Tier drivers also support a Type 3 ODBC-JDBC Bridge. Compatibility What JDBC Connection Formats Do Single-Tier Drivers Support? Single-Tier drivers support Type 1 (JDBC-ODBC Bridge) JDBC connections. They also provide ODBC-JDBC Bridge connectivity. Compatibility What Network Protocols Do You Support? OpenLink supports the TCP/IP and IPX/SPX protocols. Compatibility What Suitable Software Should Be Used? Get a uname -a from all machines on which software would be installed. Get the name of the database to which the user wants to connect. See if OpenLink has a matching machine and database installation or database installation media. If OpenLink has the requisite materials, OpenLink can build an agent. If OpenLink does not have the operating system or database, the user may need to consider a custom build. ALERT Users may use OpenLink's Generic ODBC drivers to connect to databases, for which no database agents exist. These users simply need an OpenLink-supported operating system, which contains 3rd-party drivers that connect to the database. Other users may benefit from Single-Tier or application server configuration Multi-Tier connections, when they have a common database on an uncommon operating system. This latter configuration requires the installation of the database native client on an OpenLink-supported O/S. Compatibility What is the Compatibility With Newer OS? Users who possess newer builds of popular operating systems. For example, OpenLink may provide software for Solaris 2.8 systems. However, users have Solaris 2.9. In this instance, consultants should encourage users to download the closest match to their operating system version. OpenLink's software is upwards compatible and should function on the newer platform. Configuration Do I need to configure my environment to support ODBC-ODBC Bridge connectivity? You need to insure that your 3rd party drivers connect to the target database. You need to insure that openlink.sh or openlink.csh is run on Unix machines that contain OpenLink Software. openlink.sh should be

The OpenLink downloads pages to search for the software for your particular OS. If your Operating System or Database is not available in the list of supported platforms, please contact your Product Support consultant or Account Manager as the software might be available internally but not publicly so. Compatibility Is Older OS Compatibility Supported? Consultants will encounter users who possess older builds of popular operating systems. For example, OpenLink may provide software for Solaris 2.5 systems. However, users have Solaris 2.4. In this instance, consultants should not encourage users to download software. OpenLink's software is not backwards compatible and may not function on the older platform. Compatibility Is there Older DB Compatibility Supported? Consultants will encounter users who possess older builds of popular databases. For example, OpenLink may provide software for Informix 7.3 systems. However, users have Informix 5. In this instance, consultants should not encourage users to download software. OpenLink's software is not backwards compatible and may not function with the older platform. Be advised - Progress databases and OpenLink's Progress software are compatible, as long as both products share the same major number. For instance, OpenLink's Progress 8 database agents will connect to most Progress 8 databases. However Progress 8 database agents will not connect to Progress 7 databases. Compatibility OpenLink Data Access Drivers Vs iODBC? iODBC.org offers free installers and instructions for the open-source iODBC Driver Manager and iODBC SDK. The installers are packaged with source code, header files, make files, and other resources of interest to the development community. These products match OpenLink Software's quality and reliability; however, they, and the iODBC.org web site, cater to highly technical individuals who know how to build the iODBC Driver Manager into their own custom solutions. OpenLink Software provides commercial quality Data Access Drivers, the Virtuoso Universal Server, diagnostic utilities, and related SDKs. In addition, the iODBC Driver Manager is bundled into the OpenLink SDKs and installers for Data Access Drivers and Virtuoso. This software is intended to service businesses and other entities which need a complete, reliable, out-of-the-box solution. OpenLink provides value added components in the OpenLink iODBC variant of the iODBC SDK. This value takes the form of ready-to-run iODBC ports for all supported platforms, and in the case of Mac OS X this currently includes an AQUA and Frameworks based ODBC Administrator. Compatibility What Are Your Prerequisites And System Requirements? Users must install OpenLink's Single-Tier drivers on a supported operating system. Users must install DB2, Informix, Ingres, and Progress drivers on a machine, which contains a functional copy of their database native client. Users must install "ODBC Lite" drivers on a system that contains a 3rd party data source, which connects to the user's database. Users must install OpenLink's Multi-Tier client and server components on one or more supported operating systems. DB2, Informix, Ingres, and Progress users must install the server components on a system, which contains the user's database or database native client. Users must install "Generic ODBC" drivers on a system that contains a

%META:TOPICPARENT{name="SingleTierLiteInstallWin32"}%= Installation and Configuration of the Lite Edition (Single-Tier) ODBC Driver for Progress SQL-89 Data Sources, for Windows=**Review Preinstallation Documentation:** [[PreinstallProgressLiteWin32|Pre-Installation Requirements]]%TOC%== Installation ==# The **Lite Edition (Single-Tier) ODBC Driver for Progress SQL-89 for Windows** is distributed in a single .msi file.%BR%%BR%//**NOTE:** [[InstallProgress92LiteWin32|Different installation and configuration instructions apply to Progress SQL-92 Data Sources]].//%BR%%BR%# Click the **Open** link that appears in your Downloads dialog.%BR%%BR%%BR%%BR%# The installer will display a **Welcome** message. Click **Next**.%BR%%BR%%BR%%BR%# The next screen will display the **License Agreement** for the OpenLink Lite Driver. Please read and check the "I accept the license agreement" checkbox. Then, click **Next.**%BR%%BR%%BR%%BR%# The driver needs a license file to operate. Click the Browse button to locate a commercial or evaluation license that you have previously downloaded onto your local hard drive. Alternatively, click the **Try & Buy** button to obtain a commercial or evaluation license. You can also tick the "I don't want to install a license file right now" check box. This option will permit you to install the product; however, you will not be able to use the product until you obtain a commercial or evaluation license key.%BR%%BR%%BR%%BR%# Click **Next.**# Choose from the **Typical**, **Complete**, and **Custom** installation types.%BR%%BR%%BR%%BR%# Click **Next.**# Click the **Install** button.%BR%%BR%%BR%%BR%# Installation is complete. Click the **Finish** button.%BR%%BR%%BR%%BR%# You may be prompted to restart your computer, if you have a pre-existing OpenLink License Manager running on your computer. This reboot not always necessary, but is generally recommended.== Configuration ==# Launch the **ODBC Administrator** [[Win32vs64OdbcAdmin | appropriate to the bitness (32-bit or 64-bit) of your client application and driver]].%BR%%BR%%BR%%BR%# Click the **System DSN** tab.%BR%%BR%%BR%%BR%# Click the **Add** button. Then, select the OpenLink "Lite" Driver for Progress (SQL-89) from the list of available drivers. //Select the Unicode version of the driver if and only if you are working with

Our OpenLink Single-Tier drivers. We recommend OpenLink's Multi-Tier drivers to evaluators in Category 2. Evaluators in Category 3 must install the OpenLink server components on their database server. NOTE:Evaluators in Category 2 may install the OpenLink server components on their database server or any machine, which contains the database native client. In this scenario, the OpenLink database agent can connect to the database through that database client. Please see the technical article on connecting via in a three-tier environment Features Do OpenLink ODBC Drivers Load Share when used in Active-Active Clusters? Our Multi-Tier drivers may be deployed in a load balancing architecture. Features Do OpenLink Drivers (ODBC or JDBC) function in Fail-over Cluster environments? Yes. OpenLink functions in Fail-over Cluster environments. Multi-Tier users must install one set of OpenLink server components (Request Broker & Database Agent) on each node. The fail-over Broker may be instantiated by shell scripts, cron, or some other startup procedure, when the active node goes down. Some environments may support multiple, running Request Brokers, so long as each Request Broker can bind to a unique IP address. Features Do OpenLink ODBC & JDBC drivers also provide data migration facilities? OpenLink's ODBC & JDBC drivers can be used in conjunction with 3rd-party data migration facilities. However, OpenLink's Virtuoso Server provides Snapshot Replication and a Virtual Database Repository. Virtuoso Snapshot Replication is similar to MS SQLServer's Data Transformation Services (DTS) Wizard. Virtuoso's Virtual Database Repository provides one with an interface and functionality similar to MS SQLServer's Linked Servers or Oracle's Heterogeneous Services. Features What Do Your Drivers Do? OpenLink's Data Access drivers enable users to establish ODBC, ADO.Net, OLEDB and JDBC connections between applications and databases. Applications use these connections to execute SQL queries against the data contained within the databases. Typical SQL queries select, insert, update, or delete data. Other queries add, modify, or delete the structures that contain the data. Features What Is The JDBC-ODBC Bridge? The JDBC-ODBC Bridge—or "Type 1" JDBC connection—allows users to establish connections to ODBC Data Source Names using a JDBC connection URL. The JDBC connection URL passes the name of a valid ODBC Data Source as a connection parameter Features What Is The ODBC-JDBC Bridge? OpenLink's ODBC-JDBC Bridge drivers allow ODBC Data Source Names to connect to JDBC connection URLs. This allows ODBC compliant applications to connect to and query JDBC data stores. Features What Is The ODBC-ODBC Bridge? OpenLink Software builds specific database agents for DB2, Informix, Ingres, MS SQLServer, MySQL, Oracle, PostgreSQL, Progress, and Sybase. However, many users have Access, Paradox, Btrieve, DBase, and other databases for which OpenLink does not build agents. The ODBC-ODBC Bridge enables users to connect OpenLink drivers to these databases. The Bridge proxies OpenLink driver connections through 3rd party drivers that already connect to the database. Installation Can I Install New Software On Top Of Existing Software? Users can install new software on top of existing software. However, this is not the preferred course of action, in many circumstances. Users should install new software