1. © 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Lecture 9: The Client/Server Database Environment Modern Database Management 9 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Heikki Topi

2. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 2 Client/Server Systems Networked computing model Networked computing model Processes distributed between clients and servers Processes distributed between clients and servers Client–Workstation (usually a PC) that requests and uses a service Client–Workstation (usually a PC) that requests and uses a service Server–Computer (PC/mini/mainframe) that provides a service Server–Computer (PC/mini/mainframe) that provides a service For DBMS, server is a database server For DBMS, server is a database server

3. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 3 Application Logic in C/S Systems GUI Interface Procedures, functions, programs DBMS activities Processing Logic I/O processing I/O processing Business rules Business rules Data management Data management Storage Logic Data storage/retrieval Data storage/retrieval Presentation Logic Input–keyboard/mouse Input–keyboard/mouse Output–monitor/printer Output–monitor/printer

4. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 4 Client/Server Architectures File Server Architecture File Server Architecture Database Server Architecture Database Server Architecture Three-tier Architecture Three-tier Architecture Client does extensive processing Client does little processing

5. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 5 File Server Architecture All processing is done at the PC that requested the data All processing is done at the PC that requested the data Entire files are transferred from the server to the client for processing Entire files are transferred from the server to the client for processing Problems: Problems: Huge amount of data transfer on the network Huge amount of data transfer on the network Each client must contain full DBMS Each client must contain full DBMS Heavy resource demand on clients Heavy resource demand on clients Client DBMSs must recognize shared locks, integrity checks, etc. Client DBMSs must recognize shared locks, integrity checks, etc. FAT CLIENT

6. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 6 Figure 9-2 File server model FAT CLIENT

7. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 7 Two-Tier Database Server Architectures Client is responsible for Client is responsible for I/O processing logic I/O processing logic Some business rules logic Some business rules logic Server performs all data storage and access processing Server performs all data storage and access processing  DBMS is only on server

8. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 8 Advantages of Two-Tier Approach Clients do not have to be as powerful Clients do not have to be as powerful Greatly reduces data traffic on the network Greatly reduces data traffic on the network Improved data integrity since it is all processed centrally Improved data integrity since it is all processed centrally Stored procedures  DBMS code that performs some business rules done on server Stored procedures  DBMS code that performs some business rules done on server

9. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 9 Advantages of Stored Procedures Compiled SQL statements Compiled SQL statements Reduced network traffic Reduced network traffic Improved security Improved security Improved data integrity Improved data integrity Thinner clients Thinner clients

10. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 10 Figure 9-3 Database server architecture (two-tier) Thinner clients DBMS only on server

11. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 11 Three-Tier Architectures Thin Client PC just for user interface and a little application processing. Limited or no data storage (sometimes no hard drive) GUI interface (I/O processing) Browser Business rules Web Server Data storage DBMS Client Application server Database server

12. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 12 Figure 9-4a Generic three-tier architecture Thinnest clients Business rules on separate server DBMS only on DB server

13. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 13 Advantages of Three-Tier Architectures Scalability Scalability Technological flexibility Technological flexibility Long-term cost reduction Long-term cost reduction Better match of systems to business needs Better match of systems to business needs Improved customer service Improved customer service Competitive advantage Competitive advantage Reduced risk Reduced risk

14. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 14 Application Partitioning Placing portions of the application code in different locations (client vs. server) AFTER it is written Placing portions of the application code in different locations (client vs. server) AFTER it is written Advantages Advantages Improved performance Improved performance Improved interoperability Improved interoperability Balanced workloads Balanced workloads

15. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 15 Common Logic Distributions Figure 9-5a Two-tier client- server environments Figure 9-5b n-tier client- server environment Processing logic could be at client, server, or both Processing logic will be at application server or Web server

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

17. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 17 Middleware Software that allows an application to interoperate with other software Software that allows an application to interoperate with other software No need for programmer/user to understand internal processing No need for programmer/user to understand internal processing Accomplished via Application Program Interface (API) Accomplished via Application Program Interface (API) “glue” The “glue” that holds client/server applications together

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

19. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 19 Database Middleware ODBC –Open Database Connectivity ODBC –Open Database Connectivity Most DB vendors support this Most DB vendors support this OLE-DB OLE-DB Microsoft enhancement of ODBC Microsoft enhancement of ODBC JDBC –Java Database Connectivity JDBC –Java Database Connectivity Special Java classes that allow Java applications/applets to connect to databases Special Java classes that allow Java applications/applets to connect to databases

20. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 20 Client/Server Security Network environment  complex security issues Network environment  complex security issues Security levels: Security levels: System-level password security System-level password security for allowing access to the system for allowing access to the system Database-level password security Database-level password security for determining access privileges to tables; read/update/insert/delete privileges for determining access privileges to tables; read/update/insert/delete privileges Secure client/server communication Secure client/server communication via encryption via encryption

21. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 21 Keys to Successful Client-Server Implementation Accurate business problem analysis Accurate business problem analysis Detailed architecture analysis Detailed architecture analysis Architecture analysis before choosing tools Architecture analysis before choosing tools Appropriate scalability Appropriate scalability Appropriate placement of services Appropriate placement of services Network analysis Network analysis Awareness of hidden costs Awareness of hidden costs Establish client/server security Establish client/server security

22. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 22 Benefits of Moving to Client/Server Architecture Staged delivery of functionality speeds deployment Staged delivery of functionality speeds deployment GUI interfaces ease application use GUI interfaces ease application use Flexibility and scalability facilitates business process reengineering Flexibility and scalability facilitates business process reengineering Reduced network traffic due to increased processing at data source Reduced network traffic due to increased processing at data source Facilitation of Web-enabled applications Facilitation of Web-enabled applications

23. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 23 Using ODBC to Link External Databases Stored on a Database Server Open Database Connectivity (ODBC) 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 API provides a common language for application programs to access and process SQL databases independent of the particular RDBMS that is accessed Required parameters: Required parameters: ODBC driver ODBC driver Back-end server name Back-end server name Database name Database name User id and password User id and password Additional information: Additional information: Data source name (DSN) Data source name (DSN) Windows client computer name Windows client computer name Client application program’s executable name Client application program’s executable name

24. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 24 ODBC Architecture (Figure 9-6) Each DBMS has its own ODBC-compliant driver Client does not need to know anything about the DBMS Application Program Interface (API) provides common interface to all DBMSs

25. Chapter 9 © 2009 Pearson Education, Inc. Publishing as Prentice Hall 25 Using JDBC to Link External Databases Stored on a Database Server Java Database Connectivity (JDBC) Java Database Connectivity (JDBC) API that Enables Java programs to execute SQL statements and connect to database servers API that Enables Java programs to execute SQL statements and connect to database servers Whereas ODBC is language independent, JDBC is specific to Java Whereas ODBC is language independent, JDBC is specific to Java Based on X/Open SQL Call Level Interface Based on X/Open SQL Call Level Interface Two layers: Two layers: JDBC API for communication from application to JDBC driver manager JDBC API for communication from application to JDBC driver manager JDBC Driver API for communication from driver manager to drivers JDBC Driver API for communication from driver manager to drivers SQLJ (SQL-Java): SQLJ (SQL-Java): Embedded SQL in Java Embedded SQL in Java SQL routines using Java SQL routines using Java SQL types using Java SQL types using Java