The Client/Server Database Environment: Modern Database Management 8 Edition

Chapter 9:
The Client/Server Database

Environment
Modern Database Management
8th Edition
Jeffrey A. Hoffer, Mary B. Prescott,
Fred R. McFadden
© 2007 by Prentice Hall 1

Objectives
 Definition of terms
 List advantages of client/server architecture
 Explain three application components:
presentation, processing, and storage
 Suggest partitioning possibilities
 Distinguish between file server, database server,
3-tier, and n-tier approaches
 Describe and discuss middleware
 Explain database linking via ODBC and JDBC
Chapter 9 © 2007 by Prentice Hall 2
Client/Server Systems
 Networked computing model
 Processes distributed between clients and
servers
 Client–Workstation (usually a PC) that
requests and uses a service
 Server–Computer (PC/mini/mainframe)
that provides a service
 For DBMS, server is a database server
Application Logic in C/S Systems
Presentation Logic
 Input–keyboard/mouse
GUI Interface
 Output–monitor/printer
Processing Logic
 I/O processing Procedures, functions,
 Business rules programs
 Data management
Storage Logic
 Data storage/retrieval DBMS activities

Client/Server Architectures
Client does
extensive processing
 File Server Architecture
 Database Server Architecture
 Three-tier Architecture
Client does little
processing

File Server Architecture
 All processing is done at the PC that requested

the data FAT CLIENT
 Entire files are transferred from the server to the
client for processing
 Problems:
 Huge amount of data transfer on the network
 Each client must contain full DBMS
 Heavy resource demand on clients
 Client DBMSs must recognize shared locks, integrity checks,
etc.
Figure 9-2 File Server Architecture
FAT CLIENT

Two-Tier Database Server
Architectures
 Client is responsible for
 I/O processing logic
 Some business rules logic
 Server performs all data storage and

access processing
 DBMS is only on server

Advantages of Two-Tier Approach
 Clients do not have to be as powerful

 Greatly reduces data traffic on the network
 Improved data integrity since it is all
processed centrally
 Stored procedures  DBMS code that
performs some business rules done on
server

Advantages of
Stored Procedures
 Compiled SQL statements
 Reduced network traffic
 Improved security
 Improved data integrity
 Thinner clients

Figure 9-3 Two-tier database server architecture
Thinner
clients
DBMS only
on server

Three-Tier Architectures
GUI interface
Client (I/O processing)
Browser
Application server Business rules Web Server
Database server Data storage DBMS
Thin Client
 PC just for user interface and a little application
processing. Limited or no data storage (sometimes no
hard drive)
Figure 9-4 Three-tier architecture
Thinnest
clients
Business rules
on separate
server
DBMS only on
DB server

Advantages of Three-Tier
Architectures
 Scalability
 Technological flexibility
 Long-term cost reduction
 Better match of systems to business needs
 Improved customer service
 Competitive advantage
 Reduced risk
Application Partitioning
 Placing portions of the application code in

different locations (client vs. server)
AFTER it is written
 Advantages
 Improved performance
 Improved interoperability
 Balanced workloads

Common Logic Distributions
Figure 9-5a Two-tier client-
server environment
Processing logic could be
at client, server, or both
Figure 9-5b n-tier client-

server environment
Processing logic
will be at
application server
or Web server

Role of the Mainframe
 Mission-critical legacy systems have tended to remain on
mainframes
 Distributed client/server systems tend to be used for
smaller, workgroup systems
 Difficulties in moving mission critical systems from
mainframe to distributed
 Determining which code belongs on server vs. client
 Identifying potential conflicts with code from other applications
 Ensuring sufficient resources exist for anticipated load
 Rule of thumb
 Mainframe for centralized data that does not need to be moved
 Client for data requiring frequent user access, complex graphics,
and user interface

Middleware
 Software that allows an application to
interoperate with other software
 No need for programmer/user to
understand internal processing
 Accomplished via Application Program
Interface (API)
The “glue” that holds client/server applications together

