Home » Archived » BIRT » Loosing JDBC Connection Properties at Runtime
| Loosing JDBC Connection Properties at Runtime [message #547183] |
Thu, 15 July 2010 20:28  |
 Robert Aust
Messages: 17
Registered: July 2009 |
Junior Member |
|
|
Hi there,
I'm trying to setup BIRT 2.5.2 runtime inside my WebApp using the
EngineAPI [without Viewer]. I got the Plattform and Engine started OK
and now want to run a simple test report...and am running out of luck :
In my report a defined the datasource :
<data-sources>
<oda-data-source
extensionID="org.eclipse.birt.report.data.oda.jdbc" name="DS_AUAT" id="94">
<list-property name="privateDriverProperties">
<ex-property>
<name>contentBidiFormatStr</name>
<value>ILYNN</value>
</ex-property>
<ex-property>
<name>metadataBidiFormatStr</name>
<value>ILYNN</value>
</ex-property>
</list-property>
<property
name="odaDriverClass">oracle.jdbc.driver.OracleDriver</property >
<property
name="odaURL">jdbc:oracle:thin:@mucu9352.server.wesabc.net:1536:ebcrpegt </property>
<property name="odaUser">awgwtec</property>
<encrypted-property name="odaPassword"
encryptionID="base64">YXdnd3RlYw==</encrypted-property>
</oda-data-source>
</data-sources>
First, I had it in a library but to keep it simple, I put the datasource
plain into the report.
In local preview in Birt Designer the report runs perfectly with this
definition.
Running this report inside my WebApp fails, because it cannot open the
datasource.
I turned on logging in org.eclipse.birt.report.data.oda.jdbc.Connection
and it showed me, that somehow the properties are lost. It gives :
FINE: Connection.open(Properties). connProperties =
OdaPropertyConfigId=org.eclipse.birt.report.data.oda.jdbc_DS _AUAT;contentBidiFormatStr=ILYNN;metadataBidiFormatStr=ILYNN ;
Jul 15, 2010 10:04:37 PM
org.eclipse.birt.report.data.oda.jdbc.Connection close
FINE: Connection closed.
Jul 15, 2010 10:04:37 PM
org.eclipse.birt.report.data.oda.jdbc.JDBCException JDBCException
FINE: odajdbc.driver.DriverMissingProperties
Jul 15, 2010 10:04:37 PM
org.eclipse.birt.data.engine.odaconsumer.ConnectionManager openConnection
SEVERE: Unable to open connection.
It only prints those two Bidi [whatever that is?!] properties but
obviously does not get the other properties like Driver, URL, User,
Password.
Why are they getting lost?
Thanks to any advice.
Robert.
|
|
|
| Re: Loosing JDBC Connection Properties at Runtime [message #547375 is a reply to message #547183] |
Fri, 16 July 2010 13:42  |
|
Robert,
Do the sample db reports run?
Where do you have the oracle driver located (in the jdbc plugin's driver
folder)?
Jason
On 7/15/2010 4:30 PM, Robert Aust wrote:
>
> Hi there,
>
> I'm trying to setup BIRT 2.5.2 runtime inside my WebApp using the
> EngineAPI [without Viewer]. I got the Plattform and Engine started OK
> and now want to run a simple test report...and am running out of luck :
>
> In my report a defined the datasource :
>
> <data-sources>
> <oda-data-source extensionID="org.eclipse.birt.report.data.oda.jdbc"
> name="DS_AUAT" id="94">
> <list-property name="privateDriverProperties">
> <ex-property>
> <name>contentBidiFormatStr</name>
> <value>ILYNN</value>
> </ex-property>
> <ex-property>
> <name>metadataBidiFormatStr</name>
> <value>ILYNN</value>
> </ex-property>
> </list-property>
> <property name="odaDriverClass">oracle.jdbc.driver.OracleDriver</property >
> <property
> name="odaURL">jdbc:oracle:thin:@mucu9352.server.wesabc.net:1536:ebcrpegt </property>
>
> <property name="odaUser">awgwtec</property>
> <encrypted-property name="odaPassword"
> encryptionID="base64">YXdnd3RlYw==</encrypted-property>
> </oda-data-source>
> </data-sources>
>
> First, I had it in a library but to keep it simple, I put the datasource
> plain into the report.
>
> In local preview in Birt Designer the report runs perfectly with this
> definition.
> Running this report inside my WebApp fails, because it cannot open the
> datasource.
> I turned on logging in org.eclipse.birt.report.data.oda.jdbc.Connection
> and it showed me, that somehow the properties are lost. It gives :
>
> FINE: Connection.open(Properties). connProperties =
> OdaPropertyConfigId=org.eclipse.birt.report.data.oda.jdbc_DS _AUAT;contentBidiFormatStr=ILYNN;metadataBidiFormatStr=ILYNN ;
>
> Jul 15, 2010 10:04:37 PM
> org.eclipse.birt.report.data.oda.jdbc.Connection close
> FINE: Connection closed.
> Jul 15, 2010 10:04:37 PM
> org.eclipse.birt.report.data.oda.jdbc.JDBCException JDBCException
> FINE: odajdbc.driver.DriverMissingProperties
> Jul 15, 2010 10:04:37 PM
> org.eclipse.birt.data.engine.odaconsumer.ConnectionManager openConnection
> SEVERE: Unable to open connection.
>
> It only prints those two Bidi [whatever that is?!] properties but
> obviously does not get the other properties like Driver, URL, User,
> Password.
> Why are they getting lost?
>
> Thanks to any advice.
> Robert.
>
>
|
|
|
| Re: Loosing JDBC Connection Properties at Runtime [message #547395 is a reply to message #547375] |
Fri, 16 July 2010 15:14 |
Robert Aust
Messages: 17
Registered: July 2009 |
Junior Member |
|
|
Hi Jason,
good idea - I will try the sample db.
By now, I also think that it is a classloading problem, I've so far
tried several constellations:
My webapp runs inside a WebSphere 6.1 which provides a JNDI-DataSource
for my Oracle-Database [which the rest of the application uses] - so the
driver IS already in the classpath of the AppServer.
I have tried using this JNDI-Datasource in the report - no success.
I have tried setting the passIn-Connection [which I then obtained
beforehand from the DataSource and put inAppContext] - no success. [It
actually says the the connection is not alive - which I'm sure, it is!]
I also tried the PassInDriverPath to point to ojdbc14.jar - no success.
It always gives me some sort of Datasource/Driver-Error.
I had the ojdbc14.jar all the time in the runtime in
...plugins/org.eclipse.birt.report.data.oda.jdbc_2.5.2.v2010 0205
and I also had some "bundleentry.."-messages for it in the EngineLog.
For historical reasons I still had the ojdbc14.jar also in my
WEB-INF/lib of my war - which probably isn't needed.
Could that be the problem?
I just removed it and am preparing another test sequence ... I have 2
installations of my application [ear-File] - one with Classloader
PARENT_FIRST, one with PARENT_LAST - to see, if that makes a difference.
We'll see..
Robert
Am 16.07.2010 15:42, schrieb Jason Weathersby:
> Robert,
>
> Do the sample db reports run?
> Where do you have the oracle driver located (in the jdbc plugin's driver
> folder)?
>
> Jason
>
>
> On 7/15/2010 4:30 PM, Robert Aust wrote:
>>
>> Hi there,
>>
>> I'm trying to setup BIRT 2.5.2 runtime inside my WebApp using the
>> EngineAPI [without Viewer]. I got the Plattform and Engine started OK
>> and now want to run a simple test report...and am running out of luck :
>>
>> In my report a defined the datasource :
>>
>> <data-sources>
>> <oda-data-source extensionID="org.eclipse.birt.report.data.oda.jdbc"
>> name="DS_AUAT" id="94">
>> <list-property name="privateDriverProperties">
>> <ex-property>
>> <name>contentBidiFormatStr</name>
>> <value>ILYNN</value>
>> </ex-property>
>> <ex-property>
>> <name>metadataBidiFormatStr</name>
>> <value>ILYNN</value>
>> </ex-property>
>> </list-property>
>> <property
>> name="odaDriverClass">oracle.jdbc.driver.OracleDriver</property >
>> <property
>> name="odaURL">jdbc:oracle:thin:@mucu9352.server.wesabc.net:1536:ebcrpegt </property>
>>
>>
>> <property name="odaUser">awgwtec</property>
>> <encrypted-property name="odaPassword"
>> encryptionID="base64">YXdnd3RlYw==</encrypted-property>
>> </oda-data-source>
>> </data-sources>
>>
>> First, I had it in a library but to keep it simple, I put the datasource
>> plain into the report.
>>
>> In local preview in Birt Designer the report runs perfectly with this
>> definition.
>> Running this report inside my WebApp fails, because it cannot open the
>> datasource.
>> I turned on logging in org.eclipse.birt.report.data.oda.jdbc.Connection
>> and it showed me, that somehow the properties are lost. It gives :
>>
>> FINE: Connection.open(Properties). connProperties =
>> OdaPropertyConfigId=org.eclipse.birt.report.data.oda.jdbc_DS _AUAT;contentBidiFormatStr=ILYNN;metadataBidiFormatStr=ILYNN ;
>>
>>
>> Jul 15, 2010 10:04:37 PM
>> org.eclipse.birt.report.data.oda.jdbc.Connection close
>> FINE: Connection closed.
>> Jul 15, 2010 10:04:37 PM
>> org.eclipse.birt.report.data.oda.jdbc.JDBCException JDBCException
>> FINE: odajdbc.driver.DriverMissingProperties
>> Jul 15, 2010 10:04:37 PM
>> org.eclipse.birt.data.engine.odaconsumer.ConnectionManager openConnection
>> SEVERE: Unable to open connection.
>>
>> It only prints those two Bidi [whatever that is?!] properties but
>> obviously does not get the other properties like Driver, URL, User,
>> Password.
>> Why are they getting lost?
>>
>> Thanks to any advice.
>> Robert.
>>
>>
>
|
|
|
| Re: Loosing JDBC Connection Properties at Runtime [message #547407 is a reply to message #547395] |
Fri, 16 July 2010 16:18 |
Robert Aust
Messages: 17
Registered: July 2009 |
Junior Member |
|
|
Hi again,
Good news is : I got a simple report with SampleDB [select * from
products] to work as pdf.
Looks perfectly clean from the log :
FINE: *START*
Jul 16, 2010 5:45:11 PM
org.eclipse.birt.report.data.adapter.impl.ModelAdapter
WARNING: handle type: org.eclipse.birt.report.model.api.OdaDataSetHandle
Jul 16, 2010 5:45:11 PM org.eclipse.birt.report.data.oda.jdbc.Connection
open
FINE: Connection.open(Properties). connProperties =
odaDriverClass=org.eclipse.birt.report.data.oda.sampledb.Dri ver;odaURL=jdbc:classicmodels:sampledb;OdaPropertyConfigId=o rg.eclipse.birt.report.data.oda.jdbc_DS_SAMPLE;OdaConnProfil eName=;odaUser=ClassicModels;
Jul 16, 2010 5:45:11 PM org.eclipse.birt.report.data.oda.jdbc.Connection
close
FINE: Connection closed.
Jul 16, 2010 5:45:11 PM
org.eclipse.birt.report.data.oda.sampledb.SampledbPlugin
INFO: Sampledb plugin starts up. Current startCount=0
Jul 16, 2010 5:45:11 PM
org.eclipse.birt.report.data.oda.sampledb.SampledbPlugin
INFO: Creating Sampledb database at location
/tmp/BIRTSampleDB_1279295111415_270b270b
Jul 16, 2010 5:45:12 PM org.eclipse.birt.report.data.oda.jdbc.Connection
createStatement
FINE:
Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
Jul 16, 2010 5:45:12 PM org.eclipse.birt.report.data.oda.jdbc.Connection
close
FINE: Connection closed.
Jul 16, 2010 5:45:12 PM org.eclipse.birt.report.data.oda.jdbc.Connection
FINE: *END*
Bad news : My report against my Oracle-Database still doesn't work.
I have now removed ojdbc14.jar from the .war-file and from what I can
see, the log looks "quite" OK :
INFO: JDBCDriverManager: found JAR file drivers/ojdbc14.jar.
URL=bundleentry://7.fwk334042089/drivers/ojdbc14.jar
Jul 16, 2010 5:44:21 PM org.eclipse.birt.report.data.oda.jdbc.Connection
FINE: *START*
Jul 16, 2010 5:44:21 PM
org.eclipse.birt.report.data.adapter.impl.ModelAdapter
WARNING: handle type: org.eclipse.birt.report.model.api.OdaDataSetHandle
Jul 16, 2010 5:44:21 PM org.eclipse.birt.report.data.oda.jdbc.Connection
open
FINE: Connection.open(Properties). connProperties =
odaDriverClass=oracle.jdbc.driver.OracleDriver;odaURL=jdbc:o racle:thin:@mucu9352.server.westlb.net:1532:ebcrappt;OdaProp ertyConfigId=org.eclipse.birt.report.data.oda.jdbc_DS_UAT;od aPassword=***;odaUser=wgwtec;contentBidiFormatStr=ILYNN;meta dataBidiFormatStr=ILYNN;
Jul 16, 2010 5:44:21 PM org.eclipse.birt.report.data.oda.jdbc.Connection
close
FINE: Connection closed.
Jul 16, 2010 5:44:21 PM org.eclipse.birt.report.data.oda.jdbc.Connection
createStatement
FINE:
Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
Jul 16, 2010 5:44:21 PM org.eclipse.birt.report.data.oda.jdbc.Connection
createStatement
FINE:
Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
Jul 16, 2010 5:44:21 PM org.eclipse.birt.report.data.oda.jdbc.Connection
createStatement
FINE:
Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
Jul 16, 2010 5:44:21 PM org.eclipse.birt.report.data.oda.jdbc.Connection
createStatement
FINE:
Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
Jul 16, 2010 5:44:21 PM org.eclipse.birt.report.data.oda.jdbc.Connection
createStatement
FINE:
Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
Jul 16, 2010 5:44:21 PM org.eclipse.birt.report.data.oda.jdbc.Connection
close
FINE: Connection closed.
- it finds the jar-file and obviously loads the driver OK.
- the connection properties are OK now - but it still cannot execute the
query. Looks like the engine tries 5 times and then gives up.
The resulting pdf only contains static texts - no data.
It looks about the same, when I use a PassInConnection from the
WebSphere-DataSource :
FINE: *START*
Jul 16, 2010 5:56:05 PM
org.eclipse.birt.report.data.adapter.impl.ModelAdapter
WARNING: handle type: org.eclipse.birt.report.model.api.OdaDataSetHandle
Jul 16, 2010 5:56:05 PM org.eclipse.birt.report.data.oda.jdbc.Connection
open
FINE: com.ibm.ws.rsadapter.jdbc.WSJdbcConnection@23762376
Jul 16, 2010 5:56:05 PM org.eclipse.birt.report.data.oda.jdbc.Connection
createStatement
FINE:
Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
Jul 16, 2010 5:56:05 PM org.eclipse.birt.report.data.oda.jdbc.Connection
createStatement
FINE:
Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
Jul 16, 2010 5:56:05 PM org.eclipse.birt.report.data.oda.jdbc.Connection
createStatement
FINE:
Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
Jul 16, 2010 5:56:05 PM org.eclipse.birt.report.data.oda.jdbc.Connection
createStatement
FINE:
Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
Jul 16, 2010 5:56:05 PM org.eclipse.birt.report.data.oda.jdbc.Connection
createStatement
FINE:
Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
Jul 16, 2010 5:56:05 PM org.eclipse.birt.report.data.oda.jdbc.Connection
close
FINE: Connection closed.
Jul 16, 2010 5:56:05 PM org.eclipse.birt.report.data.oda.jdbc.Connection
FINE: *END*
It recognizes and opens the supplied connection, tries 5 times [without
giving some kind of error?!] and closes - and the report has no data.
Later,
Robert.
Am 16.07.2010 17:14, schrieb Robert Aust:
>
> Hi Jason,
>
> good idea - I will try the sample db.
> By now, I also think that it is a classloading problem, I've so far
> tried several constellations:
>
> My webapp runs inside a WebSphere 6.1 which provides a JNDI-DataSource
> for my Oracle-Database [which the rest of the application uses] - so the
> driver IS already in the classpath of the AppServer.
> I have tried using this JNDI-Datasource in the report - no success.
> I have tried setting the passIn-Connection [which I then obtained
> beforehand from the DataSource and put inAppContext] - no success. [It
> actually says the the connection is not alive - which I'm sure, it is!]
> I also tried the PassInDriverPath to point to ojdbc14.jar - no success.
> It always gives me some sort of Datasource/Driver-Error.
>
> I had the ojdbc14.jar all the time in the runtime in
> ..plugins/org.eclipse.birt.report.data.oda.jdbc_2.5.2.v20100 205
> and I also had some "bundleentry.."-messages for it in the EngineLog.
>
> For historical reasons I still had the ojdbc14.jar also in my
> WEB-INF/lib of my war - which probably isn't needed.
> Could that be the problem?
> I just removed it and am preparing another test sequence ... I have 2
> installations of my application [ear-File] - one with Classloader
> PARENT_FIRST, one with PARENT_LAST - to see, if that makes a difference.
>
> We'll see..
> Robert
>
>
>
>
>
> Am 16.07.2010 15:42, schrieb Jason Weathersby:
>> Robert,
>>
>> Do the sample db reports run?
>> Where do you have the oracle driver located (in the jdbc plugin's driver
>> folder)?
>>
>> Jason
>>
>>
>> On 7/15/2010 4:30 PM, Robert Aust wrote:
>>>
>>> Hi there,
>>>
>>> I'm trying to setup BIRT 2.5.2 runtime inside my WebApp using the
>>> EngineAPI [without Viewer]. I got the Plattform and Engine started OK
>>> and now want to run a simple test report...and am running out of luck :
>>>
>>> In my report a defined the datasource :
>>>
>>> <data-sources>
>>> <oda-data-source extensionID="org.eclipse.birt.report.data.oda.jdbc"
>>> name="DS_AUAT" id="94">
>>> <list-property name="privateDriverProperties">
>>> <ex-property>
>>> <name>contentBidiFormatStr</name>
>>> <value>ILYNN</value>
>>> </ex-property>
>>> <ex-property>
>>> <name>metadataBidiFormatStr</name>
>>> <value>ILYNN</value>
>>> </ex-property>
>>> </list-property>
>>> <property
>>> name="odaDriverClass">oracle.jdbc.driver.OracleDriver</property >
>>> <property
>>> name="odaURL">jdbc:oracle:thin:@mucu9352.server.wesabc.net:1536:ebcrpegt </property>
>>>
>>>
>>>
>>> <property name="odaUser">awgwtec</property>
>>> <encrypted-property name="odaPassword"
>>> encryptionID="base64">YXdnd3RlYw==</encrypted-property>
>>> </oda-data-source>
>>> </data-sources>
>>>
>>> First, I had it in a library but to keep it simple, I put the datasource
>>> plain into the report.
>>>
>>> In local preview in Birt Designer the report runs perfectly with this
>>> definition.
>>> Running this report inside my WebApp fails, because it cannot open the
>>> datasource.
>>> I turned on logging in org.eclipse.birt.report.data.oda.jdbc.Connection
>>> and it showed me, that somehow the properties are lost. It gives :
>>>
>>> FINE: Connection.open(Properties). connProperties =
>>> OdaPropertyConfigId=org.eclipse.birt.report.data.oda.jdbc_DS _AUAT;contentBidiFormatStr=ILYNN;metadataBidiFormatStr=ILYNN ;
>>>
>>>
>>>
>>> Jul 15, 2010 10:04:37 PM
>>> org.eclipse.birt.report.data.oda.jdbc.Connection close
>>> FINE: Connection closed.
>>> Jul 15, 2010 10:04:37 PM
>>> org.eclipse.birt.report.data.oda.jdbc.JDBCException JDBCException
>>> FINE: odajdbc.driver.DriverMissingProperties
>>> Jul 15, 2010 10:04:37 PM
>>> org.eclipse.birt.data.engine.odaconsumer.ConnectionManager
>>> openConnection
>>> SEVERE: Unable to open connection.
>>>
>>> It only prints those two Bidi [whatever that is?!] properties but
>>> obviously does not get the other properties like Driver, URL, User,
>>> Password.
>>> Why are they getting lost?
>>>
>>> Thanks to any advice.
>>> Robert.
>>>
>>>
>>
>
|
|
|
| Re: Loosing JDBC Connection Properties at Runtime .. solved [message #547425 is a reply to message #547407] |
Fri, 16 July 2010 17:52 |
Robert Aust
Messages: 17
Registered: July 2009 |
Junior Member |
|
|
Hello,
it finally works.
Afer a load of classload-problems with commons-logging, xml.. and
OracleDriver, I got the report running.
It seems, that it is OK to have the oracle driver loaded in WebSphere,
when it's needed for the datasource. But it is not allowed to be in
WEB-INF/lib of the .war-File, where BIRT-API is included.
After I removed that, the driver worked from the
...runtime/plugins-directory. Directly from the dataSource in the report
as well as with PassInConnection.
In the end there was a bug in my report with the columnbinding in grid.
It showed proper results in designer - but in runtime it did not.
That's why there were 5 statements in the logs below : I was using 5
fields from the query.
I'll have to look into that.
Thanks!
Robert
Am 16.07.2010 18:19, schrieb Robert Aust:
>
> Hi again,
>
> Good news is : I got a simple report with SampleDB [select * from
> products] to work as pdf.
> Looks perfectly clean from the log :
>
> FINE: *START*
> Jul 16, 2010 5:45:11 PM
> org.eclipse.birt.report.data.adapter.impl.ModelAdapter
> WARNING: handle type: org.eclipse.birt.report.model.api.OdaDataSetHandle
> Jul 16, 2010 5:45:11 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> open
> FINE: Connection.open(Properties). connProperties =
> odaDriverClass=org.eclipse.birt.report.data.oda.sampledb.Dri ver;odaURL=jdbc:classicmodels:sampledb;OdaPropertyConfigId=o rg.eclipse.birt.report.data.oda.jdbc_DS_SAMPLE;OdaConnProfil eName=;odaUser=ClassicModels;
>
> Jul 16, 2010 5:45:11 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> close
> FINE: Connection closed.
> Jul 16, 2010 5:45:11 PM
> org.eclipse.birt.report.data.oda.sampledb.SampledbPlugin
> INFO: Sampledb plugin starts up. Current startCount=0
> Jul 16, 2010 5:45:11 PM
> org.eclipse.birt.report.data.oda.sampledb.SampledbPlugin
> INFO: Creating Sampledb database at location
> /tmp/BIRTSampleDB_1279295111415_270b270b
> Jul 16, 2010 5:45:12 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> createStatement
> FINE:
> Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
>
> Jul 16, 2010 5:45:12 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> close
> FINE: Connection closed.
> Jul 16, 2010 5:45:12 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> FINE: *END*
>
> Bad news : My report against my Oracle-Database still doesn't work.
> I have now removed ojdbc14.jar from the .war-file and from what I can
> see, the log looks "quite" OK :
>
> INFO: JDBCDriverManager: found JAR file drivers/ojdbc14.jar.
> URL=bundleentry://7.fwk334042089/drivers/ojdbc14.jar
> Jul 16, 2010 5:44:21 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> FINE: *START*
> Jul 16, 2010 5:44:21 PM
> org.eclipse.birt.report.data.adapter.impl.ModelAdapter
> WARNING: handle type: org.eclipse.birt.report.model.api.OdaDataSetHandle
> Jul 16, 2010 5:44:21 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> open
> FINE: Connection.open(Properties). connProperties =
> odaDriverClass=oracle.jdbc.driver.OracleDriver;odaURL=jdbc:o racle:thin:@mucu9352.server.westlb.net:1532:ebcrappt;OdaProp ertyConfigId=org.eclipse.birt.report.data.oda.jdbc_DS_UAT;od aPassword=***;odaUser=wgwtec;contentBidiFormatStr=ILYNN;meta dataBidiFormatStr=ILYNN;
>
> Jul 16, 2010 5:44:21 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> close
> FINE: Connection closed.
> Jul 16, 2010 5:44:21 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> createStatement
> FINE:
> Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
>
> Jul 16, 2010 5:44:21 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> createStatement
> FINE:
> Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
>
> Jul 16, 2010 5:44:21 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> createStatement
> FINE:
> Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
>
> Jul 16, 2010 5:44:21 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> createStatement
> FINE:
> Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
>
> Jul 16, 2010 5:44:21 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> createStatement
> FINE:
> Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
>
> Jul 16, 2010 5:44:21 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> close
> FINE: Connection closed.
>
> - it finds the jar-file and obviously loads the driver OK.
> - the connection properties are OK now - but it still cannot execute the
> query. Looks like the engine tries 5 times and then gives up.
> The resulting pdf only contains static texts - no data.
>
> It looks about the same, when I use a PassInConnection from the
> WebSphere-DataSource :
> FINE: *START*
> Jul 16, 2010 5:56:05 PM
> org.eclipse.birt.report.data.adapter.impl.ModelAdapter
> WARNING: handle type: org.eclipse.birt.report.model.api.OdaDataSetHandle
> Jul 16, 2010 5:56:05 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> open
> FINE: com.ibm.ws.rsadapter.jdbc.WSJdbcConnection@23762376
> Jul 16, 2010 5:56:05 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> createStatement
> FINE:
> Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
>
> Jul 16, 2010 5:56:05 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> createStatement
> FINE:
> Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
>
> Jul 16, 2010 5:56:05 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> createStatement
> FINE:
> Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
>
> Jul 16, 2010 5:56:05 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> createStatement
> FINE:
> Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
>
> Jul 16, 2010 5:56:05 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> createStatement
> FINE:
> Connection.createStatement(org.eclipse.birt.report.data.oda. jdbc.JdbcSelectDataSet)
>
> Jul 16, 2010 5:56:05 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> close
> FINE: Connection closed.
> Jul 16, 2010 5:56:05 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> FINE: *END*
>
> It recognizes and opens the supplied connection, tries 5 times [without
> giving some kind of error?!] and closes - and the report has no data.
>
> Later,
> Robert.
>
>
> Am 16.07.2010 17:14, schrieb Robert Aust:
>>
>> Hi Jason,
>>
>> good idea - I will try the sample db.
>> By now, I also think that it is a classloading problem, I've so far
>> tried several constellations:
>>
>> My webapp runs inside a WebSphere 6.1 which provides a JNDI-DataSource
>> for my Oracle-Database [which the rest of the application uses] - so the
>> driver IS already in the classpath of the AppServer.
>> I have tried using this JNDI-Datasource in the report - no success.
>> I have tried setting the passIn-Connection [which I then obtained
>> beforehand from the DataSource and put inAppContext] - no success. [It
>> actually says the the connection is not alive - which I'm sure, it is!]
>> I also tried the PassInDriverPath to point to ojdbc14.jar - no success.
>> It always gives me some sort of Datasource/Driver-Error.
>>
>> I had the ojdbc14.jar all the time in the runtime in
>> ..plugins/org.eclipse.birt.report.data.oda.jdbc_2.5.2.v20100 205
>> and I also had some "bundleentry.."-messages for it in the EngineLog.
>>
>> For historical reasons I still had the ojdbc14.jar also in my
>> WEB-INF/lib of my war - which probably isn't needed.
>> Could that be the problem?
>> I just removed it and am preparing another test sequence ... I have 2
>> installations of my application [ear-File] - one with Classloader
>> PARENT_FIRST, one with PARENT_LAST - to see, if that makes a difference.
>>
>> We'll see..
>> Robert
>>
>>
>>
>>
>>
>> Am 16.07.2010 15:42, schrieb Jason Weathersby:
>>> Robert,
>>>
>>> Do the sample db reports run?
>>> Where do you have the oracle driver located (in the jdbc plugin's driver
>>> folder)?
>>>
>>> Jason
>>>
>>>
>>> On 7/15/2010 4:30 PM, Robert Aust wrote:
>>>>
>>>> Hi there,
>>>>
>>>> I'm trying to setup BIRT 2.5.2 runtime inside my WebApp using the
>>>> EngineAPI [without Viewer]. I got the Plattform and Engine started OK
>>>> and now want to run a simple test report...and am running out of luck :
>>>>
>>>> In my report a defined the datasource :
>>>>
>>>> <data-sources>
>>>> <oda-data-source extensionID="org.eclipse.birt.report.data.oda.jdbc"
>>>> name="DS_AUAT" id="94">
>>>> <list-property name="privateDriverProperties">
>>>> <ex-property>
>>>> <name>contentBidiFormatStr</name>
>>>> <value>ILYNN</value>
>>>> </ex-property>
>>>> <ex-property>
>>>> <name>metadataBidiFormatStr</name>
>>>> <value>ILYNN</value>
>>>> </ex-property>
>>>> </list-property>
>>>> <property
>>>> name="odaDriverClass">oracle.jdbc.driver.OracleDriver</property >
>>>> <property
>>>> name="odaURL">jdbc:oracle:thin:@mucu9352.server.wesabc.net:1536:ebcrpegt </property>
>>>>
>>>>
>>>>
>>>>
>>>> <property name="odaUser">awgwtec</property>
>>>> <encrypted-property name="odaPassword"
>>>> encryptionID="base64">YXdnd3RlYw==</encrypted-property>
>>>> </oda-data-source>
>>>> </data-sources>
>>>>
>>>> First, I had it in a library but to keep it simple, I put the
>>>> datasource
>>>> plain into the report.
>>>>
>>>> In local preview in Birt Designer the report runs perfectly with this
>>>> definition.
>>>> Running this report inside my WebApp fails, because it cannot open the
>>>> datasource.
>>>> I turned on logging in org.eclipse.birt.report.data.oda.jdbc.Connection
>>>> and it showed me, that somehow the properties are lost. It gives :
>>>>
>>>> FINE: Connection.open(Properties). connProperties =
>>>> OdaPropertyConfigId=org.eclipse.birt.report.data.oda.jdbc_DS _AUAT;contentBidiFormatStr=ILYNN;metadataBidiFormatStr=ILYNN ;
>>>>
>>>>
>>>>
>>>>
>>>> Jul 15, 2010 10:04:37 PM
>>>> org.eclipse.birt.report.data.oda.jdbc.Connection close
>>>> FINE: Connection closed.
>>>> Jul 15, 2010 10:04:37 PM
>>>> org.eclipse.birt.report.data.oda.jdbc.JDBCException JDBCException
>>>> FINE: odajdbc.driver.DriverMissingProperties
>>>> Jul 15, 2010 10:04:37 PM
>>>> org.eclipse.birt.data.engine.odaconsumer.ConnectionManager
>>>> openConnection
>>>> SEVERE: Unable to open connection.
>>>>
>>>> It only prints those two Bidi [whatever that is?!] properties but
>>>> obviously does not get the other properties like Driver, URL, User,
>>>> Password.
>>>> Why are they getting lost?
>>>>
>>>> Thanks to any advice.
>>>> Robert.
>>>>
>>>>
>>>
>>
>
|
|
|
Goto Forum:
Current Time: Thu Apr 25 07:33:22 GMT 2024
Powered by FUDForum. Page generated in 0.03786 seconds |
] 
Search
Help
Register
Login
Home
