Skip to main content

OOW2008 Afterthoughts


As Oracle Open World 2008 is 1,5 week behind us, it is about time to finish up my posts on this subject - and get rid of my notes. So let's take a quick look on the sessions I didn't mention already.


Forms2APEX Migration
David Peake introduced the "soon-to-come" APEX 3.2 release. The most important new feature (or maybe the only new feature) is the support for migrating Oracle Forms to APEX. He emphasized that there is no need from an Oracle support perspective to move from Forms to APEX. You should only go for this route if there is a sufficient business justification for it. A migration from Forms to APEX has to be considered as a real project, consisting of Analysis, Design, Convert, Post Migration, Acceptance and Training. The Forms2APEX toolkit is in no way a silver bullet. There will be a lot of handcraft involved to achieve acceptable results. Especially for more complex Forms you'll need a lot of effort to get similar functionality in APEX. Luckily the tool helps you to identify non converted code. Coming to a theatre near you at the end of 2009....

Inside the Oracle 11g Optimizer: Removing the mystery
A session somewhat out of the APEX scope, but nevertheless very interesting. The highlights of the new 11g optimizer stuff are:
  1. Full control over the execution plans, using SQL Plan Management (SPM). Using SPM, a change in an execution plan has to verified before it is actually used.
  2. Extended Optimizer Statistics to collect statistics over a group of columns.
  3. Improved Statistics Collection :
    1. AUTO_SAMPLE_SIZE - With the speed of 'estimate' (or even faster) you can get the quality of 'compute'.
    2. Incremental Global Statics for partitioned tables: global statistics are built from the partition statistics.
  4. Adaptive Cursor Sharing & Enhanced Bind Peeking: In version 10g and before an execution plan was determined by the initial value of a bind variable and the same execution plan is shared regardless the subsequent bind variables. But a select on emp 'where job=VP' returns only one row and will probably benefit of using an index on job. But if a select on emp 'where job=WORKER' returns 90% of the rows, the same execution plan is used. Starting from 11gR1 the same query can have more execution plans depending on the values of the bind variables. With Adaptive Cursor Sharing plans are shared when bind values are (more or less) the same and a new plan is generated when the binds are not equivalent.
Tom Kyte's Sessions
Tom Kyte did a number of sessions that week and I visited two. In one of the sessions - the Oracle Develop keynote - Tom did a great ad for APEX. He called APEX the best Oracle tool around, next to SQL Developer and SQL Plus!
Tom told the audience about his experience on the questions raised on the asktom-site. He gets a lot of questions regarding the tuning of queries. Most of the time the response is "Why would you do that?". So often it is better not to tune the query, but tune the question (or the process)!
In his session about managing change Tom announced that the long awaited Online Application Upgrade will be part of 11gR2 (ofcourse with the regular disclaimers). Oracle showed this impressive feature already at OOW in 2006 (see my post about that here), and it will finally make it into the next release of 11g!

The power of the APEX Repository
Patrick Wolf did an impressive presentation - with beautiful pictures Γ nd sound - on the repository. You can use the repository not only to store the APEX-metadata, but you can use the data inside also for quality checks, documentation, sitemaps, application page flow, generic code, monitoring and modification - using an export file or (more dangerous) directly in the tables.

Building large commercial applications with APEX
The guys from PAETEC impressed the audience with their presentation on the APEX version of Pinnacle, their tool for Service Life Cycle Management. It is a large application consisting of around 800 tables and 2000 pages in 19 applications. They build it in 2 years with 20 developers. So who dares to say APEX is only for Excel or Access replacement?
They extensively use the APEX repository to generate information on the pages and did some advanced tweaking by modifying the arrays used for rendering, just before the page is painted. Using their own framework they emphasized the separation of layers: Presentation with no validation at all, business rules using views and triggers and the data. So a three tier model, but with all tiers in the database!

Building a Web 2.0 interface with APEX
Marc Lancaster had the questionable honour to do the last APEX presentation of this OOW. He explained the advantages of Javascript, AJAX, JSON and external libraries. He is using ExtJS extensively on his demo site. To summarize:
• Takeaways
– AJAX doesn't have to use XML, or be asynchronous
– Javascript performance is rapidly improving
– Consider Namespacing when integrating Javascript libraries.
• Key concepts
– Start learning and using AJAX and JSON
– Progressively add functionality through templates
– Look for low hanging fruit
– Javascript libraries can do the heavy lifting
– Apex will us jQuery in version 4.0.
• Lessons learned
– Factor in time to build templates
– Always consider page loading performance.



Wrap up

To conclude, this year's OOW was again a huge event, and with lots of opportunities to attend good sessions, meet old friends and create new friends. Thanks to all who made this a unforgettable week!
2 comments

Popular posts from this blog

Showing a success message after closing a modal dialog

APEX 5 comes with Modal Dialogs out of the box. Very neat. Especially for adding and changing data. And to minimise the number of time a user has to click, it could be useful to add a "Close Dialog" process after the actual data processing. When the data processing fails, the Dialog stays on top showing the error. When data processing runs fine, the Dialog is closed ... without any confirmation. And this might be scary for a shaky user.

So how can we provide the user some feedback? On Page 4 of the Sample Dialog Application you can see one solution: up on a Dialog Closed Event on the parent page it does a redirect to refresh the parent page appending the success message of the "Close Dialog" process. This has two drawbacks. First, it probably refreshes more than necessary. And second, if you're using multiple layers of dialogs (dialogs that open other dialogs) the message appears in the "parent dialog".
As an alternative you could follow these steps: 1…

It's happening again ... running for the ODTUG Board of Directors πŸ˜‰

For the third time in a row I'll be running for ODTUG's Board of Directors. But after ending as a runner up twice, I am sure I'm going to make it this time! But not without your help!

My campaign statement this year is:
I have been attending and presenting at Kscope conferences since 2007. This not only resulted in a vast amount of knowledge, but also - and even more important - a huge number of friends from all over the globe.  I want to see ODTUG grow and spread this community feeling even more! 
My experience as an attendee, presenter and content lead has provided the basic foundation to be a director. Next to that, my personality and (global) network will be beneficial to the whole board and organization. 
Since March I have served on the Board of Directors in a limited term for a Director who stepped down due to a career change. This has allowed me to have unique insight of all the things that are going on in and around the ODTUG organization. As the train was already ro…

APEX 5 New Static File Features

In APEX 4 you could upload files - like CSS files, JavaScript files, Images and whatever else you like - into the APEX Repository. When you navigate to Shared Components, there is a Files section that offers three different options:
CSS Files are always uploaded (and changed !) for the whole Workspace. For Images and Static Files (usually JavaScript) you could choose whether they should be available for the whole Workspace or for a specific Application only. And if you had a lot of files - e.g. a lot of images - then you had to go through the upload process one-by-one. But that's usually a one time only thing. If you make changes to the CSS and JavaScript files - and that's a continuous process in development - then you had to delete the existing file and upload the new one. Over and over again. And meanwhile fighting the cache of the webserver and your browser.  And another irritating issue: You couldn't use relative references in your CSS or JavaScript files as they just…