Codeplex shutting down – BizTalk Tools

It was announced in March that Codeplex was shutting down.

As of this post, we’ve disabled the ability to create new CodePlex projects.  In October, we’ll set CodePlex to read-only, before shutting it down completely on December 15th, 2017.

So various tools and code that are used for BizTalk have moved to a new home.

Below is a list of their new locations

Projects not yet moved

Gone

Does anyone know where the below has gone?

  • PowerShell Provider BizTalk see Archive copy
    • For BizTalk 2010 or earlier, Matt Corr from Mexia posted a copy of the BizTalkFactory.PowerShell.Extensions.Setup – v1.4.0.1.msi here on his Dropbox account: https://t.co/0Oe1WSkO7X
    • With BizTalk 2013 onwards, the PowerShell Provider comes with the BizTalk SDK: C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\SDK\Utilities\PowerShell
    • A copy of the Getting Started Guide for 1.4.0.1 can be found here 

 

If you have other tools that you know off, feel free to share in the comments.

Advertisements

Tokenizing the BizTalk Tracking Settings

At my work, for all new BizTalk projects we use the BizTalk Deployment Framework (BTDF).  One of the features it has is to have a master binding file where you tokenize some of the settings that vary between environments such as URLs and usernames.

We have also started tokenizing the BizTalk tracking settings.  This means that your deployment will automatically have different tracking for different environments and you don’t accidentally blow out your tracking database in Production by having body tracking on, but have it on the environments you are most likely to need it, like Development ones.

Full Body tracking in Development,  less tracking in Test and Production.
Below is what the SettingsFileGenerator.xml looks like
TrackingSettings
And in your PortBindingMaster.xml some examples of how to use these.
For Orchestrations
<Service …… TrackingOption=”${Orchestration_Tracking}” >
 
In the Send and Receive Ports
<Tracking>${OneWay_SendPort_Tracking}</Tracking>
And the Pipelines
<ReceivePipeline …. TrackingOption=“${Pipeline_Tracking}” />

BizTalk Assessment: How to check if Windows Defender is running on BizTalk Server with PowerShell — SANDRO PEREIRA BIZTALK BLOG

Sandro Pereira wrote a blog about Windows Defender and BizTalk 2016.   Well worth a read.

Why checking if Windows Defender is running on BizTalk Server, or another anti-virus, is important?

They tend to be a little slow, so tuning it well is important for archive a better performance and by default Windows Defender is configured on that machines. Not only as a negative impact in the general performance of the machine but also can have a huge impact on BizTalk Server performance.

Read the article here BizTalk Assessment: How to check if Windows Defender is running on BizTalk Server with PowerShell — SANDRO PEREIRA BIZTALK BLOG

.Net 4.6 now supported for BizTalk 2013 R2, BHM 4.1 released

Over a year ago we hit a situation where we got a warning from BHM about .Net 4.6 not being supported, which was a bit of effort to sort out.

Today I looked at the release notes for the latest BizTalk Health Monitor, v4.1 and noticed that in the release notes it said “Removed BizTalk 2013 R2 .NET 4.6.x warning since it is now supported”.   I then checked Hardware and Software Requirements for BizTalk Server 2013 and 2013 R2 and sure enough, they have now listed .Net 4.6 as supported for BizTalk 2013 R2.

Here are the other changes for BizTalk Health Monitor

• Fixed issue with losing monitoring configuration
• Upgraded update mechanism to handle all components of BHM
• Added support for displaying each view of a BHM report in HTML format
• Improved update to happen on secondary thread
• Improved the ChkBHMRep.exe tool
• Added support for BizTalk 2013 R2 CU6, BizTalk 2016 CU1, and BizTalk 2016 FP1 (Feature Pack 1)
• Improved report to provide DTA purge job parameters with improved formatting
• Added warning for infinite max SQL memory config
• Fixed some issues with detecting Host Integration Server CUs
• Removed BizTalk 2013 R2 .NET 4.6.x warning since it is now supported
• Updated query and rules repository

 

BizTalk Documenter – Moved to Github

Do the the impending closure of CodePlex, the BizTalk Documenter project has been moved to Github

It needs a bit of work to ensure that all the prerequisites are automatically included as per the issue #1 Unable to build.   Just a matter of finding the time or a volunteer to get this done.

If you have any other issues or suggestions for improvement, please do raise it as an issue.

Cumulative Update package 6 for BizTalk Server 2013 R2

CU 6 for BizTalk Server 2013 R2 is out, details are here.

Summary.

There are 16 issues fixed in this CU.

There are 6 fixes to do with the SAP adapter to do with the NCo connection type.  So if you use that and are having issues you will probably want to release this to your test environments ASAP and re-test.

There are 2 fixes to do with File receive locations using alternate credentials.

2 fixes for the MIME/sMime pipeline component.

1 Fix each for the JSON decoder, MQ Series adapter, FTP adapter, message tracking and BizTalk DTA.

For some reason they have not yet updated the page Service Pack and cumulative update list for BizTalk Server to include this CU as yet.

BizTalk Server 2016 Cumulative Update Pack 1

CU 1 for BizTalk Server 2016 is out, was announced and available here.

It includes

A list of all CU’s for all versions of BizTalk back to 2006 R2 can be found at kb 2555986 Service Pack and cumulative update list for BizTalk Server

Also see How to check the CU level of BizTalk Server quickly