Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

The problem while doing Birt report deployment

I am trying to develop a report by using Birt embedded in JAZZ client. Everything goes well when I just use JAZZ data source, but it shows the rest error message when I use JDBC data source. Does any one know how to solve this problem?

Ps.I have added the related db2 driver jar files into RTC's class path.


Error Message:
Table (id = 118):
+ An exception occurred during processing. Please see the following message for details:
Cannot open the connection for the driver: org.eclipse.birt.report.data.oda.jdbc.
Cannot load JDBC Driver class: com.ibm.db2.jcc.DB2Driver.

0 votes



13 answers

Permanent link
You need to put the JDBC driver jars under org.eclipse.birt.report.data.oda.jdbc/drivers

0 votes


Permanent link
You need to put the JDBC driver jars under org.eclipse.birt.report.data.oda.jdbc/drivers


It only works for RTC client but sever.

The error message I got was from server site.

0 votes


Permanent link
On 10/29/2009 11:22 PM, s861520 wrote:
rjaouaniwrote:
You need to put the JDBC driver jars under
org.eclipse.birt.report.data.oda.jdbc/drivers

It only works for RTC client but sever.

The error message I got was from server site.


Could you please log a defect with the error message, and we'll look
into it?

Thanks,

james
RTC Reports Team Lead

0 votes


Permanent link
How can I post the log file? send it to you?

I have captured some screenshot.


On 10/29/2009 11:22 PM, s861520 wrote:
rjaouaniwrote:
You need to put the JDBC driver jars under
org.eclipse.birt.report.data.oda.jdbc/drivers

It only works for RTC client but sever.

The error message I got was from server site.


Could you please log a defect with the error message, and we'll look
into it?

Thanks,

james
RTC Reports Team Lead

0 votes


Permanent link
On 11/3/2009 10:22 PM, s861520 wrote:
How can I post the log file? send it to you?

I have captured some screenshot.


jmoodywrote:
On 10/29/2009 11:22 PM, s861520 wrote:
rjaouaniwrote:
You need to put the JDBC driver jars under
org.eclipse.birt.report.data.oda.jdbc/drivers

It only works for RTC client but sever.

The error message I got was from server site.


Could you please log a defect with the error message, and we'll look
into it?

Thanks,

james
RTC Reports Team Lead



If it's not sensitive, you can attach the log file to the work item. If
it's sensitive, just email it to me.

james
RTC Reports Team Lead

0 votes


Permanent link
You need to put the JDBC driver jars under org.eclipse.birt.report.data.oda.jdbc/drivers on the server side also.

Are you running Tomcat or Websphere?

0 votes


Permanent link
I am running Websphere.

You need to put the JDBC driver jars under org.eclipse.birt.report.data.oda.jdbc/drivers on the server side also.

Are you running Tomcat or Websphere?

0 votes


Permanent link
I'm running into the same error message show above running jazz on tomcat. The org.eclipse.birt.report.data.oda.jdbc was jarred up. I created a directory called org.eclipse.birt.report.data.oda.jdbc_2.3.2.r232_v20090212 and put unjarred the contents in there and copied the com.ibm.db2.jdbc_9.5.0.jar file in the "drivers" directory.
No luck getting that to work.
However, the directory path looks suspect and is not under tomcat. It's located at: /local/jazz/server/update-site/plugins/org.eclipse.birt.report.data.oda.jdbc_2.3.2.r232_v20090212/drivers

tomcat appears to be installed at /local/jazz/server/tomcat
Any suggestions?

I would have expected the birt plugins to be located at: /local/jazz/server/tomcat/webapps/jazz/WEB-INF/eclipse/plugins
But the following are all that I see there:

com.hp.hpl.jena.rdf_2.6.0.I200910212101

