Blog
 

When it comes to troubleshooting operational problems in BizTalk Server, the first place the BizTalk administrator or support person will look is the standard BizTalk Admin Console. Once if they can't find anything obvious in the Admin Console, their next point of search will be the Event Viewer in the physical BizTalk Server machines and sometimes...

SOAP & REST based Web Services are one of the most used technologies in integration scenarios. In the last few years, the need for HTTP based communication with external vendors/systems has increased significantly. Pretty much it became a norm to expose the API's of the system for external consumption. Examples: Salesforce API, Microsoft Graph API...

As you will probably be aware of, BizTalk Server heavily relies on SQL Server databases for storing, for example, the configuration of BizTalk artifacts and the state of in-flight and completed processes. After installing and configuring BizTalk Server, few databases are created. The most important databases are the Configuration database, the...

Microsoft BizTalk Server being a middleware platform sitting right in the middle of the organisation connecting all the systems together, it's inevitable there will be some regular operational challenges. When you are talking to multiple systems, it's hard to control every end systems. Some of the common problem you encounter will be a partner...

To be able to do his job, a BizTalk administrator needs to know what kind of processes flow through the BizTalk environment. This insight can be used for a number of purposes, like:

In their day to day operations, BizTalk administrators will regularly need to check the status of different BizTalk artifacts. There might be multiple reasons to do so, amongst which are:

Recently I was designing a Cosmos DB SQL API solution for a client. During testing we were constantly getting http status code 429 - Too many Requests errors. We manually had to increase the Throughput for a collection. This got to be tedious.