Common Client Interface
Using the exposed Common Client Interface, the application server can effectively incorporate the services of the Resource Adapter into its operations while insulating the applications themselves from the underlying implementation of the EIS
What is the relevance of the CCI to EIS's and EAI
The Connector Architecture provides a common client interface for different type of EIS's.

This interface, called the Common Client interface (CCI), is an application contract (a set of API's) between application components and the resource adapter.

Because a resource adapter is specific to its EIS there is typically a different resource adapter for each type of database or EIS.

The CCI provides an API that is common across heterogeneous EIS's. As a result, Entrprise Application Integration (EAI) vendors do not have to adapt their products to each specific EIS client API.
An EAI (Enterprise Application Integration) vendor can use the CCI as a standard way to plug in resource adapters for heterogenous EIS's

A vendor builds an application integration framework using the CCI, and this framework provides a higher level functionality to the underlying EIS's.

The CCI client API relies on simple remote function calls to provide access the EIS data. It provides sufficient functionality that applications can create and manage connections to an EIS, execute am interaction, and access data records.

CCI Overview
The Connector Architecure CCI defines a set of interfaces and classes whose methods allow a client to perform typical EIS connection, remote function execution, and data access operations. These interfaces and classes, which are all found in the javx.resource.cci package, divide functionality into four categories
  • Conection
  • Interaction
  • Data
  • Metadata
Clients, or application components, use the Connection Interfaces to represent connections, specifically a connection factory and an application-level connection.

Intraction Interfaces enable a component to execute or drive an interaction with an EIS instance.

Application components use the Data Interfaces to represent the data structures that are involved in an interaction with an EIS instance.

The metadata interfaces provide meta information about a resource adapter implementation and an EIS connection.
To access an EIS from a J2EE client, you need to first establish and define a connection to the EIS.

The term EIS refers to a data store or database, or other mechanism that stores data on an enterprise scale. For simplicity, we use the term database to refer to any kind of data store.

For each operation you want to perform on the data store or database, an interaction is established and defined, together with the creation of a record for transferring data into or out of the database.

Rather than directly access the EIS, clients use the CCI to interact with a resource adapter, which is
a software component provided by an EIS vendor for a specific EIS.

By designing resource adapters that comply with the specifications of the Connector architecture, EIS vendors make it possible for developers to write transportable code for accessing EISs without having to know the underlying semantics of the resource manager that handles the EIS.

Copyright 1997-2006  The InterNet Agency.    All rights reserved.
We welcome your comments to the Webmaster