BizTalk360 High Available Setup Guide

BizTalk360 High Available Setup Guide

High availability, Multi server, Multi-environment Infrastructure Guide

This article will help you to understand the architecture of the infrastructure details for various scenarios of high availability, multi-server and multiple environments setup.

With regards to High Availability of BizTalk360, there are few parts which can be made Highly Available/Load Balanced:

  1. The User Interface
  2.  The Windows NT services (Monitoring & Analytics)
  3. The BizTalk360 database

The User Interface (UI)

The UI, including the REST services, can be made Highly Available by installing BizTalk360 on multiple servers. By putting a software/hardware load balancer (NLB) in front of these BizTalk360 servers, the UI of BizTalk360 can be accessed via the virtual address which is provided by the NLB.
Independently whether one of the BizTalk360 servers is down, you will always be able to access BizTalk360 via the address of the NLB. This is in no way related to the high availability of the BizTalk360 NT services.

The BizTalk360 Windows NT services

Depending on the license tier a company goes for, BizTalk360 comes with the following Windows NT services:

  • One for the Monitoring activities
  • One for collecting Analytical data (only needed in case of Platinum license)

To split the responsibilities of the NT services, each of these services contains several sub-services. One of these sub-services is used for heartbeat and will be used in case BizTalk360 is installed on multiple servers.

BizTalk360 High Available Setup Guide_Monitoring Service Screen

The picture shows the BizTalk360 Monitoring Service, including its sub-services. See below list, for some more explanation about the capabilities:

  1. Refresh and Restart buttons – With the Refresh button, the status of the Monitoring service and its sub-services are retrieved. The Restart option enables you to restart the Monitoring services. As a result, the sub-services will also be restarted
  2. Start and Pause buttons – Each sub-service can be Started/Paused individually. By selecting one or more sub-services with the check boxes, you can Start/Pause multiple sub-services at once
  3. Service Name column – This column shows the name of all sub-services. Based on that, you will understand the responsibilities of each sub-service. As mentioned earlier, the Heart Beat sub-service is one of them
  4. Polling (Sec) column – Each sub service has its own polling interval, after which the sub-service will do its job. It is not possible to change this interval. In the Last Execution column, the date and time of the last execution of each sub-service is shown
  5. Current State column – This column shows the actual state of each sub-service. By default, all these sub-services should be Started
  6. Last Status – This column shows whether the last execution of the sub-service was successful or not
  7. Exception – In case the last execution was not successful, the exception of the last execution is shown in this column

To make these NT services highly available, BizTalk360 needs to be installed in multiple servers. At these servers, the BizTalk360 NT services must be started. From that moment on, the heartbeat of the services will be monitored cross-wise between the services on the BizTalk360 servers. For each (Monitoring and Analytics) service only one on either BizTalk360 machine can be Active. In other words, this is an Active-Passive configuration. Active-Active is not supported!

Below screenshot shows a configuration in which the BizTalk360 Monitoring service is installed in 2 servers. As you can see, the BTS2016LAB02 server is Active, which means that it is performing the monitoring tasks. The other server, the BTS2016LAB03, is not active. However, this server can be activated by clicking the Activate button.

Again, it is important to remember that although BizTalk360 can be installed on multiple servers, only one of these servers can be Active and performing the monitoring tasks.

BizTalk360 High Available Setup Guide_High Availability Screen

In such multi-BizTalk360 server setups, in case the heartbeat sub-service on the Active BizTalk360 machine is not responding, there is automated fail-over of the BizTalk360 NT services taking place. So, the tasks of the BizTalk360 NT services will be performed by the server which was, until then, Passive. Thereby, High Availability is reached.

The BizTalk360 database

For making the BizTalk360 database highly available, you need to use a clustered SQL instance. That could be the same SQL instance as where the BizTalk databases reside, but could also be a separate (clustered) instance.

Different standalone and multi-server scenarios

As BizTalk Server can also be made High Available and Load Balanced, there are quite a lot of different scenarios possible, with respect to the server setup of both products. Let’s have a look at the most common scenarios and see how these scenarios affect the BizTalk360 licensing.

Scenario 1 – Standalone BizTalk server and standalone BizTalk360 server

First scenario, let us see how a simple solution, like having a standalone BizTalk Server and a standalone BizTalk360 environment setup will look like.

Following are the prerequisites:

  1. 1 x BizTalk Server
  2. 1 x MS SQL Server
  3. 1 x BizTalk360 server
  4. 1 x valid BizTalk360 server license (total BizTalk Server count will be 1 in this scenario)

BizTalk360 High Available Setup Guide_Scenario1

Scenario 2 – Multiple BizTalk servers and a standalone BizTalk360 server

In our following scenario, we will see how to have multiple BizTalk Servers and a standalone BizTalk360.

Following are the prerequisites:

  1. 2 x BizTalk Server
  2. 1 x MS SQL Server
  3. 1 x BizTalk360 server
  4. 1 x valid BizTalk360 server license (total BizTalk Server count will be 2 for the BizTalk360 license)

BizTalk360 High Available Setup Guide_Scenario2

  • Though we require one BizTalk360 license, the max server count for the license, should be = 2 as BizTalk360 is licensed per number of BizTalk servers in the BizTalk group
  • If both BizTalk servers (BTSRVR1, BTSRVR2) are active, it means that this is a multi-server environment
  • If BTSRVR1 is active and BTSRVR2 is passive (or vice versa), then it is High Availability

Scenario 3 – Multiple BizTalk servers and multiple BizTalk360 servers

Below is the diagram that explains how to have a multiple server setup for both BizTalk Server and BizTalk360 servers and its pre-requisites:

  1. 2 x BizTalk Server
  2. 1 x MS SQL Server
  3. 2 x BizTalk360 servers
  4. 1 x valid BizTalk360 server license (Total BizTalk Server count will be 2 for the BizTalk360 license)

BizTalk360 High Available Setup Guide_Scenario3

In this scenario, we have used two BizTalk360 servers, pointing to the same BizTalk group, which makes BizTalk360 highly available.

Scenario 4 – 2 multi-server BizTalk groups and multiple BizTalk360 servers

Now, we will see another scenario where we have multiple BizTalk Server environments; both BizTalk Server & BizTalk360 are highly available.

Following are the prerequisites:

  1. 2 x 2 BizTalk Server
  2. 2 x MS SQL Server
  3. 2 x BizTalk360 server
  4. 2 x valid BizTalk360 licenses (total BizTalk Server count will be 2 for each BizTalk360 license)

