next up previous contents
Next: E.3 Zukunft von JMAPI Up: E Email-Korrespondenz mit Sun Previous: E.1 Fragen zur JMAPI-Architektur

E.2 Verwendbare Datenbanken und Treiber

Date: Thu, 2 Apr 1998 07:10:46 -0700 (MST)
From: Bill Birnbaum <Bill.Birnbaum@East.Sun.COM>
To: Julian Kolodko <julian.kolodko@star.com.au>
Cc: bill.birnbaum@East.Sun.COM,
    jmapi-interest@East.Sun.COM
Subject: Tested Database/JDBC combinations

Attached is the list of databases and JDBC driver we have had working as
outlined in the README:


1.1 DATABASE OPTIONS

As you can imagine, testing the combination of databases, operating systems,
and drivers that JMAPI will support is a fairly large task. This release
supports Sybase, Oracle, and JDBC. We are in the process of writing the
installation and setup instructions on how to use these various options.

We will also provide a list of specific versions of databases and drivers
that we will support. We have found many differences with the JDBC driver
implementations and only a few of them have the necessary compliance level
to support JMAPI.

Here is a list of databases that JMAPI supports and the interfaces used to
support each:

 Database           Version      OS                 Driver



 Sybase             10.x         Solaris & NT 3.5   Native JMAPI Driver

 Sybase             11           NT 4.0             Native JMAPI Driver

 Sybase             11           Solaris & NT       JDBC

 Oracle             7            Solaris & NT       Native JMAPI Driver

 Oracle             8            Solaris & NT       JDBC

 MS SQL             6            NT                 JDBC



1.2 JDBC SUPPORT IN THIS RELEASE

This JMAPI release includes support that allows you to use a JDBC driver to
connect to a JDBC-compliant database. While any JDBC 1.2 compliant Type 4
driver should work, we have tested only with Connect Software's FastForward
JDBC driver. For more information on this driver see the Connect home page
at:

http://www.connectsw.com



> Hello all
> 
>       Try as I might, I can not find a JDBC capable database and driver
> that will actually work with JMAPI.  I've tried Progress(v7.3D and v8.2A),
> Postgress (v6.0 - I have not tried v6.3 and the new JDBC driver as yet), and
> MSQL.  I've tried drivers from Openlink, InterSolv and Sun.  The common
> problem with all these combinations is that none of them support Level 3
> Transaction Isolation (thats what jrb.util.TestJDBCDriver reports anyhow).
> 
>       When I run setupdb.bat using a Progress database I get errors like
> "Unable to understand after create" (from Intersolv Drivers)  and "Could not
> get tableschema info - Syntax error or access error: Base jmapi does not
> exist" (from Openlink drivers).
> 
>       Why the correlation between Level 3 Isolation and problems with
> tables?  Is this level of consistency control really needed?
> 
>       Has anyone ever managed to get a JDBC database to talk to JMAPI?
> Can anyone suggest an alternate driver/database?  Could this be a problem
> with Progress?
>       
>       Thanks for your help
> 
>       Julian Kolodko
>       Star Systems
>



Copyright Munich Network Management Team