Jump to: navigation, search

Difference between revisions of "Cassandra Scripted Data Source (BIRT)"

 
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{Backlink|Report Developer Examples (BIRT)}}  
 
{{Backlink|Report Developer Examples (BIRT)}}  
BIRT Designer and runtime deployment packages now support scripted data source connections for use with Cassandra distributions, including:
+
BIRT 4.2.2 and later supports scripted data source connections for use with Cassandra distributions, including:
 
*Apache Cassandra
 
*Apache Cassandra
 
*Datastax Cassandra Community
 
*Datastax Cassandra Community
 
*Datastax Cassandra Enterprise
 
*Datastax Cassandra Enterprise
BIRT connects to and queries a Cassandra data source using the Hector API. You must install the Hector client library JAR files in the appropriate folder. You can download the JAR files from [https://github.com/hector-client/hector/downloads here].
+
BIRT connects to and queries a Cassandra data source using the Hector API. You must copy the Hector client library JAR files to the appropriate folders for both BIRT Designer and the BIRT runtime deployment application. You can download the JAR files from [https://github.com/hector-client/hector/downloads here].
== Installing the Hector client library JAR files for use with BIRT Designer ==
+
== Copying the Hector client library JAR files for use with BIRT Designer ==
org.eclipse.birt.me.prettyprint.hector_<version>/lib folder, and then restart BIRT Designer or the runtime deployment application.
+
Copy the JAR files to the org.eclipse.birt.me.prettyprint.hector_<version>/lib/ folder and restart BIRT Designer. If you do not copy the JAR files, the following error message appears when you select Cassandra Scripted Data Source in the New Data Source wizard:<br><br>
== Installing the Hector client library JAR files for use with the BIRT runtime deployment application ==  
+
Unable to find Hector client library jars to support Cassandra Scripted Data Source
This example was built and tested with BIRT 2.2 RC0.
+
== Copying the Hector client library JAR files for use with a BIRT runtime deployment application ==  
== Example Files==
+
For OSGi BIRT runtime deployment, copy the JAR files to the org.eclipse.birt.me.prettyprint.hector_<version>/lib/ folder and restart the runtime deployment application. If the "Servlet ViewerServlet is not available" error message appears, copy the org.apache.commons.logging_<version>.jar (available in WEB-INF/platform/plugins/) to the birt/WEB-INF/lib/ folder. This is a known issue with tomcat-6 that is independent of Cassandra scripted data sources. <br>
[https://bugs.eclipse.org/bugs/attachment.cgi?id=97678 Example Report Zipped]
+
For non-OSGi BIRT runtime deployment, copy the JAR files to the <installation_folder>/webapps/birt_runtime/scriptlib/ folder and restart the runtime deployment application.<br>
 
+
If you do not copy the JAR files, the following error message appears at runtime:<br><br>
== Description==
+
Caused by: org.eclipse.birt.core.exception.CoreException: Error evaluating Javascript expression. Script engine error
This example accesses a city locator from zip code web service located here:
+
http://www.webservicex.net/uszip.asmx?WSDL.
+
 
+
The above URL is entered in the data source WSDL URL property.  The data set is set to the  
+
getInfoByZIP Method. The default SOAP request template generated by the driver supplies one data set parameter for the
+
zip code. It is important to remember any part of the SOAP request can be modified. To link a portion of the
+
SOAP request to a data set parameter use the
+
&?symbol?&
+
syntax, where symbol is the name of the data set parameter.  In the data set editor this parameter can be linked to a
+
report parameter. In this example symbol is linked to the report parameter zipcode.
+
 
+
Once the response is returned, it is parsed just like the XML data source using XPath syntax.
+
 
+
== Comments ==
+
Please enter comments below by selecting the edit icon to the right.
+
You will need a Bugzilla account to add comments.
+
----
+
 
+
It appears that the web service that this report uses is no longer available.
+
 
+
___
+
 
+
Changed the report to use a new web service.
+
 
[[Category:BIRT]]
 
[[Category:BIRT]]
 
[[Category:BIRT Example]]
 
[[Category:BIRT Example]]
 
[[Category:BIRT Example Report]]
 
[[Category:BIRT Example Report]]

Latest revision as of 16:19, 19 February 2013

< To: Report Developer Examples (BIRT)
BIRT 4.2.2 and later supports scripted data source connections for use with Cassandra distributions, including:

  • Apache Cassandra
  • Datastax Cassandra Community
  • Datastax Cassandra Enterprise

BIRT connects to and queries a Cassandra data source using the Hector API. You must copy the Hector client library JAR files to the appropriate folders for both BIRT Designer and the BIRT runtime deployment application. You can download the JAR files from here.

Copying the Hector client library JAR files for use with BIRT Designer

Copy the JAR files to the org.eclipse.birt.me.prettyprint.hector_<version>/lib/ folder and restart BIRT Designer. If you do not copy the JAR files, the following error message appears when you select Cassandra Scripted Data Source in the New Data Source wizard:

Unable to find Hector client library jars to support Cassandra Scripted Data Source

Copying the Hector client library JAR files for use with a BIRT runtime deployment application

For OSGi BIRT runtime deployment, copy the JAR files to the org.eclipse.birt.me.prettyprint.hector_<version>/lib/ folder and restart the runtime deployment application. If the "Servlet ViewerServlet is not available" error message appears, copy the org.apache.commons.logging_<version>.jar (available in WEB-INF/platform/plugins/) to the birt/WEB-INF/lib/ folder. This is a known issue with tomcat-6 that is independent of Cassandra scripted data sources.
For non-OSGi BIRT runtime deployment, copy the JAR files to the <installation_folder>/webapps/birt_runtime/scriptlib/ folder and restart the runtime deployment application.
If you do not copy the JAR files, the following error message appears at runtime:

Caused by: org.eclipse.birt.core.exception.CoreException: Error evaluating Javascript expression. Script engine error