|
Re: IBM Java Toolbox (JT400.jar) JDBC Driver Extremely Slow Performance [message #179963 is a reply to message #176260] |
Tue, 25 July 2006 13:01 |
Eclipse User |
|
|
|
Originally posted by: susanb.softlanding.com
I followed the Birt World article "Using BIRT on the iSeries", up to the
point of designing a report, and I am experiencing the same. Actually, most
times I never even get to the data set dialog. Eclipse seems to hang on the
New Data Set dialog. Have you , or anyone else, gotten any further with
using the jt400.jar?
Thanks,
Susan
|
|
|
Re: IBM Java Toolbox (JT400.jar) JDBC Driver Extremely Slow Performance [message #180055 is a reply to message #179963] |
Tue, 25 July 2006 20:32 |
Robert McCoy Messages: 2 Registered: July 2009 |
Junior Member |
|
|
No, due to other project priorities we have had to leave Birt alone for the
time being. We currently use Actuate eReports for our reporting (it is
being phased out since Actuate is now involved in the BIRT project). We
experienced the same issue using the jt400.jar JDBC driver in that product.
We have switched to using the Sun ODBC-JDBC bridge driver which uses ODBC to
make the connection. The response time is phenomenally different. The Sun
bridge would complete a report in a matter of seconds and the jt400 would
literally take minutes.
We have inquired with IBM to determine if it is an issue with the driver
itself but have gotten no where. I was hoping with BIRT rising popularity
that someone would have the same issue and would know how to work around
this issue.
However, I have used other utilities with the jt400.jar driver and they
perform great. I'm not sure what the difference is. One would think that
it may be BIRT not properly using the driver to make the connection.
By the way Susan, I see that your email address is SoftLanding.com. I am a
big fan of the plugins you all have put out! Sorry I couldn't be much help.
Hopefully someone else may be able to shed some light on the situation.
"Susan Bradeen" <susanb@softlanding.com> wrote in message
news:ea54ng$2v6$1@utils.eclipse.org...
> I followed the Birt World article "Using BIRT on the iSeries", up to the
> point of designing a report, and I am experiencing the same. Actually,
most
> times I never even get to the data set dialog. Eclipse seems to hang on
the
> New Data Set dialog. Have you , or anyone else, gotten any further with
> using the jt400.jar?
>
> Thanks,
> Susan
>
>
|
|
|
Re: IBM Java Toolbox (JT400.jar) JDBC Driver Extremely Slow Performance [message #180243 is a reply to message #180055] |
Wed, 26 July 2006 15:04 |
Eclipse User |
|
|
|
Originally posted by: markp.softlanding.com
Robert McCoy wrote:
> However, I have used other utilities with the jt400.jar driver and
> they perform great. I'm not sure what the difference is. One would
> think that it may be BIRT not properly using the driver to make the
> connection.
I think the problem is that BIRT tries to automatically retrieve all of
the schemas and tables without letting you apply a filter to the
process. In our case, we have 5000 libraries/schemas on our iSeries,
with probably 10 times that many tables. So BIRT is locked up trying
to get at that information.
If the schemas could be filtered before it tries to connect it would
help. The DTP project lets you define JDBC drivers and then browse
schemas and tables. It also lets you define filters on the connection.
So I can filter by a specific library to only see tables in that
library. This works much faster in retrieving the information.
BIRT probably needs something like that added to make it work
effectively with an iSeries.
Mark
|
|
|
|
Powered by
FUDForum. Page generated in 0.04746 seconds