What is coming in BizTalk360 Version 9.0 Phase 3?

What is coming in BizTalk360 Version 9.0 Phase 3?

We are super excited to share the list of features that are planned for our upcoming BizTalk360 release 9.0 Phase 3. We always aim to constantly improve our product in every release, based on customer feedback and their business needs. Generally, we release a new version each quarter. In August 2019, we released Version 9.0 Phase 2. Now Version 9.0 Phase 3 is planned for late November and our team is energetically working towards it.

Reporting for Analytics custom widget

The BizTalk360 Reporting feature offers out of the box capabilities that allow users to create schedules and generate PDF documents of critical performance metrics at specific time periods.

From v9.0 phase 3 on,  you can configure analytics custom widgets with the performance metrics of your BizTalk environment such as Messaging Performance, Message Transmission failure rate, Server performance, etc . and get that as a report, based on the schedule configuration.

For example, you can get a report by the end of the day with the number of messages processed for a particular schema or a particular send port.

Analytics-Custom-Widget-Report

Database Size Monitoring

This feature will be helpful for BizTalk administrators who frequently check the database growth to ensure the health of the BizTalk databases.

Some of the BizTalk databases can grow extremely big; it’s not uncommon to have over 1 million records in certain tables (ex: MessageInOutEvents table in Tracking Database). As the database size grows, the SQL server will need more memory and CPU to read data from the tables, and when the size of each table increases, it slows down the DB operations and affects the BizTalk operation.

With Database Size Monitoring, you can monitor the database and log file size of below BizTalk and BizTalk360 databases, by simply configuring the error and warning threshold values for the database and log file sizes.

  • BizTalkDTADb
  • BizTalkMgmtDb
  • BizTalkMsgBoxDb
  • BizTalkRuleEngineDb
  • BAM Db’s
  • SSODB
  • BizTalk360

For example, If the size of the BizTalkDTADb is greater than a threshold value configured, then you will get notified.

Database-Size

Configurable polling interval for monitoring

The BizTalk360 Monitoring Service usually runs every 60 seconds and checks for the status of the artifacts which are mapped for monitoring, which include Application artifacts, File/FTP/SFTP, Queues, web endpoints, etc. We got requests from a few of our customers that they have configured multiple endpoints for monitoring and the BizTalk360 monitoring service calls the endpoint for every 60 secs to check the status, but they don’t want to call the endpoints frequently i.e. every 60 secs. So, to improve this, we are providing an option to configure the polling interval for monitoring; depending on the configurated time, only then the monitoring service calls the endpoint.

SQL Server Cluster Monitoring

In BizTalk360, we have a BizTalk and SQL Server Monitoring which allows you to monitor the Disks, System Resources, Event Log, and NT Services. From this version on, we extend our support to monitor the SQL Server cluster. By configuring the SQL Server network name for monitoring, BizTalk360 will start monitoring the current active node and in case of failover scenario, BizTalk360 will automatically take the active server for monitoring.

SQl-Cluster

Sql-Cluster-2

Support SQL Authentication SQL Query

The standard BizTalk Admin Console does not come with any capabilities related to accessing SQL Server data. This leaves the support people to rely on external SQL tools like SQL Server Management Studio (SSMS). Tools like SSMS are designed for DBA’s and Developers, and it’s not particularly friendly when it comes to pure support and management; a level of technical expertise is required to be able to use SSMS. We understood the practical challenges of not having an integrated SQL data access tool along with the BizTalk Administration and the challenges it exposes.

That’s why we have already built the “Secure SQL Queries” feature in BizTalk360.

Using Database Query monitoring, you can set up thresholds that are limited to database scalar values. For every BizTalk360 Monitoring cycle, the monitoring service will validate the results of the SQL query against the configured threshold values. If any violation happens, it will trigger a notification to the configured emails in the alarms.

However, since BizTalk360 does not support SQL authentication, currently you cannot access Azure databases from Secure SQL query and in Database Query monitoring. From this version on, the product supports SQL authentication for database access. You can query your Azure databases from the BizTalk360 Database query monitoring and Secure SQL Query sections.

Logic Apps Improvements

From this version on, you can provide access restrictions for logic apps. Based on the role, you can define which user can manage (enable, disable, delete, trigger) the Logic Apps.

Additional details such as Version, Last Run Time and Last Run Status of the logic app will get listed in the grid.

Copy Alarm along with artifact mapping

The first step in monitoring by using BizTalk360 is to create Alarms. Alarms in BizTalk360 act like a package to associate things together. We already have an option to copy the alarm which will copy only the alarm configuration. Now we are extending this to copy the alarm along with the artifact mapping configuration.

Alarm and Monitoring Dashboard Improvements

Below are some of the improvements, we have planned for this release in the Monitoring section:

  • Indication of alarm status (Enabled/Disabled)
  • Last Execution Time of the alarm
  • Number of Alerts Notified (2/3)
  • Indication whether Auto Correct is enabled or not
  • The artifacts from the collapsed view will be made clickable to route to the respective configuration

Performance data collection improvement for DTA

We already optimized performance data collection in the last release. in this release, we are improving on DTA performance data collection. With this, we allow users to choose the relevant DTA metrics, which will reduce the number of calls to the DTA database.

Conclusion

Considering the feedback from our customers, BizTalk360 will continue to provide more useful features on every release.

Why not give BizTalk360 a try! It takes about 10 minutes to install on your BizTalk environments and you can witness and check the security and productivity of your own BizTalk Environments.

The post What is coming in BizTalk360 Version 9.0 Phase 3? appeared first on BizTalk360.

Integrate BizTalk Performance data with Dynatrace from BizTalk360

Integrate BizTalk Performance data with Dynatrace from BizTalk360

BizTalk360 is a one-stop tool for operations, monitoring and application performance management (APM) of BizTalk environments.

We get to see a few of our customers utilizing modern SaaS-based Application Monitoring/Analytics platforms like New Relic, AppDynamics, Dynatrace, etc., for their global enterprise analytics/monitoring requirements. In earlier releases, we have already integrated New Relic and AppDynamics in BizTalk360.

In BizTalk360 version 9.0 Phase 2, we have integrated Dynatrace in BizTalk360; with this, you can see the BizTalk Server related performance metrics in Dynatrace.

Why did we integrate Dynatrace in BizTalk360

Dynatrace is an APM tool which has a generic capability to monitor operating systems, network protocols, system metrics, network infrastructure, applications, etc. However, there is no out of the box Dynatrace plugin or agent for BizTalk Server. This means that the user needs to install an open-source plugin Fastpack (which has been updated a couple of years back and it is not up to date with the latest BizTalk release) on all the BizTalk Servers running in the environment, along with some configuration changes at BizTalk host instances config file btsntsvc.exe.config. BizTalk360 is an agentless, non-intrusive software product which requires zero configuration on BizTalk servers. 

