MIS 385/MBA 664
Systems Implementation with DBMS/
Database Management
Dave Salisbury
[email protected] (email)
http://www.davesalisbury.com/ (web site)
Chapter 9 Client-Server
Environment
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
Client/Server Systems
Networked computing model
Processes distributed between clients
and servers
ClientWorkstation (usually a PC) that
requests and uses a service
ServerComputer (PC/mini/mainframe)
that provides a service
For DBMS, server is a database server
Application Logic in C/S Systems
Presentation Logic
Inputkeyboard/mouse
Outputmonitor/printer
GUI Interface
Processing Logic
I/O processing
Business rules
Data management
Storage Logic
Data storage/retrieval
Procedures, functions,
programs
DBMS activities
Client/Server Architectures
File Server Architecture
Database Server
Architecture
Three-tier Architecture
Client does
extensive
processing
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.
File server architecture
FAT
CLIENT
Two-Tier Architecture
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
Two-tier architecture
Thinner
clients
DBMS only
on server
Three-Tier Architectures
Client
GUI interface
(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)
Three-tier architecture
Thinnest
clients
Business rules on
separate server
DBMS only on
DB server
Advantages of Three-Tier
Architecture
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
Processing logic could be at
client, server, or both
Processing logic will be
at application server or
Web server
Role of the Mainframe
Mission-critical legacy systems tend to stay on
mainframes
Client/server systems tend to be small
workgroup systems
Problems 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)
Message-Oriented Middleware (MOM)
push technology server sends information to client
when available
Object Request Broker (ORB)
asynchronous calls between the client via message
queues
Publish/Subscribe
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
middleware between applications and database servers
Database Middleware
ODBCOpen Database Connectivity
OLE-DB
Most DB vendors support this
Microsoft enhancement of ODBC
JDBCJava 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
Database-level password security
for allowing access to the system
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)
Required parameters:
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:
Data source name (DSN)
Windows client computer name
Client application programs executable name
Java Database Connectivity (JDBC) is similar to ODBCbuilt specifically for Java applications
ODBC Architecture
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
