Netscape Application Server Application Server for Business-Critical Applications Presented By : Khalid Ahmed DS 520 - Fall 98.

Slides:



Advertisements
Similar presentations
WSUS Presented by: Nada Abdullah Ahmed.
Advertisements

Objectives In this session, you will learn to:
IIS Technologies.
Technical Architectures
Web Server Hardware and Software
Distributed Systems Architectures
ISYS 546 Client/Server Database Application Development.
BICS546 Client/Server Database Application Development.
15 Chapter 15 Web Database Development Database Systems: Design, Implementation, and Management, Fifth Edition, Rob and Coronel.
Introduction to ASP.NET. 2 © UW Business School, University of Washington 2004 Outline Static vs. Dynamic Web Pages.NET Framework Installing ASP.NET First.
DATABASE APPLICATION DEVELOPMENT SAK 3408 The Web and DBMS.
Introduction to Web Database Processing
Kashif Jalal CA-240 (072) Web Development Using ASP.NET CA – 240 Kashif Jalal Welcome to week – 2 of…
Web Servers How do our requests for resources on the Internet get handled? Can they be located anywhere? Global?
Building Enterprise Information Portal using Oracle Portal 3
J2EE Java 2 Enterprise Edition. Relevant Topics in The Java Tutorial Topic Web Page JDBC orial/jdbc
Client/Server Architecture
Electronic Commerce Last Week Internet utility programs
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 12 Slide 1 Distributed Systems Design 1.
Understanding and Managing WebSphere V5
The Client/Server Database Environment
Client/Server Architectures
System Architecture & Hardware Configurations Dr. D. Bilal IS 592 Spring 2005.
Hands-On Microsoft Windows Server 2008 Chapter 1 Introduction to Windows Server 2008.
1 Web Database Processing. Web Database Applications Static Report Publishing a report is prepared from a database application and exported to HTML DB.
INTRODUCTION TO WEB DATABASE PROGRAMMING
FALL 2005CSI 4118 – UNIVERSITY OF OTTAWA1 Part 4 Web technologies: HTTP, CGI, PHP,Java applets)
Architecture Of ASP.NET. What is ASP?  Server-side scripting technology.  Files containing HTML and scripting code.  Access via HTTP requests.  Scripting.
Introduction to ASP.NET. Prehistory of ASP.NET Original Internet – text based WWW – static graphical content  HTML (client-side) Need for interactive.
Copyright © cs-tutorial.com. Introduction to Web Development In 1990 and 1991,Tim Berners-Lee created the World Wide Web at the European Laboratory for.
Databases and the Internet. Lecture Objectives Databases and the Internet Characteristics and Benefits of Internet Server-Side vs. Client-Side Special.
Week 7 Lecture Web Database Development Samuel Conn, Asst. Professor
Basics of Web Databases With the advent of Web database technology, Web pages are no longer static, but dynamic with connection to a back-end database.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 12 Slide 1 Distributed Systems Architectures.
Chapter 4: Core Web Technologies
Technology Overview. Agenda What’s New and Better in Windows Server 2003? Why Upgrade to Windows Server 2003 ?  From Windows NT 4.0  From Windows 2000.
5 Chapter Five Web Servers. 5 Chapter Objectives Learn about the Microsoft Personal Web Server Software Learn how to improve Web site performance Learn.
第十四章 J2EE 入门 Introduction What is J2EE ?
® IBM Software Group © 2007 IBM Corporation J2EE Web Component Introduction
Enterprise Java Beans Java for the Enterprise Server-based platform for Enterprise Applications Designed for “medium-to-large scale business, enterprise-wide.
CS480 Computer Science Seminar Introduction to Microsoft Solutions Framework (MSF)
DEV-5: Introduction to WebSpeed ® Stephen Ferguson Sr. Training Program Manager.
Unit – I CLIENT / SERVER ARCHITECTURE. Unit Structure  Evolution of Client/Server Architecture  Client/Server Model  Characteristics of Client/Server.
Introduction to the Adapter Server Rob Mace June, 2008.
The Client/Server Database Environment Ployphan Sornsuwit KPRU Ref.
1 Welcome to CSC 301 Web Programming Charles Frank.
Mainframe (Host) - Communications - User Interface - Business Logic - DBMS - Operating System - Storage (DB Files) Terminal (Display/Keyboard) Terminal.
Personal Computer - Stand- Alone Database  Database (or files) reside on a PC - on the hard disk.  Applications run on the same PC and directly access.
INTRODUCTION TO WEB APPLICATION Chapter 1. In this chapter, you will learn about:  The evolution of the Internet  The beginning of the World Wide Web,
Microsoft Management Seminar Series SMS 2003 Change Management.
© FPT SOFTWARE – TRAINING MATERIAL – Internal use 04e-BM/NS/HDCV/FSOFT v2/3 JSP Application Models.
WEB SERVER SOFTWARE FEATURE SETS
CSC 480 Software Engineering Lecture 17 Nov 4, 2002.
Electronic Commerce Semester 1 Term 1 Lecture 7. Introduction to the Web The Internet supports a variety of important tools, such as file transfer, electronic.
System Architecture & Hardware Configurations Dr. D. Bilal IS 582 Spring 2008.
Lect5.ppt - 02/23/06 CIS 4100 Systems Performance and Evaluation Lecture 6 by Zornitza Genova Prodanoff.
E-commerce Architecture Ayşe Başar Bener. Client Server Architecture E-commerce is based on client/ server architecture –Client processes requesting service.
Configuring SQL Server for a successful SharePoint Server Deployment Haaron Gonzalez Solution Architect & Consultant Microsoft MVP SharePoint Server
1 Chapter 1 INTRODUCTION TO WEB. 2 Objectives In this chapter, you will: Become familiar with the architecture of the World Wide Web Learn about communication.
E-Business Infrastructure PRESENTED BY IKA NOVITA DEWI, MCS.
Netscape Application Server
The Client/Server Database Environment
Introduction to J2EE Architecture
#01 Client/Server Computing
Chapter 3: Windows7 Part 4.
An Introduction to Computer Networking
Web Development Using ASP .NET
Web Application Server 2001/3/27 Kang, Seungwoo. Web Application Server A class of middleware Speeding application development Strategic platform for.
#01 Client/Server Computing
Presentation transcript:

