Networks in Operation. Computer Networks External Resources: Much of the complexity of modern networks arise from the huge quantity of distributed resources.

Slides:



Advertisements
Similar presentations
Welcome to Middleware Joseph Amrithraj
Advertisements

Chapter 9: The Client/Server Database Environment
Windows NT server and workstation Name: Li Shen Course: COCS541 Instructor: Mort Anvari.
COM vs. CORBA.
Database Architectures and the Web
Client/Server Computing Ajay Kumar Shrivastava. Network Operating System (NOS) It manages the services of the server It exists at the session and presentation.
Chapter 7 LAN Operating Systems LAN Software Software Compatibility Network Operating System (NOP) Architecture NOP Functions NOP Trends.
I.1 Distributed Systems Prof. Dr. Alexander Schill Dresden Technical University Computer Networks Dept.
Distributed components
Computers Are Your Future © 2008 Prentice-Hall, Inc.
Chapter 17: Client/Server Computing Business Data Communications, 4e.
1 Pertemuan 13 Servers for E-Business Matakuliah: M0284/Teknologi & Infrastruktur E-Business Tahun: 2005 Versi: >
Computers Are Your Future © 2006 Prentice-Hall, Inc.
Software Engineering and Middleware: a Roadmap by Wolfgang Emmerich Ebru Dincel Sahitya Gupta.
Overview Explain three application components: presentation, processing, and storage Distinguish between file server, database server, 3-tier, and n-tier.
Server Platforms Week 11- Lecture 1. Server Market $ 46,100,000,000 ($ 46.1 Billion) Gartner.
Middleware Technologies compiled by: Thomas M. Cosley.
Distributed Information Systems - The Client server model
12 Chapter 12 Client/Server Systems Hachim Haddouti.
12 Chapter 12 Client/Server Systems Database Systems: Design, Implementation, and Management, Fifth Edition, Rob and Coronel.
The Architecture of Transaction Processing Systems
Understanding Networks I. Objectives Compare client and network operating systems Learn about local area network technologies, including Ethernet, Token.
Chapter 9: The Client/Server Database Environment
Systems Architecture, Fourth Edition1 Internet and Distributed Application Services Chapter 13.
.NET Mobile Application Development Introduction to Mobile and Distributed Applications.
1 © Prentice Hall, 2002 The Client/Server Database Environment.
Lecture The Client/Server Database Environment
The Client/Server Database Environment
Chapter 3 Database Architectures and the Web Pearson Education © 2009.
Information Systems Today: Managing in the Digital World TB4-1 4 Technology Briefing Networking.
Stuart Cunningham - Computer Platforms COMPUTER PLATFORMS Network Operating Systems Week 9.
1 Computer (Transport) Layer F Manages communication between two computers F Platform independence: one computer does not know even what platform the other.
Lecture On Database Analysis and Design By- Jesmin Akhter Lecturer, IIT, Jahangirnagar University.
SAP R/3 System: Client Server Overview (Buck-Emden & Galimow, 1998) Dr. K. Palaniappan.
Enterprise Systems MIS 181.9: Service Oriented Architecture 2 nd Semester,
1 © Prentice Hall, 2002 Chapter 8: The Client/Server Database Environment Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott,
MBA 664 Database Management Systems Dave Salisbury ( )
Database Architectures and the Web Session 5
Application Layer CHAPTER 2. Announcements and Outline  Administrative Items  Questions? Recap 1.Introduction to Networks 1.Network Type 2.N etwork.
Client Server Technologies Middleware Technologies Ganesh Panchanathan Alex Verstak.
Networking Basics Lesson 1 Introduction to Networks.
Choosing NOS can be a complex and a difficult decision. Every popular NOS has its strengths and weaknesses. NOS may cost thousands of dollars depending.
9/5/2012ISC329 Isabelle Bichindaritz1 Web Database Environment.
Basic Communications Overview of communication technology.
Lecture 3: Sun: 16/4/1435 Distributed Computing Technologies and Middleware Lecturer/ Kawther Abas CS- 492 : Distributed system.
© 2005 by Prentice Hall 1 Chapter 9: The Client/Server Database Environment Modern Database Management 7 th Edition Jeffrey A. Hoffer, Mary B. Prescott,
PPTTEST 10/6/ :29 1 IT Ron Williams Business Innovation Through Information Technology Networking.
Csi315csi315 Client/Server Models. Client/Server Environment LAN or WAN Server Data Berson, Fig 1.4, p.8 clients network.
Unit – I CLIENT / SERVER ARCHITECTURE. Unit Structure  Evolution of Client/Server Architecture  Client/Server Model  Characteristics of Client/Server.
1 Introduction to Middleware. 2 Outline What is middleware? Purpose and origin Why use it? What Middleware does? Technical details Middleware services.
Remote Access Using Citrix Presentation Server December 6, 2006 Matthew Granger IT665.
SEMINOR. INTRODUCTION 1. Middleware is connectivity software that provides a mechanism for processes to interact with other processes running on multiple.
Lecture 22: Client-Server Software Engineering
William Stallings Data and Computer Communications
3-Tier Architecture Chandrasekaran Rajagopalan Cs /01/99.
CSC 480 Software Engineering Lecture 17 Nov 4, 2002.
E-commerce Architecture Ayşe Başar Bener. Client Server Architecture E-commerce is based on client/ server architecture –Client processes requesting service.
© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Lecture 9: The Client/Server Database Environment Modern Database Management 9 th Edition.
Chapter 9: The Client/Server Database Environment
Database Architectures and the Web
The Client/Server Database Environment
Server Client Application Development
The Client/Server Database Environment
Chapter 9 – RPCs, Messaging & EAI
Chapter 9: The Client/Server Database Environment
Database Architectures and the Web
#01 Client/Server Computing
Computer (Transport) Layer
Ch > 28.4.
#01 Client/Server Computing
Presentation transcript:

