Close

BizTalk CAT

The BizTalk CAT Instrumentation Framework is a high performance tracing/logging framework for BizTalk that builds upon the Event Tracing for Windows (ETW) infrastructure. The Controller is designed for use both on development machines and production servers. Compared to System.Diagnostic.Trace, Enterprise Library Tracing or Log4Net, CAT has a negligible impact on performance. To use the BizTalk CAT…

BizTalk 2016 and SQL Server AlwaysOn

Below description is a summary of: High Availability using SQL Server Always On Availability Groups. Traditionally, BizTalk uses SQL Server Failover Clustering and Log Shipping to provide high availability, backup and restore, and disaster recovery for its on-premises databases. In Azure IaaS (Azure virtual machines), previous versions of SQL Server do not support Failover Cluster Instances…

WCF-WebHttp adapter in BizTalk

Configuring a WCF-WebHttp send port for calling a REST service in BizTalk is pretty straight-forward. On the General tab specifiy a base URL and a BtsHttpUrlMapping. For instance: Base URL: https://service.local:8443 <BtsHttpUrlMapping> <Operation Method=”PUT” Url=”/api/Contact/{UID}” /> </BtsHttpUrlMapping> In this case the URL contains a variable which can be specified via the variable mapping. Note that…

Use ESB Exception Handling Only

Most of the time, you only want to use the exception handling functionality of the ESB Toolkit. In that case you can include the necessary artefacts in a BizTalk.Framework application. You will still have to create the ESB Exception database via the ESB Configuration Tool first. Next, in case you use the BizTalk Deployment Framework…

Dealing with SOAP faults in orchestrations

Suppose you have to call a SOAP service that doesn’t return typed SOAP faults, but only untyped SOAP faults. In that case, when you hit Add Generated Items / Consume WCF Service, you will get a porttype with operations that only have request and response messages. To catch untyped soap faults, you will have to…

Reconfigure BizTalk

Let’s say you have a configured BizTalk Server in development with a few applications running and various custom host instances. Let’s say you configured BizTalk using a local admin account and instead you wanna configure BizTalk with a domain admin account. Enterprise SSO and all BizTalk host instances have to be running under the domain…

Cannot use Add Generated Items

In a BizTalk project I had a problem that I couldn’t use Add Generated Items to consume a webservice and generate the orchestration (plus porttypes and messagetypes in message types in orchestration view), messages and bindings. What I did have was a WSDL file, yet not a so-called single wsdl. For that reason I first had…

BizTalk terminate instances

Recently I had a problem that I couldn’t delete a running instance in BizTalk. So, I tried to install the BizTalkTerminator, but I kept getting an error when trying to start up the terminator. Luckily I found a SQL script you can run to reslove the issue. Remember to first stop all BizTalk instances and…

Moving BizTalk and system databases

After installation of BizTalk and SQL Server I found that the SQL Server data files were stored on the installation drive, directory D:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\. The client had explicitly indicated that the data files should be stored on the G drive and the log files on the H drive. I found that I had to…