Installing the Experience Optimization Query service
The Experience Optimization Query service takes care of communication with the Experience Optimization Query Server.
- Copying resources for the Query service installation
Copy microservice resources to your target machine. - Configuring the Query service
Tell the Query service information about your Fredhopper setup. - Configuring logging for the Query Service
Configure logging by editinglogback.xml, the configuration file for the Logback logging framework used by Content Delivery. - Installing the Query service as a standalone microservice
Run the appropriate microservice installation PowerShell or Unix script to install and run the standalone microservice. - Securing the microservice with SSL
You may wish to secure your microservice using Secure Socket Layer (SSL), so that an HTTPS connection is required to interact with the service. If you do, you require a certificate signed and issued by a Certificate Authority (CA), a private key, and a keystore containing both of these. You then configure the keystore in the application.properties file of your microservice. You can reuse the same certificate, key and keystore for multiple microservices, so long as they are all running on the same machine. This section assumes that you have no certificate, key or keystore yet. If you do, you can skip the topics that do not apply. - Registering the Query Service as a Capability
You can make the Query Service discoverable through the Content Delivery Discovery Endpoint by adding it as a Capability to the Discovery Service's Storage Layer configuration file and then updating the Capability registry. - Copying resources for the Query service installation
Copy microservice resources to your target machine. - Configuring the Query service
Tell the Query service information about your Fredhopper setup. - Setting a log location for your microservice
By default, Content Delivery microservices write their log files to a folder called c:/SDLWeb/log/. Set a proper location in the Logback configuration file for your microservice, logback.xml. - Installing the Query service as a standalone microservice
Run the appropriate microservice installation PowerShell or Unix script to install and run the standalone microservice. - Securing the microservice with SSL
You may wish to secure your microservice using Secure Socket Layer (SSL), so that an HTTPS connection is required to interact with the service. If you do, you require a certificate signed and issued by a Certificate Authority (CA), a private key, and a keystore containing both of these. You then configure the keystore in the application.properties file of your microservice. You can reuse the same certificate, key and keystore for multiple microservices, so long as they are all running on the same machine. This section assumes that you have no certificate, key or keystore yet. If you do, you can skip the topics that do not apply. - Registering the Query Service as a Capability
You can make the Query Service discoverable through the Content Delivery Discovery Endpoint by adding it as a Capability to the Discovery Service's Storage Layer configuration file and then updating the Capability registry.