BizTalk360 Version 8.4 Public Webinar
May 25, 2017
BizTalk Server Licensing Widget
Lot of BizTalk users struggle to understand how many BizTalk Server licenses are required for their servers. We at BizTalk360 thought it will be a good idea to transform that knowledge into a small widget in BizTalk360. Out of the box, BizTalk360 ships with this new widget in version 8.4 called as “BizTalk Server License”.This widget will display key information like BizTalk Server edition, server type, processor type, number of cores, processor manufacturer, retail license cost per server, how many servers to be licensed and total cost for the environment.
Data Monitoring for Azure Logic Apps
Data monitoring in BizTalk360 allows you to monitor and trigger alerts based on historical events. Some of the common use cases of data monitoring include “No Event Alerting”. Example: If you are expected to process 5 purchase orders from a FTP location every hour and you haven’t received the expected volume, then BizTalk360 can alert the user with a threshold violation alert.
We have taken the exact same concept to Azure Logic Apps to alert you based on historical transactions within a time window.
Technology might have improved significantly with concepts like Micro Services, REST API’s etc. However, File based integration is there to stay. It’s very common in the integration world where you drop a file (purchase order, batch file, EDI transactions etc) and the integration kicks in. One of the common challenge in such integration is that what happens when the integration is broken and the files start to pile up in the pick up folder.
One of the core values of BizTalk360 is to make configuration of monitoring seamless and that’s how we differentiate ourselves from other general purpose monitoring products. In the folder monitoring case, we automatically list down all the receive locations and send ports that uses BizTalk FILE adapter and allow users to configure monitoring in pretty much 2-3 clicks.
FTP based integrations are key in most of enterprise integration scenarios. BizTalk Server comes with three different adapters FTP, FTPS and SFTP to tackle FTP scenarios where the variations are mainly around the security capabilities of the FTP server. With BizTalk360 version 8.4, you can monitor FTP locations for data pile up. We have put a lot of effort to make the configuration experience as seamless as possible. The screen will automatically list all the FTP based send ports/receive locations and all the available values like location, username etc are automatically picked up from the configuration.
IBM MQ Monitoring
Queues play a vital role in enterprise integration especially for robustness, store and forward patterns etc. In the previous releases, we introduced MSMQ and Azure Service Bus Queue. In version 8.4, we are bringing in support for IBM MQ. We support both MQSC and MQS based configurations.
In any IBM MQ queues, you can monitor for the following 4 parameters – queue depth, backout queue depth, queue usage percentage and backout queue percentage.
BizTalk Health Monitoring Integration
For many years, we had support for Message Box Viewer inside BizTalk360. We periodically run MBV in configured environments, parse and store the result and display it in the BizTalk360 web console. We also got the ability to monitor and alert users based on Message Box Viewer raised errors and warning. Two years ago, Microsoft made some major changes to Message Box Viewer, re-branded it as BizTalk Health Monitor with few additional functionalities and deprecated MBV.
In BizTalk360 version 8.4 we introduced support for BHM and deprecated MBV support.
NT Services Operation in BizTalk and SQL Servers
One of the main objective for us from the security perspective is to stop people logging on/off into production BizTalk and SQL servers during business hours. We also wanted to audit any activities performed by BizTalk support people. Even though you shouldn’t start/stop services in your environment, we noticed in some cases NT services like world wide web, enterprise single sign on, BizTalk host instances, SQL Agent, etc needs to be started/stopped for the variety of reasons. Currently, users will RDP or have remote MMC snap-in to manage NT services in BizTalk and SQL servers. With BizTalk360 version 8.4, you can manage them directly in the web console. In addition, the activities will be audited by BizTalk360.
Manage SQL Jobs Operation from web console
SQL jobs play a vital role in a BizTalk Server environment. SQL Jobs are responsible for keeping your BizTalk environment healthy. They take care of routine house keeping activities like moving data from Message Box database to Tracking database, purging/archiving tracked data, backup/disaster log shipping etc.
In BizTalk360 version 8.4, we brought capabilities to manage SQL jobs directly from the web console. This functionality of monitoring SQL Jobs has been in the product for a very long time.
The BizTalk Health Monitor (BHM) feature in BizTalk360 version 8.4 will allow our clients to quickly configure, manage, and schedule health monitoring. Tallan is always looking to reduce our clients’ BizTalk administration overhead and BizTalk360 is a big part of that.
Version 8.4 of BizTalk360 goes one step further in monitoring BizTalk environments — Monitoring of file directories and FTP sites allows the monitoring scope to be extended to components that are often excluded from the view of IT teams.
The new features of version 8.4 takes it a step further, making BizTalk360 even greater. Especially the folder and FTP/SFTP monitoring feature are valued a lot in our day-to-day operations. It is also good to see that BHM now is supported.
Bouvet Norge AS, Norway