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; } } }

How to use the connection pool?

Allaj

When the Dataset is created, there is an option to specify the JNDI URL. However, the driver , the DB URL that includes the DB name, user ID and password are still required on that window, even though that server.xml ( for Tomcat for example) has this information. It is unclear how such an application ( report) can be installed in the production, while the user id and password are hardcoded in the DataSet set up ( which could be testing database userID and password). Is there any way to keep this information configurable? Why it doesn?t use this information from the server.xml?
Your help is very much appreciated.
thanks

Find more posts tagged with

Comments

Mega

I think you are misplacing things... 
A dataset uses a datasource 
 
Datasource is where you fill that info 
 
 
On my opinion the best solution was applied: 
BIRT looks for the JNDI resource, which is going to be found in your prod server and therefore use it. If it doesn't find that resource it uses the db url, user and password you provide to it (for local testing). 
 
<a class='bbc_url' href='http://wiki.eclipse.org/index.php/BIRT/FAQ/Data_Access#Q:_What_is_the_precedence_when_both_JDBC_URL_and_JNDI_name_are_specified.3F'>BIRT/FAQ/Data Access - Eclipsepedia</a>

Allaj

thanks for the tip.

I was just hoping that the tool would allow to test the JNDI connection. But because there is always another way of accessing the DB, you cannot really tell if the JNDI set up is working. Or may be there is a way?
thanks