Here you can see the BizTalk360 and Dynatrace comparison in detail.

As mentioned, few of our customers are using SaaS-based analytics platforms and they would like to see the BizTalk360 Analytical data (collected for BizTalk Server environment) over there. So we thought of integrating APM tools in BizTalk360.

How does BizTalk360 collect performance metrics

Unlike other tools, BizTalk360 doesn’t need an agent to be installed in the BizTalk Servers to collect performance data and it does not require any configuration changes at the server level. 

Just follow the below simple steps:

  1. In the BizTalk360 Analytics configuration section, choose the various performance counters that you want to collect data
  2. Enable the Performance data collection for the respective BizTalk/SQL servers of your BizTalk environment

BizTalk360-Analytics

That’s it! Now the BizTalk360 Analytics Service will start collecting the performance data for the selected performance counters in the respective servers.

The cool thing here in BizTalk360 is, it’s not required that the BizTalk360 Analytics Service should run on all the BizTalk (and/or SQL) servers in your BizTalk environment.

BizTalk360 has a purging policy with which you can easily maintain the collected performance data and, to avoid performance issues, purge it after the configured period.

How to Configure Dynatrace in BizTalk360

You can easily configure your Dynatrace environment in BizTalk360, by providing your Dynatrace environment details such as tenant id and API key in the Dynatrace configuration section under (BizTalk360 Setting -> Analytics Configuration).

BizTalk360-Dynatrace-Configuration

Ok, let’s see how BizTalk360 pushes the collected performance metrics to Dynatrace.

BizTalk360 Analytics Service holds a sub-service for Dynatrace which creates custom metrics in your Dynatrace environment for all the counters which you have enabled in the BizTalk360 Analytics configuration section. Each minute the sub-service will start pushing the collected BizTalk Server performance data to the respective custom metrics. These custom metrics data can be mapped to a custom chart and viewed in your Dynatrace dashboard.

To push performance data to Dynatrace, BizTalk360 uses the Dynatrace exposed TimeSeries API’s – “Custom Metrics” and “Post data point of a metrics”.

Note: In Dynatrace you have only 100 custom metrics available for free per environment. If you want to view more than 100 performance counters, then you need to purchase the custom metrics for the same from Dynatrace.

However from BizTalk360 V9.2, we provide an option to manage the performance metric data collection in Manage Analytics section (BizTalk360 settings->Manage Analytics ->Choose the Environment->Select the Server->Manage Metrics ), you can choose the required metrics for data collection as below. With this, you can limit the number of counters to be created in Dynatrace.

manage-performance-metrics

To be able to use the integration with Dynatrace from BizTalk360, you must have :

  • A Dynatrace environment details (tenant id and API key )
  • Enough custom metrics in your Dynatrace environment
  • BizTalk360 v9.2 or later. Download the latest version of BizTalk360 from –  http://www.biztalk360.com/free-trial/
  • BizTalk360 Platinum license
  • You must be a Super User in your BizTalk360 application to configure the Dynatrace environment in BizTalk360

How to view BizTalk360 Analytics data in Dynatrace

  1. Log into your Dynatrace Environment
  2. Create a custom chart widget in the dashboard
  3. Configure the custom chart by selecting performance categories, say BizTalk Messaging Performance, Failure Rate, Processor, etc. and select the respective custom metrics

You will start seeing the analytical data of the mapped custom metrics in the dashboard.

Below are some of the important performance metrics you can see in your Dynatrace dashboard.

BizTalk and SQL Server Health

  • CPU Usage
  • Memory Usage
  • Disk Free Space
  • Average Disk Queue Length
  • Network Performance
  • IIS Request Per Sec
  • IIS Worker Process: CPU Usage
  • IIS Worker Process: Memory Usage

BizTalk-Server-Health

Host Performance

  • Host Instance performance by CPU
  • Host Instance Performance by Memory
  • CPU Consuming Host Instances
  • Top 10 Memory Consuming Host Instances

Host-Performance

BizTalk Messaging Performance

  • BizTalk Host Performance
  • Documents Receive/Second
  • Documents Processed/Second
  • Inbound Latency (Sec)
  • Outbound Latency (Sec)
  • Outbound Adapter Latency (Sec)
  • Request -Response Latency

BizTalk-Messaging-Performance

Throttling Performance

  • Message delivery Throttling State
  • Message Publishing Throttling State
  • Message Delivery Outgoing Rate
  • Message Delivery Incoming Rate
  • Active Instance Count
  • Database Size
  • Database Session
  • Database Session Threshold
  • In-Process message Count
  • In-Process Message Count threshold
  • Message publishing incoming Rate
  • Message Publishing Outgoing Rate

throttling-performance

Conclusion 

Considering the feedback from our customers, BizTalk360 will continue to provide more useful features in every release. Why not give BizTalk360 a try! It takes about 10 minutes to install on your BizTalk environments and you can witness and check the security and productivity of your own BizTalk environments. 

The post Integrate BizTalk Performance data with Dynatrace from BizTalk360 appeared first on BizTalk360.

Recap of the BizTalk Sessions during Integrate 2019

Recap of the BizTalk Sessions during Integrate 2019

It was again time for the most awaited conference in the Microsoft Integration space and the execution happened successfully! INTEGRATE is a global annual conference organized by BizTalk360 for people working in the Microsoft Integration space. Here, we bring the highlights of all the BizTalk sessions at the #INTEGRATE 2019 UK. 

The Value of Hybrid integration – Paul Larsen

Paul Larsen, a Principal Program Manager for the Microsoft Corporation in Redmond, presented the session “The Value of Hybrid Integration” by explaining about the legacy of BizTalk Server and he gave meaning to the word Hybrid with some examples. He made the big announcement “BizTalk Server 2020” and confirmed that it will be released at the end of 2019. 

Paul announced the important feature updates in BizTalk Server 2020:

This version of BizTalk Server will have capabilities to deploy BizTalk Server applications using VSTS, make backups to Blob Storage and so on. It will also have integration with App Insights, Event Hubs, Power BI, etc. 

Migration Tool

Paul talks about the BizTalk Server Migration tool and Host Integration Server 2020. This Migration tool will be helpful on dehydrating our configuration on old BizTalk Server environments and rehydrate that configuration to new Azure IaaS VM’s or local VM’s. Microsoft IT developed the BizTalk Server Migration tool which they use to migrate their own BizTalk environments. Because the architecture of BizTalk Server is kept common between BizTalk Server 2010, 2013, 2013 R2 and 2016, the migration does not affect the underlying layer of BizTalk Components.

Logic Apps IBM 3270 Connector

Next, Paul made an announcement on the Logic Apps connectors for 3270 screen scraping which is available in preview. During an entertaining demo, Paul explained how the 3270 screens are used and how the 3270 Logic Apps connectors can be used.

 

