Using default JDBC driver on Websphere
Options
When I deploy a BIRT report, I am required to have my JDBC driver location identified in the .rptdesign.
<data-sources>
<oda-data-source extensionID="org.eclipse.birt.report.data.oda.jdbc"
name="e-forms xxx00099t11" id="735">
<property
name="odaDriverClass">com.microsoft.sqlserver.jdbc.SQLServerDriver
</property>
<property name="odaURL">jdbc:sqlserver://xxx00099t11</property>
<property name="odaUser">myUserid</property>
<encrypted-property name="odaPassword"
encryptionID="base64">yZWFkZ=
</encrypted-property>
</oda-data-source>
I would rather have websphere 6.1 manage the driver location. How do I do this?
Skip
<data-sources>
<oda-data-source extensionID="org.eclipse.birt.report.data.oda.jdbc"
name="e-forms xxx00099t11" id="735">
<property
name="odaDriverClass">com.microsoft.sqlserver.jdbc.SQLServerDriver
</property>
<property name="odaURL">jdbc:sqlserver://xxx00099t11</property>
<property name="odaUser">myUserid</property>
<encrypted-property name="odaPassword"
encryptionID="base64">yZWFkZ=
</encrypted-property>
</oda-data-source>
I would rather have websphere 6.1 manage the driver location. How do I do this?
Skip
0
Comments
-
Hi Skip,
Instead of hardcoding the location of the JDBC driver info, you can pass in a JNDI URL and BIRT will use the connection from your JNDI connection pool. You can also use the property binding tab in the data source to modify the connection info at runtime using parameters.Warning No formatter is installed for the format ipb0
Categories
- All Categories
- 111 Developer Announcements
- 49 Articles
- 103 General Questions
- 123 IM Services
- 40 OpenText Hackathon
- 31 Developer Tools
- 20.6K Analytics
- 4.1K AppWorks
- 8.9K Extended ECM
- 897 Cloud Fax and Notifications
- 77 Digital Asset Management
- 9.3K Documentum
- 29 eDOCS
- 123 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 1 XM Fax