nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Lib Dynamic Data Source from Resource Property

mldickey

I'm using Eclipse-Helios 20100617-1415 and BIRT 2.6.1. I've also tried Ganymede and BIRT 2.3.1.

I have what I thought would be among the simplest of cases for dynamically providing the db url, user, and password from a resource property file. But it isn't working.

In my local.properties file I have something like:
database_url=jdbc:oracle:thin:@localhost:1521:xe
database_user=dbuser
database_pass=u8sjsmd8YY==

And from the library file, I have a data source defined on the Property Binding screen as:
JDBC Driver Class: oracle.jdbc.OracleDriver
JDBC Driver URL: params["database_url"]
User Name: params["database_user"]
Password: params["database_pass"]

It works fine if I create a report and use the library if I define the url, user, and password explicitly.

Thank you for your help.

Find more posts tagged with

Comments

mldickey

Blast, I see that I made assumptions about the binding of local property values from resource files to "params." But I've not yet been able to work out grabbing the resource file values and using them for data source connectivity. And I see that many others have struggled too.

Does anyone have that working?

mldickey

I did create a connection profile in a library, and I was able to use that in a report. But let me step back and give our "requirements" or desires:

~ We do not want to modify the report file or the library at all across various environments (local dev workstation, development server, QA server, production server).

~ We want the library to be able to "look up" or otherwise determine which environment it's in, and use appropriate connect info to the DB.

This last point is the sticky one for now. There are a couple ways of doing that - but we prefer to define the connect info directly in a prop file (or similar). Prop files are plain text, we can have them setup differently in each environment, and we can edit them very easily without bringing up an IDE or engaging in other cumbersome deployment activities.

Relatedly, we prefer NOT to have a single property "env=prod" wherein there is code in the library to check for "env=prod" and then set attributes dynamically within. This places too much configuration information within a file that must be tested and redeployed should anything change (such as DB server name, port, etc.).

Basically, we want to optimize for simplicity in configuration as our reports migrate through the deployment cycles on their way to live/production service.

It does not seem that connection profiles meet that kind of simplicity (the data file is not plain text) - but I may be (as I've done before!) missing something. Smile

Thank you again and humbly request for any further help and direction.

kmelby

Resurrecting this thread...

All the requirements desired in the above post are exactly what I'm currently looking for. Has anyone been able to figure out a way to do this?