BizTalk Server Fast & Loud Part II: Optimizing BizTalk – Sandro Pereira

Sandro Pereira, as usual, sets the scene of the session by comparing BizTalk Server Performance to different types of cars like Formula 1 cars, BMW cars, and Truck Cars. He explained the different parameters that affect the performance of BizTalk Server with the functioning of a car (Memory, Network, Disk Space, BizTalk Server, SQL Server).

Next, Sandro provided different tips to optimize the performance:

  1. What is your requirement? 
    To improve the performance of the BizTalk environment, choose the right set of infrastructure to manage your business requirement
  2. Message Processing (Slowing Down) 
    BizTalk message processing can be slowed down when there are quite huge volumes of messages. In that case, use queues to process the messages
  3. Techniques to optimize the performance 
    Sandro explained the different techniques which can be used to fix the performance issue  
      • Observation 
      • Analysis 
      • Apply Fixes
  1. Redesign the system 
    If an existing BizTalk solution is a bottleneck in the performance, you can suggest redesigning the solution to meet the business requirement and space, to scale the solution for future challenges.

  2. Move to Historic Data (Tracking) 
    Sandro explained how to manage historical data. Storing the data is important, but use the minimum tracking necessary, to avoid database and disk performance issues.
  3. SQL Server Memory optimization 
    Use SQL Server memory configuration to optimize the performance of the message processing. 


    Sandro then explained two real-time solutions in which performance improvement was achieved;

Cock Sector World Leader 

Sandro told about how the BizTalk Team scaled the solution when the performance was hit in one of the manufacturing sections; 

  1. Follow the sequences based on the number of messages (5 million messages) 
  2. Dividing the process – Parallel process (Queues) 
  3. Scaling up the SQL Server Tier 
  4. Move data to Historic (Enable the Minimum tracking) 

Banking System

Sandro explained how his team provided the solution with a Banking system, with an example of opening a Banking Account scenario. He gave various techniques used in the Banking Solution;

      1. Azure 
      2. API Management 
      3. Composite Orchestrations 

To process the data to open a banking account takes more than 1 min to process the data. Sandro explained the factors that affect the performance;

      1. Network/LDAP 
      2. Composite Orchestration Expression shape  
      3. Resources Unload (Slow First hit) 

He continued to be telling about fine-tuning the performance to process the creating bank account by;

      1. Improving warming up by Recycling BizTalk and IIS 
      2. Memory  
      3. IIS Application Pool 
      4. MQ Agent Recycling 

 He then explains various solutions to optimize performance; 

      1. BizTalk Polling Intervals in MQ Agent (Careful on the set the polling) 
      2. Tune the performance with multiple configurations 
      3. Orchestration Dehydration (Composite Orchestration) 
      4. SQL Affinity – Maximum amount of memory usage
      5. Priority in BizTalk: Set Priority Send port priority (10 lowest – 1 Faster) 

Scripting a BizTalk Server installation – Samuel Kastberg

Installing and configuring BizTalk server is not straightforward, and it can take a lot of time. It is useful to have scripts to run in a different environment and get everything in place. Samuel, Senior Premier Field Engineer at Microsoft, explains the importance of scripting BizTalk Server installation and during his session, he provides all kind of tips and tricks for scripting such an installation.

He listed what you should script:

    1. Things you can control
    2. Things you want to do it repeatedly
    3. Good Candidates
    • Windows Features
    • Provision VM’s in Azure (if the environment needs to be created in Azure)
    • BizTalk features and group configurations
    • MSDTC settings, Hosts, Host Instances
    • Visual Studio, SQL server
    • Your  favorite Monitoring tool
    • Bad candidate-Things which are going to change over time

Samuel advised considering below points before you start scripting;

    1. Decide what your main drivers are, repetition and control are the drivers to automate, standardized developer machines, disaster recovery preparation, and test environments
    2. Decide what your baseline is and document it, think what could change in 6 months or a year
    3. Document the execution process, scripting is not a replacement for the documentation
    4. Set a timeframe for your work

Reference – https://skastberg.wordpress.com/2019/04/13/automating-biztalk-server-installation-and-configuration/

Windows feature installation

  1. Choose different tools of your taste
  2. Use the Server Manager to check for the installed features

Ensure the features and configurations you need are in place and use PowerShell cmdlets to install the required Windows features.

BizTalk Server Feature Installation

Setting up the BizTalk Server product consists of installation and configuration. Installation adds the binaries to the system, while configuration enables you to create or join a BizTalk Group and enable/configure other features as Rules Engine, BAM and EDI.

Setup/Add Local – Export configuration .xml file (select the required features).

Installing CU/Adapter pack – More complex

Configuration File – Used for providing the required parameters

    1. Consists of feature element – Each one maps to specific sections in the configuration tool
    2. Each feature contains one or more questions – Answer attribute selected = True
    3. Export from config.exe
    4. Edit the export to be a template- Replace the real values at configuration time. You need one file while creating a group

Configure Host and instances – Use WMI or PowerShell provider

Create handlers – Use WMI and PowerShell

Handling secrets – Use KeyPass, Key Vault. KeyPass to use when no internet access is available.

Before using it in the real world: Test the Script in your environment!!!

Conclusion

Do you want to hear about the latest and greatest in Microsoft Integration? It’s not yet too late! By the end of the month, Integrate also comes to the USA and there are still tickets available! Check the web site!

 

The post Recap of the BizTalk Sessions during Integrate 2019 appeared first on BizTalk360.

BizTalk360 v9.0 Released

BizTalk360 v9.0 Released

It’s time to upgrade your BizTalk360 installation! We are here with our next release of BizTalk360, v9.0. We always aim to constantly improve our product based on customer’s feedback and their business needs. The features added in this release are typically chosen from our feedback portal and based on the impact and the number of requests.

Benefits out of this release

BizTalk360 Auditing – When you are a group of support people, diagnosing and solving problems in your production environment, it’s important to keep track of who is doing what in the environment. With BizTalk360 activities auditing, you can easily identify who did what.

SMTP Notification Channel – Managing the email recipients which are mapped to an alarm is very simple now. With the SMTP notification channel, you can configure email distribution lists which can be mapped to multiple alarms. In addition to this, you can also configure specific team member emails to receive Up and Auto Correct alerts.

Switch User Role – The User roles can be changed in a single step. You can easily convert a super user to a normal user and vice versa.

Unmapped Application Artifacts – We don’t want you to miss artifacts for monitoring. With this new Unmapped application artifacts feature, you can determine the artifacts which are not (yet) mapped for monitoring.

System Alerts – The BizTalk360 administrator can get to know about the health of BizTalk360 environment through System Alerts. The administrator can now get alerts about BizTalk360 License expiration, Unmapped application artifacts list and Monitor error details.

