One of the main troubleshooting tools is MicroStrategy Health Center. It exists in order to help identify and fix issues with the MicroStrategy platform. In addition, it can send e-mails to the system administrator.
We already created Master Health Agent in order to set up Operations Manager. In Configuration Manager, we have two options: to create a Master Health Agent (MHA) or a Health Agent (HA). An MHA serves as a hub and collects information from HAs across networks. In other words, we can deploy HAs on every MicroStrategy Client, Intelligence Server, web server and Mobile Server in order to collect information about MicroStrategy components and hardware.
Let's look at the Health Center interface.
Go to the Linux server and open the terminal:
# cd /mstr10/microstrategy_home/HealthCenterInstance/bin # ./mstrsuppappgui
Enter the hostname, port, and password that was created in the Configuration Wizard:
Tip
You may notice that the name of the host has been changed. During the writing of the book, our VM with MicroStrategy crashed and we had to restore it from a VMware snapshot. It is very important to have backups of production MicroStrategy metadata as well as the operating system with the MicroStrategy Server installation.
We can build our topology by adding all the machines that are related to MicroStrategy implementation. There is detailed information about Health Center configuration on Linux at the following link: https://community.microstrategy.com/t5/Server/TN39868-How-to-configure-MicroStrategy-Health-Center-in-a-UNIX/ta-p/189920.