Transformation of a message into different formats is an essential part of business. SOA, as a integration product, has many options to perform transformation tasks. To name a few :
1. Mapset feature in Oracle B2B
2. XSLT transformation
1. Mapset feature in Oracle B2B: This is used for transforming the native data to another native format. This is highly useful for EDI, HL7 standard documents. This involves of creating a mapper file using Oracle Document Editor software using the 2 different document definitions.
2. XSLT transformation : This is based on XML standards and XSLT can be developed to build desired transformation. In order to use this feature for EDI, HL7 standard documents, it is required to translate the native file in to XML and then develop the XSLT using the required XSDs as definitions
Pros and cons of both the features
- Mapset can be used when the transformation is 1:1 and not multiple transformation. XSLT caters to fanout with different transformations
- Mapset need additional knowledge of Document editor and B2B, where as XSLT need the good knowledge of XML, XSD and XSLT syntaxes
- XSLT is widely used and have good set of expert resources availabitlity. Mapset is tightly coupled with B2B and not much of expertise
- Any changes to XSLT is easier than the changes for Mapset. Hence XSLT can be managed easily
- Mapset is limited to Native to Native transformation, where XSLT can be used for any combination of native (after translation to XML), XML formats