BizTalk360 High Available Setup Guide_Scenario4

As we have seen, there can be several combinations of server setups, and it is purely based on the customer’s requirement and their infrastructural policies. What we explained are 4 various scenarios and their requirements. These are basic setups and the fundamentals will not change, even if you have other scenarios.

Author: Mekala Ramesh

Test Lead at BizTalk360 – Software Testing Engineer having diverse exposure in various features and application testing with a comprehensive understanding of all aspects of SDLC. Strong knowledge to establish the testing process from the scratch. Love to test the software product to deliver it with good quality. Strongly believes on “Testing goes beyond just executing the test protocol”.

Stop Alerts for Maintenance during Business Holidays

Stop Alerts for Maintenance during Business Holidays

Introduction

We are super excited to announce the availability of another interesting improvement in our upcoming version! BizTalk360 will allow you to setup monitoring maintenance, based on the business holidays configured for the environment.

Sometimes, administrators setup the maintenance period during new deployments or installation of security patches in their BizTalk environment. In such situations, to temporarily stop the monitoring in BizTalk360, there is a feature available “Stop Alerts for Maintenance”. Using this capability, the user can set the multiple future maintenance windows to stop false alerts being triggered from BizTalk360. This feature can be found in the Settings area of the application.

Stop Alerts for Maintenance during public Holidays_settings section

Initially, BizTalk360 allowed users to set only a single maintenance window. From v8.8 onwards, users can setup multiple future maintenance windows. So, during these maintenance periods the alarms will be disabled and no notifications will be sent from BizTalk360. At the same time, a maintenance notification will be shown in the Home dashboard and in the Stop Alerts for Maintenance Settings section. Refer to this article, to know more about this enhancement.

What is the new enrichment?

The basic idea here, is that perhaps if a user is able to setup multiple maintenance windows, they need to configure the business holidays individually. It will take much of your time, to configure for every single environment in BizTalk360. To reduce the time and ease the maintenance configuration for the users, the capability to add business holiday calendars has been introduced.

Stop_Alerts_for_Maintenance_during_business_Holidays_business_Holiday_calendar_tab_sub_section_in_settings_section

What is a business holiday calendar?

BizTalk360 provides this new capability to configure the business holidays in a calendar. These business holiday calendars can be mapped during maintenance window setup. This new configuration section is introduced in the Monitoring Notification settings section as “Configure Business Holidays”.

Using this intuitive UI, users can configure the business holidays in a calendar and save it for further mapping during the maintenance setup process.

Stop_Alerts_for_Maintenance_during_business_Holidays_Create_new_business_Holiday_Calendar

Let’s take an example: as a user, I wanted to configure a calendar for London business holidays. By clicking the “New” button, you can access the screen to configure the business holiday calendar.

Stop_Alerts_for_Maintenance_during_business_Holidays_business_holiday_calendar_configuration_section

After providing the basic details (Holiday Calendar Name, Description, Status), you can configure the dates for the business holiday in the Calendar Configuration part of the screen. For each date selection, a set of text boxes will be generated. The user has the liberty to provide their own text for the selected dates. On the right-hand side of the calendar configuration section, there are two checkboxes. Using these checkboxes, a user can include Saturdays and Sundays in the maintenance window. You can select both options or either one option, based on the business need.

Stop-Alerts-for-Maintenance-during-public-Holidays_Adding_public_holidays_to_the_calendar

Once the calendar is configured with business holidays, the user can save it for further use. The calendar will be listed in the Manage Business Holiday grid view. At any point in time, a user can add/delete new business holidays to the existing calendar configuration and save it. The changes will be updated automatically and maintenance will happen accordingly.

Preventing the business holiday calendar from accidental deletion

There is a chance that a configured calendar becomes deleted accidentally. The UI is designed in such a way that accidental deletion of calendars which are associated with maintenance windows is prevented. By any chance, if a user tries to delete a calendar which is associated with a maintenance window, a message will be shown in the UI that deletion is prevented.

Stop_Alerts_for_Maintenance_during_business_Holidays_business_Holiday_Calendar_Delete_Scenario_error_message

How to associate the business holiday calendar to maintenance windows?

In the Stop Alerts for Maintenance settings page, A new section is introduced to configure the business holiday calendars. All the configured calendars with Status enabled will be displayed in the “Select Business Holiday Calendar” dropdown list. A user can select the desired calendar and use it for a maintenance window. During the business holiday, a maintenance window will be active.

Stop_Alerts_for_Maintenance_during_business_Holidays_Holiday_Calendar_association_for_alert_maintenance

There is a new tab “Business Holidays” added in the grid section to view the configured business holidays to the calendar.

Stop_Alerts_for_Maintenance_during_business_Holidays_List_of_dates_configured_in_the_calendar_will_be_displayed

Excluding alarms during maintenance

wherewith this capability, users can exclude alarms during the maintenance. This means, that, except the selected alarms, other alarms will undergo maintenance.

Scenario: Enable Monitoring for few alarms (for example to monitor system resources) during deployments or security patch updates.

Let’s consider a situation, where administrators have configured critical alarms to monitor the system resources (CPU usage, Memory usage) of their BizTalk Environment in BizTalk360. It is important to monitor these resources in their BizTalk Environment to identify any performance glitches as early as possible to avoid significant business consequences.

In such scenarios, there will be a need to keep those alarms always on. Though the environment is in maintenance mode, if administrators wanted to monitor their system resources, they can make use of this new capability.

This capability is very useful in situations where administrators don’t want to receive alerts during the weekends except for few alarms.

Stop_Alerts_for_Maintenance_during_business_Holidays_Exclude_alarms_during_maintenance_option

Conclusion

Definitely, these improvements are like icing on the cake to our existing Stop Alerts for Maintenance capability. Happy migrating and try BizTalk360!!!

Get started with the free 30 days trial. For any queries/feedback please write to us support@biztalk360.com.

Author: Mekala Ramesh

Test Lead at BizTalk360 – Software Testing Engineer having diverse exposure in various features and application testing with a comprehensive understanding of all aspects of SDLC. Strong knowledge to establish the testing process from the scratch. Love to test the software product to deliver it with good quality. Strongly believes on “Testing goes beyond just executing the test protocol”.

Introducing additional column filters capability in BizTalk360

Introducing additional column filters capability in BizTalk360

Introducing new capability “Add/Remove” column headers

Here is another interesting capability, we are transporting in our upcoming version. Tired of filtering data using the static predefined columns? Hereafter, no worries. Grid columns in BizTalk360 are getting a fresh look. You can customize the column headers which are most important to your business scenario.