com.ibm.db2.jdbc_9.5.0.jar
com.ibm.icu_3.8.1.v20080530.jar
com.ibm.sistdase.json_1.0.0.I200905282001.jar
com.ibm.team.http.client.impl_1.0.2.I201002181410.jar
com.ibm.team.http_1.0.2.I200911232126.jar
com.ibm.team.jfs.app.cache.provider.memcached_1.0.0.I200908260004.jar
com.ibm.team.jfs.app.cache_1.0.2.I200912012235.jar
com.ibm.team.jfs.app.error_1.0.2.I200912012235.jar
com.ibm.team.jfs.app.friendsconfig_1.0.2.I201002051406.jar
com.ibm.team.jfs.app.http.cache_1.0.1.I200909041225.jar
com.ibm.team.jfs.app.http_1.0.2.I200912012235.jar
com.ibm.team.jfs.app.memcached_1.0.1.I200909041225.jar
com.ibm.team.jfs.app.oauth_1.0.2.I200912031748.jar
com.ibm.team.jfs.app.query_1.0.2.I200912012235.jar
com.ibm.team.jfs.app.servlet_1.0.2.I200912012235.jar
com.ibm.team.jfs.app.util_1.0.1.I200909041225.jar
com.ibm.team.jfs.app.xml_1.0.2.I200912012235.jar
com.ibm.team.jfs.app_1.0.2.I200912012235.jar
com.ibm.team.json_1.0.0.I200908182153.jar
com.ibm.team.repository.common.json_1.0.2.I200910052001.jar
com.ibm.team.repository.jndi_1.0.2.I200910022140.jar
com.ibm.team.repository.provision_1.0.2.I200910282338.jar
com.ibm.team.repository.web.nl1_1.0.2.v201003022319.jar
com.ibm.team.repository.web.nl2_1.0.2.v201003022319.jar
com.ibm.team.repository.web_1.0.2.I200911242312.jar
com.ibm.team.server.httpcore.bridge_1.0.1.I200909032301.jar
javax.xml.stream_1.0.0.20090824
net.jazz.ajax.nl1_1.0.1.v201003022319.jar
net.jazz.ajax.nl2_1.0.1.v201003022319.jar
net.jazz.ajax.service.nl1_1.0.2.v201003022319.jar
net.jazz.ajax.service.nl2_1.0.2.v201003022319.jar
net.jazz.ajax.service_1.0.2.I201002252337.jar
net.jazz.ajax_1.0.1.I201002190250.jar
net.jazz.web.app.nl1_1.0.2.v201003022319.jar
net.jazz.web.app.nl2_1.0.2.v201003022319.jar
net.jazz.web.app_1.0.2.I200912031748.jar
net.jazz.web.client.nl1_1.0.0.v201003022319.jar
net.jazz.web.client.nl2_1.0.0.v201003022319.jar
net.jazz.web.client_1.0.0.I200906031613.jar
net.jazz.web.core.nl1_1.0.1.v201003022319.jar
net.jazz.web.core.nl2_1.0.1.v201003022319.jar
net.jazz.web.core_1.0.1.I200909032147.jar
net.jazz.web.ui.nl1_1.0.2.v201003022319.jar
net.jazz.web.ui.nl2_1.0.2.v201003022319.jar
net.jazz.web.ui_1.0.2.I200912012235.jar
net.jazz.web.util.nl1_1.0.2.v201003022319.jar
net.jazz.web.util.nl2_1.0.2.v201003022319.jar
net.jazz.web.util_1.0.2.I201003012300.jar
net.oauth_0.1.20081127.I200907161501.jar
org.apache.ant_1.7.0.v200803061910
org.apache.commons.codec_1.3.0
org.apache.commons.fileupload_1.2.0
org.apache.commons.io_1.2.0.v20090903
org.apache.commons.logging.log4j_1.0.4.jar
org.apache.commons.logging_1.0.4.v20080605-1930.jar
org.apache.http.client_4.0.0.beta2
org.apache.http_4.0.0
org.apache.james.mime4j_0.4.0.v20090903
org.apache.log4j_1.2.12.20090824
org.apache.naming_5.5.20
org.dojotoolkit.dijit_1.2.0.jar
org.dojotoolkit.doh_1.2.0.v20090605.jar
org.dojotoolkit.dojo_1.2.0.jar
org.dojotoolkit.dojox_1.2.0.jar
org.dojotoolkit.shrinksafe_1.0.1.I200909112123.jar
org.eclipse.core.contenttype_3.3.1.R34x_v20090825-1137.jar
org.eclipse.core.jobs_3.4.1.R34x_v20081128.jar
org.eclipse.core.runtime_3.4.0.v20080512.jar
org.eclipse.equinox.app_1.1.0.v20080421-2006.jar
org.eclipse.equinox.common_3.4.0.v20080421-2006.jar
org.eclipse.equinox.http.registry_1.0.100.v20080427-0830.jar
org.eclipse.equinox.http.servlet_1.0.100.v20080427-0830.jar
org.eclipse.equinox.http.servletbridge_1.0.0.v20080427-0830.jar
org.eclipse.equinox.preferences_3.2.201.R34x_v20080709.jar
org.eclipse.equinox.registry_3.4.0.v20080516-0950.jar
org.eclipse.equinox.servletbridge_1.0.101.R34x_v20090114-1346.jar
org.eclipse.osgi.services_3.1.200.v20071203.jar
org.eclipse.osgi_3.4.3.R34x_v20081215-1030.jar
org.mozilla.rhino_1.6.7.r22x_v20090812.jar
org.opengroup.arm40-fragment.jar

0 votes


Permanent link
On 5/18/2010 6:07 PM, reysa wrote:
I'm running into the same error message show above running jazz on
tomcat. The org.eclipse.birt.report.data.oda.jdbc was jarred up. I
created a directory called
org.eclipse.birt.report.data.oda.jdbc_2.3.2.r232_v20090212 and put
unjarred the contents in there and copied the
com.ibm.db2.jdbc_9.5.0.jar file in the "drivers"
directory.
No luck getting that to work.
However, the directory path looks suspect and is not under tomcat.
It's located at:
/local/jazz/server/update-site/plugins/org.eclipse.birt.report.data.oda.jdbc_2.3.2.r232_v20090212/drivers

tomcat appears to be installed at /local/jazz/server/tomcat
Any suggestions?


Did you try to delete the tomcat work directory? Tomcat sometimes keeps
a cache of the plugins and won't use new copies unless you delete the
work directory.

james
RTC Reports Team Lead

0 votes


Permanent link
jmoody wrote:
Did you try to delete the tomcat work directory? Tomcat sometimes keeps
a cache of the plugins and won't use new copies unless you delete the
work directory.


Just did and now nothing works. I thought you meant the entire jazz/server/tomcat/work directory. Maybe you just meant a particular plugin. I'll reload the jazz server and put in the driver before starting it and let you know.

0 votes

1–15 items
page 1of 1 pagesof 2 pages

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Oct 28 '09, 8:42 p.m.

Question was seen: 14,998 times

Last updated: May 29 '13, 10:03 a.m.

Confirmation Cancel Confirm