Using Connection Pool Support

Re: Using Connection Pool Support

Please see https://bugs.eclipse.org/bugs/show_bug.cgi?id=131662#c7 for a
description of this JNDI feature.
It has been tested to work fine with WebLogic 8.1.

To setup BIRT report designer to be a remote client of a JNDI factory
service,
you may optionally setup a jndi.properties file in the
birt.report.data.oda.dbc/drivers subfolder.
For the WebLogic JNDI server environment, you may put the following
name-value property pair entries in the jndi.properties file:

java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://jndiServer:7001
java.naming.security.principal=myusername
java.naming.security.credentials=mypassword

where "jndiServer" is the machine name where the JNDI server is running,
"7001" is the port number that the domain server is listening.
"myusername" is the user name configured in the Weblogic domain server, and
"mypassword" is the password.

"weblogic.jndi.WLInitialContextFactory" is the Weblogic provided factory
class that knows how to talk to a Weblogic server. This factory class is in
"weblogic.jar" file, normally found in /weblogic81\server\lib
folder.
You need to manually add this jar in the Report Designer's classpath, so that
it can find it.

In BIRT, when you design an oda.jdbc data source, specify your JNDI Name
value in the "JNDI URL" property. You can also use property binding to map
it to a report parameter, which allows you to change the values used at
runtime.
The JNDI URL property value is the name you have configured in your JNDI
server's JDBC->"Data Source" object's JNDI Name.
The JDBC's Driver Class and URL properties are optional for Weblogic JNDI
service, since it supports client-side access from the report designer, and
thus no need to fall back to use a JDBC connection directly. You may also
want to leave the Username and Password properties with an empty value, which
would allow the JNDI service to use the java.naming.security.principal and
credentials values instead.