...
By default, the API Gateway cache is enabled because the <EnableGatewayTokenCache> element is set to true in the <API-M_HOME>/repository/conf/api-manager.xml file:
| Purpose | Configuration Elements |
|---|---|
| Enable the API Gateway |
| Cache | Under |
| Disable the Key |
| Cache | Under <CacheConfigurations>, set <EnableKeyManagerTokenCache>false</EnableKeyManagerTokenCache> |
| Note |
|---|
If you need to enable Gateway caching across the entire cluster, see Working with Hazelcast Clustering. However, WSO2 does not recommend Hazelcast clustering, because you can seamlessly deploy WSO2 API Manager using local caching in a clustered setup without using Hazelcast clustering. |
...
| Purpose | Configuration Elements |
|---|---|
| Disable the API Gateway cache.Cache | Under |
| Enable the Key Manager cache.Cache | Under <CacheConfigurations>, set <EnableKeyManagerTokenCache>true</EnableKeyManagerTokenCache> |
| Change the key cache duration, which Key Cache duration (By default, this expires after 900 seconds by default). | <TokenCacheExpiry>900</TokenCacheExpiry> |
...