Netscape Application Server Application Server for Business-Critical Applications Presented By : Khalid Ahmed DS Fall 98

OLD CLIENT-SERVER MODEL  Connection Clients were required to have dedicated lines, leased lines, dialups, or some other access to the Server. u Network Protocol Clients had to use the same network protocols as the Server they wanted to communicate with, TCP/IP, IPX/SPX, NetBUI, etc. u Hardware Requirements Clients had to meet specific machine requirements: microprocessor speed; screen resolution; RAM; hard disk space; modem speed; etc. Clients were required to make a huge investment in hardware.

OLD CLIENT-SERVER MODEL u Operating System Requirements The Clients had to run a specific Operating System and version. u Software Updates Application updates via floppy disks or CDs were frequent. The Client was required to perform the costly installation or update.

New Client-Server Model  Internet Connection Clients need only have access to the Internet to access a website. Network requirements are largely eliminated because TCP/IP is the default Internet protocol. Now it’s easy for clients to communicate with a server.  Instant Access Clients no longer need to install or update applications, they simply access the service on a website. Any updates you’ve made to the application will be immediately available. Now it’s easy and inexpensive for you to update your services. u Client Browser Clients can use almost any browser and they don’t need special hardware. They can also use any Operating System and version for which a web browser exists. Now it’s inexpensive for clients to access a server.

DB Databases Documents Enterprise Data Web Server CGI, SSJS, NSAPI, ISAPI, WAI, Etc. Client Browser Internet Connection Basic Web Applications

Robust Web Applications Presentation Tier Rich Clients (Java C/C++, VB ) Web Browser Business Logic Tier Web Servers Application Servers Data Tier Databases Enterprise C/S Applications Legacy Systems Documents HTTP IIOP

Requirements of Web-based Business Applications u Transaction Management Capabilities u Scalability u High Performance u Robustness u Security In order to deploy robust applications over the web, the web solution must deliver on the following key requirements for business critical computing:

