External BIRT Viewer for BMC Remedy

<div>
Hi.
I need to run Remedy WEB reports and custom reports made in BIRT Designer with arsys.oda driver datasources.
 
Right now I can create and run reports directly in BIRT 4.5 Designer. But I need to run them in BIRT Viewer. I tried one which is coming with BIRT Runtime package (WebViewerExample). Now, when I try to run report in viewer Im getting error in viewer log:
 
Unable to load or instantiate the custom ODA driver class. (com.bmc.arsys.oda.runtime.impl.ARDriver)
 
But I put all three jar files from midtier to WEB-INF\lib direcroty of viewer, and this is the only jar files that were needed by BIRT Designer to create and run reports with BMC Remedy datasources:
 
com.bmc.arsys.oda.designtime_8.1.0.build001.jar
com.bmc.arsys.oda.runtime_8.1.0.build001.jar
com.bmc.arsys.studio.api_8.1.0.build001.jar
 
Can anybody tell me, how to configure standalone BIRT Viewer to run Remedy WEB reports?
</div>

Find more posts tagged with

Comments

JFreeman

I do not have access to a BMC Remedy data source. However, I just tested with MySQL by creating a clean deployment without the MySQL driver and publishing a report that uses it. I get the same type of error about unable to load the driver. I then added the driver into the WEB-INF\lib directory of the deployment and after a restart of tomcat the report is running as expected.
 
Did you make sure to restart your web server after adding the oda jars?

Mike Chepaykin

Hi Jesse, thanx for your reply.
 
Sure I did restart Tomcat, twice.
 
Is there any difference in using jdbc and oda drivers by BIRT Viewer? Is there any difference in using data access drivers by Designer and Viewer? How can I turn on most verbose Viewer logs to see - why exactly Viewer cant find jar files in WEB-INF\lib directory?
 
I can share data access driver jars with you but you have to have BMC Remedy ARS server installed to use them. Do you?

JFreeman

I do not have access to a BMC Remedy installation.
 
The ODA needs to be in the class/build path which should be in the WEB-INF/lib directory.
Perhaps it is a dependency issue that is happening.
 
You can increase the log level in the web.xml for the viewer:
<pre class="_prettyXprint _lang-xml">
<context-param>
<param-name>BIRT_VIEWER_LOG_LEVEL</param-name>
<param-value>WARNING</param-value>
</context-param>
</pre>
I would change it to INFO or DEBUG and try again to see if you can get more detailed errors.

Mike Chepaykin

Hi Jesse.
 
Here is viewer log with log level ALL:
 
<a data-ipb='nomediaparse' href='https://drive.google.com/file/d/0B1LfLtGu413aM094WlliVGZvR0U/view?usp=sharing'>https://drive.google.com/file/d/0B1LfLtGu413aM094WlliVGZvR0U/view?usp=sharing</a>
 
Here is ODA driver jar file:
 
<a data-ipb='nomediaparse' href='https://drive.google.com/file/d/0B1LfLtGu413aVWhqcjB4TXFEY2s/view?usp=sharing'>https://drive.google.com/file/d/0B1LfLtGu413aVWhqcjB4TXFEY2s/view?usp=sharing</a>
 
Could it be a problem, that this jar has "nested" jar file with actual classes of the driver?

JFreeman

The nested JAR may be the source of the issue.
Can you extract the nested JAR into the WEB-INF/lib and see if you get a different result?