CWP differences between API Gateway 10.1 and 11.0

Products

• CA API Gateway

Issue/Introduction

A question on upgrading API Gateway 10.1 to 11.0. The gateway was integrated with API Developer Portal 5.1.2.

After the upgrade of API Gateway and also the Portal was enrolled, some differences were found in the values of four Cluster Wide Properties (CWP) below. But, no documentation on these CWPs is found.

What does the CWP mean? And, does this difference have any impact on API Gateway behavior?

1. audit.acknowledge.highestTime
2. portal.application.increment.start
3. portal.deleted.apis.folderId
4. portal.l7.ratequota

Environment

Release : 11.0

Resolution

Here are answers to them.

1. audit.acknowledge.highestTime

This is internal CWP for watching over audit acknowledgment between policy manager and gateway. You may ignore it.

2. portal.application.increment.start

This CWP is used/set by the legacy Portal incremental application sync scheduler. The initial value is 0. It is updated by the current system time each time the application sync is triggered and executed. If the application sync is configured as a message-based sync, you can ignore this CWP. In Portal 5.1.2, if the proxies are upgraded to the latest Portal integration bundle or if the proxy is newly enrolled one, the application sync is automatically toggled to the message-based sync.

3. portal.deleted.apis.folderId

This is not used anymore. You can ignore it.

4. portal.l7.ratequota

This CWP value is set by the the Portal based on the Rate Limits and Quotas config on Portal side in order to apply the runtime enforcement. You can ignore the difference.