Shortcomings of the Web for Deploying Business Applications u Lack of transaction management capabilities and stateless environment. u No model for application scalability. u Unpredictable performance under heavy and varying loads. u Difficult application deployment and management. u Lack of end-to-end security.

Netscape Application Server ( NAS ) u Rapid deployment of transactional applications. u Session and state management. u High scalability. u High performance. u Security. u Dynamic content generation. u Management capabilities. Netscape application server is a programmable application server. It provides all the core system and application services required to enable rapid deployment and facilitate management of high volume, transaction-based web applications. Some of it’s key features include:

Key Components of Netscape Application Server

Netscape Application Server Architecture

Netscape Application Server Components u Web Server to Netscape Application Server (NAS) Communication Communication between a web server and NAS occurs through NSAPI, ISAPI and optimized CGI. Communication with the web browsers occurs through the HTTP, SHTTP or SSL protocols. u Load Balancing System Incoming requests first pass through the NAS load balancing system, which directs requests to available servers for optimized processing under heavy loads. u Request Management System The NAS is a multi-threaded system and the Request Management System assigns threads from a dynamic thread pool to process the requests.

Netscape Application Server Components u Application Logic Processing System The application logic processing system handles all requests related to processing business logic. Requests are identified by their Globally Unique IDentifier (GUID) and checked against the Global Directory Service (GDS). The GDS determines the language of the application logic object. It then loads the appropriate language specific handler for the request.It could be a.class file for a java application or a.DLL file for a C++ application. u System and Application Services These services can be broadly classified into four categories:

Netscape Application Server Components u Administrative Services The administrative services provides us with a framework for managing distributed NAS and applications. It supports Java based administrator tools for easy point-and-click management of servers and applications.  Kernel Services It provides low-level services to all the other services and sub-systems. l Transaction Management System l Database Access Services l Presentation Services l Application Services

How does the NAS operate ? When a request comes in from a web browser, the request is passed to the web server via the HTTP, SHTTP or SSL protocol. The request is processed by the appropriate Web Connector such as NSAPI (for Netscape webservers) or ISAPI (for Microsoft web servers). The request is then forwarded to a correspondong Listener. The web connectors and listeners manage the passing of requests from the web server to the NAS. In a environment with multiple NAS, a request is first handled by the Load Balancing System. It then directs the request to the server best suited for this process. The Request management system

How does the NAS operate ? then assigns threads from a dynamic thread pool to process the request. The request is then handed to the application logic processing system where the appropriate application logic is executed to process the request. Application logic processing might involve calling one or more functions from the following subsystems:  Data Access Services such as database access operations and connection caching.  Transaction management system such as transaction manager and database request manager.  System and Application Services such as session manager and distributed state manager.  Presentation Services such as presenting formatted data to the browser.

NAS Applications as part of a three-tiered environment. The applications on a Netscape Application Server run in a distributed, three-tiered environment.

NAS Applications as part of a three-tiered environment. Client Tier The first tier is the client or user interface tier. The software providing the user interface can be either a web browser displaying a HTML page or a client application installed on desktop PC’s. Middle Tier The middle tier is the NAS. This tire consists of server machines running both NAS software and server-side application code. Database Tier The database tier consists of one or more database servers, which can be from different vendors.

Netscape Application Builder Rapid Development of Business Applications Wizards for Point-&-click Development Pre-built Application Services and Class Libraries (Java, C/C++) Reusable Application Components Distributed Deployment of Application Components Distributed Development Using Three-Tier Programming Model

Netscape Application Builder Robust Application Development Tools Application Logic Designer HTML Designer Query Designer Project Manager Third-party Tool Support

Netscape Server administration Advanced cluster management Enterprise-wide views of all servers and processes Event monitoring & alerts Multi-view graphical performance monitoring ACL, User & Group Management Load balancing customization Application administration Application partitioning Integrated deployment

Summary Key Benefits of the Netscape Application Server: n Enables Rapid Development of Business Applications n Provides Industry Leading Performance & Scalability n Provides High Availability & Reliability n Enables Enterprise Application Integration Allows Client-Independence (HTML, Java, C++, VB) n Provides Open & Extensible Architecture