MDS support in OSB 12c

So here is the much awaited feature of OSB.

This was a big demerit in OSB 11g that it was not supporting MDS.

Though there were out of box solutions but we were always waiting for an inbuild solution from oracle to provide native support to MDS from SOA.And here in 12c they have provided this feature, Now you can access the MDS for common artifacts in OSB too.

However this MDS is a local store in your local machine or the machine where server is installed.

So for design time you are good and point the artifacts from local drive but at run time, the MDS artifacts will need to be migrated to OSB Server for reference just like we used to do earlier. So underlying mechanism is same however instead of saying local reference they have provide an automated structure to refer artifacts using MDS

We will try to understand this by creating a OSB proxy service based on a schema store in the MDS.

Lets drag and drop a pipeline activity in the pipeline/Split joins swim lane





Now in the next page select service as messaging type and select Request as XML type now in the Schema click onthe search icon and a new pop up gui will come. there click on import schema files as shown



And you can find out that you can now point it to the SOA-MDS artifacts








The MDS reference here is actually a local copy , the reference does point to oramds:/apps just like SOA MDS does will need to be imported as a local copy in OSB. Infact this is very much inline with the architecture of Service bus. A service bus is designed to have a stateless configuration, having a MDS support will defy this. So the conclusion is that 12c has made your life easy for development purpose and points all the common artifacts to MDS but underlying concept is same as we have used in 11g.