Copy to Clipboard – With this,user can copy the field values in a single click from the BizTalk360 UI.

Let’s jump into the features in detail

BizTalk360 Auditing

BizTalk360 has a powerful operational governance and auditing capability to maintain the logs of the user activities in the system. This feature helps the BizTalk administrators to find out “Who did what” in the environment over a period of time. BizTalk360 already has the capability to audit BizTalk level activities. You can think of actions on BizTalk Applications, Service Instances, Host Instances, BizTalk and SQL Servers, ESB Messages and Business Rules.

For this release we have implemented BizTalk360 activities auditing. This will give a clear insight about the various activities performed by the user in the Manage Alarm, Artifacts Mapping, and Secure SQL query sections. 

Alarm operations such as new alarm creation, changing the alarm status (Enable/Disable), deleting an alarm, updating alarm details will be logged with the existing and new values, along with the user details. Administrator can also view the artefact mapping details. For instance, if any artifacts have been added or removed from an alarm mapping for monitoring, that will be logged.

Secure SQL query auditing includes Creating new query, Editing/Deleting the query and Query import.

 

SMTP Notification Channel

The SMTP Notification Channel provides an ability to create email distribution lists by grouping email ids based on the business needs.

Using the same email recipients for multiple alarms was not easy in earlier versions; the recipient’s details needed to be entered for each alarm.  To overcome this, we have introduced the SMTP Notification channel, through which the user can configure email distribution lists under one channel and can be mapped to multiple alarms. In addition to this, we have added email grouping for Up Alert and Auto Correct Alert. With this, the user can configure different email ids to receive Up and Auto Correct alerts.

Switch User Roles

In earlier versions, there was no option to convert a Super user to a Normal user or vice versa. To change the user roles, the profile needed to be deleted and recreated again, which is a time-consuming process. This has been solved in this version; the user roles can quickly be converted in a single step, by editing the user and toggling the user roles.

Unmapped Application Artifacts List

BizTalk360 can monitor amongst others BizTalk application artifacts. With this new Unmapped application artifacts feature, you are able to determine the artifacts which are not (yet) mapped for monitoring.

You will get a summarized list of unmapped application artifacts in the Monitoring Dashboard. This list contains the artifacts which are not mapped to any of the alarms for monitoring. For instance, if any new artifacts have been added in your BizTalk environment, we will bring that to your notice and you can easily map the artifacts for monitoring.

System Alerts

BizTalk360 is the single tool to manage operational activities, monitoring and analytics of the mission-critical BizTalk environment. Systems Alerts are sent to the BizTalk360 administrator about the health of BizTalk360 environment. The administrator can now easily get the alerts about BizTalk360 License expiration and Unmapped application artifacts list in the BizTalk environment.

The list of Unmapped application artifacts can be notified based on the alert schedule in the system settings. License Expiration notification will be automatically be triggered on 30, 15, 7 and 2 days before the license expiry.

Copy To Clipboard

Our business data is highly valuable. The information uses contain decision-making and problem-solving. From v9.0 on, the Copy to Clipboard option is provided to copy information in a single click from the BizTalk360 UI to the Windows Clipboard.

Few Enhancements and Bug Fixes

Besides these new features, we have also brought several enhancements and bug fixes.

Default Auto Correct Reset Interval

Auto healing is an existing feature which tries to bring the artifacts back to the expected state after a violation has occurred. The system will retry the auto healing process for a configured number of times. Once the retry limit is reached, the auto healing process will be stopped. The user can set the number of retries and reset it when the maximum limit is reached. However, it can be time-consuming to set the reset interval time for every configured auto correct. To overcome this, an option to set the default auto-correct reset interval is introduced in the System settings section.

Monitoring Dashboard Improvements

The BizTalk360 ‘Monitoring Dashboard‘ becomes the one-stop point for support people to view the health status of the BizTalk environment. You can see the summarized dashboard can be seen in a much enriched view.

Now the monitoring graph can be resized based on the screen resolution.

Blade Improvements

When multiple blades are opened, there was a partial inconsistency with the blades. Already opened blades remained open until the user close it manually. Now, the blade will get closed when the user clicks on another blade and the user is able to view only the relevant blades.

Conclusion

Considering the feedback from our customers, BizTalk360 will continue to provide more useful features. Why not give BizTalk360 a try! It takes about 10 minutes to install on your BizTalk environments and you can witness and check the security and productivity of your own BizTalk Environments. 

 

The post BizTalk360 v9.0 Released appeared first on BizTalk360.

What is coming in v9.0

What is coming in v9.0

 BizTalk360 enhances the complex administrative tasks into a modern easier task. We always aim to constantly improve our product based on our customer’s feedback and their business needs. We have recently released V8.9.5. The upcoming version 9.0 features are typically chosen from our customer feedback based on the impact and the number of requests.

You asked and we are implementing the below features for v9.0.

Alarm Auditing

When we work on cutting edge technology, security is one of the important factors we always need to consider. Keeping that in mind, earlier we implemented Governance and Auditing which actually audits BizTalk level activities from BizTalk360. You can think of actions on BizTalk Applications, Service Instances, Host Instances, BizTalk and SQL Servers, ESB Messages and Business Rules.

Many customers requested us that it could be great if Biztalk360 activities such as Alarms, User access policy activities also audited. So, for this release we have implemented Alarm activities. Alarm operations such as new alarm creation, deleting an alarm, changing the alarm status (Enable/Disable), editing alarm details will be audited with the existing and new values, along with the user details. With this, the administrator will get clear picture of all the alarm activities.

Also, we have taken Secure SQL Query auditing. If any query has been created or modified this will be audited. We also implemented auditing of the ‘Execute’ operation. So, with this administrator can easily look for, who has executed which query and which parameter value are passed for the query execution in detail.

 

SMTP Notification Channel

In BizTalk360 version 8.0, we introduced Notification Channels. With this , it’s easy to send alerts to any external systems like your ticketing system, internal databases, calling REST endpoints or executing PowerShell scripts.

To add more value to this, we are bringing the SMTP Notification Channel which provides an ability to create an email distribution lists by grouping email ids based on the business needs. The monitoring service will generate a notification to a group of people by simply configuring the recipient address (To, CC) in the channel. Once the SMTP notification channel is configured it can be used in all the alarms just, by enabling the channel. This will prevent the user to type email ids over and over again.

UnMapped Artifacts List

When the artifacts are mapped for monitoring, BizTalk360 will take care of it and intimates users when any violation occurs. But, what happens if you missed to map some artifacts for monitoring? You will not get any notification for this, right?! Of course, we don’t want you to miss artifacts for monitoring.

This  problem will be solved in v9.0, you will get a summarized list in the Monitoring Dashboard. This list contains  the status of the artifacts which has been mapped for monitoring and also the unmapped artifacts list. For instance, if any new artifacts have been added in your BizTalk environment, we will bring that to your notice and you can easily map the artifacts for monitoring. Also, we will forward the list of unmapped artifacts to the system administrator based on the configured interval time.

 

