Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "BPS50"
(→Web Services ODA Data Source Specification) |
|||
| Line 62: | Line 62: | ||
The following ODA public connection properties are exposed by this driver. The values of these public properties can be bound to report-scope Javascript expressions by using the property binding feature of BIRT reports. | The following ODA public connection properties are exposed by this driver. The values of these public properties can be bound to report-scope Javascript expressions by using the property binding feature of BIRT reports. | ||
| − | {| border="1" cellspacing="0" cellpadding="5" align=" | + | {| border="1" cellspacing="0" cellpadding="5" align="center" |
! Property Name | ! Property Name | ||
! Display Name | ! Display Name | ||
| Line 78: | Line 78: | ||
| Connection Timeout (in seconds) | | Connection Timeout (in seconds) | ||
| Number of seconds allowed for establishing a connection. Default value is 60 if it is not defined. | | Number of seconds allowed for establishing a connection. Default value is 60 if it is not defined. | ||
| + | |- | ||
|} | |} | ||
| + | |||
==Web Services ODA Data Set Specification== | ==Web Services ODA Data Set Specification== | ||
Revision as of 21:18, 31 January 2007
Contents
Web Services Data Source
This project aims to provide Web Services Data Source ODA implementation for BIRT
Specification Leads
Gary Xue, Actuate Corp.
Lin Zhu, Actuate Corp.
Description
The BIRT Web Services Data Source is an ODA extension that enables BIRT (and other Eclipse DTP/ODA enabled application) to query SOAP-based web services and use the query response as a source of reporting data.
Revision History
2007-1-31 [Gary Xue]: Initial draft
Introduction
The BIRT Web Services Data Source is an ODA extension that enables BIRT (and other Eclipse DTP/ODA enabled application) to query SOAP-based web services and use the query response as a source of reporting data.
The Web Services ODA (WS-ODA) extension is built on top of the DTP/XML data source (XML-ODA). The WS-ODA driver reuses XML-ODA driver’s XML to relational data mapping facility to handle the tabular conversion (“flattening”) of SOAP response data. The WS-ODA driver therefore has a dependency on the XML-ODA driver.
Features and Requirements
WSDL Support
WSDL is the most common service description language for Web Services. The WS-ODA design-time driver understands WSDL, and can use information contained therein to help the user define the following properties required by the runtime driver: the soap endpoint, the soap request template (by reading the request message schema) and the XML-relational mapping (by using the response message schema).
This driver supports WSDL 1.1.
Data Set Parameter Support
The WS-ODA driver supports data set parameters. User-defined data set parameters may be created, and any part of the SOAP request may be bound to the runtime value of a data set parameter.
User Editable SOAP Request
Where the WSDL descriptor of a web service is not available, the user may directly enter the template SOAP request message. Data set parameters may be added to the SOAP request using special syntactic markers. The user may also modify the SOAP message template initially generated from WSDL.
Java Code as XML Source
Java classes that implements a number of driver-defined connection and query methods may be used as the source of the XML data. This is useful in the case where the user already has client code to process the web service request, or when the web service uses a connection or authentication scheme that’s not supported by the WS-ODA driver.
SOAP over HTTP Support
The WS-ODA driver has native support for web services that uses SOAP over HTTP. The full SOAP message, including SOAP headers of the request and response messages, can be accessed by the data source consumer.
Full Range of XML to Relational Mapping
The entire XML to relational mapping facility of the DTP/XML ODA driver, including its drag-and-drop mapping UI and its advanced XPath expression support, is available to the WS-ODA driver to map a SOAP response message to a tabular result set.
Web Services ODA Data Source Specification
Data Source Name and Identifier
The ODA Data Source for the Web Services ODA driver is named “Web Services Data Source”. The ODA data source identifier and the data source runtime driver plugin name is “org.eclipse.datatools.enablement.oda.ws”. The data source designer plugin name is “org.eclipse.datatools.enablement.oda.ws.ui”.
Data Source Public Properties
A Web Services Data Source defines properties for establishing a connection to a web services provider. The connection can be made by the driver via SOAP/HTTP, or through a user-provided Java class.
The following ODA public connection properties are exposed by this driver. The values of these public properties can be bound to report-scope Javascript expressions by using the property binding feature of BIRT reports.
| Property Name | Display Name | Description |
|---|---|---|
| soapEndPoint | SOAP End Point | A URL for the SOAP/HTTP endpoint that the driver should connect to. E.g., "http://www.classicmodelsinc.com:5670/products" |
| connectionClass | Connection Class Name | If this property is defined, connection is made through a user-provided Java class by this name. See Section 3.4 for specification of the custom connection class. |
| connectionTimeOut | Connection Timeout (in seconds) | Number of seconds allowed for establishing a connection. Default value is 60 if it is not defined. |