Overview of Oracle applications on the Web
Optimizing Web database application performance
There are ways to optimize performance at the network, hardware, database, application, and content levels.
It is critical to understand that many factors can hamper Web database performance, and how best to optimize performance at each of these levels. Factors you should keep in mind are listed in the table below.
Optimize Performance Table
Oracle data request
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