This page last changed on Feb 26, 2008.
This topic describes mapping functions in data services to SQL objects.
A SQL Map enables you to publish data service functions as SQL objects (which are created when you specify the mapping). Using SQL Maps, you can expose data services modeled in ALDSP as relational data sources. This enables you to use reporting tools (such as Crystal Reports and Microsoft Access, among others), Java applications, and development tools (such as Data Tools Platform or SQL Explorer) to access information from data services using SQL queries (through a JDBC client).
As the following figure shows, source data can be consolidated, integrated, and transformed using ALDSP data services. The source data itself can come from disparate sources throughout the enterprise, including relational databases and web services, among others. Using SQL Maps you can, in turn, expose the data service operations as a relational data source accessible using SQL queries. This enables JDBC clients to access data consolidated through ALDSP.
SQL mappable data service functions can be thought of as relationally-compatible XQuery functions. Depending on their signature, you can publish such functions for use as SQL tables or stored procedures. The association between the function and the SQL object is defined at design time when creating a SQL map.
The following summarizes the types of data service functions you can publish as SQL tables or stored procedures:
You can map library data service database functions to functions, but not to SQL tables and stored procedures.
The following general conditions apply when exposing data service operations as relational data sources:
|Document generated by Confluence on Apr 28, 2008 15:57|