First of all, DVM is one of the features that will remain as a part of Oracle Service Bus in future. But yes, I’m not going to discuss how to create Domain Value Mapping (DVM) in ESB control. I will try to put some other information I have been working on and I have observed.
In a real time scenario there it is very common that two applications being integrated use two different values to represent the same information. Creating DVMs helps to hold a specific category of value mappings among multiple applications. Thus, multiple DVMs which are available across multiple applications enable you to associate values from one application with values from another.
Once DVM is created, you can find the metadata file at
The file containing DVM data can be found at
< ?xml version = '1.0' encoding = 'UTF-8'?>
< name="StateCodes" isnew="null">
<>Mapping of state names, abbreviations, and codes < /description>
<> < name="Long">< name="Abbrev">< name="Short"> < /columns>
< /cell> Massachusetts |Mass< /cell><>MA< /cell>< /row>|
California< /cell><> < /cell><>CA< /cell>< /row> Calif
< /rows> < /dvm>
You can always create the similar xml files manually. Just make sure that you keep the name of the file similar to the name attribute in DVM tag. Then you can simply import this new DVM in the ESB Console.
What looks like below at the design time,
< /imp1:name> <>
< /imp1:country> < /imp1:Root> < /xsl:template>
If you know only BPEL and ESB (or say the well-known SOA Suite), then you may also like to note that DVMs is used in implementation of AIA also.
So, is it the end of discussing DVM ? No, one last point. Typically in real time scenario, at the starting of development, you will get the list of code-value pair and generally they are very large in number. So, be prepared to create some Java program to make it .xml file which can be imported in ESB Console instead of entering all the code-value pair.
So, are you ready to work with DVMs?