Request Transformation
The Request Transformation action specifies:
The XSLT Transformation File to transform request messages from clients into a format required by the native API.
In some cases a native API might need to transform messages.
For example, you might need to accommodate differences between the message content that a client is capable of submitting and the message content that a native API expects. For example, if the client submits an order record using a slightly different structure than the structure expected by the native API, you can use this action to transform the record submitted by the client to the structure required by the native API.
When this action is configured for a proxy API, the incoming requests from the clients are transformed into a format required by the native API, before Mediator sends the requests to the native APIs.
Input Parameters
Transformation File | File. Mandatory. Click Choose, select the XSL transformation file from your file system and click OK. When you virtualize an API, the transformation file is validated. If there are no validation errors, the XSLT file is displayed as a download link in the same dialog. If the transformation file is invalid (for example, non-XSLT file), this will be indicated by a warning icon. Note: | If you make changes to the XSLT file in the future, you must republish the API. |
Important: | The XSL file uploaded by the user should not contain the XML declaration in it (for example, xml version="1.0" encoding="UTF-8"). This is because when the API is published to Mediator, Mediator embeds the XSL file in the virtual service definition (VSD), and since the VSD itself is in XML format, there cannot be an XML declaration line in the middle of it. This can lead to unexpected deployment issues which can be avoided by making sure the XSL file does not contain the declaration line. |
|