Switch User Roles

 

As of now in BizTalk360, once a user profile is created, the user roles (Super, Normal) cannot be modified at any point. To change the user roles, the profile needs to be deleted and recreated again which is a time-consuming process. This will be solved just by editing and changing the user roles. So Super Users can quickly be converted to Normal users and vice versa in a single step.

Copy to Clipboard

Our business data is highly valuable. The information uses contains decision-making and problem-solving. From v9.0 we are providing an option to copy your information’s in a single click from  the BizTalk360 UI to the Windows Clipboard.

 

Apart from these new features, we are working on improvements in the following sections.

 

Monitoring Dashboard

The BizTalk360 ‘Monitoring Dashboard‘ becomes the one-stop point for support people to view the health status of BizTalk environment. We have planned to do some changes on monitoring dashboard UI which helps you to see the summarized dashboard in much enriched view.

AutoCorrect reset

In BizTalk360 we have the Auto Healing functionality with which, if your artifacts go down, the system will try to auto heal the violation. The system will retry the auto healing process for a configured number of times. Once retry limit is reached the auto healing process will be stopped.

In v8.9.5 we introduced the auto reset option for the auto healing process, in which, after the configured interval time, the retry count will be reset to 0 and starting the auto healing process again. We kept the “interval time to reset the retry count” to 0. This means that the retry limit will never reset, unless the user goes and manually change the interval time. This is quite a tedious process when you have huge number of artifacts mapped for auto healing.

This problem will be solved as we will provide an option to define the default interval time globally. So once you update the interval time it will be used for all the artifacts.

Conclusion

Considering the feedback from our customers, BizTalk360 will continues to provide more useful features. Now we would like you to hear from you, so please take some time to fill this questionnaire to help us prioritize the next upcoming feature tasks. Stay tuned for next version v9.0.

Why not give BizTalk360 a try! It takes about 10 minutes to install on your BizTalk environments and you can witness and check the security and productivity of your own BizTalk Environments. Get started with the 

 

 

 

The post What is coming in v9.0 appeared first on BizTalk360.

Determine Ready to Run / Active Service Instance Details with Custom Widgets

Determine Ready to Run / Active Service Instance Details with Custom Widgets

When messages flow into the BizTalk Server, the messages may get persisted in BizTalk Server’s MessageBox database. For a healthy BizTalk environment, it’s important to keep an eye on the number of service instances in the environment.For example, having a large number of suspended service instances will bloat your message box database and adversely affect the overall performance of your environment.

Administrator should always  keep an eye on the service instances count via the BizTalk Administrator group hub page. The person who is monitoring this, need to be a BizTalk expert and understand the importance of each state. The group hub page only displays the instance count and it won’t tell you whether this is still at a healthy level. Whereas with BizTalk360 you can set the Warning and Error threshold levels (instance counts) for each states at application level. Once the number of instances count increases above the threshold, the system will send notification alert.

Also, the administrator can set up an alarm like “If there are >20 Suspended Service Instances between 09:00 AM and 05:00 PM, resume all the instances”. He can simply log in to the BizTalk360 Data Monitoring Dashboard to see the status of the message box data for the day. He can also set up email notifications for the alarm. By doing so, the administrator eliminates the need to often log in to the BizTalk360 application and check for the status of the service instances.

Custom widget to list all service instance details which are active for a long period

Custom Widget is one of the interesting and powerful features available in BizTalk360. With a custom widget, users can easily integrate third-party portals like Power BI, Sales Force or internal portals. You can also easily display Secure SQL Queries query results , monitor BizTalk Artefact statuses etc.

For instance, if a host instance is too busy to process all its associated service instances , then those instances will be in “Ready to Run” state until the host instance has available resources. When this situation remains for a longer timeframe, the service instances are going to get accumulated, thereby bloating the message box.

With the below script you can quickly create a custom widget to look up the number of service instances which are in the active state for a particular period of time. Say, the administrator can easily check service instance details which are in the Ready to Run or Active state for more than 15 minutes.

Creating such a widget, consists of the following steps:

  1. Create a Secure SQL Query
  2. Bind the SQL Query result to the custom widget

Both steps are described below.

1) Create Secure SQL Query

The below query retrieves the Service Instances which are in the Active state for more than 30 minutes.

DECLARE @dt DATETIME = ( DATEADD(MINUTES,-30,GETUTCDATE()))

exec ops_OperateOnInstances @snOperation=0 ,@fMultiMessagebox=0 ,@uidInstanceID='00000000-0000-0000-0000-000000000000', @nvcApplication=N'', @snApplicationOperator=0, @nvcHost=N'' ,@snHostOperator=0,@nServiceClass=111,@snServiceClassOperator=0,@uidServiceType='00000000-0000-0000-0000-000000000000', @snServiceTypeOperator=0, @nStatus=2, @snStatusOperator=1 ,@nPendingOperation=1 ,@snPendingOperationOperator=0,@dtPendingOperationTimeFrom='1753-01-01 00:00:00', @dtPendingOperationTimeUntil='9999-12-31 23:59:59.997', @dtStartFrom='1753-01-01 00:00:00', @dtStartUntil=@dt ,@nvcErrorCode=N'',  @snErrorCodeOperator=0 ,@nvcErrorDescription=N'' ,@snErrorDescriptionOperator=0,@nvcURI=N'',@snURIOperator=0,@dtStartSuspend='1753-01-01 00:00:00', @dtEndSuspend='9999-12-31 23:59:59.997', @nvcAdapter=N'', @snAdapterOperator=0, @nGroupingCriteria=0, @nGroupingMinCount=0,@nMaxMatches=10,@uidAccessorID='*******',@nIsMasterMsgBox=0;

2)Bind the SQL Query result to a custom widget 

You can create the custom widget and use below code. Don’t forget to include your environment details like the credentials of the BizTalk360 service account, etc.

<div id="WidgetScroll" style="top:30px;" data-bind="addScrollBar: WidgetScroll, scrollCallback: 'false'">
<table class="table table-lists">
<thead>
<tr>
<th style="width:30%">Application Name</th>
<th style="width:30%">Instance Id </th>
<th style="width:30%"> Service ID</th>
<th style="width:30%">Created Date</th>
<th style="width:30%">State</th>
</tr>
</thead>
<tbody>
<!-- ko if: (ServiceInstanceDetails()) -->
<!-- ko foreach: ServiceInstanceDetails() -->
<tr>
<td data-bind="text: nvcName"></td>
<td data-bind="text: uidInstanceID"></td>
<td data-bind="text: uidServiceID"></td>
<td data-bind="text: dtCreated"></td>
<td data-bind="text: nState"></td>
</tr>
<!-- /ko -->
<!-- /ko -->
</tbody>
</table>
</div>
<script>
// BEGIN User variables
username = ""; // BizTalk360 service account
password = ""; // Password of BizTalk360 service account
environmentId = ""; // BizTalk360 Environment ID (take from SSMS or API Documentation)
queryId = ""; // Id of the Secure SQL Query (take from SSMS)
queryName = ""; // Name of the Secure SQL Query as it is stored under Operations/Secure SQL Query
sqlInstance = ""; // SQL Instance against which the SQL Query must be executed
database = ""; // Database against which the SQL Query must be executed
sqlQuery = " " // The Secure SQL Query created in step1
bt360server = ""; // Name of the Server where biztalk360 is hosted
// END User variables

