Where Test is the catalog and TestDataServices~MyFolder is the schema. Path from the DSP project folder up to the folder name of the data source separated by a ~ (tilde)įunction without parameters return type schema's elementsįunction with parameters return type schema's elementsįor example, if you have an application Test with a project TestDataServices, and CUSTOMERS.ds with a function getCustomers() under a folder MyFolder, the table getCustomers can be describes as: Test.TestDataServices~MyFolder.getCustomer The following table shows the equivalent terminology between the two. This means that Data Services Platform terminology and the terminology used when accessing data through the Data Services Platform JDBC driver, which provides access to a database, is different. The driver also contains the following DSP product libraries: wlclient.jar, ld-client.jar, Schemas_UNIFIED_Annotation.jar, jsr173_api.jar, and xbean.jar.ĭata Services Platform and JDBC Driver TerminologyĭSP views data retrieved from a database as comprised of data sources and functions.The Data Services Platform JDBC driver contains the following third party libraries: Xerces Java - 2.6.2 : xercesImpl.jar, xmlParserAPIs.jar, and ANTLR 2.7.4 : antlr.jar.Supports Data Services Platform with JDK 1.4.The Data Services Platform JDBC driver has the following features: Features of the Data Services Platform JDBC Driver To expose non-flat data services, you can create flat views to be used from the JDBC driver. (Parameterized flat data services are exposed as SQL stored procedures.) Because SQL provides a traditional, two-dimensional approach to data access (as opposed to the multiple level, hierarchical approach defined by XML), the Data Services Platform JDBC driver can only be used to access data through data services that have a flat data shape that is, the data service type cannot have nesting.Īlso, SQL tables do not have parameters therefore, the Data Services Platform JDBC driver only exposes non-parameterized flat data service functions as tables. There are several constraints associated with the Data Services Platform JDBC driver. Internally, DSP translates SQL queries into XQuery. From the point of view of the client, the DSP integration layer appears as a relational database, with each data service function comprising a table. The JDBC driver increases the flexibility of the DSP integration layer by enabling access from database visualization and reporting tools, such as Crystal Reports. The Data Services Platform JDBC driver enables JDBC and ODBC clients to access information available from data services. The JDBC driver is intended to enable SQL access to data services. Your configuration settings may affect performance.Ībout the Data Services Platform JDBC Driver Note: For data source and configuration pool information, refer to the WebLogic Administration Guide. Using Reporting Tools with the Data Services Platform ODBC-JDBC Driver.Connecting to Data Services Platform Client Applications Using the ODBC-JDBC Bridge from Non-Java Applications.Connecting to the JDBC Driver from a Java Application. Installing the Data Services Platform JDBC Driver with JDK 1.4x.About the Data Services Platform JDBC Driver.This chapter explains how to install and use the Data Services Platform JDBC driver. You can use the JDBC driver to execute SQL92 SELECT queries, or stored procedures over DSP applications. The driver implements the java.sql.* interface in JDK 1.4x to provide access to an DSP server through the JDBC interface. The BEA AquaLogic Data Services Platform (DSP) JDBC driver gives client applications a means to obtain JDBC access to the information made available by data services. Using the Data Services Platform JDBC Driver
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |