Openlink lite jdbc drivers for odbc

Author: n | 2025-04-23

Download OpenLink Lite JDBC Drivers for ODBC latest version for Windows free to try. OpenLink Lite JDBC Drivers for ODBC latest update: Ma Download OpenLink Lite ODBC Drivers for JDBC latest version for Windows free to try. OpenLink Lite ODBC Drivers for JDBC latest update: Febru

OpenLink Lite ODBC Drivers for JDBC - CNET Download

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.

OpenLink Lite JDBC Drivers for ODBC - CNET Download

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

OpenLink Lite ODBC Drivers for JDBC (32-bit) for Windows

If the software and operating system are compatible. 2. Ask about operating system patches. Patches can interfere with installs on otherwise supported operating systems. 3. Check file and directory permissions. 4. Use the Windows explorer or Unix df -k to check disk space. 5. Insure unnecessary processes are shutdown. 6. Determine how far the installation has progressed. Some Windows installers hang during registry update. However, the actual installation is complete and functional. 7. Attempt to recreate the problem in-house.Consultants should report persistent installation problems to the Tech Support Manager. These problems may indicate critical install bugs. Troubleshooting What Do I Do When The Installation Process Produces Errors? Use the following guidelines to eradicate installation problems: 1. Obtain the name of the installation file. Obtain the name and version of the operating system. (Use uname -a on Unix.) Compare the two resources to determine if the software and operating system are compatible. 2. Ask about operating system patches. Patches can interfere with installs on otherwise supported operating systems. 3. Check file and directory permissions. 4. Use the Windows explorer or Unix df -k to check disk space. 5. Insure unnecessary processes are shutdown. 6. Determine how far the installation has progressed. Some Windows installers hang during registry update. However, the actual installation is complete and functional. 7. Search OPIE for a description of the actual error. 8. Attempt to recreate the problem in-house.Consultants should report persistent installation problems to the Tech Support Manager. These problems may indicate critical install bugs. Troubleshooting What Do I Need To Test The JDBC-ODBC Bridge? You need a functional ODBC Data Source Name (DSN). This DSN may use OpenLink or non-OpenLink drivers. You need to install Sun's Java Runtime Environment (JRE) on the same machine as the ODBC Data Source. You need to install OpenLink's Single-Tier JDBC driver on the machine that contains the ODBC Data Source and the JRE. You need to run your JAVA application on the machine that contains OpenLink's Single-Tier JDBC driver. Troubleshooting What Do I Need To Test The ODBC-JDBC Bridge? You need JDBC drivers that connect to your target data source. You need to install your Single-Tier client driver or Multi-Tier server components (Request Broker & JDBC Bridge Agent) on the machine, which contains the JDBC connection URL. Your JDBC client application must reside on the machine that contains the Single-Tier client driver or the Multi-Tier client components. Troubleshooting What Do I Need To Test The ODBC-ODBC Bridge? You need 3rd party ODBC drivers that connect to your database; You need to install your Single-Tier driver or Multi-Tier driver server components (Request Broker & Generic ODBC Agent) on the machine, which contains the 3rd party ODBC drivers; Your client application must reside on the same machine as the Single-Tier driver or the Multi-Tier driver client components. Troubleshooting What Environment Variables Need To Be Set On Unix Systems? Users need to run openlink.sh or openlink.csh in the appropriate shell to set the following variables on all unix systems: CLASSPATH A JAVA. Download OpenLink Lite JDBC Drivers for ODBC latest version for Windows free to try. OpenLink Lite JDBC Drivers for ODBC latest update: Ma Download OpenLink Lite ODBC Drivers for JDBC latest version for Windows free to try. OpenLink Lite ODBC Drivers for JDBC latest update: Febru

New OpenLink ODBC-JDBC Lite Bridge Driver (Connector) for

