Data Services Developer's Guide : How To Create Physical Data Services Based on SQL Statements
This page last changed on Jan 09, 2008 by tkatz.
eDocs Home > BEA AquaLogic Data Services Platform 3.0 Documentation > Data Services Developer's Guide
|
Relational Type | Description |
---|---|
Tables and Views |
Displays all public tables and views in the selected data source. |
Stored Procedures |
Displays all public stored procedures in the selected data source. |
SQL Statement |
Allows creation of a SQL statement for extracting relational data from the data source. |
Database Function |
Allows creation of an XQuery function in a library data service based on build-in or custom database functions. |
You can build library data service functions based on SQL statements. The XQuery engine uses the statement to retrieve metadata which is, in turn, formulated into a function that can be used by other data services or made public.
After selecting the SQL Statement option the next page of the wizard allows you to enter a SELECT statement and any necessary parameters.
You can type or paste your SELECT statement into the SELECT statement box, indicating parameters with a question-mark symbol.
?
Using one of the ALDSP samples, the following SELECT statement can be used:
SELECT * FROM RTLCUSTOMER.CUSTOMER WHERE CUSTOMER_ID = ?
For the parameter field, you would need to select a data type. In this case, CHAR or VARCHAR.
![]() | Notes:
|
You can add SQL statement or stored procedure operations based on the same data source to an existing physical data service based a SQL statement.
![]() | Add an External Function to an Existing Physical Data Service |
![]() | This general topic applies to setting properties for all types of library data service functions. |
Use the Review New Data Service Operations page to:
![]() | In some cases this option may not be available. |
The root element, which is read only, is also displayed.
On the Review New Data Service(s) page you can set, confirm or, optionally, change suggested data service names depending on the type of physical data service you are creating.
The nominated name for a new data service is, wherever possible, the same as the source object name. In some cases, however, names are adjusted to conform with XML naming conventions.
![]() | XML Name Conversion Considerations |
Name conflicts occur when there is a data service of the same name present in the target directory. Name conflicts are highlighted in red.
There are several situations where you will need to change the name of your data service:
Data services always have the file extension:
.ds
![]() |
Document generated by Confluence on Jan 15, 2008 11:02 |