Application of the JDBC wrapper in IBM Infosphere Federation Server V9.7

Basic concepts of the federated database

The federated database is a special distributed data management system consisting of a set of data sources, where a DB2 database acts as a federated server, and operations on other data sources can be seen as being done on the server, And the operations of these data sources through the federated system do not affect their respective independence and integrity.

The federated database has the following characteristics:

Transparency: The underlying multiple data sources are transparent to the user, and all operations on these data sources are like those in an DB2 database.

Heterogeneity: to meet different data and data source requirements in an enterprise environment.

Extensibility: The federated database provides interfaces that enable flexible and seamless addition of new data sources through these interfaces, and federated databases can also support non relational data sources.

High performance: The federated database optimizes the operations performed, and the use of federated systems does not require certain methods to evaluate the query to achieve high performance.

With the help of the federated database, it is easier and more efficient to access multiple heterogeneous data sources.

Figure 1 is the schema for the DB2 federated database. As you can see, applications can use any of the supported interfaces (Odbc,jdbc,web service clients) to deal with federated servers. The federated server uses the wrapper module to deal with remote data sources.

Figure 1. Schema of the Federated database

As part of the interaction between the federated database and the data source, the wrapper plays an important role in building relationships with different data sources. A wrapper module is a shared library of entry points that are accessed by a class of data sources. Figure 2 shows the components of the wrapper module.

where the wrapper (wrapper) represents a type of remote data source, the server (servers) represents a specific database that uses a wrapper connection. A nickname represents a specific logical table in the server. Users (user) provide the information needed to authenticate from end users to a particular server, and the connection (Connection) represents a connection between the federated system and the remote database. Operation (Operation) encapsulates all the information required for operations that need to be performed at the remote database.

Figure 2. Composition of the wrapper module