Skip to main content
Support

KB Article #178746

Upgradeconfig fails to upgrade pre-7.5.1 configuration containing API Manager

Problem

Both upgradeconfig and Policy Studio's automatic upgrades fail to upgrade a pre-7.5.1 configuration containing API Manager with an error similar to:

7.3.x to 7.5.x:

ERROR 2017/06/14 21:19:44.465 KPS Table with alias: PortalOrganizationStoreLDAP does not exist.

7.4.x to 7.5.x

java.lang.IllegalArgumentException: Cannot refine property with name: expired, as this property is not defined in the type: API Portal_PortalVirutalizedAPI

or

[...]

Caused by: java.lang.Exception: Cannot find property type details for property: expired, type: API Portal_PortalVirtualizedAPI

Resolution

This is because the structure of the API Manager schema changed in Cassandra. Upgrade therefore requires not only a change in the FED, but also changes to the old KPS data so that it can be loaded in the new schema. All of these updates can only be performed by sysupgrade. So there is a limitation in that pre-7.5.1 FEDs containing API Manager cannot be upgraded using upgradeconfig or Policy Studio in some cases.


It may be possible to bypass this issue by checking for and fixing a possibly broken reference under: Policies —> Generated Policies —> Rest APIs —> Templates —> Default Portal-registered API, then exporting the default KPS stores from a default API Manager configuration (API Server, API Portal & OAuth) and importing them into the migrated policies.