Create Physical Data Services from Relational Tables and Views
This page last changed on May 05, 2008.
Oracle Data Service Integrator Documentation > Data Services Developer's Guide How To Create Physical Data Services from Relational Tables and ViewsThe following topics describe how to create physical data services from relational tables and views:
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
Selecting SQL Table and View Objects for ImportTo create a physical data service based on a relational table or view:
A list of available database table and view SQL objects appears. Objects are grouped based on the relational data sources catalog and/or schema. In the example of an RTLCUSTOMER catalog, the ADDRESS and CUSTOMER tables both become physical data services.
Simply check the desired objects or their container, which will select all enclosed tables or views. Table and View Objects Selected for ImportIf you click on an individual object such as ADDRESS or CUSTOMER, information describing the database's primary key(s), column name, type and nullability appears. For example the CUSTOMER table contains a CUSTOMER_ID field of type VARCHAR. That column is not nullable, meaning that it must be supplied with any updates. Physical Data Service PropertiesFiltering SQL Objects Using SearchThe Search option available when creating a physical data service can be especially useful when:
%audit2003% The above search command retrieves all objects that contain the enclosed string. Using JDBC Syntax to Search SQL ObjectsYou can search through available SQL objects using standard JDBC wildcard syntax.
Another example: CUST%, PAY% entered in the Tables/Views field the above search string returns all tables and views starting with either CUST or PAY. Special Considerations When Searching Stored ProceduresIf no items are entered for a particular field, all matching items are retrieved. For example, if no filtering entry is made for the Procedure field, all stored procedures in the data object will be retrieved. Setting Properties for New Data Service OperationsEach new entity data service is created with a Read function that contains all the metadata elements identified during data service creation. It can be thought of as comparable to the following construct in the relational world: select * from <table> Use the Properties dialog to:
The root element, which is read-only, is also displayed.
Setting Properties for New Data Service FunctionsDefault Naming ConventionsThere are several default naming conventions associated with new data services:
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 Database-specific Catalog and Schema ConsiderationsDatabase vendors variously support database catalogs and schemas. Vendor Support for Catalog and Schema Objects
XML Name Conversion ConsiderationsWhen a source name is encountered that does not fit within XML naming conventions, default generated names are converted according to rules described by the SQLX standard. Generally speaking, an invalid XML name character is replaced by its hexadecimal escape sequence (having the form xUUUU). For additional details see section 9.1 of the W3C draft version of this standard: |
Document generated by Confluence on Jan 13, 2009 15:57 |