Contents x
    v8.4.3675.2104
    • 31 Mar 2021
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    v8.4.3675.2104

    • Updated on 31 Mar 2021
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article Summary

    Release Date: 21 April 2017

    Table of Contents

    • Brand New Features
    • Enhancements
    • Bug Fix

    Brand New Features

    FeatureAbout the featureModules and Section in BizTalk360
    Logic Apps Data MonitoringIn v8.1, we introduced Azure Services Monitoring and in the subsequent releases, we enabled operations on Logic Apps. In this release, we have added Data monitoring capabilities in Logic Apps, this will help the users in monitoring various performance Metrix logged by logic apps.Home > Monitoring > Data Monitoring
    IBM MQ MonitoringBizTalk360 now has the capability to monitor the health of IBM MQ for various parameters such as Current Queue Depth, Backout queue Depth, Current Queue usage, and Backout Queue Usage.Home > Monitoring > Manage Mapping > IBM MQ
    File location MonitoringBizTalk360 now has the capability to monitor File locations configured in BizTalk receive locations and send ports for file count and size threshold limits.Home > Monitoring > Manage Mapping > File Location
    FTP location MonitoringBizTalk360 now has the capability to monitor FTP locations configured in BizTalk receive locations and send ports for file count and size threshold limits.Home > Monitoring > Manage Mapping > File Location
    SFTP location MonitoringBizTalk360 now has the capability to monitor SFTP locations configured in BizTalk receive locations and send ports for file count and size threshold limits.Home > Monitoring > Manage Mapping > File Location
    BizTalk and SQL NT ServicesIn this release, BizTalk360 allows BizTalk and SQL NT services operations. The user can perform various operations like Start, Stop, Restart, Pause and Resume. The NT services operation will appear in a separate tab in the existing BizTalk Server Details and SQL Servers screens.Home > Operations > Infrastructure Settings
    SQL Server JobsWe have added a new tab to the SQL Server Instances screen to manage SQL Server Jobs in BizTalk360. With this feature, the user can Start and Stop SQL jobs from BizTalk360.Home > Operations > Infrastructure Settings
    BizTalk Server Licensing Information WidgetWe have a new widget added into Home Dashboard that will display the BizTalk Server License details. such as BizTalk edition, Server type, Processor, Manufacturer, Number of BizTalk Servers, Total number of license needed and estimated pricing.Home Dashboard

    Enhancements

    EnhancementComments/Fix ProvidedSection in BizTalk360
    BizTalk Health Monitoring (BHM)Previously, BizTalk360 had full support for MBV. Since Microsoft deprecated it and introduced BHM, there were few workarounds that our customers used to integrate BHM with BizTalk360. From this release, BHM is fully supported in BizTalk360 out of the box.Home > Operations > Infrastructure Settings
    Alarm ConfigurationsWe have now enabled options to rename alarms and bulk enable/disable the alarms. Earlier, the user cannot rename an alarm created in BizTalk360, now the user can change the name of the alarm and these changes will reflect in the Monitoring Dashboard as well.Home > Monitoring > Manage Alarms
    URL override in Webhook Notification ChannelIn the earlier versions, the users were unable to set alarm specific notification channels in BizTalk360. Now the user can override the Notification channel URL while creating a new alarm. This will help the user to set alarm specific notification channels.Home > Monitoring > Alarms
    Performance Enhancements in Logic Apps MonitoringWe have also improved the performance of Logic Apps Monitoring by creating separate API calls to get the Logic Apps data.Home > Monitoring > Manage Mapping > Azure Services

    Bug Fixes

    Reported IssueComments/Fix ProvidedSection in BizTalk360
    Alarm Export/Import issue in a multiserver environmentIn a multiserver environment, when the alarm is exported from one instance and imported to another instance the alarm did not work as expected. This issue is fixed and working as excepted.Home > Monitoring > Alarms
    Was this article helpful?
    What's Next