url = 'http://' + bt360server + '/BizTalk360/Services.REST/BizTalkGroupService.svc/ExecuteCustomSQLQuery';
ServiceInstanceDetails = ko.observable();

x2js = new X2JS({ attributePrefix: '', arrayAccessForm: "property", arrayAccessFormPaths: ["root.records.record"] });

ServiceInstanceDetailsList = function () {
var _this = this;
_this.getServiceInstanceDetails(function (data) {

var results = x2js.xml_str2json(data.queryResult);
if (Array.isArray(results.root.records.record)){
ko.utils.arrayForEach(results.root.records.record,function(item){

switch (item.nState){
case "1":
item.nState="Ready to Run";
break;
case "2":
item.nState="Active";
break;
}
});
_this.ServiceInstanceDetails(results.root.records.record);
}
else {
_this.ServiceInstanceDetails([results.root.records.record]);
}
});
};
getServiceInstanceDetails = function (callback) {
var _this = this;
$.ajax({
dataType: "json",
url: _this.url,
type: "POST",
contentType: "application/json",
username: _this.username,
password: _this.password,
data:
'{"context":{"environmentSettings":{"id":"' +
_this.environmentId +
'","licenseEdition":0},"callerReference":"REST-SAMPLE"},"query":{"id":"' +
_this.queryId +
'","name":"' +
_this.queryName +
'","sqlInstance":"' +
_this.sqlInstance +
'","database":"' +
_this.database +
'","sqlQuery":"' +
_this.sqlQuery +
'","isGlobal":false}}',
cache: false,
success: function (data) {
callback(data);
},
error: function (xhr, ajaxOptions, thrownError) {
alert(xhr.status);
alert(xhr.responseText);
},
});
};
ServiceInstanceDetailsList();
</script>

After you have created the custom widget and properly provided your environment details, it will look similar to the picture below.

We have written multiple articles about the capabilities of custom widgets, both in our blog, but also in the Documentation portal. You can check them out below:

Conclusion

It has been extremely beneficial to ensure the environment is healthy. With this custom widget you can easily get a clear insight about long running service instance details in a single view. If you have a particular scenario in which custom widgets could be useful, but you don’t know how to set this up, feel free to contact us at support@biztalk360.com.

Introducing BizTalk360 v8.9.5

Introducing BizTalk360 v8.9.5

We always aim to constantly improve our product based on our customer feedback and the business needs of our customers. Keeping that in our mind, we add some significant features in every single release.  In this blog, you can get to know about all the stimulating features we have shipped in our latest v8.9.5 release.

Quick Alarm 

Are you new to BizTalk360?  Now you can easily setup monitoring, just in a Single click by using a Quick Alarm.

The Quick Alarm feature has been brought into the product to give a unified experience to the user to easily set up monitoring. A Quick alarm is a consolidated alarm which selects a few artefacts from the BizTalk Applications and map them for monitoring, under various categories (Threshold, Data Monitoring, Health Check) .

Quick Alarms can be configured from Monitoring Dashboard and from Manage Alarm section just by providing the alarm name and email id. This configuration also takes care of SMTP setup if you have not yet configured it in your environment. So once a Quick Alarm has been configured, you will be notified through email if any monitoring violation happens.

Send Port Group Operations

One of the powerful features in BizTalk Server is Send Port Groups, which help to route a single message to more than one destination.Send Port Group operations and monitoring is one such important feature we did not yet include in BizTalk360. At a point, we received a feedback from one of our customer “As they were not able to fully start/stop the applications from BizTalk360 when they have Send Port Groups configured ” .Hence, we have taken it for v8.9.5.

Now, you can perform operations such as start/stop/enlist/unenlist the Send Port Groups from BizTalk360. With this new capability it is possible to manage the operation of BizTalk applications (Start & Stop) for all the artifacts of each application  in BizTalk360. This implementation makes the life easier for the BizTalk support engineers without context switching between BizTalk admin console and BizTalk360.

One of the main objectives for us from the security perspective is auditing. We have leveraged the governance and audit capability to capture all the activities of Send Port Groups performed by all the users within BizTalk360.

Send Port Group Monitoring

From the latest version, you can completely manage and monitor your Send Port Groups from BizTalk360. Create an alarm, map the Send Port Groups for monitoring by setting up the expected state. If any threshold violation occurs, you will be notified. You can also setup auto-healing for this monitoring; once the Send Port Group goes down, then BizTalk360 will try to auto heal it to the expected state.

Alarm Auto Reset

We allow users to configure number of alerts to be triggered within stipulated duration if any threshold violation happens . When the configured alert reaches it limit ,it cannot be reset unless if the threshold violation resolves or user reset it manually .This is an impacting issue for some customers who monitor several artefacts under same alarm .In this scenario, when artefact 1 goes down, you will get notified with down alerts on periodic interval based on your configuration. Later no further notification will be sent when any other artefact goes down , since the number of alerts has already reached its maximum count .This problem is now resolved with the Alarm auto reset functionality, in which the alert counter will automatically reset after configured time. So, there is no chance of missing alerts when your artefacts are going down.

Auto Correct Reset

Auto healing is one of the dominant features available in BizTalk360. When you configured auto correct for your artefacts, the system will try to always maintain the expected state which you have set for those artefacts. When the artefacts state changes then the system tries to bring it back to the expected state. Here, the maximum retry is based on user configuration. So, what happens when it reaches the max retry count? It will not try to auto correct the state. To overcome this problem, we have introduced a new capability called Auto Reset. From this version on, the retry count will get automatically reset as per the user configuration (e.g.: 10 mins).

So when you configured Auto-healing for your artefacts, it is guaranteed the system will always try to maintain the expected state without any downtime with this new capability.

Delete ESB Fault Message

With the ESB Fault Delete functionality, you can delete the fault messages which are not important for resubmission.

Let us consider this scenario, a send port that you are using in your application fails unexpectedly, therefore both the service instance and the message become suspended and the fault information is written into the ESB exception database. Once the exception is corrected and resubmitted for further go, there may be two scenarios which will come into picture:

  1. Messages which are submitted successfully are residing in the ESB Exception database and are of no further use.
  2. Messages are rerouted to the ESB Exception database due to recurrent failure. In this specific case, the original message also available in the ESB portal.

