Skip navigation.
Downloads | Product Documentation | Support

Concepts Guide

# Architecture

This chapter describes the architecture of BEA AquaLogic Data Services Platform (DSP). The following topics are covered:

- WebLogic Platform and Data Services Platform
- Data Services Platform Architecture
- Data Services Platform Components

# WebLogic Platform and Data Services Platform

Data services can be developed as a Workshop application or as a project within another type of Workshop application, such as a portal, web application, or business process. The runtime platform for Data Services Platform is WebLogic Server. DSP can take full advantage of the services provided by WebLogic Server, such as scalability and clustering, and the full array of J2EE features and services. It operates seamlessly with other applications running in a WebLogic Server.

Client applications that want to use DSP services only need to establish an initial context to the WebLogic Server where DSP is deployed. The initial context, a JNDI mechanism for identifying a resource on a network, is similar to a database connection in that it identifies the location of a server and includes any required connection parameters, such as user names and passwords.

Once the initial context is established, the client can instantiate data services and use them to get and update information.

For complete information on BEA WebLogic Server, see WebLogic Server documentation at the following URL:

http://edocs.bea.com/wls/docs81/index.html

# Data Services Platform Architecture

As shown in Figure 2-1, DSP provides a data integration layer between data sources and data users.

The core of the Data Services Platform runtime component is the data processing engine. It is a distributed query processor that divides user requests into optimized sub-queries, which when possible are processed concurrently against the data sources. The core is supplemented by security and caching components and interfaces for acquiring and delivering information, as described further in the following section.

Figure 2-1 Data Services Platform Components Architecture

# Data Services Platform Components

As depicted in Figure 2-1, the components and features of DSP include:

- Data Processing Engine. The data processing engine is optimized for distributed data access to databases, Web services, and files.
- Cache. By caching frequently accessed data, you can improve response time and reduce load on back-end resources. For more information, see Performance and Caching.
- Security. In addition to taking advantage of security features of the underlying WebLogic server, DSP lets you set read and update permissions for functions. For more information, see Securing Enterprise Data.
- Client API. Application developers have several options for accessing data. The Service Data Objects API allows client applications to read and update the data through a typed or untyped interface. Query-oriented access is supported for XQuery through the ad hoc query mechanism. In addition, the DSP JDBC driver enables JDBC clients, including SQL tools, access the information served by DSP services.
- Data source API. DSP supports many data source types, including:

- Relational sources
- Web services
- XML files
- Delimited files
- Custom Java functions

- Data Services Platform Console. The DSP Console allows you to manage function caching and access, as well as internal server behavior such as thread usage and memory. It also gives usage statistics regarding data services.
- Design Tools. DSP includes tools for creating the data services layer, including tools for modeling and developing data services and creating XQuery functions. For more information, see Unifying Information with Data Services.