Externalizing Configurations
In API Gateway, the inter-component and cluster configurations are stored in different files. These configurations help to define how API Gateway connects with components such as Elasticsearch, Kibana, and Filebeat. You also use these configurations to define cluster configuration for API Gateway. With this feature, you can manage and provision the configurations from a centralized location using one or more configuration files. The configuration files can be in YAML or properties format. It can be either of the following ways:
A consolidated configuration file (defining all the inter-components and cluster configuration settings).
A set of individual files defining each of the inter-components (such as Elasticssearch, Kibana, and Filebeat connections) and cluster ( Elasticsearch and Terracotta) configuration settings.
The above mentioned configuration files are listed in the master configuration file, config-sources.yml. Both the master configuration and external configuration files are located in the SAGInstallDir\IntegrationServer\instances\instance_name\packages\WmAPIGateway\resources\configuration folder. Externalizing configuration helps the API Gateway administrator and operational teams to provision the API Gateway configurations dynamically.