| Static Birt Reports [message #143247] |
Sun, 12 March 2006 06:40  |
Eclipse User |
|
|
|
Originally posted by: vksharma44.hotmail.com
I am querying a very large Data Set 5 Million rows and the report
generation is slow. Is there any way I can generate the report every
night and deploy it as a HTML so that end users always see the HTML and do
not have to run the report query and load the server.
|
|
|
|
| Re: Static Birt Reports [message #143838 is a reply to message #143247] |
Tue, 14 March 2006 22:42  |
| Eclipse User |
|
|
|
Originally posted by: mike.ourworld.com
Vik wrote:
> I am querying a very large Data Set 5 Million rows and the report
> generation is slow. Is there any way I can generate the report every
> night and deploy it as a HTML so that end users always see the HTML and do
> not have to run the report query and load the server.
Not sure if this is possible. Anyone.
|
|
|
|
| Re: Static Birt Reports [message #143968 is a reply to message #143247] |
Wed, 15 March 2006 14:36 |
| Eclipse User |
|
|
|
Originally posted by: b.noemailspam.nothere
You can use the Engine API RunAndRender task to generate your report as
an html file and drop it into a directory of your choice.
See the BIRT Report Engine API page.
http://www.eclipse.org/birt/phoenix/deploy/reportEngineAPI.p hp
You could then use cron or similar to start the report generation each
evening.
Vik wrote:
> I am querying a very large Data Set 5 Million rows and the report
> generation is slow. Is there any way I can generate the report every
> night and deploy it as a HTML so that end users always see the HTML and
> do not have to run the report query and load the server.
|
|
|
|
| Re: Static Birt Reports [message #144728 is a reply to message #144166] |
Thu, 16 March 2006 21:02 |
| Eclipse User |
|
|
|
Originally posted by: m.n.com
And see what is being done with Pentaho. www.pentaho.org
Paul Furbacher wrote:
> Vik wrote:
>
>> I am querying a very large Data Set 5 Million rows and the report
>> generation is slow. Is there any way I can generate the report every
>> night and deploy it as a HTML so that end users always see the HTML
>> and do not have to run the report query and load the server.
>
>
> [Another message in this thread describes something similar.]
>
>
> OpenSymphony's Quartz comes to mind. Set up a "job" in Quartz to
> do the report generation at a convenient hour (in the middle
> of the night). Set the output of the report to the expected
> location in your Web app's directories. BIRT's runtime engine
>
> http://www.eclipse.org/birt/phoenix/deploy/
>
> would crank out the report. Your code would update a "reports"
> table in your database with a new report entry.
>
> You choose your design: save the report to a blob in the "reports"
> table or save it to the file system. (I usually prefer the latter.
> That requires that I save the filename as part of each record in
> the "reports" table.)
>
> The Web page which provides links to daily reports would
> of course be dynamic -- i.e., your code should read the db table
> which maintains the link/filename information for each daily report
> and create the appropriate links.
>
> Quartz is here:
>
> http://www.opensymphony.com/quartz/
>
>
> Quartz tutorial:
>
> http://www.opensymphony.com/quartz/wikidocs/Cookbook.html
>
>
> Here's an O'Reilly article to get you started:
>
>
> http://www.onjava.com/pub/a/onjava/2006/03/01/job-scheduling -in-web-application.html
>
>
>
> And finally, do it in Spring:
>
> http://www.springframework.org/docs/reference/scheduling.htm l
>
>
> --
>
> Paul Furbacher
> http://www.teamb.com
|
|
|
Powered by
FUDForum. Page generated in 0.04561 seconds
] 
Search
Help
Register
Login
Home
