Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

The Readiness of ADF Essentials for Public-facing Web Applications

1,377 views

Published on

An investigation into the readiness of ADF Essentials as a low-cost, production-strength solution for a public-facing web application.

Published in: Technology, Education
  • Be the first to comment

The Readiness of ADF Essentials for Public-facing Web Applications

  1. 1. The Readiness of ADF Essentials for Public-facing Web Applications Darren Matchett – Lansen Consulting
  2. 2. Agenda • Part 1 – Choosing our tech • Part 2 – Review of JDeveloper 12c
  3. 3. My Background • • • • UK EFTPOS industry 8 years Converted to Java in 2007 ADF & WebCenter since 2010 Joined Lansen Consulting 2013
  4. 4. Lansen Middleware 1. Java Application Servers 2. Unstructured Data 3. Application Development Product Specialties • Oracle ADF and ADF Mobile, • Oracle WebCenter Portal, • Jenkins, Subversion, LoadUI, Ant and Groovy, • Oracle BPM. __________________________________________________________________ At Lansen we have embraced the Agile development methodology, with regular user sessions and development showcases to the business. We also encourage and champion the case for enhanced developer discipline, promoting features such as a continuous build process and a regular “code check-in” process for developers.
  5. 5. Agile Methodology
  6. 6. Problem Statement • New public-facing web application required • Must have a booking app capability • Must allow registered user access
  7. 7. Low Licence Cost Solutions
  8. 8. ADF Essentials – What’s Missing? • • • • • • • • • Mobile Desktop Integration Security Web Service Data Control Remote taskflows Business Component’s Service Interfaces Data Controls for BI Essbase and BAM MDS, OPSS, OWSM, EM, MBeans, HA and Clustering
  9. 9. ADF Essentials – Suitability? • Our app only impacted by: Security • J2EE JAAS security is a valid workaround • BUT – what about programmatic login?
  10. 10. Not this…
  11. 11. Nor this…
  12. 12. But like this.
  13. 13. If only we could use Java EE6…
  14. 14. Enter JDeveloper 12c • • • • • Released July 2013 ADF 12.1.2 Supports Java EE 6 Servlets 3.0 API compliant Supports GlassFish 3.1
  15. 15. JDeveloper 12c: What’s new? • This window when you open via icon:
  16. 16. JDeveloper 12c: What’s new? • Open via icon: • Open via project .jws file:
  17. 17. JDeveloper 12c: Oddities
  18. 18. JDeveloper 12c: Mangled PageDef!
  19. 19. JDeveloper 12c: Niggles • No auto date coercion between different date formats • Table properties:
  20. 20. GlassFish Highlights • CI remote deployment easier than WebLogic • Deploy to a cluster or single instance • Easy to set-up security realms
  21. 21. GlassFish Lowlights • No side-by-side/rolling deployments • Server needs regular maintenance – Clean-up and re-start every X re-deploys • Known issue deploying from JDev to remote GlassFish servers
  22. 22. JDeveloper 12c: GlassFish Performance • • • • Develop->deploy cycle extremely slow IDE freezes occasionally for no obvious reason Memory leakage – frequently need to restart Local GlassFish deployments regularly fail
  23. 23. JDeveloper 12c: GlassFish Deployment
  24. 24. JDeveloper 12c: GlassFish Debugging • Remote debugging works just as well as WebLogic • Hot JVM deploy works a treat while remote debugging • Changes to .jspx and .jsff however NOT automatically re-deployed
  25. 25. Recommendations • Use WebLogic for local development where possible – (break your code if you must!) • Re-start your local GlassFish server and JDeveloper regularly
  26. 26. Questions

×