Oracle Apex Technical Introduction

2,364 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,364
On SlideShare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
91
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Oracle Apex Technical Introduction

  1. 1. Technical Overview Christian Rokitta 2010
  2. 2. Wat is APEX?● Historisch Overzicht● Techniek & Architectuur● Positionering● Functionaliteit/Features● Verder nog ...
  3. 3. 2010 Application Express 4.0Historie Websheets, Dynamic Actions, Plug-Ins, RESTful Web 2009 Application Express 3.2 Forms Conversion 2008 Application Express 3.1 Interactive Reports, BLOB 2007 Application Express 3.0 Flash Charts, PDF Printing, Access Application Migration 2006 Application Express 2.2 Packaged Applications 2006 Application Express 2.1 Oracle XE 2005 HTML DB 2.0 SQL Workshop 2004 HTML DB 1.6 Themes 2004 HTML DB 1.5 First Release
  4. 4. Architectuur OverzichtAPEX Listener●Embedded PL/SQL Gateway●ModPLSQL● 9iR2, 10g, 11g, XE
  5. 5. mod_plsql?! htp.print(Hello BOL);Oracle Web Toolkit
  6. 6. PL/SQL Web Toolkit
  7. 7. mod_plsql: DAD $ORACLE_HOMEApachemodplsqlconfdads.conf<Location /bol> SetHandler pls_handler Order deny,allow Allow from all AllowOverride None PlsqlDatabaseUsername bol PlsqlDatabasePassword bol PlsqlDatabaseConnectString lt-crokitta:1521:xe ServiceNameFormat PlsqlAuthenticationMode Basic PlsqlDefaultPage bol.hello_world PlsqlDocumentPath docs</Location>
  8. 8. PL/SQL Web ToolkitCREATE OR REPLACE PROCEDURE hello_worldISBEGIN HTP.htmlopen; HTP.headopen; HTP.title (BOL - Demo: Hello World); HTP.headclose; HTP.bodyopen; HTP.header (1, Hello World);
  9. 9. PL/SQL Web ToolkitCREATE OR REPLACE PROCEDURE hello_world (p_wie varchar2 DEFAULT World )ISBEGIN HTP.htmlopen; HTP.headopen; HTP.title (BOL - Demo: Hello World); HTP.headclose; HTP.bodyopen; HTP.header (1, Hello || p_wie);
  10. 10. APEX Passing Parameters (f?p syntax) f?p=App:Page:Session:Request:Debug:ClearCache:itemNames:itemValues:PrinterFriendlyApp: application ID or alphanumeric alias●Page: page number or alphanumeric alias●Session: Identifies a session ID●Request: Sets the value of REQUEST. Each application button sets the value of●REQUEST to the name of the button. This enables accept processing to reference thename of the button when a user clicks it.Debug: Displays application processing details. Valid values for the DEBUG flag are YES●or NO.ClearCache: Clears the cache. This sets the value of items to null.●ItemNames: Comma-delimited list of item names used to set session state with a URL.●ItemValues: List of item values used to set session state within a URL.●PrinterFriendly: Determines if the page is being rendered in printer friendly mode.●
  11. 11. ArchitectuurAPEX Listener ●Java based ●Certified against WebLogic, SUNOracle Glassfish, OC4J, Apache (, iAS)
  12. 12. Architectuur Page Processing●Show: page rendering process. It assembles all the page attributes (includingregions, items, and buttons) into a viewable HTML page●Accept: performs page processing. It performs anycomputations, validations, processes, and branching.Each request opens / closes Database session!!●
  13. 13. APEX DAD & DB Schema´s DAD APEX_PUBLIC_USER F APEX_040000SCHEMA_A SCHEMA_B SCHEMA_C
  14. 14. Architectuur Workspace
  15. 15. ArchitectuurIntegrated Applications
  16. 16. Use Cases Data-driven Applications Oracle Forms Modernization Develop opportunistic and departmental Leverage SQL & PL/SQL declarative productivity applications programming skills to move Forms applications to HTML / Web 2.0 Online Reporting Build SQL-based reporting applications on existing database schemasSpreadsheet Web-ification Access Replacement Consolidate outgrown Access applicationsConvert spreadsheets to Web applications to the Oracle database with an APEX Webwhere they can be concurrently viewed and front endedited
  17. 17. Departemental DatabaseDecentralized Development, Centralized Management
  18. 18. Rapid Application DevelopmentDesign Develop Deploy
  19. 19. Target Community
  20. 20. Wat is APEX?● Administration● SQL Workshop● Application Builder● Team Development
  21. 21. Administration
  22. 22. SQL Workshop
  23. 23. Application Builder
  24. 24. Team Development
  25. 25. Verder nog ...● SQL Developer Integratie● Runtime Installation● Release Deployment / OTAP / Versiebeheer
  26. 26. Export/Import1: Application Builder
  27. 27. Export/Import 2: Command Line Utilities● APEXExport.class - Java program used to export Oracle Application Express applications● APEXExportSplitter.class - Java program used to split Oracle Application Express export files into separate SQL scripts
  28. 28. Usage APEXExport used to export applications or workspaces -db: Database connect url in JDBC format -user: Database username -password : Database password -applicationid : ID for application to be exported -workspaceid : Workspace ID for which all applications to be exportedor the workspace to be exported -instance : Export all applications -expWorkspace : Export workspace identified by -workspaceid or all workspaces if -workspaceid not specified -skipExportDate : Exclude export date from application export files -expPubReports : Export all user saved public interactive reports -expSavedReports: Export all user saved interactive reports -expIRNotif : Export all interactive report notifications -expFeedback : Export team development feedback for all workspaces or identified by -workspaceid to development ordeployment -expTeamdevdata : Export team development data for all workspaces or identified by -workspaceid -deploymentSystem : Deployment system for exported feedback -expFeedbackSince : Export team development feedback since date in the format YYYYMMDD
  29. 29. APEXExportSplitterfilename-help : < print this syntax >-flat : < flat file structure >-debug : < print debug info >-update : < create update file >-nochecksum : < dont check for changes >
  30. 30. Command Line ImportAssumes you are running the script connected toSQL*Plus as the Oracle user APEX_040000 or as the owner (parsing schema) of the application.

×