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

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…

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…

Using LDAP for Authentication and Authorization within APEX

One of my current customers would like to use their LDAP (Microsoft Active Directory) server for authentication and authorization of APEX applications. Of course we tried to set up a standard LDAP Authenication that's available within APEX. But we couldn't get that to work. Maybe it has to do with the fact that the client stored their Users within Groups within Groups within .... . Or maybe it doesn't do a full tree walk in the directory. Or maybe it is just because it is Microsoft - and not Oracle Internet Directory (OID). So we moved to a custom Authentication using the DBMS_LDAP functions (and some examples from the Pro Oracle Application Express book and Tim Hall - a.k.a. Oracle Base).

One of the issues we encountered that we wanted to use the user's login name, like "jdoe" and not his full name ("John Doe"). And the login name is stored in the "sAMAccountName" attribute. But authenticating using just "jdoe" didn't work. …