Compatibility Can I mix and match client and server components from different OpenLink versions? OpenLink Software does not support mixed-version installations. Mismatched client and server software may not hinder a user's ability to connect and query. However, version incompatibility issues will arise over time. In fact, users who mix OpenLink 3.x and OpenLink 4.x software can expect specific problems with stability, transactions, and threading. These problems can only be resolved by upgrading the older component. Compatibility Can I run OpenLink 32-bit data access drivers (ODBC or JDBC) on a 64-bit operating system? OpenLink 32-bit data access drivers (ODBC or JDBC) software runs on 64-bit operating systems. However, OpenLink's 32-bit data access drivers are designed for use with 32-bit applications. Connectivity is possible to 64-bit applications that ship with 32bit libraries. However, OpenLink does not recommend this configuration. Compatibility Can I use 64-bit OpenLink ODBC or JDBC Drivers on a 32-bit operating system? OpenLink Software does not recommend this configuration. Compatibility Can I run multiple versions at the same time? Users like to run multiple driver versions for comparative purposes. Single-Tier users simply install their new drivers to a new directory. Multi-Tier drivers should install their new drivers to different directories, as well. In addition, Multi-Tier users must insure that their Request Brokers use separate TCP/IP Listen ports. Compatibility Do I need ODBC or JDBC Drivers? If you are unsure of whether you require our ODBC or JDBC drivers, please review the questions posed below: Do you need to query a database with a 3rd party application? Is your application ODBC- or JDBC- compliant? Does your network environment support the TCP/IP or SPX protocol? OpenLink's Data Access Drivers provide ODBC and JDBC connectivity between compliant applications and databases. Moreover, OpenLink's drivers use the TCP/IP network protocol to achieve this connection. Consequently, if your response is YES to the aforementioned questions, you need these drivers. If you are still unsure, please consult your Database Administrators, System Administrators, or other knowledgeable staff. Users who respond NO to one or more questions must clarify their needs with either a Support Consultant or their Account Manager. We offer other solutions which might be what you require. Compatibility Do OpenLink ODBC Drivers work with Oracle Heterogeneous Services? Our ODBC drivers work in conjunction with Oracle's Heterogeneous Services. Compatibility Do OpenLink ODBC Drivers work with SQLServer Linked Servers? OpenLink's 5.x+ drivers support ODBC API calls made by MS SQLServer's Linked Servers. We also provide an alternative OLE DB provider for use with this and similar products. Compatibility Does OpenLink ODBC Drivers work with the SQL Server DTS Wizard? OpenLink's 5.x+ drivers support ODBC API calls made by MS SQLServer's DTS Wizard. We also provide an alternative ODBC provider for ADO.NET and OLE.DB for use with this and similar products. Compatibility Do you have 16Bit drivers? OpenLink produced 16Bit 1.x builds. These builds are not available to the general public. Compatibility How can I tell if OpenLink produces software for a particular operating system or database? Go to

OpenLink Software - ODBC Drivers for JDBC-ODBC (Pricing)

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

OpenLink Software - ODBC Drivers for JDBC (Pricing)