In BizTalk360, we have introduced a new option “Delete” to clear the messages which are not required anymore. Additionally, all the deleted activities are audited in both Governance & Auditing and Live feed section to ensure the security.

Custom User Profile Templates

When we work on cutting edge technology, security is one of the important factors we always need to consider. When a new user is created, you can provide access to the corresponding features based on the roles of the user. Consider a scenario where the customer would need to provide similar permissions to multiple users. It could be very time-consuming to make the changes for every user. BizTalk360 made this process very easy for the users by introducing the capability to create custom profile templates. You can create a custom template with the desired features selected and choose the template while creating the users.

Few Enhancements and Bug Fixes

Besides these new features, we have also brought a number of enhancements and bug fixes.

Filter Operators Improvements

BizTalk360 has the capability to query the data from various databases to show important data such as Service Instance details, Tracked/Message service details, ESB and so on. To filter the data from the corresponding database, BizTalk360 provides rich Query Builder capabilities. From this version on, we have added few additional operators in line with the BizTalk Admin console for easy access to the data in both the Operation and Data Monitoring sections.

Notification Channel Improvements

 Associated Alarm

 Imagine a user wants to know about the mapping of a specific notification channel out of all the configured alarms in the environment. This was a tedious task in earlier versions of BizTalk360.

To get the quick status of the notification channel association with Alarms, we brought the new option “Associated Alarms” in the Setting side, to view all the mapped alarms in a single view.

DLL Reconfiguration

There was no option to reconfigure the notification channel, if any changes were made in the existing notification channel DLL. You need to go and change all the properties in all the alarms where the specified notification channel is mapped. Now, the reconfiguration process will be seamless from the UI without touching the database.

License Expiry Reminder

To provide an insight about the type of license and date of expiry , License expiry notification will be shown in UI for all the license types (Commercial, Partner & Product Specialist).

We have closed around 24 support tickets as part of fixing the issues in different areas. Please refer the Release Notes – https://docs.biztalk360.com/docs/v8951122201

Get Started Today !!!

Conclusion

Why not give BizTalk360 a try! It takes about 10 minutes to install on your BizTalk environments and you can witness and check the security and productivity of your own BizTalk Environments. Get started with the free 30 days trial.

Easily set up monitoring with Quick Alarms

Easily set up monitoring with Quick Alarms

Are you new to BizTalk360 ? Now you can easily setup monitoring just in a Single click!
The Monitoring capabilities are a key feature of BizTalk360. Setting up monitoring is a very easy and quick task. With a two-step process, you create an alarm and map the artefact(s) to be monitored. We wanted to make this much easier for our customers. So keeping that in mind we bring the new feature ‘Quick Alarm’ in our upcoming release v8.9.5 .

What is a Quick alarm?

A Quick Alarm is a consolidated alarm which selects a number of artefacts from the BizTalk Applications, which are in the Start/Stop/Partially Started state, and map them for monitoring. Under various categories (Threshold, Data Monitoring, Health Check) a Quick alarm maps the following resources for threshold monitoring:

  • Receive Locations
  • Send Ports
  • Orchestrations
  • Host Instances
  • Host Throttling
  • SQL Jobs
  • BizTalk Servers

For Data Monitoring (with basic filter configuration) the Quick Alarm is configured for:

  • Process Monitoring
  • Message Box
  • Tracking
  • BAM
  • EDI
  • ESB

Is a Quick Alarm different from normal alarms?

No, a Quick alarm is not all different from normal BizTalk360 alarms. Quick Alarms have been brought into the product to give an unified experience to the user to easily set up monitoring. A Quick alarm supports all the normal BizTalk360 alarm capabilities, like:

• Reset notification count
• Copy the alarm configurations
• Change status – Enable/Disable Alarm
• Once a Quick Alarm is configured it can be edited or deleted any time

Quick Alarm can be configured in 2 ways

  1. From the Dashboard
    When no alarms have been configured in your environment, you can configure a Quick alarm either from the general Monitoring Dashboard or from the Data Monitoring Dashboard.

Quick Alarm Configuration

2) From the Manage Alarms section
You can also create a Quick Alarm from the Manage alarms section by selecting the ‘Quick Alarm’ button, even though you have already configured some alarms.

Configure Quick Alarm From Manage Alarm Section

Note: There is no restriction on the number of Quick Alarms you create. You can create any number of Quick Alarms in your environment. Though how many times you create a Quick Alarm with the same set of applications, it will always configure the same artefacts for monitoring.

Once a Quick Alarm has been configured you will be notified through email.

• If there is any threshold violation on the mapped artefacts
• Data monitoring alerts on every 15 mins
• Health check alert on 12 PM everyday

These configurations can be changed later at any point in time.

If in case BAM, EDI,ESB is not configured in the environment, the Quick Alarm configuration skips these and configure the rest of the resources for monitoring.

Who can create a Quick Alarm

A Quick alarm can be configured only by super users. This facility is restricted for normal and NT Group Users.

SMTP Configuration

If SMTP is not configured in the Settings side, the Quick Alarm configuration will automatically update the default BizTalk360 SMTP account.

Note: This default settings can be modified at anytime.
The Quick Alarm configuration will not modify/update anything if you have already configured your SMTP account. It uses your configured SMTP details for sending alerts.

Conclusion

A Quick alarm is an easy and fast way to set up monitoring of the most important artifacts of your BizTalk artifacts. Are you tired of constantly having to monitor your BizTalk environment in a manual fashion? Give BizTalk360 a try and take benefits of Quick Alarms. A trial version of BizTalk360 can be requested here.

Event Log Data Monitoring in BizTalk360

Event Log Data Monitoring in BizTalk360

Event logs are normally used to inform about an important event in the running applications and subsystems, which plays a vital role in troubleshooting problems.

While monitoring multi-server environments, how many times in a day does your administration team log in to multiple servers to check for the root cause of a problem? Have you ever thought of a tool that could help you avoid this time-consuming process? Yes, BizTalk360’s in-built Advanced Event Viewer (AEV) helps you solve this business problem.

Set-up AEV to retrieve the event data you want from your BizTalk and SQL servers in your environment and display it all in a single screen, where you can use the rich query capabilities to search and analyze the data.

How to Set Up AEV in BizTalk360

As a first step, in BizTalk360 settings, you need to configure event logs and event sources that you want to monitor and then Enable AEV for the environment. Now the BizTalk360 Monitoring service will collect event log data for all the configured servers in that environment and store it in BizTalk360 DB.

What ‘s new in v8.6?

