UNIT- III

CHAPTER IN BOOK- 11
DAY- 24

-K. Indhu
 SYLLABUS COVERED HERE
• Multidatabase Systems
• Designing Access layer classes

17-MAR-14 K. INDHU 2
 GOALS
1. Multidatabase Systems
i. Federated Multi-Database Systems
ii. Pictorial Representation of MDBS
iii. Characteristics of MDBS
2. Open Database Connectivity
3. Advantages of Open Database Connectivity
4. Pictorial Representation of ODBC

5. Designing Access Layer Classes

i. Duties of Access Layer
ii. Two Functionalities/Tasks performed by Access Layer
iii. Advantages of Access Layer
iv. Diagrammatic Representation of Access Layer
v. The Process

17-MAR-14 K. INDHU 3
 MULTI-DATABASE SYSTEMS
• A different approach for integrating-
– Object-Oriented Data Environment
– (with)
– Relational Data Environments
– (is)-> Multi-database Systems,
– (or)
– Heterogeneous Database Systems.

• Multi-Database Systems facilitate the Integration of

heterogeneous databases and other information sources.

• Multi-Database Systems is a heterogeneous distributed

architecture.

14-MAR-14 K. INDHU 4
 MULTI-DATABASE SYSTEMS
• Federated Multi-Database systems provide a
solution to the problem of interoperating
heterogeneous data systems.

• Federated Multi-Database systems provide

uniform access to data stored in multiple
databases that involve several different data
models.

14-MAR-14 K. INDHU 5
 MULTI-DATABASE SYSTEMS

14-MAR-14 K. INDHU 6
 CHARACTERISTICS OF MDBS
• The distinctive characteristics of Multi-database systems are:-

1. Automatic generation of a unified global database schema

from local databases.
2. Provision of cross-database functionality (global queries,
updates and transactions) by using unified schema.
3. Integration of a heterogeneous database system with multiple
databases.
4. Integration of data types other than relational data through
the use of such tools as driver generators.
5. Provision of a uniform but diverse set of interfaces (e.g., a SQL-
style interface, browsing tools, and C++) to access and
manipulate data stored in local databases.

14-MAR-14 K. INDHU 7
 OPEN DATABASE CONNECTIVITY
• Open Database Connectivity(ODBC) is an
– application programming interface(API)
– that provides solutions to the multi-database programming
problem.
– that is a Programming Solution with APIs.

• In computing, ODBC (Open Database Connectivity) is a

standard programming language middleware API for
accessing database management systems (DBMS).

• It was initially proposed by Microsoft during the early

1990s.
17-MAR-14 K. INDHU 8
 OPEN DATABASE CONNECTIVITY
• Open Database Connectivity (ODBC) is a standard that allows
programs to read from almost all of the databases currently
available.

• This means that Batch can read database formats like Microsoft
Access, Paradox, dBase and FoxPro; spreadsheets like Microsoft
Excel; and connect to external database servers such as Oracle,
Informix or Microsoft SQL Server.

• ODBC provides a mechanism for independently accessing Multiple

Database Hosts.

• ODBC and the other APIs provide standard database access through
a common client-side interface.

17-MAR-14 K. INDHU 9
 UNDERSTANDING->
OPEN DATABASE CONNECTIVITY
• The Open Database Connectivity (ODBC) interface-
– > allows front-end applications
– > to access back-end data
– > from various database management systems (DBMS).

• The interface permits maximum interoperability->

• “That is, a single application can access diverse back-end database
management systems.”

• In other words, an application developer can develop, compile, and

ship an application without targeting a specific DBMS product.
– Users can then add modules called database drivers available in ODBC,
that link the application to their choice of database management systems.

17-MAR-14 K. INDHU 10
 OPEN DATABASE CONNECTIVITY-
DEVICE DRIVER MODEL
• ODBC is based on the device driver model, where the
driver encapsulates the logic needed to convert a standard
set of commands and functions into the specific calls
required by the underlying system.

• For example, a printer driver presents a standard set of

printing commands, the API, that are converted by the
driver into the format used by the actual hardware- Printer.

• ODBC remains largely universal today, with drivers

available for most platforms and most databases.

17-MAR-14 K. INDHU 11
 OPEN DATABASE CONNECTIVITY

17-MAR-14 K. INDHU 12
 OPEN DATABASE CONNECTIVITY-
BRIDGING CONFIGURATIONS
• A bridge is a special kind of driver-> a driver that uses another
driver-based technology.

• An ADO.NET – ODBC bridge consists of->

