There are multiple components and services replying on Strategy Messaging Services. For background, we will give a brief introduction about each component/service first.

• Kafka Producer in Intelligence Server:  This component sends all the telemetry data generated by the Intelligence Server to the Messaging Services layer.
• Kafka Producer in Usher Server: This component sends all the telemetry data generated by the Usher Server to the Messaging Services layer.
• Kafka Producer in New Export Engine: This component sends all the telemetry data generated by the New Export Engine Service to the Messaging Services layer.
• Strategy Telemetry Server: This layer serves as a message broker that receives and temporarily houses all the data sent by the above producers, which is using Kafka Server. 
• Strategy Telemetry Manager: This layer is the synchronization service between Telemetry Server(s),which is using Apache Zookeeper. 
• Strategy Telemetry Store: This service consumes all telemetry data from Strategy Services layer, and do ETL process for the Platform Analytics project, also named as Platform Analytics Consumer. 
• Intelligence Server Kafka Log Consumer: This service consume all Intelligence Server and New Export Engine Diagnostics log data from Strategy Services layer. 

How to Setup Messaging Services Cluster

There are two ways to setup Messaging Services Cluster. One way is to use Strategy Installation, another way is manual setup. 

Setup Messaging Services Cluster through Strategy Installation

Here are the instructions for how to setup messaging services cluster, the steps on windows and linux are almost the same. 

• Select Components: Express Install will include the Telemetry Server. If Custom Install is chosen, make sure "Strategy Telemetry Server" is selected (it's auto selected when "Strategy Intelligence" is selected).

• Telemetry Server Configuration: If you want to setup messaging services cluster, tick the check box "Create a cluster of three or more Telemetry Servers", input the local machine name and remote machine names separately into the two input boxes. (Note: three nodes is the minimum number for setting up Kafka Cluster to ensure high availability and consistency)

After Installing Telemetry on each of the nodes listed above, all the nodes will be joined into a cluster without any manual configuration. 
Note:  If the administrator runs the Strategy Installer as root on Linux, then Messaging Services will be registered as a service named "mstr-<InstallName>-kafka-zookeeper" after ticking the check box "Register Strategy processes as a service so that processes automatically start after system startup". The "InstallName" is in MSIReg.reg file in the installation folder, under [HKEY_LOCAL_MACHINE\SOFTWARE\Strategy\DSS Suite], the format is like "<user>@<date>T<time>". You also can even rename the service, or manually copy the <Install path>/kafka-zookeeper file to /etc/init.d after installation. Then you can start, stop and check Messaging Services by one command:  service kafka-zookeeper start/stop/status .