The Web paradigm is very similar to the three-tiered client-server architecture.
WebServer performance and tuning can be addressed only from the time an URL request is received by the Web Listener, until the completed request has been serviced and returned to the client.
Most Web applications use some sort of alternative concurrency locking scheme because of the unreliability of the Internet.
Alternative locking schemes involve re-reading rows and comparing the current row contents to the prior row contents.
Web applications should have a separate server to handle and route the incoming Web requests.
Oracle provides many methods for Web connectivity, including the Web Request Broker, and CGI.
Oracle Web application should be designed only to retrieve the amount of information that the end-user desires on one page. Declaring and holding cursors can be unreliable.
This module covered the basic
concepts behind Web-based Oracle applications, and showed various techniques for maintaining Oracle performance.
Now that you have completed this module, you should be able to:
Describe how Web applications connect to an Oracle database
Describe the function of the Oracle Web Architecture
Use the Oracle Web Request Broker
Describe how Oracle manages incoming Web requests
Design Web applications for high performance
Show locking problems with Web applications
Describe and implement alternative concurrency mechanisms for Web applications
Glossary Terms
Here are some terms that may be new to you.
Hypertext Markup Language (HTML)
concurrency management
Execution Plan Techniques - Quiz
To complete this module, click the Quiz link below to check your knowledge of advanced execution plan techniques. Execution Plan Techniques - Quiz
