Query Builder with Birt [message #252346] |
Tue, 14 August 2007 09:35 |
Eclipse User |
|
|
|
Originally posted by: jagbalan.yahoo.com
Thanks Spunk. I actually was talking about dynamic report generation,
where the end user can relate some metadata that should be converted to a
query.
For example he will see Customer & Company entity. When he drags customer
name and company name to right, we should create a query like below
"select cust.custname,comp.compname from custtab cust, comptab comp where
cust.compid=comp.compid". This query will be saved and later used during
business processes like salary settlement. The design engine you are
talking about is a developer api or support end user usuable components
like jsp / applets?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
1. You can use the Design Engine (DE) API to create reports.
2. I'm not sure what you want to achieve, but when you have an existing
report design then you can use the DE API to read the SQL query text which
is used for a data set - when you create a report you can use the DE API
to
set the SQL query text.
3. XML, schema at http://www.eclipse.org/birt/2005/design (not sure
whether
it is up-to-date)
4. You can use the Report Engine API to execute reports.
5. Can you please give an example what you are trying to achieve?
Please check out the following links:
http://www.eclipse.org/birt/phoenix/deploy/designEngineAPI.p hp
http://www.eclipse.org/birt/phoenix/deploy/reportEngineAPI.p hp
Spunk
|
|
|
Re: Query Builder with Birt [message #252433 is a reply to message #252346] |
Tue, 14 August 2007 22:08 |
Der Spunk Messages: 58 Registered: July 2009 |
Member |
|
|
Jagadeesh,
BIRT does not provide such a kind of end user abstraction layer like a
Cognos Catalog/Package or BO Universe. The Design Engine API is a developer
API - you can do everything with the API what you can do with the Report
Designer and that means you have to provide the SQL statement yourself.
Sometime ago a "Web Based Report Designer" (WRD) subproject was announced
that may have met your requirements, but this subproject seems to be
abandoned - at least it is still mentioned on this old BIRT web page
http://www.eclipse.org/birt/project/ : "... The goal of this project is to
provide an accessible and easy-to-use report design environment to meet the
needs for ad hoc report creation by business users within any java
application."
Therefore you have to make such an abstraction layer yourself (or buy one
....) .
A simplified version of such an abstraction layer, i can think of, would be
a collection of predefined datasets in a library from which the user can
choose from, e.g. datasets with names like "Customer data only", "Customer
with Company data", the user chooses one of them and the columns he wants to
see in the report. Then you "only" need to put a table with data bindings to
the selected columns of the selected dataset into the report via the DE API.
The high-end version would be something like an Eclipse Plugin, based on
EMF/GEF/DTP to design the entities and relationships and to describe the
structure that the end user will work with (catalog/package/universe), and a
SQL generator that creates the "hopefully correct ;-)" SQL query based on
the selection of the end user.
Spunk
"Jagadeesh" <jagbalan@yahoo.com> schrieb im Newsbeitrag
news:ad28a79faa1d0844c4a9a1f9f01fb2ea$1@www.eclipse.org...
> Thanks Spunk. I actually was talking about dynamic report generation,
> where the end user can relate some metadata that should be converted to a
> query. For example he will see Customer & Company entity. When he drags
> customer name and company name to right, we should create a query like
> below "select cust.custname,comp.compname from custtab cust, comptab comp
> where cust.compid=comp.compid". This query will be saved and later used
> during business processes like salary settlement. The design engine you
> are talking about is a developer api or support end user usuable
> components like jsp / applets?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >
> 1. You can use the Design Engine (DE) API to create reports.
> 2. I'm not sure what you want to achieve, but when you have an existing
> report design then you can use the DE API to read the SQL query text which
> is used for a data set - when you create a report you can use the DE API
> to set the SQL query text.
> 3. XML, schema at http://www.eclipse.org/birt/2005/design (not sure
> whether it is up-to-date)
> 4. You can use the Report Engine API to execute reports.
> 5. Can you please give an example what you are trying to achieve?
>
> Please check out the following links:
> http://www.eclipse.org/birt/phoenix/deploy/designEngineAPI.p hp
> http://www.eclipse.org/birt/phoenix/deploy/reportEngineAPI.p hp
>
> Spunk
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03023 seconds