What is this new implementation?

Grid columns can be dynamically removed or added based on the user preference. As per the settings in the configuration section, columns will be aligned and displayed in the grid view. These customized column settings can be saved for future reference as well. We are sure, this capability will add more value when the administrator is looking for the instances/messages based on various conditions.

As an initial phase, this implementation has been done in the following areas in BizTalk360:

  1. Message Box Queries
  2. Graphical Flow (Tracking)
  3. Electronic Data Interchange

Why we implemented the Additional column filters in BizTalk360?

Let’s take an example. For a healthy working system, all the service instances must complete message processing successfully and clean up periodically. For this, the administrator keeps an eye on the message box queries interface for any instances hanging in error states like suspended (Resumable) and suspended (Non-Resumable). The administrator may look for errors based on specific parameters like Service Instance ID, Service Type ID, URI. In such cases, BizTalk360 has limited static columns (Service Name, Application, Service Class, Status, Creation Time and few more) to fetch and view the information in the Message Box database and for few other features.

We constantly listen to our customers’ feedback and ensure necessary improvements are made in the product regularly. These improvements will ease their day to day operations of their BizTalk Server environment. Therefore, this new capability called “Add/Remove grid columns” is implemented.

Hide or show a column

In the corresponding sections (Message Box Queries, Graphical Flow (Tracking), Electronic Data Interchange) there is a new option introduced “Edit Columns”. Through this, all the possible columns will be listed, which are essential to filter the data. Based on the (de)selection, columns are displayed or removed from the grid view. This functionality enables the user to choose the columns which are required to be shown in the grids.

Additional_Columns_filters_configuration_screen

Filtering context promoted properties made easy

As you all probably know, there are two types of properties in the context of the messages:

  1. MessageDataPropertyBased (Message Properties)
  2. MessageContextPropertyBased (Context Properties)

Basically, to process and track the messages, some properties will be promoted during the transaction. The promotion of the properties varies based on different business scenarios.

Let’s consider a scenario. Suppose a particular message got a huge number of properties promoted and the administrator wanted to narrow down the search in BizTalk360. Until our previous versions that would be a difficult task.

This search is simplified by now by making use of this new capability. You can select the important context promoted properties and save it. This customized setting will be there in the tool until the user prefers to delete the saved query. Following screenshots will provide an insight of how this new feature eases the operation of administrators.

Below screenshot represents the column grid view when the message has quite a number of context promoted properties. Data is accessed and visible, only the column headers are resized.

After executing the query, the result grid shows up, including the context properties. To make the screen more useful, you can select which fields you want to see in the grid and which ones don’t need to be shown.

Below, the configuration screen to select and deselect the columns.

additional column filters capability - Context promoted properties configuration screen

Once the needed fields have been selected in the configuration screen, the grid immediately reflects that configuration.

additional column filters capability - Context promoted properties grid view

How does BizTalk360 save the customized column settings?

BizTalk360 allows saving as many patterns as the user wants. I mean, to search the messages based on different scenarios, admins prefer different filter conditions to validate. In those situations, BizTalk360 allows to save different query filters and keeps them for future use.

Let me give you a detailed example. If you want to search for service instances based only on the applications and Error code, you just select those columns in the configurations screen. This change makes the grid realign based on the selection with applications and error code columns. The second step would be to preserve the selected columns for future reference. To achieve that, you need to save the query. This way, you can retrieve the same query, including the same context properties, in the future.

Easy migration from one environment to another

This is another interesting existing capability, we are having in BizTalk360. As a best practice to protect the production environment, all the data settings and testing are carried out in non-production and UAT environments.

If all the configurations are done in those environments and BizTalk360 is ready to be deployed to the production environment, users don’t need to worry about the recreation of those configurations in the new environment as this is where our import and export capability plays a vital role. Just by the click of a button in the UI, you will be able to export and import all the data between source and destination environment.

Download the customized column data using the Export to Excel capability

This is not a new capability in BizTalk360. As we enhanced, to support the column customization, users can also download this data by using the Export to Excel capability. 

Conclusion

We believe this new capability will provide extensive search ability and get the desired result in a blink of an eye. Happy migrating and try BizTalk360!!!

Get started with the free 30 days trial. For any queries/feedback please write to us support@biztalk360.com.

Author: Mekala Ramesh

Test Lead at BizTalk360 – Software Testing Engineer having diverse exposure in various features and application testing with a comprehensive understanding of all aspects of SDLC. Strong knowledge to establish the testing process from the scratch. Love to test the software product to deliver it with good quality. Strongly believes on “Testing goes beyond just executing the test protocol”.

Centralized Advanced Event Log viewer performance improvement for getting better insights about your BizTalk Environment

Centralized Advanced Event Log viewer performance improvement for getting better insights about your BizTalk Environment

In this blog post, I wanted to highlight the performance improvements of advanced event viewer collection logic in our upcoming version 8.9. This change will provide a fine-grained access to enable specific servers for the Event Log collection that are more important to you.

Windows Event Log Monitoring to detect the data breach

What would you do if you were faced with a critical issue in your BizTalk Environment in your enterprise? Think about this for a moment. Do you have an efficient process to respond to the problem? Are you equipped with the right set of tools to mitigate the problem in your environment? Sometimes, despite our best efforts, an issue may happen in unexpected ways and cause significant problems to the business.

In this situation, the Windows Event Log viewer is a handy tool for the BizTalk Administrators/support engineers to monitor their BizTalk environments and to detect any data breach or for any specific exception. At the same time, if the BizTalk servers are deployed in highly available setup and with clustered SQL server architecture, searching the Event Log from all of these servers together is like looking for a needle in a haystack.

Become the God of the Event Logs with BizTalk360 centralized Advanced Event Log viewer capability

Log data can be huge even in small integration business units. Many of the log entries might be routine messages about the BizTalk environment I.e. services and job status, that are mostly of no concern to you, but other messages like suspension of any service instances, system throttling state, state of host instances, etc., that is critical to your day to day business transactions.

However, to search for this logs in all the servers by logging into the physical server and correlate the Event Logs is a tedious process for the BizTalk support engineers /Administrators. This is where lots of their valuable time is wasted.

Who would not be happy if there is a capability to provide access to all the Event Logs across all the configured servers? Therefore, BizTalk360 provides you centralized access to all the Event Logs across all the servers in a rich web-based UI. To know more about the Advanced Event viewer, visit this blog “Why did we build Centralized Advanced Event Viewer for BizTalk Administration?”