Types of Middleware
 Remote Procedure Calls (RPC)
 client makes calls to procedures running on remote computers
 synchronous and asynchronous
 Message-Oriented Middleware (MOM)
 asynchronous calls between the client via message queues
 Publish/Subscribe
 push technology  server sends information to client when
available
 Object Request Broker (ORB)
 object-oriented management of communications between clients
and servers
 SQL-oriented Data Access
 middleware between applications and database servers

Database Middleware
 ODBC–Open Database Connectivity
 Most DB vendors support this
 OLE-DB
 Microsoft enhancement of ODBC
 JDBC–Java Database Connectivity
 Special Java classes that allow Java
applications/applets to connect to databases

Client/Server Security
 Network environment  complex
security issues
 Security levels:
 System-level password security
 for allowing access to the system
 Database-level password security
 for determining access privileges to tables;
read/update/insert/delete privileges
 Secure client/server communication
 via encryption

Keys to Successful Client-Server
Implementation
 Accurate business problem analysis
 Detailed architecture analysis
 Architecture analysis before choosing tools
 Appropriate scalability
 Appropriate placement of services
 Network analysis
 Awareness of hidden costs
 Establish client/server security

Benefits of Moving to Client/Server
Architecture
 Staged delivery of functionality speeds
deployment
 GUI interfaces ease application use
 Flexibility and scalability facilitates
business process reengineering
 Reduced network traffic due to increased
processing at data source
 Facilitation of Web-enabled applications
Using ODBC to Link External Databases
Stored on a Database Server
 Open Database Connectivity (ODBC)
 API provides a common language for application programs
to access and process SQL databases independent of the
particular RDBMS that is accessed
 Required parameters:
 ODBC driver
 Back-end server name
 Database name
 User id and password
 Additional information:
 Data source name (DSN)
 Windows client computer name
 Client application program’s executable name
Java Database Connectivity (JDBC) is similar to ODBC–built specifically for Java applications

ODBC Architecture
(Figure 9-6)
Client does not need to

know anything about the
DBMS
Application Program
Interface (API) provides
common interface to all
DBMSs
Each DBMS has its own ODBC-compliant driver

The Client/Server Database Environment: Modern Database Management 8 Edition

Uploaded by

Copyright:

Available Formats

The Client/Server Database Environment: Modern Database Management 8 Edition

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

The Client/Server Database Environment: Modern Database Management 8 Edition

Uploaded by

Copyright:

Available Formats

Chapter 9:

The Client/Server Database

© 2007 by Prentice Hall 1

Chapter 9 © 2007 by Prentice Hall 4

 Database Server Architecture

Chapter 9 © 2007 by Prentice Hall 5

 All processing is done at the PC that requested

Chapter 9 © 2007 by Prentice Hall 7

 Server performs all data storage and

Chapter 9 © 2007 by Prentice Hall 8

 Clients do not have to be as powerful

Chapter 9 © 2007 by Prentice Hall 9

 Improved data integrity

Chapter 9 © 2007 by Prentice Hall 10

Chapter 9 © 2007 by Prentice Hall 11

Application server Business rules Web Server

Database server Data storage DBMS

Chapter 9 © 2007 by Prentice Hall 13

 Placing portions of the application code in

Chapter 9 © 2007 by Prentice Hall 15

Figure 9-5b n-tier client-

Chapter 9 © 2007 by Prentice Hall 16

Chapter 9 © 2007 by Prentice Hall 17

The “glue” that holds client/server applications together

Chapter 9 © 2007 by Prentice Hall 18

Chapter 9 © 2007 by Prentice Hall 19

Chapter 9 © 2007 by Prentice Hall 20

Chapter 9 © 2007 by Prentice Hall 21

Chapter 9 © 2007 by Prentice Hall 22

Chapter 9 © 2007 by Prentice Hall 24

Client does not need to

Each DBMS has its own ODBC-compliant driver

Chapter 9 © 2007 by Prentice Hall 25

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.