– an ADO.NET Provider
– which uses the services of an ODBC driver to connect to a target
database.
– This provider translates ADO.NET method calls into ODBC function
calls.
– Programmers usually use such a bridge when a particular database
lacks an ADO.NET provider.
– Microsoft ships one as part of the MDAC system component bundle,
together with other database drivers, to simplify development in C#.

17-MAR-14 K. INDHU 13
 OPEN DATABASE CONNECTIVITY

17-MAR-14 K. INDHU 14
 ADVANTAGES OF ODBC
1. It allows software developers to write desktop
applications without the burden of learning multiple
database APIs.

2. It has ability to store data for various applications or data

from different sources in database.

3. Details of back-end data structure is hidden from the

user.

4. ODBC has strong industry support. Used by both

Microsoft and Apple.

17-MAR-14 K. INDHU 15
 DESIGNING ACCESS LAYER CLASSES
• The place where the data actually reside is called as DATA
SOURCE.

• This place-> DATA SOURCE can be a:-

– File,
– Relational-Database,
– Mainframe,
– Internet, or
– DCOM.

• The main idea behind creating an access layer is to create a

set of classes that know how to communicate with the
place(s) where the data actually reside (OR) DATA SOURCE.

17-MAR-14 K. INDHU 16
 DESIGNING ACCESS LAYER CLASSES
• TWO IMPORTANT DUTIES OF ACCESS LAYER:-
1. The access classes must be able to translate any data-
related requests from the business layer into the
appropriate protocol for data access.

2. The access classes also must be able to translate the

data retrieved back from data-source, into the
appropriate business objects.

• Thus the access layer’s main responsibility is to-

– provide a link between-> business (or) view objects (and)
data-store.

17-MAR-14 K. INDHU 17
 DESIGNING ACCESS LAYER CLASSES
• Access layer performs BELOW major tasks:-
1. Translate the request:-
– Data-Request--->
– FROM Business Layer--->
– TO Access Layer[converts data-request into proper query-language]--->
– [Query interacts with] Data-Store--->
– [Fetches data from Data-Store] Data-Results

2. Translate the results:-

– Data-Results--->
– FROM Access Layer[converts results into business objects]--->
– TO Business Layer--->
– [Result displayed in] View Layer.

17-MAR-14 K. INDHU 18
 DESIGNING ACCESS LAYER CLASSES
• ADVANTAGES OF THIS APPROACH:-
1. The front-end- design is not tied to any database-
engine.

2. With this approach, we very easily can switch from one

database to another with no major changes to the user-
interface or business-layer objects.

3. If we change from one database to another, all we need

to do is to change ONLY the access class methods.

17-MAR-14 K. INDHU 19
 DESIGNING ACCESS LAYER CLASSES
• ADVANTAGES OF THIS APPROACH:-

4. Access layer classes provide easy migration to emerging

distributed object technology, such as CORBA and
DCOM.

5. The classes should be able to address the (relatively)

modest needs of two-tier client/server architectures as
well as the difficult demands of fine-grained, peer-to-
peer distributed object architectures.

17-MAR-14 K. INDHU 20
 DESIGNING ACCESS LAYER CLASSES

17-MAR-14 K. INDHU 21
 DESIGNING ACCESS LAYER CLASSES-
THE PROCESS
• The access layer design process consists of these following
activities:-
• 1. For every business class identified <---> Create one access
class in the access layer package.
• That is, For every business class that has been identified &
created
<--->
• MIRROR the Business – Class – Package into Access – Class –
Package.

• 2. Define relationships:- The same rule as applies among

business class objects also applies among access classes.

17-MAR-14 K. INDHU 22
 DESIGNING ACCESS LAYER CLASSES-
THE PROCESS
• 3. Simplify classes and relationships. The main goal here is
to eliminate redundant or unnecessary classes or structures.
In most cases, we can combine simple access classes and
simplify the super-sub class structures.
– 3.1. Redundant classes:- If you have more than one class that
provides similar services, simply select one and eliminate the
other(s).
– 3.2. Method classes:- Revisit the classes that consist of only one or
two methods to see if they can be eliminated or combined with
existing classes.

• 4. Iterate and refine.

17-MAR-14 K. INDHU 23
 DESIGNING ACCESS LAYER CLASSES-
THE PROCESS

17-MAR-14 K. INDHU 24
17-MAR-14 K. INDHU 25
17-MAR-14 K. INDHU 26
17-MAR-14 K. INDHU 27
 CLASS DIAGRAM OF ATM

17-MAR-14 K. INDHU 28
HAPPY LEARNING!!!