No Fear! No Agent required. BizTalk360 provides agentless Event Log collection:

For Event Log collection, BizTalk360’s Advanced Event Viewer does not require a separate agent to be installed on each server. The BizTalk360 Monitoring service collects Event Log and is present as part of the BizTalk360 installation. In this way, BizTalk360 performs Event Log collection task without introducing any additional load to the servers.

Why this performance improvement required?

The Advanced Event Viewer is the most used feature in BizTalk360, where the administrators use this capability for their day to day business operations and monitoring with ease. To do so, there are some settings which need to be configured in BizTalk360. These settings are bound to the BizTalk environment level. In case of highly configured business architecture (Eg: 5 BizTalk Servers and 5 SQL Server with clustered setup), there may be millions of transactions which will happen on a regular basis.

From BizTalk360 V8.6 onwards, we have provided a new capability to monitor the Event Logs of the BizTalk & SQL servers. For this, we are calling the Windows Management Instrumentation service every minute. Because of the restriction with the environment level, all the servers will be polled every minute to collect the Event Log data.

We have received few support tickets where this specific logic is consuming a lot of memory and spikes the CPU performance of their BizTalk & SQL Servers. There are workarounds already suggested to our customers to make use of this capability in the best way, by configuring the sources which are required for them and remove the unnecessary sources. However, there are no options to enable the Event Log collection per individual server. Therefore, we have improved performance of the collection logic in our V8.9 version.

Comprehensive Event Logs collection using the newly introduced configuration method

 In our previous versions, up to V8.8, Event Log collection logic is not segregated based per server. To enable the Event Log collection, it is bound to the BizTalk environment and not on an individual server level. However, the user has control on configuring the sources based on the need.

Below screenshot represents our old screen in the Settings side to enable the Event Log viewer in order to view the logs in BizTalk360.

BizTalk360 Advanced Event viewer Event Log collection performance improvement- Old Screen

We have revisited the collection logic in our new version to improve the performance. Since the configuration is bound to the environment, the user doesn’t have control over the individual servers. In the new version of BizTalk360, users can control the Event Log collection according to individual servers. As an administrator, you know the value of each source which needs most considerations. So, there is an option as well in BizTalk360 to configure the BizTalk & SQL server sources separately.

Using these settings, you can customize and narrow down your Event Log search.

BizTalk360 Advanced Event viewer Event Log collection performance improvement - New_source_segregation_settings_screen

BizTalk360 Advanced Event viewer Event Log collection performance improvement - Server_configuration_screen

Improving the Archiving and Retrieving of Event Logs capability

Event Log retrieval is fairly a cumbersome task for the administrators from all the configured servers individually. BizTalk360 provides to download all the Event Log messages in a single place. Archived Event Logs give a lot of insight into the performance of your BizTalk environment unless all the Event Logs are archived in a central location. This way operators are able to access them at any time.

BizTalk360 Advanced Event viewer Event Log collection performance improvement - Export to Excel capability

Changes in the Event Log Data Monitoring section

Monitoring BizTalk Servers in a connected environment is the prime requirement for organizations – large or small.

The first thing we wanted, was to show the common issues/problems in the blink of an eye when an administrator needs it. The Advanced Event Viewer, in the Operation section of BizTalk360, would show users instantly, details of any Event Log about their BizTalk Environment. To know more about operations of Advanced Event Viewer refer to this article.

The second thing was the exact opposite – if there are some issues that should never happen, but they did in your Biztalk Environment, we would want you to know about it as well – once again, instantly. This is why we have built advanced Data Monitoring for Event Logs.

Previously, irrespective of the server selection, all the configured sources are displayed in the sources drop-down list. Now, based on the server selection, the sources will be collected and listed. This would minimize the turnaround time of creating the data monitor by selecting the required sources easily. Below screenshot refers to the new changes done in our new version of BizTalk360. Using this Data Monitoring capability, BizTalk360 will continuously monitor without any manual intervention and attention.

BizTalk360 Advanced Event viewer Event Log collection performance improvement - Data Monitoring New screen

Conclusion

We are sure, this implementation will highly optimize the BizTalk360 Advanced Event Viewer collection logic. Happy migrating and try BizTalk360!!!

Get started with the free 30 days trial. For any queries/feedback please write to us support@biztalk360.com.

Author: Mekala Ramesh

Test Lead at BizTalk360 – Software Testing Engineer having diverse exposure in various features and application testing with a comprehensive understanding of all aspects of SDLC. Strong knowledge to establish the testing process from the scratch. Love to test the software product to deliver it with good quality. Strongly believes on “Testing goes beyond just executing the test protocol”.

How we solved daylight saving issue?

How we solved daylight saving issue?

DST in General

It is a universal practice around the world to observe daylight saving time(DST). We all moved our clocks one hour forward this last March. We woke up an hour sooner, had some additional espresso and tried to adjust to the jet-lag. Every spring we set the clocks forward and winter we turn the clock back. Most nations do not participate in DST and even within the USA, not all the states are participating in DST.

Real business scenario

In the software business, it is fundamental part to deal with business situations cautiously during the DST time. For instance, a company has rules created in an order taking system, that the order depends on the time of the order – if the clock changes, the rules might not be as clear. Like this, there are infinite scenarios we can consider.
In the integration business arena, a flow of the business information may happen from one end of the world to another. For this kind of situations, the business decision logic may work based on the time. Likewise, in BizTalk Server, administrators dependably should watch out for the deployed applications, its artifacts states and flow of the information. In case of anything turns out badly, there may be a huge effect on the mission-critical business (Eg: Banking, Insurance, Healthcare, Logistics etc.,). To stay away from these issues, BizTalk360 is used as an integral tool in 500+ business in 30+ nations.

Advanced Monitoring in BizTalk360

In BizTalk360, we have powerful monitoring capabilities to monitor the business information using the query builder functionality, which is looking for the information about suspended service instances, running service instances, tracked Service instances and tracked message events. Similarly, you can query BAM views, perform activity searches, filter out ESB exceptions, query the event logs and monitor Azure Logic apps.

Daylight Saving: Data Monitoring Dashboard

While monitoring this data, BizTalk360 will send notifications to many notification media. These media contain Email, SMS, inbuilt notification channels like Slack, ServiceNow, and Webhook. Customers can also create their own notification channels to receive the alerts from BizTalk360. To know more about our advanced data monitoring capability click here “https://assist.biztalk360.com/support/solutions/folders/1000221446”.

Problem Statement

