You can use the Service Monitor to review and maintain the properties for each of the other Composer microservices. It provides a centralized location where Composer configuration properties can be maintained. However, it requires that the Composer configuration microservice be configured and started first.
The Composer configuration microservice is packaged with the Spring Cloud Configuration server, which allows Composer to easily integrate with its Spring-based microservices and provides the mechanism by which Composerproperty settings can be persisted in a supported PostgreSQL metastore or in a GitHub repository. The following diagram depicts this relationship.
If you have the configuration microservice configured and running in a high availability environment, you can maintain properties for microservices of a given type in a single location in the Service Monitor. For example, if you have two query engine microservices running in your high availability environment, you can change the properties for both microservices in a single location, ensuring that the query engine microservices operate in the same manner across the product nodes. A
config-server-upload.jar utility is provided that can be used to migrate the microservice properties from your standalone Composer servers to the Composer configuration data in the high availability PostgreSQL data store, where the configuration microservice can maintain them. For more information see Migrate Properties to the Configuration Server.
See the following sections: