DataPower API Gateway

v5 policy emulation limitations

This page details the limitations of v5 policy emulation for the current release.

  • The reverse solidus character (\) might be removed from policy property values.
  • The source parameter for XSLT and GatewayScript policies is base-64 encoded to preserve escaping. It cannot be easily viewed from the DataPower command line or the DataPower WebGUI.
  • Some DataPower service variables (for example, var://service/mpgw/skip-backside) might not be applicable in API Gateway, depending on how the variables are used.
  • User-defined policies that make any alterations to a DataPower context are not supported.
  • Execution of a 1.0.0 policy may fail if a previous 2.0.0 policy updates the message.body content type (for example, from XML to JSON, or JSON to XML).
  • A proxy 1.5.0 policy can return an incorrect response if it is the last action within a switch case or otherwise property. The response is parsed. The correct behavior is to not parse the response. To work around this issue, set the final-action:true parameter on the proxy.
  • Proxy 1.5.0 and invoke 1.5.0 policies do not preserve the gtid header.
  • The cache-putpost-response property is not included in the schema for invoke 1.5.0 and proxy 1.5.0 policies.
  • Setting HTTP response headers in a v5 user-defined policy, GatewayScript policy, or XSLT policy is not supported.
  • Non-UTF-8 characters are not supported.
  • JSON data returned in the response of an API running in v10 with v5 emulation is formatted without spaces.
  • The v5 user-defined policy emulation feature creates v5 compatible context. After running the user-defined policy, the emulation feature analyzes the context and converts it back to DataPower® API Gateway compatible context. The computations involved in this process might negatively impact the DataPower API Gateway performance. For better performance, use a non-emulated user-defined policy. For more information, see Authoring Policies for DataPower API Gateway.
  • In the V5E framework, the maximum file size for parsing XML data is 4194304 bytes. Currently, users cannot modify parse settings for GatewayScript.
  • API Gateway doesn't have XML Manager. Thus, all configuration set in XML Manager in v5 doesn’t take effect in v5e.