We wanted to share our experience in solving a daylight-saving issue in our application for a specific scenario, where the email alerts are sent from the application properly during the normal days, whereas false alerts will be sent once during the daylight-saving time. We started investigating the scenario in deep to nail down the problem.

Forward Scenario

Consider below EST (Eastern Time Zone, UTC-5:00) DST change as an example.

Daylight Saving: Forward example

Set the system time zone settings as (UTC-08:00) Pacific Time (US & Canada) in BizTalk360.
Sunday, 11 March 2018, 02:00:00 clocks were turned forward 1 hour, to 03:00:00.
Let’s consider a scenario where Message Box data monitor is configured to monitor the suspended service instances for a purchase order application on an hourly basis. There is a column to show “Next Run At“ time which populates the next expected cycle for the data monitor. For an hourly based scenario, it will populate data consistently to notify the next run cycle. At the time of DST, in the 1:00 am cycle, next run time should be calculated as 3:00 am. Instead of this, Next run cycle is computed as 2:00 am. The BizTalk360 monitoring service will pick this time and try to convert the invalid time for further processing. Due to the invalid time, an exception appears in the email for only that monitoring cycle.


Daylight Saving: Email notification

Backward scenario

Sunday, 4 November 2018, 02:00:00 clocks are turned backward 1 hour to 01:00:00.
In the Fallback scenario, the issue won’t appear since the clock will be turned backward 1 hour and the monitoring service will come to look for the Next run time and wait until that time for further processing.

Code Snippet

As the problem stated above, DST adjustment has not been handled in the inbuilt .Net libraries. BizTalk360 properly calculates DST from V8.8 version onwards. In the below code snippet, in the highlighted text you can find the logic.

TimeZoneInfo timeZoneInfo = TimeZoneInfo.FindSystemTimeZoneById(regionalSetting.timezone.timezoneId);
if (timeZoneInfo.SupportsDaylightSavingTime)
{
    DateTime dateTime = nextRunDateTime;

    if (timeZoneInfo.IsAmbiguousTime(dateTime))
    {}

    if (timeZoneInfo.IsInvalidTime(dateTime))
    {
        DateTime adjustedDateTime = Helper.AdjustDateTimeForDSTChange
       (dateTime, regionalSetting);
    }
}

public static bool IsValidDateTime(DateTime dateTime, SystemRegionalSetting regionalSetting)
{
    TimeZoneInfo timeZoneInfo = TimeZoneInfo.FindSystemTimeZoneById
    (regionalSetting.timezone.timezoneId);

    return timeZoneInfo.IsInvalidTime(dateTime) ? false : true;
}

public static DateTime AdjustDateTimeForDSTChange(DateTime dateTime, SystemRegionalSetting regionalSetting)
{
    TimeZoneInfo timeZoneInfo = TimeZoneInfo.FindSystemTimeZoneById
    (regionalSetting.timezone.timezoneId);

    return dateTime.Add(timeZoneInfo.GetUtcOffset(dateTime.AddDays(1)) - timeZoneInfo.BaseUtcOffset);
}

Testing

Time conversion is much more complicated than you imagine, because different countries/locales switch to daylight saving time at different dates, it is not just one sweep change. Hence, we have thoughtfully derived the scenarios for testing to cover all the combinations.

Following are the test scenarios which we need to take care of during the DST testing:
1. UTC (Coordinated Universal Time)
2. GMT time zones which observers DST during summer time (Eg: British Summer Time)
3. UTC –(Minus) time zones which observe DST (Eg: Pacific Time US & Canada)
4. UTC –(Minus) time zones which don’t observe DST (Eg: Arizona)
5. UTC + (Plus) time zones which observe DST (CEST)
6. UTC +(Plus) time zones which don’t observe DST (IST)

Conclusion

We took a just more efficient way to solve the DST issue in our recent version 8.8. Happy migrating and try BizTalk360!!! Get started with the free 30 days trial. For any queries/feedback please write to us support@biztalk360.com.

Author: Mekala Ramesh

Test Lead at BizTalk360 – Software Testing Engineer having diverse exposure in various features and application testing with a comprehensive understanding of all aspects of SDLC. Strong knowledge to establish the testing process from the scratch. Love to test the software product to deliver it with good quality. Strongly believes on “Testing goes beyond just executing the test protocol”.

Our experience in solving “webHttp” issue

Our experience in solving “webHttp” issue

The top-secret to effective product service handling is to take each complaint seriously. Even if it’s simply a misinterpretation or a mistake on the part of the customer, every complaint deserves the wholehearted attention and special handling. In our support, we often receive tickets which require neither functional investigation nor a problem with the configuration.

Recently, we have received an interesting ticket and it took considerable time to resolve, though it looked like a simple issue to deal with. In this blog, we wanted to share the troubleshooting steps we have performed and how we solved the problem. It would help many of our customers in the future to identify the problem at first hand without spending much time.

After the successful installation of BizTalk360 in the customer environment, during the first launch, the below error message was shown in the browser.

“ERROR after first time install : The extension name ‘webHttp’ is not registered in the collection at system.serviceModel/extensions/behaviorExtensions”

solving “webHttp” issue in BizTalk360

Identifying the problem:

Firstly, BizTalk360 doesn’t require any change in the configuration file. But looking at the error clearly, it’s a configuration issue and it happened during the processing of the configuration file to service the request.  As our product is being used on critical business environments, we are generally cautious in suggesting the changes in the configuration file in the customer environment and as mentioned previously it is not required.

We started from the basic troubleshooting steps one by one.

Choosing the Solution:

Ensure “HTTP Activation” is enabled under WCF:

If the “HTTP Activation” is not enabled under the WCF services It doesn’t communicate with the HTTP network protocols over the network. Hence, we checked whether this is enabled in the “Windows roles and features Wizard”.

This option was enabled and other required roles and features were enabled as per the prerequisite document.

webHTTP issue in BizTalk360

ASP.Net re-registration/ Reinstallation:

As all the configurations are perfectly enabled, which BizTalk360 requires, we nailed down and suggested to ensure the .NET3.5 is installed properly on the machine since the error would occur only if .NET3.5 is not installed correctly. To ensure this, we recommended repairing the .NET3.5 configuration elements using the tool Workflow Services Registration(WFServicesReg.exe) using the below commands.

  1. Go to C:WINDOWSMicrosoft.NETFrameworkv3.5 
  2. Run WFServicesReg.exe /c

After repairing, BizTalk360 didn’t load and the same exception appeared.

Reregistering the ASP.Net and Service models:

The ASP.NET Registration tool can be used to install and uninstall the linked version of the ASP.NET. This tool will install the ASP.NET and update the script maps of all existing ASP.NET applications and updates both classic mode and integrate mode handlers in the IIS metabase. Hence, we suggested the below command to reregister the ASP.NET.

“%WINDIR%Microsoft.NetFrameworkv4.0.30319aspnet_regiis” –i –enable

The “ServiceModelReg.exe” tool provides an ability to manage the registering of WCF and WF components on a single machine. Since we are experiencing the problem with Service activation, we have suggested registering the components using the “Service modelReg.exe” tool by executing the below command.

“%WINDIR%Microsoft.NetFrameworkv4.0.30319ServiceModelReg.exe” -iru

Even after performing the above steps the problem still appeared in the browser while loading the BizTalk360.

Application pool Configuration verification:

It is important to make the value “true” for the property “Enable 32-bit Applications” as the machine is running on a 64-bit and it is important to access a 32-bit application running under IIS. This is because, by default, IIS launched CGI applications on 64-bit work process if you’re running it under a 64-bit Windows.

This option was set to “True” as well.

webHTTP issue in BizTalk360

Active Execution of the chosen Solution:

Always while resolving the customer solution, we shouldn’t worry about the failure. We need to concentrate on the journey that will lead you to resolve the issue. As we tried all the possible solutions to make it work, we turned our focus on the configuration files.

BizTalk360 Web.config File Investigation:

As per the default settings, all the necessary service model extensions were added as expected and they were not manipulated as shown in the below screenshot.

webHTTP issue in BizTalk360

ASP.NET 4.0 machine.config File Investigation:

We were confident, usually the machine.config file is not altered unless otherwise if there is any specific policy from the business. However, we thought of taking a look at the machine.config file for the .NET version v4.0 in the location “C:WindowsMicrosoft.NETFramework64v4.0.30319Config”.

This Final investigation made a trick and solved the problem.

How?

The “WebHttp” service model extension was manipulated with some other values than the default value in the machine.config file as highlighted in the below screenshot. After removing the additional letters. BizTalk360 loaded properly 😊!!!

webHTTP issue in BizTalk360

PS: We recommend keeping the default machine.config file as such by default. If there is any necessity to make changes in the “Machine.config” file as per any specific internal policy or rules, we recommend installing BizTalk360 on a separate server with default ASP.NET settings. So that, BizTalk360 will get loaded without any issues.

If you have any questions, feel free to contact us at support@biztalk360.com. We are happy to assist you.

Author: Mekala Ramesh

Test Lead at BizTalk360 – Software Testing Engineer having diverse exposure in various features and application testing with a comprehensive understanding of all aspects of SDLC. Strong knowledge to establish the testing process from the scratch. Love to test the software product to deliver it with good quality. Strongly believes on “Testing goes beyond just executing the test protocol”.

You asked, we attended: ServiceNow Notification Channel Enhancement

You asked, we attended: ServiceNow Notification Channel Enhancement

Support service is one facet of business that is important to every business, regardless of industry, it is vital to delivering the best service possible to all customers.

To deliver a great product service that builds customers confidence, you must pay attention to customer feedback. Customers are a wealth of information and they can help to develop a better product.

Notifications give users confidence about the environment health status and if there is any problem they can take immediate action to solve it. BizTalk360 being a one platform solution for monitoring the BizTalk Servers, it supplies quick integration with ServiceNow, Slack, Microsoft Teams, Webhook, apart from the default notification mediums – Emails and SMS. The integration is not restricted to just these channels, it is open to the customers. They can create their own custom notification channels which they use for work.

The above said Notification channels are by default bundled with BizTalk360 and make the customer life easier and not to spend much time on configuration. You can set up different alarm types (Threshold, Regular Health check, Data Monitoring) from BizTalk360 user interface and integrate with the desired Notification channels on which you want to receive the alerts.

In this article, we will be looking at the ServiceNow integration and how we have improved it in the upcoming BizTalk360 v8.6 release.

What are ServiceNow Integration’s existing fields?

In our upcoming Version 8.6 release, we have improved the ServiceNow notification channel based on the customer feedback, so here it is! For any ticketing system, the fields which are available will help the support personnel to determine the nature of the ticket and make the corrective action in a timely manner. Till V8.5 default ServiceNow notification channel has the below three fields.

  1. Short Description
  2. Impact
  3. Urgency

ServiceNow Notification channel in BizTalk360

From V8.6 version onwards we have added the following fields to help our customer’s precisely keep track of changes happening up to the minute in their environment. By using these new fields, they can configure the additional information about the ticket from BizTalk360.

  1. Assignment Group
  2. Category
  3. Sub Category
  4. Configuration Item
  5. Additional comments

ServiceNow Notification channel in BizTalk360

What happens during the Migration?

After the migration from earlier versions to v8.6, users can continue to work on the old template without any problem.

Let’s consider the below scenario:

A customer is using BizTalk360 version 8.4 presently and have configured 10 Alarms in their environment for monitoring and enabled the default ‘ServiceNow’ notification channel for sending the alerts. After the migration to the new version 8.6, there won’t be any change in the existing configuration in the alarms level. It will have the same configuration with the default 3 fields as such in V8.5

Once the user reconfigures the ServiceNow channel in Settings->Monitoring Notification->Manage Notifications channel, new changes will be applied. As per the configuration in BizTalk360, alert in ServiceNow channel will have the following fields.

ServiceNow Notification channel in BizTalk360

ServiceNow Notification channel in BizTalk360

Happy Migrating and try out the fresh installation once the release is announced!!! We are always happy to receive the customer’s feedback. Please write to support@biztalk360.com.

Author: Mekala Ramesh

Test Lead at BizTalk360 – Software Testing Engineer having diverse exposure in various features and application testing with a comprehensive understanding of all aspects of SDLC. Strong knowledge to establish the testing process from the scratch. Love to test the software product to deliver it with good quality. Strongly believes on “Testing goes beyond just executing the test protocol”.

BizTalk360 Support Team meets the Microsoft Escalation Team

BizTalk360 Support Team meets the Microsoft Escalation Team

biztalk360 team meets microsoft escalation support team

Community events are an integral part of BizTalk360. TechMeet360 is an innovative technology event drive taken by BizTalk360 where all the technical admirers integrate and get endless possibilities to learn and explore different cutting edge technologies.

