Portal Application Sync Not Working If Using Legacy Portal Bundle
Document ID :
Last Modified Date :
Show Technical Document Details
CA API Developer Portal
CA API Management SaaS
CA API Management Gateway
CA API Developer Portal:Release:4.2
CA API Management SaaS:Release:4.2
CA API Management Gateway:Release:9.1
CA API Management Gateway:Release:9.2
CA API Management Gateway:Release:9.3
API MANAGEMENT SAAS:APIPRS
The CA API Gateway ("Gateway") may not sync applications with the CA API Developer Portal ("Portal") when legacy Portal bundles are used on the Gateway.
Bundles affected are those built pre-March 2016.
This issue can affect Gateway nodes integrated with Portal version 4.2.7 in SaaS environments (released June 11 & 12, 2018), and Gateway nodes integrated with on-premise Portal version 220.127.116.11, specifically if the Gateway nodes are using a Portal bundle dated prior to March 2016.
This issue is caused by a mix of older Portal bundle versions/build dates, and a table name change in the database.
Update the Portal bundle
on the Gateway to the latest version.
It is considered
best practice to update the Portal bundles
during the upgrade process, as noted in the
. This issue should not be seen as long as that best practice is followed.
The process of updating the Portal bundle on the Gateway involves a restart of the Gateway service on
each node in the cluster
before it takes effect.
Upgrade the Portal
Integrate On-Premise API Gateway/Proxies
Was this information helpful?