Migrating gateway extensions
Use the appropriate procedure for migrating extensions to either a v10 DataPower® Gateway (v5 compatible) or a v10 DataPower API Gateway.
Migrating gateway extensions to a v10 DataPower Gateway (v5 compatible)
About this task
Follow these steps to migrate gateway extensions to a v10 DataPower Gateway (v5 compatible).
archive:unpackstep. No further manual steps are required.
Migrating gateway extensions to a v10 DataPower API Gateway
Before you begin
- Post-request assemblies are not compatible with the API Gateway and cannot be migrated using this process. Pre-request, post-response, and post-error can be migrated using these steps.
- Any modifications to the DataPower v5 Multiprotocol Gateway cannot be migrated using these steps
because the API Gateway does not use a Multiprotocol Gateway. The modifications will still be in the
gateway-extension.zipthat is pushed to API Manager, and the artifacts might still be imported to DataPower. These artifacts can be deleted from the DataPower appliance.
- Any load-balancer modifications cannot be migrated using these steps as the load-balancer DataPower object is not used in the same manner in the API Gateway. These artifacts can be deleted from the DataPower appliance.
About this task
You can migrate pre-request and post-response global assemblies contained within v5 extensions to
API Gateway using the v5-emulation layer. The migration utility bundles the entire v5 extension file
and groups them by gateway service during the
port step. During the
push step, the v5 extensions are pushed to the Gateway Service, and pre-hook and
post-hook global assemblies are enabled using global policy files that were generated previously
port-to-apigw step. DataPower object modifications or additions that are
not v5 framework changes or load-balancer changes are also automatically imported during this
Global assemblies that are pre-request or post-response are utilized through the v5-emulation
layer as an Assembly Function. They are referenced by the global policy files auto-generated by the
migration utility during the
gateway-extension.zipfile is pushed to the DataPower API Gateway service.
gateway-extension.zipthat is pushed to the single gateway service.