1) The end user on the web makes a request to display data from the Oracle database
2) The request is received by the Web listener, which creates a connection with the Web Request Broker. The request is routed to a Web Request Broker. This can be a CGI, (WRB) Web Request Broker, or other custom software that intercepts the incoming reports
3) The request is then parsed by the broker and translated into a database request
4) The request is routed to the database server via Oracle Network Services where it is intercepted by the Oracle listener
5) The listener establishes a connection to Oracle and passes the SQL to Oracle for execution
6) The Oracle database services the request and sends raw row data back to the broker.
7) The broker then re-formats the row data into HTML or ASP
8) The resulting Web Page is routed back to the requesting Web users
Multiple factors affect the performance of a Web database application. As Oracle DBAs, we need to examine the database interface layer, and how the table row requests are serviced by the Oracle database.
Our tuning opportunity is from the time an URL request is intercepted until the Oracle transaction is completed and returned to the client. We
need to focus on the processes happening between the time the query enter the Web request broker, and the result row data
is shipped to the Web broker. This is the same Oracle database that is used in other environments, using a web-based front-end interface.
The next lesson is about the Web Request Broker, its components, and how they function.