Networks in Operation

Computer Networks External Resources: Much of the complexity of modern networks arise from the huge quantity of distributed resources and the difficulties inherent in finding, accessing and managing those resources.

Network Software System Software must: Find requested resources on the network Negotiate resource access with distant resources allocation software Receive and deliver the resources to the requesting user or program Listen for resource requests Validate resource requests Deliver resources via the network

Network Software Operating Software Network Operating System (NOS) Server Operating System Transaction Processing Monitor (TP Monitor) Applications Systems DBMS Application Software

Network Operating Systems (NOS) Normally support both Ethernet and token passing Support WAN interfaces Supports WAN protocols including TCP/IP

Workstation Functions APPLICATION REDIRECTION NETWORK INTERFACE OPERATING SYSTEM CPU NIC

Client Functions Application execution Fat and thin clients Network access Network software and hardware (NIC) Application software maintenance Remote resources

Server NOS Software Manages central services and external interfaces Directory services Translation protocol

Server Functions Shared resources File and print services Application management Network operating system Access to the network Higher layer functions Security Backup and professional support

Network Operating Systems UNIX and LINUX Novell NetWare Microsoft Windows NT family Others: OS/390, Palm, etc.

UNIX 32 Bit Computer Operating System with networking built in Commonly a server environment Open platform system (all machines in some version) Virtual machine multi-tasking

LINUX Open architecture operating system Substantial free upgrades and special routines are available Developed by Linus Torvalds for the Intel Runs on a very wide range of platforms Supported by several 3rd party companies (e.g. Red Hat, Caldera)

Windows 2000/NT/XP 32 Bit Operating System with multitasking and multi-threading Built-in networking GUI interface Intel based

Novell NetWare Server operating system Includes global directory services Security and multi-environment functions mature Remote management IPX protocols vs. IP

OS/390 Mainframe The primary operating system used in IBM mainframes. OS/390 was originally the MVS/ESA operating system renamed and repackaged in 1996 with an extensive set of utilities. Enhancements in usability and workload balancing have made OS/390 stand apart from its MVS heritage.

Operating System Shipments in 1998

Client/Server Architecture An architecture in which the client (personal computer or workstation) is the requesting machine and the server is the supplying machine, both of which are connected via a network.

