Skip to main content

Collaborate 2011 - Day 3

Day 3 started out with a 8 AM (!) presentation on Mobile Application Development. Didn't cover any APEX specific details, more about the general things to consider when developing these kinds of apps. Like how to handle multiple platforms, like IOS and Android - and over 10 others. Native apps are preferred above browser apps (and any APEX app will be a browser app). The solution for handling all these different platforms is to use a framework (like jQuery Mobile). For data integration, you should use webservices in order to keep the bandwith usage as small as possible.
The next session had the (lomg) title Enhancing your Data Warehouse Data Completeness using APEX. The presenter showed a (very simple) application to authorize and monitor Excel uploads and changes made to the master data of a data warehouse. Nothing very new...
Then David Peake presented on APEX integrating with E-Business Suite. Since v12, EBS doesn't support mod-plsql extensions anymore. But, luckily, there is a solution for that. You have to run EBS 12.1.3 and an additional patch, but then you're there.Recommended is you should set up a separate webserver and listener for APEX (using Glassfish and APEX Listener), and not use the APPS scheme for the workspace, but create a separate one with access to only the APPS objects needed for the customizations. All the details are in this whitepaper.
Last before lunch, there was a 30 minute session about APEX for DBA's. The message here was to kill all the spreadsheets and bring them over to APEX. Isn't always easy, but still worthwhile. The funny thing is, once the spreadsheet is turned into an Interactive Report, users downloaded that one again...in Excel..sigh.
Then there was a 3 hour break. Meant to spend time in the exhibition hall, but I thought the pool was a better place to be!
After that, I attended the session Developing Multi-client applications with APEX. In the presented solution multiple applications existed that are used by multiple clients - without seeing eachothers data. One master table (with the "client" info) was the parent to all tables - or the grandparent. And add an addtional line to the where clause of all queries. (I would have implemented the "client-id" in all tables to make it easier and use the VPD-properties built into APEX). Some smart customization stuff though: Using replacement strings (like &XYZ.) for customizing Tab labels, URL's and even colors and region widths in the templates!
Last session of today was the APEX Panel. Together with Scott Spendolini and David Peake, we tried to answer the questions from the audience. Good questions came up and we even ran 15 minutes out of time.
After the exhibition hall drinks, I attended the traditional ACE dinner. Good food and pleasant company!
1 comment

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…