|
Hi
all,
I want to suggest another option for JDBC
solutions.
My
company, MERANT, specializes in a middleware JDBC solution called
SequeLink. We actually work with Sun in the ongoing development of the
JDBC standard, and our SequeLink JDBC product is 100% Pure Java. SequeLink
runs on just about any platform (NT, Unix, OS/390), including AS/400 (of
which I am the primary support rep for SequeLink, hence my subscription to this
mailing list).
Here's
some links for more info:
http://www.merant.com/about/news/dd/991103.asp
http://www.merant.com
That's
probably enough to get you going. Please feel free to email me at my
address below if you have further questions!
Thanks
for the forum!
Dave D'Amico
SequeLink Level 2 Support
MERANT DataDirect
( 800-443-1601 (Option 3, 2, Case #)
+ Dave.D'Amico@Merant.com
A personal comment on jdbc:
We used the jdbc drivers from websphere on the as/400 (both
toolbox and native) for about 17 months. To make a long story short -
the performance just isnt there.
I know others have had a great experience with jdbc.
We brought in several such lucky folks as consultants to learn from their
experiences. Some techniques do help - stored procedures,
analyzing sql optimizer diagnostics, etc. Bottom line, though, is
that we get much better (like over 50%) performance using record-level
i/o. I know we lose portability by going to record-level access,
but a portable slow-running servlet is just no good to
us. We really just got to the point where we had no
choice.
I am not saying everyone should dump jdbc for record-level
i/o, but I have a feeling there are others out there with the same experience
we had. Anyone else go from jdbc to record-level i/o or are unhappy with
jdbc performance in websphere on an as/400?
----- Original Message -----
Sent: Thursday, November 11, 1999 4:38
AM
Subject: Re: forcing native access with
websphere and toolbox
If you use JDBC, you can use the toolbox JDBC drivers to
connect to the AS/400 from anywhere. If you are running your servlets on the
AS/400, you can configure your servlet to use the native DB2 JDBC drivers
instead of the toolbox drivers for faster access. (Not sure how it compares
to record level access- I imagine record level performs faster). Another
advtange of JDBC is that your servlet will likely run on any java platform
and connect to any database, depending on the SQL that you use
instead.
Interesting about how you must connect as QTMHHTTP to
bypass TCP/IP on the 400 -- I did not know that.
Luther
----- Original Message -----
Sent: Wednesday, 10 November 1999
21:36
Subject: forcing native access with
websphere and toolbox
Tip of the day: IBM Java Toolbox Record Level
I/O from Servlets
...
| 
midrange.com
