Configuring MDS Customisation Layer and Layer Value Combination in ADF by Andrejus Baranovskis

With this post I would like to dive a bit deeper into MDS customisation and layer combination handling. By default, there is defined customisation layer – site. Typically we set our own customisation values for this layer, as a result – all customisations usually are stored under site layer. There could be situations, when more advanced setup would be required – to be able to control layer and layer value combination in a custom way. In other words – to be able to define your own custom layer and then provide customisation values for this layer (MDS customisations will be stored under custom_layer/custom_layer_value, instead of default site/custom_layer_value). Oracle docs would not describe how to handle on runtime layer name to be dynamic and retrieve it from some sort of configuration file. I’m going to describe a technique for this, allowing to combine and group MDS customisations under custom layer and layer values folders.
Sample application – MDSCustomizationsApp_v3.zip is implemented with a separate JDEV project for MDS customisation files. There is no site layer, it starts with profile1/profile2 and then goes with MDS layer values group1/group2. Layer profile1/profile2 switch is dynamic and handled by custom MDS customisation class implemented in the project. This is how it looks like in JDEV (Customisation Context is set with profile2 name) – MDS layer name is retrieved from a custom JAR file stored under JDEV structure (I will describe it below): Read the complete article here