RelationalDBDesignRelationalDBDesign 


Web Applications   «Prev  Next»
Lesson 6Tuning tips for Web-based Oracle connectivity
Objective See how Oracle manages incoming Web requests.

Tuning tips Web-based Oracle connectivity

Replicated environment in Web interfaces to Oracle

The Oracle Web architecture has steadily evolved over the past few years. Like all very large database systems, most Web interfaces to Oracle databases use a replicated environment. Critical tables are replicated with Oracle snapshots into separate database schemas, often on different database servers. When a request is received, a customized Web listener directs the traffic to the least frequently used replicated database.
Remember to separate the performance issues associated with the WebServer from the Oracle database performance issues. The WebServer is an entirely separate piece of software with its own set of components, and is tuned independently from the Oracle database.

Web-based Applications and Client-server Applications

We can think of the models for Web-based applications and client-server applications as being very similar. A Web-based Oracle application can be viewed as a three-tiered client-server application.
The MouseOver below describes these similarities.

A client-server architecture has a PC-based client
  1. A client-server architecture has a PC-based client, just like the Web architecture.
  2. Just as a PC-client request will be intercepted by an application server, a Web-based request may be intercepted by a WebServer layer. This is known as the middle layer.
  3. Both the WebServer and the application layer format the request into an Oracle SQL data request and pass the request (via Net8) to the database server.
The next lesson discusses tips for designing Oracle Web applications.

Tuning Tips - Exercise

Before we continue, let us test your knowledge of Oracle WebServer components and architecture with a matching Exercise.
Tuning Tips - Exercise