1 / 46

Web applications and Oracle

Web applications and Oracle. FIS 432/632. Intranets, Extranets, and the Internet. The Ideal Client. The Five Wa y s of Building Oracle Web Applications. Java Servlets (and J a va Server Pages) PL/SQL Stored P rocedures (and PL/SQL Server Pages) Designer PL/SQL Web Generator

rusty
Download Presentation

Web applications and Oracle

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Web applications and Oracle FIS 432/632

  2. Intranets, Extranets, and the Internet

  3. The Ideal Client

  4. The Five Ways of Building Oracle Web Applications • Java Servlets (and JavaServer Pages) • PL/SQL Stored Procedures (and PL/SQL Server Pages) • Designer PL/SQL Web Generator • Oracle 9i Application Server Portal (previously called WebDB) • Oracle Developer (Forms and Reports)

  5. Java Servlets

  6. Java Servlets • The user requests a Web page (by typing in a URL, clicking a link, or pressing a button). • The Apache HTTP server determines that the request is for a Java servlet and passes the request to the mod_jserv module. • The mod_jserv module passes the request to the JServ servlet engine. • The JServ servlet engine loads the requested servlet, creates a request object, which includes all the information from the request, and a response object, and passes both to the servlet. • The servlet class executes, using JDBC to connect to the database if necessary. It writes the output to the response object.

  7. Advantages and Disadvantages

  8. PL/SQL Web Applications

  9. PL/SQL Web Applications • The user requests a Web page by typing in a URL, clicking a linkor pressing a button. • The Apache HTTP server determines that the request is for a PL/SQL stored procedure and passes it to mod_plsql. • The mod_plsql module uses the information in the URL along with the configuration information in the Database Access Descriptor to determine to which Oracle user in which database it should connect. It then invokes the procedure in the database. • The stored procedure runs, using the procedures in the HTTP package to write output in a buffer. • The mod_plsql module returns the output in the buffer through the Apache HTTP server to the Web browser.

  10. Advantages and Disadvantages

  11. Oracle Designer • Normal PL/SQL Web applications, i.e. HTML-based • Desired functionality is modelled in the Designer tools together with the data model • Designer PL/SQL Web Generator produces PL/SQL code from the model

  12. Advantages and Disadvantages

  13. Oracle Portal • HTML-based (using PL/SQL) • Browser-based: All development work is done in the browser with Wizards • Portal generates PL/SQL stored procedures making extensive use of special Portal packages

  14. Advantages and Disadvantages

  15. Oracle Forms: Getting the Forms Applet to the User

  16. Oracle Forms: Getting the Forms Applet to the User • The user requests the first Web page of the application. • The Apache HTTP server determines that the request is for a CGI program and passes the request to the mod_cgi module. • The mod_cgi module starts the Forms CGI program. • The Forms CGI program produces an HTML page with an instruction to load the Forms applet. • The HTML page is passed back to the Web browser through the mod_cgi module and the HTTP server. • The Web browser automatically requests the Forms applet from the HTTP server (and possibly the JInitiator Java plug-in). • The HTTP server delivers the Forms applet (and JInitiator) to the Web browser, that starts the JVM and the applet.

  17. Oracle Forms: Running a Web Forms Application

  18. Oracle Forms: Running a Web Forms Application • The Forms applet contacts the Forms Listener to start a session. This connection does not involve the Apache HTTP server in any way—it goes straight from the applet to the Forms Listener. • The Forms Listener starts a Forms Runtime Engine for that client. • The Forms Runtime Engine establishes a connection to the database and to the client applet.

  19. Advantages and Disadvantages

  20. Oracle Reports

  21. Oracle Reports • The user requests the report by typing in a URL or clicking a link. • The HTTP server passes the request to the mod_cgi module. • The mod_cgi module invokes the Reports CGI program. • The Reports CGI or servlet reformats the request and passes it on to the Reports Server. • The Reports Server checks whether the desired report already exists in the report cache. If the report is not in the cache, the Reports Server assigns the report to the next available Reports Runtime Engine. • The Reports Runtime Engine connects to the database, retrieves and formats the data, and writes the report in the cache. • The Reports Server instructs the requesting Web browser to pick up the report through the HTTP server. • The Web browser requests the report from the Web server. • The Web server delivers the report.

  22. Advantages and Disadvantages

  23. Choose Your Weapon • Who will be using your application? Intranet, extranet, Internet users? • How complex is the user interface you need?

  24. Building Applet-Based Applications • Using Web Forms • Using Java applets

  25. Building HTML-Based Applications • What language skills do your developers have? • Is it important to be independent of Oracle?

  26. Generating Applications If you can live with the user interface they offer, Oracles code-generating tools allow much higher developer productivity • Oracle Portal is fully browser-based: The application developer defines the application by filling in fields in a form • Oracle Designer is a full-featured CASE tool: The developer uses a number of development tools that work against a common repository storing a model of your application.

  27. Could I Have That in Writing? • Printing from Java applets is tedious (and is for security reasons disabled by default) • Printing from HTML gives only rudimentary control over the appearance of the printed page. • PDF format allows you to produce good-looking reports in a Web browser and on paper • Oracle Reports can produce reports in both HTML and PDF

  28. Summary • Heads-down users might need a Java applet application: Use Oracle Forms • Casual users and Internet users need an HTML-based application • Build HTML-based applications with Oracle Designer if you can • You can use either PL/SQL or Java for handwritten parts of HTML-based applications: • Java is vendor independent and offers the advantages of modern object-oriented programming • PL/SQL offers unbeatable performance for database-intensive applications. • Portal is promising as integration point for all applications, but not a real alternative for application development

  29. The Designer Approach • Computer-Aided Software Engineering • A Model stored in a Repository • Generates code at the push of a button • Many waysto use • Information Engineering • Rapid Application Development • Version Control possible

  30. The Designer Tools

  31. Building Applications with Designer Logical Data Design Data/FunctionMapping FunctionDesign Transform Transform Physical TableDesign Table/ModuleMapping ModuleDesign Database Tables etc. PL/SQL packages

  32. Advantages Disadvantages Using the E-R Diagrammer Using the Design Editor Building the Database When building the database, the end result is the same: tables in the database. But you have two ways of getting there: you can either start with an Entity-Relationship model in the E-R modeler or go directly to the Design Editor. Focus on logical design Several tools involved Entire design in one step Must code PK and FK columns

  33. Design Capture • Reading the definition of existing database objects into the Repository • Making changes in Designer • Generating a script to implement the changes

  34. Building an Employee List The hierarchy of objects: • Module • Module Component • Table Usage Context items:The columns appearingon the Record List

  35. The Basic Employee List Without setting preferences and applying formatting, the application doesn't look very appealing

  36. Important Generator Preferences

  37. Formatted Employee List Using a format package and a standard preference set improves the look

  38. Adding a Query Form • Appears automatically if any items are queryable • Intelligent date interval • Oracle interMedia Text querying

  39. The Query Form for the Employee List From and To date with pop-up calendar

  40. Maintain Employees • Continue your work on a copy • Add insert, update, delete functionality to the module component • Define operations on bound items

  41. Building an Employee List The hierarchy of objects: • Module • Module Component • Table Usage • Lookup tables

  42. Adding Lookups

  43. Employee Detail with Lookup Department name comes from lookup table Manager name selected via List-of-Values

  44. Multi-Record View Forms Multi-record View Forms are a Designer6i feature

  45. Master-Detail Design

  46. Master-Detail Web Page

More Related