Migration of Portal 3.5 with 2 loadbalanced Gateway

Document ID : KB000118509
Last Modified Date : 16/11/2018
Show Technical Document Details
The migration of portal 3.5 to 4.2.x can be done using https://docops.ca.com/ca-api-developer-portal/3-5/en/migrate-to-enhanced-experience-api-portal
This article covers a use-case where 2 gateways are synchronize with 3.5 portal and needs to be ported to 4.2.x environment.

I'm currently migrating the 3.5 portal to the 4.2.8 version of CA Enhanced Portal, following these documentation links :
https://docops.ca.com/ca-api-developer-portal/3-5/en/migrate-to-enhanced-experience-api-portal/migration-prerequisites https://docops.ca.com/ca-api-developer-portal/3-5/en/migrate-to-enhanced-experience-api-portal/migration-prerequisites/changing-gateway-association-to-target-portal

How can I change the synchronization of  of my gateways (there are 2 nodes which share the same APIs and are load balanced) ? I would like to know the recommended way of doing this migration.


Enhanced Experience API Portal- 4.2.8 


Create 1 tenant with 2 proxies
Synchronize the first gateway by creating a proxy
Synchronize the second gateway by adding a new proxy

You can create the additional proxies on the EE Portal using /admin/api-proxy. Follow steps 5-7 and 11 on https://docops.ca.com/ca-api-developer-portal/3-5/en/migrate-to-enhanced-experience-api-portal/migration-prerequisites/changing-gateway-association-to-target-portal to connect the Gateway to the Portal proxy.

Additional Information:
Other relevant links for migration