Enabling Developer Portal feature flags on OpenShift and Cloud Pak for Integration
Use a template override to update the installation CR with settings that control the default behavior of the Developer Portal subsystem.
About this task
You can add a template override to the Developer Portal subsystem CR to change the default behavior of the Portal subsystem, or to turn specific features on and off. Table 1 describes the available feature flags.
Feature flag name | Default value | Pod | Container | Description |
---|---|---|---|---|
DISABLE_MEMCACHE |
false | www |
admin |
Controls whether the distributed in-memory cache is disabled. From IBM® API Connect 10.0.5.6
Portal web sites use a distributed in-memory cache by default, instead of using cache tables in the
main site database. This update provides better performance for web site operations, but does mean
that the cache needs to be repopulated when any of the Portal pods or virtual machines are
restarted, for example, during an upgrade. While the cache is being repopulated, there is a
reduction in performance. You can set the |
ENABLE_TRUSTED_REVERSE_PROXY |
false |
www |
admin |
Controls whether the Drupal If you have multiple load balancers and reverse proxies in your upstream network, and the
perimeter module is triggered, the incorrect IP address might be banned rather than the intended
client IP address. However, you can manage which IP addresses are banned by using the Drupal
The Drupal module inspects the To use this module, you must ensure that all of the proxies in your upstream network, including
the ingress controller, are configured correctly so that the
x-forwarded-for header
is passed through to the portal-www pod. For example, the default behavior of the
nginx-ingress-controller is to ignore the inbound x-forwarded-for
header, and create a new one. To change this behavior, update the
nginx-ingress-controller
configmap with the following information:
Warning: Enable this feature flag only if you
trust your upstream reverse proxies, as it is possible to trick the
x-forwarded-for
header. |
MEMCACHE_MEMORY_LIMIT |
"128" or
"256" |
www |
admin |
Controls the amount of memory that the distributed in-memory cache can use, before space is freed up by removing the least used entries. The default memory limit value depends on your deployment profile, for example:
DISABLE_MEMCACHE setting, or change the memory limit
by setting a specific MEMCACHE_MEMORY_LIMIT value. Note that the value is always in
MB, and is always set as a number enclosed in quotes, for example "512" .Note:
|
PORTAL_SKIP_WEB_ENDPOINT_VALIDATION |
false |
www |
admin |
Controls whether the Portal subsystem checks whether the Portal web endpoint is accessible. Sometimes, the endpoint cannot be reached, for example due to the complexity of the networks. In
which case the following type of error can be seen in the
portal-www pod, and
admin container
logs: You can
disable the check by setting this flag to true . |