Eclipse Community Forums: BIRT » Best Practice of How to Manage reports from different Environments? Dev, QA and Prod?

Home » Archived » BIRT » Best Practice of How to Manage reports from different Environments? Dev, QA and Prod?

Best Practice of How to Manage reports from different Environments? Dev, QA and Prod? [message #1000375]

Mon, 14 January 2013 11:08

Eclipse User

Just curious how do you manage the DB connections of BIRT reports moving between different environments like DEV, QA and PROD?

We are trying to implement BIRT reports into our Java web applications, I am able to create reports and using the viewer to display reports in the browser. Just want to hear your suggestions that what is the best practice of handleing DB connections between different application server environments?

Your input is greatly appreciated!

Re: Best Practice of How to Manage reports from different Environments? Dev, QA and Prod? [message #1000383 is a reply to message #1000375]

Mon, 14 January 2013 11:19

Eclipse User

We use a report library (rptlibrary) approach. The rptlibrary file on a given application server folder holds the database connection for that environment. All production BIRT reports utilize the report library and inherit its database connection.

Previous Topic:	How does BIRT determine the jdbc resultset datatypes?
Next Topic:	Html reports without charts

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 25 05:51:35 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter