This page last changed on Mar 13, 2008.
eDocs Home > BEA AquaLogic Data Services Platform Documentation > Data Services Developer's Guide > Contents How To Create Physical Data Services Based on SQL StatementsThe following topics cover the actions necessary to create physical data services from SQL statements: Setting Up the Physical Data Service Creation WizardPhysical data services are created using a wizard. Physical Data Service Creation WizardStarting the WizardTo start the physical data service creation wizard:
Creating a New Physical Data ServiceSetting Up the Import Wizard for Relational ObjectsWhen importing a relational object available options include the ability to:
Types of available relational data sources
Entering a SQL StatementYou 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. SQL Statement Entry DialogYou 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.
Adding Operations to an Existing Data ServiceYou can add SQL statement or stored procedure operations based on the same data source to an existing physical data service based a SQL statement.
Adding a Stored Procedure or SQL Statement to a Data ServiceSetting Properties for New Library Functions
Use the Review New Data Service Operations page to:
The root element, which is read only, is also displayed. Verifying Data Service CompositionOn 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. Default Physical Data Service NamesThe 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.
About Automatic Data Service Name ChangesName 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 Apr 28, 2008 15:54 |