Skip to main content



      Home
Home » Archived » BIRT » Standalone report server in the road-map ??
Standalone report server in the road-map ?? [message #80836] Thu, 13 October 2005 23:00 Go to next message
Eclipse UserFriend
Hi Develop Team,

I am interested to know if the Standalone report server is there in the
BIRT development road-map. Its highly required for high volumn report
generation application. If its used in the application server, the
resources are limited, generally, the report generation is more resource
intensive compared to other application process, hence the neeed of
independant server to add resource as volumn incresses.

Regards,
Davis
Re: Standalone report server in the road-map ?? [message #81124 is a reply to message #80836] Fri, 14 October 2005 11:27 Go to previous messageGo to next message
Eclipse UserFriend
Davis,

I wanted BIRT to run closer to the database, and not on my application
server, so I just unzipped JBoss on my database server, threw in the birt
runtime war file, and was off and running. Has it been your experience that
BIRT has to be installed on the same server as the rest of your application?

--floor

"Davis" <davis_k_v@yahoo.com> wrote in message
news:80f7286cde9f629c2f1eada6b70f9a0e$1@www.eclipse.org...
> Hi Develop Team,
>
> I am interested to know if the Standalone report server is there in the
> BIRT development road-map. Its highly required for high volumn report
> generation application. If its used in the application server, the
> resources are limited, generally, the report generation is more resource
> intensive compared to other application process, hence the neeed of
> independant server to add resource as volumn incresses.
>
> Regards,
> Davis
>
Re: Standalone report server in the road-map ?? [message #81306 is a reply to message #81124] Sun, 16 October 2005 07:27 Go to previous messageGo to next message
Eclipse UserFriend
Hi Floor,

No, I want to run BIRT engine in a separate server different from the rest
of my applications, so that I can increase the resource as the volumn of
regeneration and concurrent users increases.

Regards,
Davis
Re: Standalone report server in the road-map ?? [message #81541 is a reply to message #81306] Mon, 17 October 2005 11:36 Go to previous messageGo to next message
Eclipse UserFriend
Cool, sounds like a good plan to me. All I'm saying is that you can already
install BIRT on any server you want. In other words, you can run the BIRT
engine in a seperate server different from the rest of your applications. I
guess there is no "BIRT Server Edition" where they just package it
differently so they can charge you a whole bunch more like commercial
applications do, but I guess I don't have a problem with that!

--floor

"Davis" <davis_k_v@yahoo.com> wrote in message
news:53f591ae9b5df9943ed79eb59a6088c6$1@www.eclipse.org...
> Hi Floor,
>
> No, I want to run BIRT engine in a separate server different from the rest
> of my applications, so that I can increase the resource as the volumn of
> regeneration and concurrent users increases.
>
> Regards,
> Davis
>
Re: Standalone report server in the road-map ?? [message #81776 is a reply to message #81541] Tue, 18 October 2005 07:29 Go to previous message
Eclipse UserFriend
Originally posted by: m.n.com

I believe floor is on the right track with this. I can see Actuate coming
out with a standalone server for this. At least first.

Anyway, there are so many ways this can be accomplished in Java and why it
so great to have BIRT (and Jasper... ). You can create a JINI service.
You can do what floor said - and use Web services or EJBs or RMI or
serialized objects over HTTP, .... You can use JMS. It really depends on
your needs and situation. So to create a server setup that meets
everyone's needs would be difficult.
Previous Topic:Image URI causes error
Next Topic:pdf - character problem
Goto Forum:
  


Current Time: Thu Jul 17 20:10:06 EDT 2025

Powered by FUDForum. Page generated in 0.40497 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top