Release Date: 19 September, 2014


Note: Version upgrade (from 7.5.1410.0 to 7.5.1800.0) as we addressed issues related to data purging, monitoring service high availability, and improved the performance while searching for an application in the Search Artifacts section.


Table of Contents


Performance Improvements

Issue
Issue Description
Module and Section in BizTalk360
Slow performance while retrieving the list of applications The application response was very slow while retrieving the list of applications from the Search Artifacts page. This was because every time the list was generated, the service retrieved the run status and configuration status of the applications. Therefore, when there were many applications in the environment, retrieving the list took a longer time. This issue is fixed and now while generating the list of applications, the service only pulls the status for the applications that will be listed instead of all the applications. Search Artifacts > Applications


Bug Fixes

Reported Issue
Comments/Fix Provided
Section in BizTalk360
Warning visual cue next to description in the email notification In the email notification (for configured alarms), the alarm description section displayed the warning visual clue (colored box) next to the description information. This issue is fixed and the email notification will no longer contain the visual cue next to the alarm description. Email notifications
Data purging not happening as expected and database size growing unexpectedly The data purging sub service was executing as expected only for the first iteration (after the monitoring service was restarted). The service did not run subsequently, and this resulted in bloating of the database size. This issue is fixed and now data purging happens as expected in every cycle and avoids bloating of the database size. Settings > BizTalk360 Health > Data Purging (Service Level)
Issue with the monitoring service High Availability The high availability logic in BizTalk360 was not functioning as expected and all the machines were running at a point of time. As a result, there was high CPU usage on the machines. This issue is fixed and the high availability logic works as expected. Settings > BizTalk360 Health > High Availability Status