Layer7 API Management

We have a requirement to migrate APIs from one Portal instance (Portal 4.2) to other, for e.g. from Development Portal instance to UAT Portal and Production Portal instances. Development API Gateway is enrolled with Development Portal instance while UAT API Gateway is enrolled with UAT Portal Instance. While the below documentation suggest steps to manage API deployments across proxies on the same Portal instance, there is no documentation around migrating APIs from one portal instance to other. It would be good to know how other projects are handling this type of requirement.

Manage API Deployments - CA API Developer Portal - 4.2 - CA Technologies Documentation 

Hi:

Many customers are using Portal API's  (PAPI) to manage migration of Portal Entities between environments if there are separate Portals in each.  A couple of notes:

• check documentation at Portal API's documentation
• utilize a Configuration Repository to release manage objects moving between environments
• are API's Portal published or Gateway Published?  For Gateway published you will have to make sure any dependent policy is migrated to the enrolled gateway using the Gateway Management Utility (GMU) or manual export/import migration of policy. 
• if necessary, some customers have migrated all portal entities from one Portal environment to another and these need to be done in a specific order because of dependencies (e.g. Applications are dependent on API's).   Some have done this with tools like Postman and Javascript utility to simplify the process of moving many objects. 
• API design is important to be able to manage environment differences (e.g. backend routing URL).

Let us know if you are unfamiliar with using Portal API's and need some examples.  

Regards, Alex.