Request Transformation policy properties
The table lists the properties that you can specify for the Request Transformation policy.
Property | Description |
---|---|
Condition | Conditions are used to specify when the policy has to be executed. You can add multiple
conditions with logical operators. Available values are:
Click Add Condition and provide the following information and click Add.
For details about the variables available in webMethods API Gateway, see Variable Framework |
Transformation Configuration: Specifies various transformations to be configured. | |
Header/Query/Path Transformation for REST API and Header Transformation for SOAP API |
Specifies the Header, Query or path transformation to be configured for incoming requests.
You can add or modify header, query or path transformation parameters by providing the following information:
You can add multiple variables and corresponding values by clicking Add. You can remove any header, query, or path transformation parameters by typing the plain value or value with a syntax. Note: It is recommended not to modify the headers
${request.headers.Content-Length}
and ${request.headers.Content-Encoding} as webMethods API Gateway adds the right values for
these headers before sending the response back to client.For details about the variables available in webMethods API Gateway, see Variable Framework Note: Payload transformation does not happen automatically for content-type transformation. When you
change the content type, ensure that you do payload transformation. For example, if you change the
content-type header from application/xml to application/json, you must also change the respective
payload from application/xml to application/json.
|
Method transformation for REST API | Specifies the method transformation to be configured for incoming requests. Select any of the HTTP Method listed:
Note: When CUSTOM is selected, the HTTP method in incoming request is sent to the native
service. When other methods are selected, the selected method is used in the request sent to the
native service.
Note: Only Method Transformation happens when configured, but you have to take
care of adding payload during transformations involving method change like GET to POST, and so
on.
|
Payload Transformation | Specifies the payload transformation to be configured for incoming requests. Provide the following information:
|
Transformation Metadata: Specifies the metadata for transformation of the incoming requests.
For example, the namespaces configured in this section can be used when you provide the syntax for
XPath ${request.payload.xpath} For example:
${request.payload.xpath[//ns:emp/ns:empName]} |
|
Namespace | Specifies the namespace information to be configured for transformation. Provide the following information:
|