API Portal - Scheduled task is deleting APIs in proxy cluster

[MAURICIO SILVA]

Hello team,

Our customer has CA API Developer Portal product installed and the following topology was suggested by CA consultant:

A sandbox API Portal installation with two enrolled on-premise API proxy clusters: Testing and Acceptance
A production API Portal installation with one enrolled on-premise API proxy cluster: Production

The APIs are created through sandbox API Portal and automatically deployed to the testing API proxy cluster. Then, these APIs are deployed to the other API proxy clusters via GMU: acceptance proxy cluster and production proxy cluster.

In acceptance proxy cluster there is no problem, but in production proxy cluster the APIs are deleted by scheduled synchronization task . Probably because the deployed APIs there aren't in production API Portal.

Is there any solution for this issue and how could I copy the APIs created through an API Portal installation directly to another one?

Thanks a lot,

------------------------------
Silva, Mauricio
------------------------------

[Leandro Dantas]

If you create an API from Portal, to migrate it you need to create in Portal first then update the policies as needed with GMU.

You can accomplish this working with Portal API .

------------------------------
Sr. Consultant Services
HCL Enterprise Studio
------------------------------

[MAURICIO SILVA]

Thanks Leandro,

Do I have to create the same APIs in both Portal installations manually?
Is there no other way to migrate the APIs from a Portal installation to another one?

[Leandro Dantas]

For different portals you will have to migrate it manually. You can automatize it working with PAPI (Portal API)  to get API configuration from sandbox and publishing into production. 

https://docops.ca.com/ca-api-developer-portal-enhanced-experience/4-3/en/publishers/portal-api-papi

------------------------------
Sr. Consultant Services
HCL Enterprise Studio
------------------------------