Sangam 14 - My Experience

It was a proud moment for myself to attend and present in Largest Independent Oracle Event in India. The conference was very well organised by AIOUG and was a way to network and learn about latest trends in Oracle Stack. Though the conference had large number of  DBA's (Yes they are super people) sessions but there were also good amount of sessions for Oracle Fusion Middleware.

Session on Big Data by Satyender was an eye opener of where we are heading towards in way to store data apart from conventional RDMS. Its the way ahead and also for Application Developers. For application developers, we should know how to use NoSQL and Big Data databases for our applications.

Session at Sangam 2014 - AIOUG

I am proud to announce that I will be Presenting a Session at Sangam 2014 this year in Bangalore India.

Sangam is a yearly Oracle User Group Conference Hosted by All India Oracle User Group (AIOUG) and is the largest Independent Oracle event in India.


Below are the details of my Session :

Session           : 201421

Session Title   : Customizations of Enterprise Applications using Meta Data Services in Oracle ADF

Duration          : 50 Minutes

Track               : Development Track

The Session will be about Customizations and Personalizations of Applications using powerful XML based MDS framework provided by Oracle ADF. It will consist of introduction to Meta Data Services (MDS) and how MDS framework is enabled in ADF applications using Jdeveloper. There will be an explanation of how MDS works behind the scenes and how requests for Customizations are being persisted in MDS Store. Finally there will be a Demo of Personalization using Jdeveloper 12c.

I am excited to talk about this topic @ Sangam14.

See you there !!

Seeded Customizations using MDS in Oracle ADF

In the last post Personalization using MDS in Oracle ADF we saw the power of MDS Framework in Oracle ADF using which Users can personalize pages, components etc according to their own need. MDS saves these changes in MDS Store based on every user and applies on the runtime to the base document.

In Personalization, user is at the driver seat , changing things according to the needs. But there are cases where the application is developed and after there is a requirement of two different flavours of the same application. For example, there is a ADF application and there are two clients. One client wants some fields to be visible and some specific color settings while other client wants other fields to be hidden and different color settings. We can also put in this way, that one client want some regions (task flows) to be displayed and other client says other regions to be displayed.

Now in these cases the , making changes to the existing application will be difficult. Most common solution will be we create two versions of application , each version having specific changes required by the client. Hmm that works good for two clients but what will happen if there are hundreds, thousands of clients. One has to create / maintain same number of versions of applications. More to it, what will happen if there will be a common functionality change which needs to go to all versions. Maintenance will become a nightmare.

So by using Seeded Customizations provided by MDS, changes for specific needs / clients can be done on base document. There will be a single Base Application and changes corresponding to all the clients/layers will be done and these changes will be applied on runtime depending upon which client is using it..