Do I Troubleshoot A Failed JDBC-ODBC Bridge Connection? 1. Insure that the ODBC Data Source Name connects to the target database. 2. Insure that Windows-based ODBC Data Sources are System Data Sources. 3. Insure that OpenLink's Single-Tier driver is installed on the machine that contains the ODBC Data Source Name. 4. Insure that you pass the exact name of the ODBC Data Source in the JDBC connection URL. 5. Insure that your Single-Tier JDBC connection URL uses the following syntax: jdbc:openlink://ODBC[/DSN][/UID][/PWD][/READONLY] For example: jdbc:openlink://ODBC/DSN=Local Oracle ODBC/UID=scott/PWD=tiger Troubleshooting How Do I Troubleshoot A Failed ODBC-JDBC Bridge Connection? 1. Insure that the JDBC connection URL connects to the target database. 2. Insure that OpenLink's Single-Tier client components or Multi-Tier server components are installed on the machine that contains the JDBC connection URL. 3. Multi-Tier users insure that oplrqb and a JDBC Bridge Agent (jdbc13_mv, jdbc14_mv, etc.) appear in the /bin sub-directory of the OpenLink server components installation. 4. Multi-Tier users insure that oplrqb and the JDBC Bridge Agent (jdbc13_mv, jdbc14_mv, etc.) return version and usage information. For example: > jdbc14_mv -? JDBC Database Agent (JDK 1.4)(multi threaded) Version 1.2 as of Thu Sep 04 2003 (Release 5.1 cvsid 00068). Compiled for Linux 2.2.25 (i686-pc-linux-glibc2.1) Copyright (C) OpenLink Software 5. Insure that you pass the exact JDBC driver name string and JDBC connection URL in your OpenLink Data Sources. You can test the driver name string with the java command. It should return version and release information. For example: > java openlink.jdbc3.Driver OpenLink Generic Driver for JDBC(TM) 3.0 Version 04.19 (Release 5.1) 6. Multi-Tier users insure that JDBC 1.1, JDBC 1.2, JDBC 1.3, or JDBC 1.4 appears in the Domain or Server Type field of the Multi-Tier Data Source Name. (Case and spacing matter!) 7. Unix Single-Tier users insure that JDBC 1.1, JDBC 1.2, JDBC 1.3, or JDBC 1.4 appears in the Existing Environment field of the Single-Tier Data Source Name. (Case and spacing matter!)If the problem persists, complete a troubleshooting worksheet. Post the results into an online support case. Troubleshooting How Do Users Start The Multi-Tier Request Broker? Windows users should take the following action: 1. Login to the machine, which contains the OpenLink server components. 2. Open the Services utility. (Control Panel) 3. Locate the OpenLink Request Broker service. 4. Highlight the service. 5. Click the Start icon.Unix users should take the following action: 1. Login to the machine, which contains the OpenLink server components. 2. cd into the root of the OpenLink installation. 3. Execute openlink.sh (Bourne/Bash shell) or openlink.csh (C shell). 4. cd into the /bin sub-directory of the installation. 5. Execute the following command: oplrqbNew Unix users may want to start the Request Broker with oplrqb +loglevel 7 +logfile oplrqb.log. This instantiates logging and will elucidate problems that may occur. Troubleshooting How can I determine which ports the Multi-Tier Request Broker uses? The Request Broker port appears in the Session Rules Book. This is the oplrqb.ini file that appears in the /bin sub-directory of the user's server components

OpenLink Software - JDBC-to-ODBC Bridge Drivers

