Chapter 9 The ClientServer Database Environment Modern Database

Chapter 9: The Client/Server Database Environment Modern Database Management 8 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. Mc. Fadden © 2007 by Prentice Hall 1

Objectives n n n n 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 n n n 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 Chapter 9 © 2007 by Prentice Hall 3

Application Logic in C/S Systems Presentation Logic n n Input–keyboard/mouse Output–monitor/printer GUI Interface Processing Logic n n n I/O processing Business rules Data management Storage Logic n Data storage/retrieval Chapter 9 Procedures, functions, programs DBMS activities © 2007 by Prentice Hall 4

Client/Server Architectures Client does extensive processing n File Server Architecture n Database Server Architecture n Three-tier Architecture Client does little processing Chapter 9 © 2007 by Prentice Hall 5

File Server Architecture n n n 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: n n Huge amount of data transfer on the network Each client must contain full DBMS n n Chapter 9 Heavy resource demand on clients Client DBMSs must recognize shared locks, integrity checks, etc. © 2007 by Prentice Hall 6

Figure 9 -2 File Server Architecture FAT CLIENT Chapter 9 © 2007 by Prentice Hall 7

Two-Tier Database Server Architectures n Client is responsible for n I/O processing logic n Some business rules logic n Server performs all data storage and access processing DBMS is only on server Chapter 9 © 2007 by Prentice Hall 8

Advantages of Two-Tier Approach n n 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 Chapter 9 © 2007 by Prentice Hall 9

Advantages of Stored Procedures n Compiled SQL statements n Reduced network traffic n Improved security n Improved data integrity n Thinner clients Chapter 9 © 2007 by Prentice Hall 10

Figure 9 -3 Two-tier database server architecture Thinner clients DBMS only on server Chapter 9 © 2007 by Prentice Hall 11

Three-Tier Architectures Client GUI interface (I/O processing) Browser Application server Business rules Web Server Database server Data storage DBMS Thin Client l Chapter 9 PC just for user interface and a little application processing. Limited or no data storage (sometimes no hard drive) © 2007 by Prentice Hall 12

Figure 9 -4 Three-tier architecture Thinnest clients Business rules on separate server DBMS only on DB server Chapter 9 © 2007 by Prentice Hall 13

Advantages of Three-Tier Architectures n n n n Scalability Technological flexibility Long-term cost reduction Better match of systems to business needs Improved customer service Competitive advantage Reduced risk Chapter 9 © 2007 by Prentice Hall 14

Application Partitioning n n Placing portions of the application code in different locations (client vs. server) AFTER it is written Advantages Improved performance n Improved interoperability n Balanced workloads n Chapter 9 © 2007 by Prentice Hall 15

Common Logic Distributions Figure 9 -5 a Two-tier clientserver environment Processing logic could be at client, server, or both Figure 9 -5 b n-tier clientserver environment Processing logic will be at application server or Web server Chapter 9 © 2007 by Prentice Hall 16

Role of the Mainframe n n n 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 n n 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 n n Mainframe for centralized data that does not need to be moved Client for data requiring frequent user access, complex graphics, and user interface Chapter 9 © 2007 by Prentice Hall 17

Middleware n n n 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 Chapter 9 © 2007 by Prentice Hall 18

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

Database Middleware n ODBC–Open n Database Connectivity Most DB vendors support this n OLE-DB n Microsoft enhancement of ODBC n JDBC–Java n Database Connectivity Special Java classes that allow Java applications/applets to connect to databases Chapter 9 © 2007 by Prentice Hall 20

Client/Server Security n n Network environment complex security issues Security levels: n System-level password security n n Database-level password security n n for allowing access to the system for determining access privileges to tables; read/update/insert/delete privileges Secure client/server communication n Chapter 9 via encryption © 2007 by Prentice Hall 21

Keys to Successful Client-Server Implementation n n n n 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 Chapter 9 © 2007 by Prentice Hall 22

Benefits of Moving to Client/Server Architecture n n n 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 Chapter 9 © 2007 by Prentice Hall 23

Using ODBC to Link External Databases Stored on a Database Server n Open Database Connectivity (ODBC) n n Required parameters: n n n API provides a common language for application programs to access and process SQL databases independent of the particular RDBMS that is accessed ODBC driver Back-end server name Database name User id and password Additional information: n n n 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 Chapter 9 © 2007 by Prentice Hall 24

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 Chapter 9 © 2007 by Prentice Hall 25