Guidance for Selecting HiT DB2 Connectivity Products

Product:

All DB2 Connectivity Products: HiT ODBC/400, HiT ODBC Server/400, HiT ODBC/DB2, HiT ODBC Server/DB2, HiT OLEDB/400, HiT OLEDB Server/400, HiT OLEDB/DB2, HiT OLEDB Server/DB2, Ritmo/i, Ritmo/DB2, HiT JDBC/400, HiT JDBC/DB2

Version:

Any

Category:

Requirements/Installation

Last Updated:

Topic ID:

7/12/2011

KBFAQ 1660

Summary:

Choosing the correct HiT Connectivity Product to use for your DB2 Environment

Follow the guidelines below to determine which HiT DB2 Connectivity product to use in your environment.

1) Which platform are you using for your application?

If the application is written in ADO.NET or Visual Studio, select Ritmo (.NET) products

If the application is written in Java, select HiT JDBC products

If the application is written in something else (i.e., Powerbuilder), you can use either HiT ODBC or HiT OLEDB.
However HiT ODBC provides support for just relational database formats while HiT OLEDB provides support
for relational PLUS all other data formats.

2) Which type of DB2 database is being accessed?

For IBM DB2 for i, select the "400" version

For IBM DB2 for Linux, Unix, Windows, or Mainframe, select the "DB2" version

3) Is the connectivity required from a client PC to a database, or from a server to a database?

(See examples below for additional guidelines.)

NOTE: If the configuration includes use of Microsoft SQL Server "linked servers," the optimal products would be HiT OLEDB.

Examples

CLIENT Version

SERVER Version

     

ODBC/400

Connecting app written in Powerbuilder on one PC to a DB2 database on IBM i (AS/400)

Connecting app written in Powerbuilder on one server to a DB2 database on IBM i (AS/400)

ODBC/DB2

Connecting app written in Powerbuilder on one PC to a DB2 database on Linux, UNIX, Windows or mainframe

Connecting app written in Powerbuilder on one server to a DB2 database on Linux, UNIX, Windows or mainframe

   

OLEDB/400

Connecting app that sends SQL statements via ADO or directly through OLE DB object properties on one PC to a DB2 database on IBM i (AS/400)

Connecting app that sends SQL statements via ADO or directly through OLE DB object properties on one server to a DB2 database on IBM i (AS/400)

OLEDB/DB2

Connecting app that sends SQL statements via ADO or directly through OLE DB object properties on one PC to a DB2 database on Linux, UNIX, Windows or mainframe

Connecting app that sends SQL statements via ADO or directly through OLE DB object properties on one server to a DB2 database on Linux, UNIX, Windows or mainframe

   

Ritmo/i

Connecting app through Visual Studio, or an app that sends SQL statements via ADO.NET or directly via its own object properties on one PC to a DB2 database on IBM i (AS/400)

Connecting app through Visual Studio, or an app that sends SQL statements via ADO.NET or directly via its own object properties on one server to a DB2 database on IBM i (AS/400)

Ritmo/DB2

Connecting app through Visual Studio, or an app that sends SQL statements via ADO.NET or directly via its own object properties on one PC to a DB2 database on Linux, UNIX, Windows or mainframe

Connecting app through Visual Studio, or an app that sends SQL statements via ADO.NET or directly via its own object properties on one server to a DB2 database on Linux, UNIX, Windows or mainframe

   

JDBC/400

Connecting app through Java-based systems on one PC to a DB2 database on IBM i (AS/400)

Connecting app through Java-based systems on one server to a DB2 database on IBM i (AS/400)

JDBC/DB2

Connecting app through Java-based systems on one PC to a DB2 database on Linux, UNIX, Windows or mainframe

Connecting app through Java-based systems on one server to a DB2 database on Linux, UNIX, Windows or mainframe