Run in a Bourne or Bash shell. openlink.csh should be run in C shell. Configuration Do I need to configure my environment to support my JDBC connections? Insure that the CLASSPATH environment variable is set on the machine that contains your JDBC client application. CLASSPATH appears in the Windows System Utility (Control Panel). Windows users need to navigate to the portion of the utility that displays their User and System settings. Unix users may use echo to display their CLASSPATH setting. For example: bash$ echo $CLASSPATH /home/openlink/v51/mt/jdk1.4 CLASSPATH must pass the full path to an OpenLink JDBC opljdbc.jar, opljdbc2.jar, opljdbc3.jar or megathin.jar, megathin2.jar file depending on your JDK. Configuration Do users need to employ special configuration to operate in a firewalled environment? Single-Tier users should not need to open ports to accommodate the Single-Tier driver. However, ports may need to be opened to facilitate connections between the database native client and the database to which it connects. Multi-Tier users need to take the following action, if a firewall surrounds the machine that contains the Multi-Tier server components Configuration How Do I Assist A User Who Does Not Know What Values To Pass To His Or Her Variables? All database specific environment variables should appear in the database user's .profile (unix) or other, standard configuration file. Users may open these files to ascertain which values need to appear in their Single-Tier openlink.ini files and their Multi-Tier oplrqb.ini files. In fact, users should execute the database user's .profile before installing Single-Tier drivers or Multi-Tier server components. The installers will detect the variables and write them into the appropriate location. The standardized, ODBC and JDBC variables pass the following values:— CLASSPATH A JAVA client variable that passes the full path to an OpenLink JDBC .jar file.— LD_LIBRARY_PATH A generic library path variable that appends the full path to OpenLink's lib sub-directory.— LIBPATH An AIX library path variable that appends the full path to OpenLink's lib sub-directory.— ODBCINI Passes the full path to ~/openlink/bin/odbc.ini.— ODBCINSTINI Passes the full path to ~/openlink/bin/odbcinst.ini.— OPENLINKINI This Single-Tier variable passes the full path to ~/openlink/bin/openlink.ini.— PATH Appends the full path to OpenLink's bin sub-directory.— SHLIB_PATH An HP/UX library path variable that appends the full path to OpenLink's lib sub-directory. Configuration How Do I Configure An JDBC-ODBC Bridge Connection? Create a Single-Tier JDBC connection URL that passes the following values:jdbc:openlink://ODBC/DSN=Valid ODBC Data Source/UID=database username/PWD=database passwordHere are some examples:jdbc:openlink://ODBC/DSN=Informix Stores7/UID=informix/PWD=informix ;jdbc:openlink://ODBC/DSN=My Oracle DB/UID=scott/PWD=tiger ;jdbc:openlink//ODBC/DSN=SQLServer Northwind Database/UID=sa Configuration How Do I Configure An ODBC-JDBC Bridge Connection? Unix Single-Tier users pass the following values in your ODBC-JDBC Bridge Data Source: — Name - Any Descriptive Title ; — Database Name - JDBC Driver Name String: openlink.jdbc3.Driver ; — Options - Functional JDBC connection URL.: jdbc:openlink://localhost:5000/SVT=Oracle 8.1.x/DATABASE=ORCL/UID=scott/PWD=tiger ; — Username - JDBC Data Source Userid ; — Existing Environment - Pass the value that corresponds to your JRE version: JDBC 1.1, JDBC 1.2, JDBC 1.3, or JDBC 1.4.Windows Single-Tier users pass the following values in your ODBC-JDBC Bridge Data Source: — Data Source. Download OpenLink Lite JDBC Drivers for ODBC latest version for Windows free to try. OpenLink Lite JDBC Drivers for ODBC latest update: Ma

OpenLink Software - ODBC-to-JDBC Bridge Drivers

ODBC or JDBC drivers or you might require one or more additional components -e.g., clients or agents-to match pre-existing software. Troubleshooting My JDBC Type 3 Connections Spawn Multiple Agents That Consume My Licenses. What Do I Do? This is expected behavior. OpenLink's 1.x and 3.x Multi-Tier connections spawn a JDBC-specific agent that spawns a database-specific agent. Hence, one JDBC connection results in two concurrent connections. OpenLink's latest drivers do not spawn both a JDBC agent and a database agent. OpenLink's new database agents are equipped to handle JDBC connections in their entirety. Troubleshooting My Request Broker shuts itself down. What do I do? Users may experience intermittent Request Broker shutdowns. This problem stems from the use of one license on multiple machines, and it produces "Duplicate Serial Number" errors. Users who encounter this problem must request an additional temporary or permanent license keys from their account manager or shut down a request broker to resolve this problem. Troubleshooting Troubleshooting registering a product with a temporary or commercial license? Use the following guidelines to troubleshoot licensing problems: 1. Ensure that the Windows Single-Tier license is placed in your Lite32 sub-directories. 2. If on Unix, ensure that the Single-Tier license is placed in the b/in sub-directory of the OpenLink installation. Alternatively, users may pass the full path to licenses to OPL_LICENSE_DIR. This variable may be set using the command line, openlink.sh, openlink.csh, or your .profile. 3. Multi-Tier users ensure the licence is placed in the bin/ sub-directory of the server component installation. 4. Ensure that ftp transfers are conducted in binary. OpenLink's .lic licenses are binary-format files. 5. Windows Single-Tier users should uninstall their software, remove all references to Single-Tier software from the registry, and reinstall, if licensing problems persist. Occasionally, Windows Single-Tier users experience registry corruption, which necessitates the registry wipe and reinstall.OpenLink consultants have other utilities that may help debugging if you suspect a license-file is corrupt.The license version must match the Single-Tier driver version or the Multi-Tier request broker and agent version. Operating System Licenses must be generated for the appropriate operating system. CPU's The number of CPUs cited in the license must match the number of CPUs present in the machine. Access Mechanism Licenses may restrict ODBC or JDBC data access. Other licenses permit both ODBC and JDBC access. Database Licenses must list each of the databases to which the user intends to connect. Applications Certain licenses are limited for use with one application.OpenLink's 1.x and 3.x ship with a license text file. Consultants may open this license with Notepad or a similar text editor. The file should contain the same parameters listed above. Troubleshooting What Component Naming Conventions is Used? OpenLink's client drivers are library files. Consequently, Windows Multi-Tier drivers begin with olod (OpenLink ODBC Driver) and end with a .dll extension. Unix Multi-Tier drivers are named oplodbc (OpenLink ODBC) and end with a .la, .sl, or .so extension. OpenLink's Single-Tier drivers have a variety of names that are too numerous to list. Windows drivers continue to

