| db vs oda connectivity for reports [message #40213] |
Thu, 20 December 2007 22:54  |
 Cameron Taggart
Messages: 28
Registered: July 2009 |
Junior Member |
|
|
I've been trying to produce reports using BIRT and CR4E (Crystal Reports for Eclipse). Both BIRT and CR4E (as of 1.0.4)
support establishing database connections through the Data Tools Platform in Eclipse 3.3. I simply want to connect to a
Sybase ASA database via JDBC.
Ideal Use Case:
* Open up the Data Source Explorer
* Select the Data Source Type: JDBC Data Source
* Select JDBC Driver Name: Sybase
(see DbVisualizer's Driver Manager)
* Enter details: Name, Database URL, User Name, Password
* Then in BIRT & CR4E, I could use the data source, selecting it by name.
Current Situation with CR4E:
It appears to be using "org.eclipse.datatools.connectivity.db". In the Data Source Explorer, I right click on
"Databases" and select "New...". After creating a New Connect Profile, I can use it from CR4E. The *blocking* problem
I have right now is the lack of support from Data Source Explorer for getting column information for tables in Sybase
ASA databases.
Current Situation with BIRT:
It appears to be using "org.eclipse.birt.report.data.oda". I don't think it can use the data source connection that I
created above. One would think it should be able to. I haven't got this working yet, but I think I have to create a
"BIRT JDBC Data Source", then export the connection profile to an xml file somewhere on the file system (via an absolute
path), then in BIRT's Report Designer, I can create a "Data Source" by specifying the location of the file and
connection profile name in a couple of properties. It would be nice if only the Connection Profile name was needed.
Exporting stuff to a xml file somewhere on the file system seems completely unnecessary.
Why is the difference between the "db" and "oda" packages? Is that now a uniform way for defining JDBC data sources
within the Data Tools Platform?
I would really like to find a fix or work-a-round for the Sybase ASA issue. If any of the DTP folks from Sybase wish to
contact me directly, please do so.
cheers,
Cameron
|
|
|
| Re: db vs oda connectivity for reports [message #40276 is a reply to message #40213] |
Fri, 21 December 2007 01:37  |
Linda Chan
Messages: 845
Registered: July 2009 |
Senior Member |
|
|
Cameron,
>> Why is the difference between the "db" and "oda" packages? Is that now a
>> uniform way for defining JDBC data sources within the Data Tools
>> Platform?
In DTP, "db" provides JDBC-specific db connection and related SQL tools.
Whereas ODA is a generic data access framework for hetergenous data sources,
including RDBMS. BIRT uses ODA to encapsulate data access to hetergeneous
data sources, where adopters can customize and provide own ODA driver to
plug in their own data source.
For the upcoming Eclipse Ganymede release (DTP 1.6), we plan to provide an
ODA wrapper to the "db" connection profiles. See Bugzilla 204343
https://bugs.eclipse.org/bugs/show_bug.cgi?id=204343. With that feature, a
BIRT data source will be able to use a DTP DB connection profile directly.
>> It would be nice if only the Connection Profile name was needed.
>> Exporting stuff to a xml file somewhere on the file system seems
>> completely unnecessary.
Specifying a file path is useful for some adopters, like those who need to
deploy BIRT report generation in a backend server environment.
Separately, exporting specific connection profiles to a different file is an
optional feature. Alternatively, you can specify the file path in which all
the connection profiles created in DSE are persisted. It is in
<yourEclipseWorkspace> /.metadata/.plugins/org.eclipse.datatools.connectivity/Serve rProfiles.dat
..
>> find a fix or work-a-round for the Sybase ASA issue
This is a completely separate issue, and has to do with the scope of support
provided by its db-specific enablement component. You might want to search
Bugzilla for existing bugs reported in that area, or create a new one, and
describe your specific issue.
Linda
DTP ODA Component Lead
|
|
|
| Re: db vs oda connectivity for reports [message #589478 is a reply to message #40213] |
Fri, 21 December 2007 01:37 |
Linda Chan
Messages: 845
Registered: July 2009 |
Senior Member |
|
|
Cameron,
>> Why is the difference between the "db" and "oda" packages? Is that now a
>> uniform way for defining JDBC data sources within the Data Tools
>> Platform?
In DTP, "db" provides JDBC-specific db connection and related SQL tools.
Whereas ODA is a generic data access framework for hetergenous data sources,
including RDBMS. BIRT uses ODA to encapsulate data access to hetergeneous
data sources, where adopters can customize and provide own ODA driver to
plug in their own data source.
For the upcoming Eclipse Ganymede release (DTP 1.6), we plan to provide an
ODA wrapper to the "db" connection profiles. See Bugzilla 204343
https://bugs.eclipse.org/bugs/show_bug.cgi?id=204343 With that feature, a
BIRT data source will be able to use a DTP DB connection profile directly.
>> It would be nice if only the Connection Profile name was needed.
>> Exporting stuff to a xml file somewhere on the file system seems
>> completely unnecessary.
Specifying a file path is useful for some adopters, like those who need to
deploy BIRT report generation in a backend server environment.
Separately, exporting specific connection profiles to a different file is an
optional feature. Alternatively, you can specify the file path in which all
the connection profiles created in DSE are persisted. It is in
<yourEclipseWorkspace> /.metadata/.plugins/org.eclipse.datatools.connectivity/Serve rProfiles.dat
..
>> find a fix or work-a-round for the Sybase ASA issue
This is a completely separate issue, and has to do with the scope of support
provided by its db-specific enablement component. You might want to search
Bugzilla for existing bugs reported in that area, or create a new one, and
describe your specific issue.
Linda
DTP ODA Component Lead
|
|
|
Powered by
FUDForum. Page generated in 0.03039 seconds
] 
Search
Help
Register
Login
Home
