Cumulative Update 5 for BizTalk Server 2013

The Cumulative update package 5 for BizTalk Server 2013 is out, kb 3194301

A mixed bag of fixes in this CU including two fixes for issues caused by two previous CUs.

3165515 & 3167704 were also in CU 4 for BizTalk 2013 R2 and 3142269 was in CU3 for R2, but some of the others may still have to be released in another CU for Biztalk 2013 R2 if they are an issue. Continue reading

BizTalk SSO & SSO Affiliate Settings

Recently at my work we’ve started using SSO Affiliate Applications to store credentials for Receive Locations and Send Ports to avoid either having the credentials in the Bindings (which is insecure) or having to re-enter the credentials after each release (which causes releases to take too long). I won’t go into details how we do that in this post, however as part of documenting this ability I went through all the adapters to see which could use SSO Affiliate Applications and which couldn’t.

Continue reading

How to check the CU level of BizTalk Server quickly

Sandro Pereira has written PowerShell scripts to quickly check the CU level of BizTalk Server

For 2010

See his blog How to check what BizTalk Server 2010 Cumulative Updates are installed in your Servers with PowerShell

Download the script from Check what BizTalk Server 2010 Cumulative Updates are installed with PowerShell

For 2013

See his blog How to check what BizTalk Server 2013 Cumulative Updates are installed in your Servers with PowerShell

Download the script from Check all BizTalk 2013 Cumulative Updates installed in server with PowerShell

For 2013 R2.

See his blog How to Check/Get the list of all BizTalk Cumulative Updates installed in the machine with PowerShell — Sandro Pereira BizTalk Blog

Download the script from Technet: Check all BizTalk Cumulative Updates installed in server with PowerShell

For 2016

See his blog How to check what BizTalk Server 2016 Cumulative Updates are installed in your Servers with PowerShell

Download script from Check what BizTalk Server 2016 Cumulative Updates are installed with PowerShell

Salesforce disabling TLS 1.0 – How to get it working for API calls via BizTalk

An approach we were considering to keep BizTalk connecting to Salesforce when they disable TLS 1..0

BizTalkBox

Salesforce will soon be disabling TLS 1.0 support.

Starting in June 2016, Salesforce will begin disabling the TLS 1.0 encryption protocol in a phased approach across impacted Salesforce services. The disablement of TLS 1.0 will prevent it from being used to access the Salesforce service within inbound and outbound connections.

More Details

In Continuation to the great post on how to call salesforce APIs via BizTalk , the WCF behaviour can be extended to inforce any other TLS protocol.

ApplyClientBehaviour method can be modified to apply security protocol on the outgoing messages. By default this is SSL 1.0

TLSBehavoir

You can pass on the parameter from the configuration like the other params.

SEcurityProtocol

WCF Behaviour extension would look something like.

BizTalkConfigTLS

View original post

BizTalk 2013 R2 known bugs, issues & quirks

Featured

Below a list of know bugs, issues, & other quirks* of BizTalk 2013 R2 (mainly CU3) and Visual Studio 2013 (update 4) , but I will update with fixes as the CUs come out or when I know about a new issue, so if you have another one I will add it (and link to it if you have a blog about it) if you let me know.

* My definitions for classifying these are
Bug
: Causes negative impact and no known work around or requires a lot of effort to work around.
Issue: Causes negative impact but has an easy or quick work around.
Missing: A feature that BizTalk doesn’t have that would make our life easier.
Quirk:  Something strange or unusual but does not cause a negative impact so far as known.

Continue reading