Query service configuration

You can build profiles for Ingest service customizations in ZooKeeper. Endpoints for configuring both development and production environment customizations are available. Note that these endpoints are available from within the Data environment and Development environment only. They are not available for the shopper to use through the Query service in either the Commerce Authoring or Live environment.

Basic authentication is used to protect all these configuration endpoints. A user having the search administrator user role can access all the configuration endpoints using basic username/password authentication.

ZooKeeper is used to store your custom configurations. At runtime, each microservice polls ZooKeeper for any custom configurations it may also have stored. It automatically overrides default behaviours such as query replies, and load custom applications such as new NiFi connectors. You can set up profiles in ZooKeeper, as well as specific custom search options such as units of measure and product colors. You can define endpoints for the REST API so that these customizations are accessible through the gateway.

Pushing ZooKeeper configurations from auth to live

Use the ZooKeeper configuration API to push all auth environment ZooKeeper configuration to the live environment. You can use the following REST API.
POST http://Zookeeperhost:zookeeperport/search/resources/api/v2/configuration/source/auth?destinationPath=configuration/live
Where:
destinationPath
The destinationPath parameter is mandatory. Not all configurations reside in the live and auth directories; one example is search profiles. The reason for this distinction is that certain configurations are foundational settings and it is not recommended that they be included with merchandising configurations.
Foundational settings affect the basic functionality of the Search runtime of auth and live and therefore should be kept identical between auth and live. This ensures that business users have the same store preview experience in the authoring environment. Search Term Association (STA) and Search rules are considered to be merchandising rules and are not related to deployment and customization. Consequently, STA and Search rules are managed by the Push-To-Live microservice. Search profiles are considered to be part of customization and are deployed with the Query image to higher environments. In this way, the search profile configuration works with the same level of code inside of the Query container.

You can configure and customize ZooKeeper in the following ways.