Moving subscriptions to migrated products

Use the API Manager to move subscriptions from the v5-compatible products (and their APIs) to the migrated version of each product.

Before you begin

If you used the --move-subscriptions option while pushing provider organization data to API Connect, skip this task.

About this task

When you are satisfied that a newly ported product and its APIs are working as expected, run the Replace command to move any subscriptions from the v5-compatible API version of the Product to the migrated DataPower API version of the product. This step moves all the subscriptions and then retires the v5-compatible product.

For more information, see Replacing a Product with another Product.

Complete the following steps to move subscriptions from each v5-compatible product to the corresponding migrated product.

Remember: Repeat this task for every migrated product.

Procedure

  1. In the navigation pane of the API Manager UI, click Manage and select the catalog that you want to work with.

    The Products page displays all of the products available in that catalog.

  2. If the product that you want to work with is contained within a Space, click the Spaces tab and select the Space that you want to work with.
  3. For the product that you are replacing, (the v5-compatible version of the product), click the options icon More actions icon, and select Replace.
  4. On the Replace page, select the replacement product (the migrated version of the product), and click Next.
  5. Select which Plans in the migrated product correspond to each plan in the old v5-compatible product.
  6. Click Replace.
    If approval is required to replace products in this catalog, an approval request is sent, and the product moves to the Pending state; the Product is replaced when the request is approved. If approval is not required, the product is replaced immediately. For information on configuring Product lifecycle approvals for a Catalog, see Creating and configuring Catalogs. For information on approving requests, see Approving Product lifecycle and subscription requests.
    Note:
    • Approval for Product lifecycle state changes in a Catalog is disabled by default. You must explicitly enable the Product lifecycle state changes that you want to enforce.
    • Product lifecycle approvals can be configured only at the Catalog level. This feature is not available at the Space level.
    • You can view the history of Product lifecycle requests and approvals, by clicking the options icon options icon alongside the Product that you want to work with, and selecting View Approval History.