Transform Step (REST Virtual Service)
Add the optional Transform step if you need to transform the request message into the format required by the native service, before CloudStreams submits the message to the native service.
As long as a consumer sends a REST request with the proper Content-Type, and as long as the HTTP method and endpoint URI are in the expected form, then CloudStreams can detect the correct service and operation; in this case, no message transformation is required. However, in some cases a virtual REST service might need to transform XML messages.
For example, you might need to accommodate differences between the message content that a consuming application is capable of submitting and the message content that a native service expects. For example, if the consuming application submits an order record using a slightly different structure than the structure expected by the native service, you can use the Transform step to transform the record submitted by the consuming application to the structure required by the Web service.
In this case, you would need to create two Transform steps:
One in the
In Sequence step, to transform or pre-process the request messages into the format required by the native service, before
CloudStreams sends the requests to the native services. To do this, you pass the message to an XSLT transformation file. (Additionally in this case, the transformation is required if the virtual service has a schema validation policy that validates the requests.)
One in the
Out Sequence step, to transform or pre-process the native service's response messages into the format required by the consumer applications, before
CloudStreams returns the responses to the consumer applications.