Concepts Guide
|
 |
 |
|
 |
 |
This chapter describes the architecture of BEA Liquid Data for WebLogic. The following topics are covered:
Liquid 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 Liquid Data is WebLogic Server. Liquid Data 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 Liquid Data services only need to establish an initial context to the WebLogic Server where Liquid Data 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 the WebLogic Server documentation at the following URL:
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/index.html
As shown in Figure 2-1, Liquid Data provides a data integration layer between data sources and data users.
The core of the Liquid Data 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 Liquid Data Components Architecture
As depicted in Figure 2-1, the components and features of Liquid Data include:
|
|
|
