Skip to main content

Abstracts accepted for IOUG Collaborate and ODTUG Kaleidoscope

Last Friday I received a mail from IOUG Collaborate telling me my abstracts were accepted. It will be my first Collaborate attendance (and my first visit to Las Vegas), so I am very honored by that!
I will do the next two presentations there:

It's great to integrate: Integrating Oracle Forms within Oracle Application Express.
Since the release of version 3.2, the Oracle Forms migration toolkit is part of Oracle Application Express. This toolkit is not a silver bullet, so for complex Forms, labor-intensive adjustments in APEX will be necessary. To preserve investments in Oracle Forms and to prevent large re-investments in APEX, it is an advantage if you fully integrate existing Oracle Forms within Oracle Application Express.
In this session you will learn how to integrate existing Oracle Forms in Oracle Application Express pages and how you can make these two technologies communicate with each other.


Tales from a Parallel Universe: Using 11gR2’s Edition Based Redefinitions (in APEX).

Of all of the new features that are included in version 11gR2 of the Oracle Database, Edition Based Redefinitions could be the one that has the highest impact on the way we develop database centric applications. With Edition Based Redefinitions you can have multiple versions of the same object in your database schema in order to support multiple releases of an application at a time.
In this session you will learn what Edition Based Redefinitions are, how to use them and how this new functionality could change the way you look at your application development lifecycle.
In this presentation there will be lots of demos, to show the potentiality in an APEX environment.


A couple of hours later I received a similar mail from ODTUG Kaleidoscope that one of the abstracts I submitted was also accepted! The one I'll do in Washington is:

Creating sub-zero dashboard plugin for APEX with Google Visualizations

APEX is cool, Google is cool, Google Visualizations are even cooler. So the combination the coolest technologies available must be sub-zero.
Using the new APEX 4.0 plug-in features I will show how to create dashboards - with charts not native available in APEX - using Google Visualizations.


So I hope to see you all in either Vegas or Washington (or both!). In the meantime I have some time (and need it!) to create the presentations - 2 out of 3, because I already did the first one a couple of times - and white papers....
2 comments

Popular posts from this blog

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid. The use case I'll cover right here is probably more common - and therefore more useful!

Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user.The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even worse) while you…

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …

Using multiple Authentication Schemes for your APEX application

Recently someone asked me how he could implement multiple authentication schemes for his APEX application. He would like to use (some kind of) Single Sign-on authentication and - as an alternative - an Application Express Authentication. The problem is ... you can only define one Authentication Scheme being "Current" for an application! So how can we solve this issue?

First, we need te be aware that multiple applications can share their authentication by using the same cookie. Thus if you specify "MYCOOKIE" as the Cookie Name in Application A as well as in Application B, you can switch from A to B and back without the need of logging in again. It doesn't matter what Authentication Scheme Type you are using!

Knowing this, we are halfway our solution. We need two Applications. One - the "real" application - using the Application Express Authentication, let's name this one "LAUNCHPAD". And another one using the Single Sign-on Authentication…