Specifying the gateway type for an API definition
An API definition is specific to one or other of the gateway types, DataPower® API Gateway or DataPower Gateway (v5 compatible). A default gateway type is set when you create an API definition, but you can edit the API configuration to specify a different gateway type.
About this task
DataPower Gateway (v5 compatible) has been available with IBM® API Connect for a number of years. The DataPower API Gateway is a new gateway that has been designed with APIs in mind, and with the same security focus as DataPower Gateway (v5 compatible).
For more information on how to choose which gateway type to use, see API Connect gateway types.
You can complete this task either by using either the API Designer UI application, or by using the browser based API Manager UI.
You must specify which type of gateway each API uses. APIs can use only one type of gateway.
When you create an API, the gateway type defaults to that which matches the Gateway Service configuration for your Sandbox Catalog. If your Sandbox Catalog does not have a Gateway Service configured, or if the Sandbox Catalog has both types of Gateway Services configured, the gateway type defaults to DataPower Gateway (v5 compatible). You can use the user interface to update this setting.
Note that when you modify your API definitions to use a specific gateway type, you must ensure that each policy and policy version in the API are supported by the gateway type. DataPower Gateway (v5 compatible) and DataPower API Gateway each support policies that the other gateway type does not. In some cases, the same policy is supported by both gateway types, but with a different version number.
For example, DataPower Gateway (v5 compatible) supports version 1.0.0 of the invoke policy, but DataPower API Gateway requires version 2.0.0.
For information on policies, see execute.
For information on policy versions, see the documentation for each individual policy. For example, to review the invoke policy, see invoke.