On April 21st 2017, a whole organizing team of Global Azure Bootcamp 2017 was gearing up for the event. All the preparation was going on in full swing. I found the wave of enthusiasm spreading on everybody’s face and doings. Administration panel was busy with final checklist preparation and gift packaging. Our Event coordinators (Arun/Sriram/Kuppurasu) were busy with accommodation arrangements for the speakers. For the first time, Microsoft speakers (Deepak Rajendran, Harikharan Krishnaraju, Vinod Sundarraj, Amit Kumar Tripathi, Madhura Bharadwaj, Karan Singh) presented at a Coimbatore event. We wanted to improve our work culture and take inspiration from Microsoft, so we invited the speakers to the BizTalk360 office for a round of technical discussion. Originally planned for 1-hour session, went close to 2.5 hours. The entire engineering team was ready with a bunch of questions to be discussed with the team during the meeting which had been arranged.

With full of excitement, it was 6.30 pm in the evening and the team here at BizTalk360 was waiting for the arrival of the speakers from Microsoft product support group, excited to welcome the team in our office. After all the welcome formalities, as planned the discussion panel had been set up and the whole BizTalk360 engineering team – Microsoft meet up began with a warm introduction.

technical group discussion

Lucky people get opportunities (we are lucky enough to get the opportunity to work at BizTalk360 since we are community focussed and not just work focussed), brave people create opportunities (here we have awesome techies to create the opportunities), and the Winners are those who convert problems into opportunities (here we all are having a record of success to convert problems into opportunities, to solve one common problem). Precisely this is what our two flagship products are built with. To solve the problems in the integration platform, we have converted the problem into a solution.

Here at BizTalk360, all the above-said things are happening in the right proportion. Opportunities will knock just once. It is up to you to make yourself grow to the next level. Every day is a new start here to grab new ways of learning technology and shape yourself personally and professionally.

The discussion arranged with Microsoft product support team was a great opportunity for us to gather their experiences and make most out of it. Discussion started with how the support process guidelines the Microsoft escalation team. Regardless of the issue, how the given problem statement to be approached and how to build a good relationship with the customer is a most essential factor of our discussion. Be it a production issue or a staging, essentially we should understand the frustration level of the customer and go ahead with isolating the problem and navigate to the root-cause. On any fine day, an issue will get resolved, but the bond between the customer and the support engineers should last long. Treat the issue of the customer from your own shoes, this makes the customer gain lot of confidence in us and our product.

Our Understandings

As the support process, has been filtered at various levels according to the expertise, the first and foremost thing is to scope the issue:

Scoping:

Before you begin troubleshooting any problem, scoping is very important. You must distinguish what is working and what is not working. From the big picture to a small pixel as a Top-Down approach.

Isolation (narrow down to the exact root cause):

Once the problem is scoped, you need to identify where the root cause lies. A checklist would be helpful after the problem is scoped. By asking more information concerning the problem will be useful to confine it from real assumption.

A simple command prompt ping can save you from the issue. Usage of multiple troubleshooting/diagnosing tools should be used to narrow down the issue. Rather than using the external tools, we can always make use of the internal tools like command prompt, event logs and IIS trace which spares your investigating time. Additionally, open-source external tools like: Fiddler, Postman, Net-Stat, Wireshark and so on will comprehensively understand the issue.

How often can web meetings be scheduled with the customer?

Good relationship starts with a verbal conversation. It is always better to immediately get on a call with the customer to understand the problem instead of going through multiple email iterations.

adapting microsoft work culture

Conclusion

The team wrapped up after the informative and interactive session.

By the end of the discussion, we were able to get the crux of Customer handling, troubleshooting tips, Technical Knowledge, Escalation Engineering and lot of friendship.

In the process of growth of our support process, we are further adapting/implementing the suggestions from the MS Escalation team to get acquainted with our customer expectations.

Author: Mekala Ramesh

Test Lead at BizTalk360 – Software Testing Engineer having diverse exposure in various features and application testing with a comprehensive understanding of all aspects of SDLC. Strong knowledge to establish the testing process from the scratch. Love to test the software product to deliver it with good quality. Strongly believes on “Testing goes beyond just executing the test protocol”.

BizTalk360 Support Team meets the Microsoft Escalation Team

BizTalk360 Support Team meets the Microsoft Escalation Team

biztalk360 team meets microsoft escalation support team

Community events are an integral part of BizTalk360. TechMeet360 is an innovative technology event drive taken by BizTalk360 where all the technical admirers integrate and get endless possibilities to learn and explore different cutting edge technologies.

On April 21st 2017, a whole organizing team of Global Azure Bootcamp 2017 was gearing up for the event. All the preparation was going on in full swing. I found the wave of enthusiasm spreading on everybody’s face and doings. Administration panel was busy with final checklist preparation and gift packaging. Our Event coordinators (Arun/Sriram/Kuppurasu) were busy with accommodation arrangements for the speakers. For the first time, Microsoft speakers (Deepak Rajendran, Harikharan Krishnaraju, Vinod Sundarraj, Amit Kumar Tripathi, Madhura Bharadwaj, Karan Singh) presented at a Coimbatore event. We wanted to improve our work culture and take inspiration from Microsoft, so we invited the speakers to the BizTalk360 office for a round of technical discussion. Originally planned for 1-hour session, went close to 2.5 hours. The entire engineering team was ready with a bunch of questions to be discussed with the team during the meeting which had been arranged.

With full of excitement, it was 6.30 pm in the evening and the team here at BizTalk360 was waiting for the arrival of the speakers from Microsoft product support group, excited to welcome the team in our office. After all the welcome formalities, as planned the discussion panel had been set up and the whole BizTalk360 engineering team – Microsoft meet up began with a warm introduction.

technical group discussion

Lucky people get opportunities (we are lucky enough to get the opportunity to work at BizTalk360 since we are community focussed and not just work focussed), brave people create opportunities (here we have awesome techies to create the opportunities), and the Winners are those who convert problems into opportunities (here we all are having a record of success to convert problems into opportunities, to solve one common problem). Precisely this is what our two flagship products are built with. To solve the problems in the integration platform, we have converted the problem into a solution.

Here at BizTalk360, all the above-said things are happening in the right proportion. Opportunities will knock just once. It is up to you to make yourself grow to the next level. Every day is a new start here to grab new ways of learning technology and shape yourself personally and professionally.

The discussion arranged with Microsoft product support team was a great opportunity for us to gather their experiences and make most out of it. Discussion started with how the support process guidelines the Microsoft escalation team. Regardless of the issue, how the given problem statement to be approached and how to build a good relationship with the customer is a most essential factor of our discussion. Be it a production issue or a staging, essentially we should understand the frustration level of the customer and go ahead with isolating the problem and navigate to the root-cause. On any fine day, an issue will get resolved, but the bond between the customer and the support engineers should last long. Treat the issue of the customer from your own shoes, this makes the customer gain lot of confidence in us and our product.