BizTalk360 already supports AEV in operations and monitoring section for a long time. While demonstrating BizTalk360 to customers, we asked for “How to monitor a specific event occurring in BizTalk environments on a specific frequency and get an alert based on Threshold conditions”. So, keeping that in mind we have implemented Event Log Data Monitoring in version v8.6.

Let us take this complex scenario to understand more about Event Log Data Monitoring.

Scenario1: User wants to monitor different event logs for multiple servers. Example: If an administrator wants to monitor ESB events from BizTalk server and also wants to ensure there is no problem in SQL servers and also to monitor ENTSSO events form SSO server.

Start Monitoring Event log Data in 3 Steps:

  • Enable AEV for an environment
  • Create a Data Monitoring Alarm
  • Create a schedule under event log and configure the rich filtering conditions based on your business needs as below.
Server Type : BizTalk, SQL
Server Names :BizTalk Server ,SQL Server,SSO Server
Event Type: Error
Event Sources: ESB Itinerary Selector, ENTSSO , MSSQLSERVER,

And group (All these below conditions are true)

Event ID Greater than or equal to 3010
Event ID Less than or equal to 3034
Message Contains 'ESB.ItineraryServices.Generic.WCF/ProcessItinerary.svc'

EventID IS Between 10500-10550
Message Contains ‘SSO Database’

When we looked in more detail, it would normally take us into running a filtering query against configured event sources in servers and alert them when certain conditions are met.

Scenario 2: To detect the same event occurring on different servers. For example, when a certain instance of an orchestration is firstly executed on server 1 and throwing a certain error and next to another instance of the same orchestration throws the same error, while the instance becomes executed on server 2, this will now easily be detected with event log data monitoring.

BizTalk360 brings all these data into a single console and on top of that provides a powerful capability to set alerts based on various thresholds.

You can also set how frequently you wanted to run the queries based on their business requirements such as the frequency of daily validations (ex every 15 mins, 1 hour etc), end of business day or even monthly events such as month-end processing. With these thresholds, the result from the query will be evaluated and in case of any threshold violation, you will be notified via notification channels/Email.

Event Log Details in Alerts

Event Log Details will be listed in alerts by enabling the option ‘Send Event Log details in Mail’ while creating the schedule.

Event Log data in the Data Monitoring Dashboard

Also, the information will be visible on the Data Monitoring dashboard, you can visualize the day calendar view. If you need to understand what happened for an execution, you can click on one of the entries in the day view of the dashboard and view the details as shown below.

Note :

  • Maintenance is very simple, once after scheduling event log data monitoring, when you disable AEV for the environment, it will stop collecting Event Log data.
  • And you don’t Worry about data growth, BizTalk360 purge policy will take care of it.
  • Apart from monitoring BizTalk specific SQL server, you can also monitor other SQL servers simply by adding SQL server names for monitoring in the settings section.
Enhancements on Monitoring Alerts and Notifications in BizTalk360 v8.5

Enhancements on Monitoring Alerts and Notifications in BizTalk360 v8.5

Monitoring and Alert notification is one of the core functionality in BizTalk360. To empower better usability of a user, we have improved the alert notification in the latest release v8.5. The enhancements are typically chosen from our customer feedback based on the impact and the number of requests.

Event Log description:

Event logs can give the early warning of impending system issues and save you from unexpected disasters. It is quite important to monitor the event logs regularly to get proper insights of any windows servers.

BizTalk360 has ‘Advanced Event Viewer’ functionality in which BizTalk360 Monitoring services collect the data from event logs from defined event sources of multiple servers. And the same can be monitored with respect to event log type (Application, Security, System, Windows PowerShell etc…), event sources of each event types and also with the specific event id and texts by configuring threshold conditions.

The best way to monitor event logs is to choose a solution that reports the Windows Event ID as well as the error message. Considering this ideology, we enhanced this in 8.5 release, so that event log will be alerted along with the description. This feature is also enabled with the filter on the number of event logs and size of the description (up to 5000 characters) in the system settings. Now user can get clear insights on any events occurred in the configured BizTalk or SQL server.

Event Log Alert with Description

Event log monitoring can be done in few easy steps

  • Enable Event Log Monitoring in Setting->Advance Event Viewer section
  • Define Email Event Log Description character count and List Count in system settings
  • Configure Monitoring Threshold conditions for event log monitoring.

Migration Scenario: To use this, the user needs to define the list count and description character count in system setting. By default, the values will be zero after migration.

Data Monitoring alerts in Notification channel

Data Monitoring is one of the powerful features in BizTalk360 which run queries against multiple data sources in BizTalk which include: Message Box Queries, Tracking Queries, BAM Queries, EDI Queries and ESB Queries, Logic Apps based on the configuration how the user wants to monitor data in each of these sources.

Previously Data Monitoring alert can be sent only through static notification end points like SMS, Email, Windows Event log and HP Operation Manager. From v8.5 we have extended custom notification support for data monitoring alert. Using this functionality, the users can get Data Monitoring alert from various external systems like Slack, ServiceNow, Web Hook and they can also build their own custom notification channels to any external systems.

To use this functionality user need to configure notification channel in setting side and enable the same in Data Monitoring alarm.

Migration Scenario: User need to enable Configured Notification Channel in Existing Data Monitoring Alarm to get Data Monitoring alert on custom notification channels.

Web Endpoint Monitoring Enhancement

We have web endpoint monitoring (ability to monitor any HTTP based URL’s) for very long time in BizTalk360, right from 6.x. In fact, this is one of the key monitoring component used by a lot of our customers. Web endpoint monitoring allows you to monitor the health of any HTTP based web service. You can monitor:

  • Response status codes
  • Response Keyword, XML, JSON
  • Response Time

You can configure BizTalk360 to trigger an alert notification if the response value is not matching your requirement. We have done following improvements on web endpoint monitoring alerts.

  • Many customers suggested to include the endpoint name in an alert email, alert history and also in monitoring graph to easily identify which endpoint has gone down in case of multiple web endpoint configured for monitoring.
  • Also Expected Return code and Response Time Alert details are included in alert for more insights.

Web EndPoint Monitoring

Folder Size Monitoring

In BizTalk360 version 8.4, we introduced the capability of folder monitoring which monitors the file count for File Locations (File, FTP and SFTP) configured in BizTalk artifacts. From 8.5, we are supporting directory size monitoring for file locations which actually monitors the size of entire folder irrespective of file mask. (i.e) the folder may contain various file types XML, txt, png etc but the configured file may be either one of this type so here, folder size means entire folder with all the file types.

With in 2-3 clicks, the user can configure monitoring threshold conditions for folder size and start monitoring and get notified as and when folder size increases/decreases.

Folder Size Monitoring

Conclusion

BizTalk360 enhances the complex administrative tasks into a modern easier task. This version of 8.5 is being added with more features thinking from a usability perspective of our customers. BizTalk360 continues to provide more such features considering the feedback from our customers and stay tuned for next version.