Shared Elasticsearch on Openshift

Product/components used and version/fix level:

webMethods API gateway and Developer portal

Detailed explanation of the problem:

To reduce the number of node on Openshift deployment, we need to use a shared Elasticsearch service. I understand that this should be okay for logs and metrics but what about config and metadata? If API gateway use Elasticsearch to store information about API definitions then how can we separate this from logs and keep it safe?
Thanks for shedding light on this topic.

Error messages / full error message screenshot / log file:

Question related to a free trial, or to a production (customer) instance?

Usage of Externalized Elastic Search for storing core configs is also supported similar to trxn data. You can use same Elastic as well but do maintain different elastic indices and house keeping on deleting txn indices and not config indices.

Refer https://documentation.softwareag.com/webmethods/api_gateway/yai10-15/webhelp/yai-webhelp/pdf/api-gateway-administration-guide.pdf, page 93 for version compatibility checks.

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.