Our Understandings

As the support process, has been filtered at various levels according to the expertise, the first and foremost thing is to scope the issue:

Scoping:

Before you begin troubleshooting any problem, scoping is very important. You must distinguish what is working and what is not working. From the big picture to a small pixel as a Top-Down approach.

Isolation (narrow down to the exact root cause):

Once the problem is scoped, you need to identify where the root cause lies. A checklist would be helpful after the problem is scoped. By asking more information concerning the problem will be useful to confine it from real assumption.

A simple command prompt ping can save you from the issue. Usage of multiple troubleshooting/diagnosing tools should be used to narrow down the issue. Rather than using the external tools, we can always make use of the internal tools like command prompt, event logs and IIS trace which spares your investigating time. Additionally, open-source external tools like: Fiddler, Postman, Net-Stat, Wireshark and so on will comprehensively understand the issue.

How often can web meetings be scheduled with the customer?

Good relationship starts with a verbal conversation. It is always better to immediately get on a call with the customer to understand the problem instead of going through multiple email iterations.

adapting microsoft work culture

Conclusion

The team wrapped up after the informative and interactive session.

By the end of the discussion, we were able to get the crux of Customer handling, troubleshooting tips, Technical Knowledge, Escalation Engineering and lot of friendship.

In the process of growth of our support process, we are further adapting/implementing the suggestions from the MS Escalation team to get acquainted with our customer expectations.

Author: Mekala Ramesh

Test Lead at BizTalk360 – Software Testing Engineer having diverse exposure in various features and application testing with a comprehensive understanding of all aspects of SDLC. Strong knowledge to establish the testing process from the scratch. Love to test the software product to deliver it with good quality. Strongly believes on “Testing goes beyond just executing the test protocol”.

BizTalk360 Support Team meets the Microsoft Escalation Team

BizTalk360 Support Team meets the Microsoft Escalation Team

biztalk360 team meets microsoft escalation support team

Community events are an integral part of BizTalk360. TechMeet360 is an innovative technology event drive taken by BizTalk360 where all the technical admirers integrate and get endless possibilities to learn and explore different cutting edge technologies.

On April 21st 2017, a whole organizing team of Global Azure Bootcamp 2017 was gearing up for the event. All the preparation was going on in full swing. I found the wave of enthusiasm spreading on everybody’s face and doings. Administration panel was busy with final checklist preparation and gift packaging. Our Event coordinators (Arun/Sriram/Kuppurasu) were busy with accommodation arrangements for the speakers. For the first time, Microsoft speakers (Deepak Rajendran, Harikharan Krishnaraju, Vinod Sundarraj, Amit Kumar Tripathi, Madhura Bharadwaj, Karan Singh) presented at a Coimbatore event. We wanted to improve our work culture and take inspiration from Microsoft, so we invited the speakers to the BizTalk360 office for a round of technical discussion. Originally planned for 1-hour session, went close to 2.5 hours. The entire engineering team was ready with a bunch of questions to be discussed with the team during the meeting which had been arranged.

With full of excitement, it was 6.30 pm in the evening and the team here at BizTalk360 was waiting for the arrival of the speakers from Microsoft product support group, excited to welcome the team in our office. After all the welcome formalities, as planned the discussion panel had been set up and the whole BizTalk360 engineering team – Microsoft meet up began with a warm introduction.

technical group discussion

Lucky people get opportunities (we are lucky enough to get the opportunity to work at BizTalk360 since we are community focussed and not just work focussed), brave people create opportunities (here we have awesome techies to create the opportunities), and the Winners are those who convert problems into opportunities (here we all are having a record of success to convert problems into opportunities, to solve one common problem). Precisely this is what our two flagship products are built with. To solve the problems in the integration platform, we have converted the problem into a solution.

Here at BizTalk360, all the above-said things are happening in the right proportion. Opportunities will knock just once. It is up to you to make yourself grow to the next level. Every day is a new start here to grab new ways of learning technology and shape yourself personally and professionally.

The discussion arranged with Microsoft product support team was a great opportunity for us to gather their experiences and make most out of it. Discussion started with how the support process guidelines the Microsoft escalation team. Regardless of the issue, how the given problem statement to be approached and how to build a good relationship with the customer is a most essential factor of our discussion. Be it a production issue or a staging, essentially we should understand the frustration level of the customer and go ahead with isolating the problem and navigate to the root-cause. On any fine day, an issue will get resolved, but the bond between the customer and the support engineers should last long. Treat the issue of the customer from your own shoes, this makes the customer gain lot of confidence in us and our product.

Our Understandings

As the support process, has been filtered at various levels according to the expertise, the first and foremost thing is to scope the issue:

Scoping:

Before you begin troubleshooting any problem, scoping is very important. You must distinguish what is working and what is not working. From the big picture to a small pixel as a Top-Down approach.

Isolation (narrow down to the exact root cause):

Once the problem is scoped, you need to identify where the root cause lies. A checklist would be helpful after the problem is scoped. By asking more information concerning the problem will be useful to confine it from real assumption.

A simple command prompt ping can save you from the issue. Usage of multiple troubleshooting/diagnosing tools should be used to narrow down the issue. Rather than using the external tools, we can always make use of the internal tools like command prompt, event logs and IIS trace which spares your investigating time. Additionally, open-source external tools like: Fiddler, Postman, Net-Stat, Wireshark and so on will comprehensively understand the issue.

How often can web meetings be scheduled with the customer?

Good relationship starts with a verbal conversation. It is always better to immediately get on a call with the customer to understand the problem instead of going through multiple email iterations.

adapting microsoft work culture

Conclusion

The team wrapped up after the informative and interactive session.

By the end of the discussion, we were able to get the crux of Customer handling, troubleshooting tips, Technical Knowledge, Escalation Engineering and lot of friendship.

In the process of growth of our support process, we are further adapting/implementing the suggestions from the MS Escalation team to get acquainted with our customer expectations.

Author: Mekala Ramesh

Test Lead at BizTalk360 – Software Testing Engineer having diverse exposure in various features and application testing with a comprehensive understanding of all aspects of SDLC. Strong knowledge to establish the testing process from the scratch. Love to test the software product to deliver it with good quality. Strongly believes on “Testing goes beyond just executing the test protocol”.