i-net KONNEKTER

JDBC 2.0 driver for Remote JDBC access

i-net KONNEKTER is a new type of JDBC driver, it is the best solution if you want to develop an applet/server application that supports different DBMS thus making it practically indispensable for every Java-developer. It enables the remote access to JDBC drivers.

You can use it with MS SQL Server, Oracle, DB2, Sybase, MySQL, PostgreSQL, Informix, ODBC, MS Access and many other databases.

Short Description

Latest driver release:	2.17
Last update:	Oct 26, 2011
Java Version:	1.1 or higher
JDBC API Level:	1.22
Driver Type:	4
Supported DBMS:	Plain Text files, CSV
Download Size:	250 KB
Driver Size:	44 KB + 39 KB

There are a dozen reasons why this new JDBC driver should catch your attention as well.

Secure data transfer The data between client and server are being encrypted. This takes place independently of the features of the underlying database.
Password security You can save the database passwords on the server. The passwords do not need to be transfered to the client and back to the server.
Connect to a database not installed on the same machine as the webserver i-net KONNEKTER can connect to a database that is not installed on the webserver without a SecurityException in the browser or a signed applet.
JDCB 2.0 support You can use the JDBC 2.0 features in the JDK 1.1.x JVM. Currently most browsers only have a JDK 1.1.x JVM thus supporting JDBC 1.22, only. You do not need to install the Java PLUGIN on every client which potentially saves you installing several megabytes of software.
DataSources You can configure DataSources on the server for virtually every database. You can do this with all JDBC drivers. The client does not need to know which database the server uses.
Simple porting of different SQL Syntax for different DBMS On the server side you can config named SQL expressions. The client only knows the name of the SQL expression. If you develop your application for different database vendors then you simply add different named SQL expressions for the different DBMS. The client side does not need to know which database runs on the server.
Hidden database structure If you use named SQL expressions a hacker won't see your database structure if the hacker looks in the code of the applet class files.

Named Parameters You can use preparedStatements and CallableStatements with named parameters. Your code is more readable.
If you have complex SQL expressions then the order of the parameters can be different for the different DBMS. With named parameters you will have no problems with the order of the parameters.
Small download The client only needs to download the client part of i-net KONNEKTER (approx. 40 KB). The JDBC drivers of all databases are on the server and do not need to be downloaded to the applet client. Thus your applet will be much faster!
Connection pooling i-net KONNEKTER makes a connection pooling over multiple clients.
Performance through JavaCommand With JavaCommand you can execute multiple statements and/or complex business logic on the server as a single command from the client.
For example:
You have a JavaCommand “CreateTicket”
You set the parameter for this command on the client machine and simply call execute().
On the server you can save a row in the tables TicketMain, TicketDetails and TicketInfo. This can be done in a single transaction.
The client made one network access only but you have saved multiple rows in a single transaction as opposed to doing it separately on the client with multiple network accesses.
Performance through fillList() With fillList() you can request all data of one column. No need to scroll through the complete ResultSet.