Unify DBIntegrator Client for JDBC; Readme

The documentation for the DBIntegrator Client for JDBC is shipped as HTML pages that you can read with your browser. Start with "DBIntegrator_JDBC.html." See the "What's New" section on the first page for information about changes to the way the product works, as well as new feature descriptions.

The Unify DataServer and DBIntegrator documentation errata can be viewed at: http://www.unify.com/support/resources/index.htm.

How to connect with a Java Application Server

JDBC 1.x compliant Java application servers typically ask for the following information:
Information nameUse this value
Driver class namesimba.jdbc.SimbaDriver
Database URLjdbc:simba:<server name>:<server port>/<data source name>
Connection Propertiesuser and password

JDBC 2.x compliant Java application servers typically ask for the following information:
Information nameUse this value
Driver class namesimba.jdbc.SimbaConnectionPoolDataSource
Data Source PropertiesserverName (hostname of the server running the DBIntegrator server), portNumber (the port on which the DBIntegrator server is listening), serverDSN (the ODBC name of the data source), user, and password

New default value for ArrayBufferSize

The default value for connection property ArrayBufferSize has been increased from 8 to 32. This change will cause an additional 24 KB of memory (the difference between 8 KB and 32 KB) to be allocated for each connection where ArrayBufferSize is not being set. For more information, see the Connecting to Data Sources section in DBIntegrator_JDBC.html.

Array Fetching must be turned on

This version of DBIntegrator Client for JDBC requires Array Fetching to be on. The ArrayFetchOn connection property must be 1, or left unset.

DATA_TYPE column of DatabaseMetaData.getColumns() and others

To avoid incorrect values for DATE and TIME types, use ResultSet.getShort(), getInt(), or getString() to get the DATA_TYPE column value when using the following methods: DatabaseMetaData.getBestRowIdentifier(), getColumns(), getProcedureColumns(), and getVersionColumns().

Cryptography is not implemented

Encryption of database connections is not available in the Unify DBIntegrator Client for JDBC driver. This means that you will not be able to connect through Unify DBIntegrator Server to data sources on encrypted Unify DBIntegrator Server servers. Since the choice of encryption on the server is that all data sources are encrypted or none of them are, encrypted Unify DBIntegrator Server servers will be completely unavailable to the Unify DBIntegrator Client for JDBC.

Firewall tunneling and keep-alives are not implemented

Tunneling through firewalls using HTTP for database connections is not available in this release of the Unify DBIntegrator Client for JDBC. Keep-alives, which are part of the tunneling feature, are also unavailable.

Keep-alives make sure that a database connection is not severed by a firewall due to inactivity. This may be the problem if you find that you are getting unexpectedly disconnected from the Unify DBIntegrator Server server while using the Unify DBIntegrator Client for JDBC through a firewall. The solution is to increase the idle time-out period for the firewall port you are connecting through.

 

$Revision: 5.2 $