BHM
  • 20 Feb 2024
  • 3 Minutes to read
  • Dark
    Light
  • PDF

BHM

  • Dark
    Light
  • PDF

Article summary

Due to the licensing restrictions of BHM, BizTalk360 does not bundle BizTalk Health Monitor (BHM) during installation. Therefore, administrators must manually install BHM separately on the server where BizTalk360 is installed.
Follow the steps as shown below to configure BHM:

  • Download BHM Version 4 from this link
  • Extract the files to your preferred location in the server where BizTalk360 is installed
  • Run BHMSetup.exe
  • Once the installation is complete, Run the BizTalkHealthMonitor.msc file from the installed folder
  • Click Analyse Now button in the BizTalk Health Monitor MMC Snap-in window

Monitor multiple BizTalk Environments

The BHM Snap-in allows monitoring multiple BizTalk environments from a single MMC. When you register BHM on a BizTalk server, by default it will add one “group” node representing the current BizTalk group. You can, however, add additional nodes corresponding to different BizTalk groups by specifying its name, the location, and the name of its Management database and the output folder.

BizTalk-Health-Monitor-Add-BizTalk-Group.png

Each group node will have its own customized settings in terms of the level of information to collect, its level of information to display, its type of notifications to enable, and its type of performance data to collect.

Profile's Configuration in BizTalk360

Once BHM is installed in the server where BizTalk360 is running, the administrator needs to configure the integration with BizTalk360. You need to run the BHM from BizTalk360 under the "BizTalk Health Monitor (Reports)" section once you have configured BHM in the System settings screen.

Follow the steps as shown below to set up the integration:

  1. Log in to the application (as a Superuser)
  2. Select  the environment from the environmental panel
  3. Select Monitoring -> Manage Mapping -> BizTalk Environment -> BHM 
  4. Click on the Configure now link
  5. BizTalk Health Monitor Download Directory - Mention the path (the path used in 'Run' to open)

Once BHM is installed on the server where BizTalk360 is running, the administrator needs to configure the integration with BizTalk360.
To be able to monitor the output of BHM runs in BizTalk360, you need to have BHM configured in the System settings screen.

  1. To schedule Execution – Select the BHM_Profile from the drop-down for which the BHM execution has to be scheduled 
  2. Day/Time - Select the day and time when the BHM should run automatically. For example, selecting Monday to Sunday at 0500 hrs means that the BizTalk Health Monitor will run every day at 0500 hrs
  3. Click Save
  4. Select BizTalk360 Health, navigate to 'Monitoring Service Status' and observe if any exception is appearing in the exception column for BHM Schedule
  5. If any EULA-related exception appears in the process, go to the below section and install the BHM_EULA.reg in the server where BHM is installed
  6. Verify once again the exception is not appearing on the BHM Console
  7. Restart the BizTalk360 Monitoring service under services.msc. Now the BHM data will automatically be collected
In the latest version of BizTalk360 you can monitor the multiple BHM_Profile which are configured in the Environment Settings -> General -> BizTalkHeatlhMonitor.

Configuring the BHM Profiles  in BizTalk360 Monitoring

In BizTalk360 users can able to map one or more profiles against an alarm to set the threshold of critical or non-critical error. In the Monitoring section, all the BHM profiles will be listed (which are configured in the BHM environment settings). 

  1. Click any one profile's row from the list
  2. In the BHM Profile Monitoring blade provide the threshold of critical or non-critical error
  3. Click on Save
  4. If the threshold conditions meet the actual value the status of the Profile will be shown in the status bar.
  5. We can able to map multiple profiles in the same alarm.

If any error has occurred, the Monitoring dashboard will show up all the error details of the mapped profiles and the overall status of the BizTalk Health Monitor.

If any EULA-related exception appears in the process, check the below section and add the BHM Registry keys in the server where BHM is installed

  • Verify once again if the exception is not appearing on the BHM Console
  • Restart the BizTalk360 Monitoring service under services. msc. Now the BHM data will automatically be collected BizTalk Health Monitor, which just has been installed on the BizTalk360 server, needs to be configured in BizTalk360. Further, a schedule must be set up, to run BHM twice per business day; at 9:00 AM and at 6:00 PM.
Once the user is upgraded to the V10.1 or higher version the previously monitored BHM_Profile will be monitored in the name of BizTalk360SystemProfiles.

BHM EULA

This issue mainly happens on a 64-bit machine. When you accept the EULA displayed by BHM, it writes the acceptance setting in the 64-bit registry hive.

[HKEY_LOCAL_MACHINE\\SOFTWARE\\BizTalkHealthMonitor\\EULA]\n\"EULAAccepted\"=\"YES\"

But BizTalk360 is 32-bit due to restrictions imposed by dependency objects like ExplorerOM, hence it always looks at the 32-bit hive (WoW64 in a 64-bit machine). To fix this issue, please create the following entry in the registry.

[HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\BizTalkHealthMonitor\\EULA]\n\"EULAAccepted\"=\"YES\"

You can create the above keys by opening regedit.exe ("Run as Administrator").


Was this article helpful?

What's Next