Centralized Architecture Not Scalable Low Bandwidth

Fat Client / File Server Scalability (server and client) Interoperability Needs bandwidth

Client / Server (fat client) Scalability (client) Interoperability Needs bandwidth

Three Tier Client / Server (fat client)

Web Network (thin client)

Client/Server Architecture Client May do some or all of the processing Requests services from the network Server Contains data and may contain programs Server downloads information (applications or data) to the client for operation

Basic Client/Server Component Model

Client/Server Components: Example

Client/Server Architectures SERVER PROCESSING CLIENT PROCESSING CENTRALIZEDSTAND-ALONE FAT SERVER FAT CLIENT

Client/Server Scalability Interoperability User buy-in Increased cost Multi-tier

One Tier System

Two Tier Client/Server

Three Tier Client/Server

Middleware Support of Connectivity

Middleware: Basic Services Client/Server Connectivity Platform Transparency Network Transparency and Isolation Application Tool Support API’s (Application Product Interfaces such as ODBC Open DataBase Connectivity) Language Support Database Management Support

Application Product Interface (API) Approaches Message Oriented Middleware (MOM) Remote Procedure Call (RPC) (NetWise, NobleNet, etc.) Database Access Middleware Distributed Transaction Processing (DTP) Monitors (Tuxedo, Encina, Top End, …) Object Request Broker (ORB ) (CORBA, OLE, OpenDOC, …)

Maintaining a Thread Versions of a server program for each client. Similar to the problems of multiprogramming in Operating Systems. Identifying a service  Service Identifier Identifying a client  Client and Server ID’s

Remote Procedure Call Approach Print roll Find students enrolled Print roll Client stub Server stub Find students enrolled Single Machine Client/Server ServerClient

RPC Sessions Distributes standard code modules Program functions distributed between client and server Stubs manage communication Client waits for response Session connected by: service port id’s + address’s

Message Oriented Sessions More complex than RPC Each message header contains enough data to route and process Messages are queued at client Client may process other actions

Middleware Support of Connectivity

TP Monitors (Transaction Processing Monitor) A control program that manages the transfer of data between multiple terminals and the application programs that serve them. In a distributed client/server environment, a TP monitor provides integrity by ensuring that transactions do not get lost or damaged. Examples of popular TP monitors are CICS, used on IBM mainframes and the UNIX- based Tuxedo and Encina products.

Application Software Distributed Computing Fat client and thin client Database Partitioning and replication Workgroup Meetingware and team support software Communications

Application Issues Interoperability (e.g. ODBC) OS support Multi-threaded or single threaded Network impact (e.g. chattiness) QoS demands Delivery: centralized, clien/server, web

Application Management Standards Supported Accepted Prohibited Version Control and Distribution License Management Virus detection and inoculation

Technologies Common WAN technologies.

ISDN Circuit Switched Data and Voice Service

Digital Subscriber Lines DSL uses packet switching technology that operates independent of the voice telephone system, allowing the telephone companies to provide the service and not lock up circuits for long calls.

Asynchronous Transfer Mode Cell switched Fast: Speeds up to 2488 Mbps Supports Quality of Service classes Used primarily as a backbone technology

ATM

ATM Traffic Classes (QoS)

Frame Relay Pricing Components Ports Maximum Bit Rate (56K, T1, etc.) Processing Committed Bit Rate Burst Rate (Discard Eligible)  Closed loop congestion control will not accept too high a load for the network  Open loop congestion control will discard excess packets if the network can’t process them

WAN Costs Circuit Charges Committed Bandwidth Peak Bandwidth Discard Priority Latency

Representative Prices per MB of traffic (Qwest, Dec. 98) Frame Relay Non-discard eligible4 cents Discard eligible3 cents ATM Constant bit rate2 cents Variable bit rate (real-time)1.2 cents Variable bit rate (non real-time).75 cents Available bit rate.55 cents Unspecified bit rate.4 cents

Representative Prices per port (Qwest, Dec. 98) 56 Kb Frame Relay$190 T-1 Frame Relay $1,595 T-3 Frame Relay $3,190

Networks