Top Banner
System Architecture & Hardware Configurations Dr. D. Bilal IS 582 Spring 2006
22
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: 3/16/06: System Architecture

System Architecture & Hardware Configurations

Dr. D. Bilal

IS 582

Spring 2006

Page 2: 3/16/06: System Architecture

System Architecture

Two major system architectures:HierarchicalClient/Server

Page 3: 3/16/06: System Architecture

Hierarchical Architecture

Processing and activities are controlled by the host system

Remote computers connected to host system have limited functions

(input/output)

Page 4: 3/16/06: System Architecture

Hierarchical Architecture

Remote computers connected to the host system emulate “dumb” terminals in communicating with the host system.

“Dumb” terminals have no or limited processing capabilities.

Page 5: 3/16/06: System Architecture

Client/Server Architecture

Client: a user’s computer

Server: a dedicated computer in a network shared by multiple users More than one server can exist in this architecture

(e.g., database server, Web server, application server, e-mail server)

Page 6: 3/16/06: System Architecture

Client/Server Architecture

A computing architecture in a LAN or WAN environmentClients on network perform certain

processing functions when requesting information from a server in the network

Page 7: 3/16/06: System Architecture

Client/Server Architecture

TCP/IP to establish communications between clients and servers

Clients handle the user interface screen formatting, display of results,

input/outputmake requests and send them to the

application server

Page 8: 3/16/06: System Architecture

Client/Server Architecture

Server searches for requested information and sends results to the client(s)

Server performs database management, information retrieval, transaction and processing tasks.

Server delivers access to files, applications, and network communications.

Page 9: 3/16/06: System Architecture

File Server Architecture

User requests information from a server

Entire database file is downloaded in the computer making the request results in slow communication between the user’s

computer and the server.

Page 10: 3/16/06: System Architecture

File Server Architecture

Software programs are loaded onto the server only.

Installing updates are done in server

Updates take less time to install than those in client/server architecture

Page 11: 3/16/06: System Architecture

Client/Server Architecture

One client may connect to one or more servers: OPAC server, Webmail server, and other servers

One server may connect to multiple clients concurrently.

Page 12: 3/16/06: System Architecture

Client/Server Architecture

Each client that is connected in a client/server network must have part of the automation software (e.g., user interface) loaded onto its hard disk that allows it to perform certain application tasks.

Page 13: 3/16/06: System Architecture

Client/Server Architecture

If all OPACs in a network must have access to the Web, all clients must have a Web browser.

If all clients must provide access to e-mail, they must have the e-mail client software loaded on them.

Page 14: 3/16/06: System Architecture

Client/Server Architecture

Servers may be large scale computers, mid-range computers, or high speed microcomputers.

True client/server means that the application was originally designed to run on a network (LAN or WAN).

Page 15: 3/16/06: System Architecture

Types of Client/Server: Two-Tier

Database processing tasks are done in the server.Application processing tasks are done in the client requesting the information. A request is generated in the client and

transmitted to the server. The Database Management System that resides on the server searches for the desired information and transmits the results of the request to the client.

Page 16: 3/16/06: System Architecture

Types of Client/Server: Three-Tier

Used when applications are in high demand.

An additional server is used for application processing tasks.

Both the client and the additional server perform application processing tasks.

The other server performs the database management tasks (searching, retrieval, etc.).

Page 17: 3/16/06: System Architecture

Types of Client/Server: Thin Clients

Computer terminals rather than desktop computers.

Do little or no data processing tasks.

Process information (input/output).

Used to lower PCs and Macs cost used in a network.

Page 18: 3/16/06: System Architecture

Types of Client/Server: Thin Clients

May be used as e-mail stations, Web access stations, and/or OPACs stations.

Can co-exist with thick or fat clients in a network.

Page 19: 3/16/06: System Architecture

Client/Server Architecture

Benefits See Bilal, 2002, pp. 33-34.

Disadvantages See Bilal, 2002, p. 34.

See client/server software architecture at

http://www.sei.cmu.edu/str/descriptions/clientserver.html

Page 20: 3/16/06: System Architecture

Options for Hardware Configurations

Non-networked (a.k.a. stand-alone)AdvantagesDisadvantages

Difference between stand-alone hardware configuration and stand-alone software configuration.

Page 21: 3/16/06: System Architecture

Options for Hardware Configurations

Networked: LAN-basedAdvantagesDisadvantages

Networked: WAN-basedAdvantages Disadvantages

Page 22: 3/16/06: System Architecture

ASP Model

ASP (Access Service Provider)

To outsource network maintenance and troubleshooting to a vendor

Vendor does database installation and update

Fee-based service