Making an OpenLink ODBC-JDBC Bridge driver

End with .dll, and Unix drivers continue to end with .la, .sl, and .so. However, the similarities end there. The actual Windows Single-Tier driver name begin with `ntl' (WinNT Lite) and end with a series of numbers and letters that denote the driver version and intended database. The actual Unix Single-Tier driver name begins with some combination of letters that represents the intended database, and it ends with _mt_lt (Multi-Threaded Lite) , _mt_lu (Multi-Threaded Lite Unicode), _st_lt (Single-Threaded Lite), _st_lu(Single-Threaded Lite Unicode). OpenLink's Unix-based iODBC Driver Manager is named libiodbc and ends with a .la, .sl, or .so extension. OpenLink's Multi-Tier Request Broker is named oplrqb. OpenLink's Multi-Tier Database Agents begin with a three or four character name that designate the intended database, and they end with a .sv (Single-Threaded version) or .mv (Multi-Threaded version) extension. Troubleshooting What Do I Do If My Applications Fail To Connect After I Upgraded My Multi-Tier JDBC Drivers? OpenLink's 1.x and 3.x Multi-Tier drivers use different JDBC connection mechanisms. The older drivers route the request through a JDBC-specific agent that speaks to a database-specific agent. Here is the sequence of events needed to perform this task: 1. User creates a JDBC connection URL. For example: jdbc:openlink://localhost:5000/SVT=Ingres II/DATABASE=iidbdb/UID=ingres/PWD=ingres/JDBCAGENT=jodbc 2. The Broker associates all JDBC connection attempts with one of the JDBC Domains that appear in the [Domain] section of the Session Rules Book (oplrqb.ini). For example: [Domain Aliases] jodbc = jodbc judbc = judbc jdbc = jdbc 3. The Broker uses the Domain Alias to resolve the connection using one of the JDBC Mapping Rules from the [Mapping Rules] section of oplrqb.ini. For example: [Mapping Rules] jodbc:*:*:java:*:*:* = accept jodbc_client judbc:*:*:java:*:*:* = accept judbc_client jdbc:*:*:java:*:*:* = accept jdbc_client *:*:*:java:*:*:* = accept judbc_client 4. The Mapping Rules associate the connection attempt with a JDBC agent configuration section. For example: [jodbc_client] Program = jodbc_sv.exe CommandLine = ;+debug ReUse = never 5. The agent configuration section controls which JDBC agent is spawned to service the connection. In the above instance, jodbc_sv.exe is spawned. The JDBC agent spawns the database agent that corresponds to the SVT parameter of the JDBC connection URL. The following sections of the Rules Book shows how SVT=Ingres II causes the JDBC agent to spawn the oig2_sv database agent: Domain Aliases] Ingres II = oig2 [Mapping Rules] oig2:*:*:*:*:*:* = reject The Ingres II Database Agent is not configured [generic_oig2] Program = oig2_sv.exe Environment = INGRES_II OpsysLogin = Yes ReUse = neverOpenLink's newest drivers omit the need for a distinct JDBC agent. JDBC-specific Domains, Mapping Rules, Agent Configuration Sections, and agents are omitted from the connection resolution. Instead, the Broker resolves the JDBC connection URL using only the SVT parameter. The database agent that is spawned is now able to handle both ODBC and JDBC connections Users may prevent most problems by removing JDBCAGENT= from their JDBC connection URLs. If problems persist, advanced users may resolve most problems by editing the Session Rules Book. New users are encouraged to contact OpenLink Product Support. Some 1.x and. Download OpenLink Lite JDBC Drivers for ODBC latest version for Windows free to try. OpenLink Lite JDBC Drivers for ODBC latest update: Ma

OpenLink JDBC-to-ODBC Bridge Drivers Are More

Scripts (install.sh) in ASCII transfer mode. FTP all other files in binary. Installation How To Uncompress Files? OpenLink's products ship in a compressed file format: — .bin Binary Mac Classic — .dmg Disk Image Mac OS X — .hqx BinHex Mac Classic — .tar Compressed Archive Unix Decompress with install.sh — .taz GZIP Archive Unix Decompress with tar -xvfz or gunzip — .zip Zip File WinZip Decompress with WinZip Installation I cannot download software to the appropriate machine. What do I do? Network or security policies may restrict a user's ability to download software onto a machine. Installation What Do I Do With The License File? Windows Single-Tier users must copy the file to their Lite32 directories. Mac and Unix Single-Tier users must copy the files to the /bin sub-directory of their OpenLink installations. No additional action is needed. All Multi-Tier users must copy their licenses to the /bin sub-directory of the OpenLink installation. Then, Multi-Tier users must restart their Request Broker services. ALERT OpenLink's 1.x and 3.x licensing mechanism differs substantially from the current procedure. Single-Tier legacy license holders must transfer their license file to the /bin sub-directory of their OpenLink installation. Then, they must run the register.exe program. Multi-Tier legacy license holders must perform the following actions: Shutdown the OpenLink Request Broker; Transfer the license file to the /bin sub-directory of their server installation; Rename license name.ini to register.ini; Run register.ini; Restart the Request Broker Service. Installation What Happened To The JdbcJodbc_sv And Judbc_sv Agents? OpenLink's 1.x and 3.x Multi-Tier connections spawned a JDBC-specific agent (jodbc_sv, judbc_sv), which spawned a database-specific agent. OpenLink's newer drivers have incorporated the functionality of jodbc_sv and judbc_sv into the database agents. Hence, separate jodbc_sv and judbc_sv agents are no longer needed. Installation What Is The Proper Way To Perform An Upgrade? Single-Tier users should terminate active ODBC connections, which use OpenLink's drivers. All Single-Tier users should back up their licenses, and Unix Single-Tier users should back-up existing odbc.ini and openlink.ini files. Finally, Single-Tier users should proceed with their upgrades. Multi-Tier users should terminate active ODBC connections, which use OpenLink's drivers. Multi-Tier users should also stop their Request Broker services. All Multi-Tier users should back-up their license and oplrqb.ini files, and Unix Multi-Tier users should back-up their odbc.ini files. Finally, Multi-Tier users should proceed with their upgrades. What about upgrading driver name or installing new driver? Internal Is OpenLink Support Staff responsible for all user problems? OpenLink Support staff should endeavor to solve most problems. However, some problems are the domain of the user. OpenLink Support staff is not responsible for extensive custom development. Users must code their own applications or seek assistance from OpenLink's Professional Services team. Likewise, OpenLink staff is not responsible for user database and network administration. — Acceptable: Can you help me write a JDBC connection URL to connect my application to Informix? — Questionable: Can you help me write a JAVA program? — Acceptable: Can you help me establish an ODBC connection to Oracle? — Questionable: Can you