What's New in BizTalk Server 2013 and 2013 R2
See what's new and what is deprecated in BizTalk Server 2013 R2 and BizTalk Server 2013.
What’s New in BizTalk Server 2013 R2?
|Support for new versions of Windows OS, SQL Server, and Visual Studio||See Hardware and Software Requirements for BizTalk Server 2013 and 2013 R2.|
|Support for JSON||BizTalk Server now supports sending and receiving JSON messages. BizTalk Server includes a wizard to generate XSD schema from a JSON instance, and an Encoder and Decoder component to use with custom pipelines. For more information, see Processing JSON messages using BizTalk Server.|
|Updates to the SB-Messaging adapter||SB Messaging adapter is enhanced to support SAS (Shared Access signature) based authentication, in addition to ACS. With this new improvement, BizTalk Server can now also interact with the on-prem edition of Service Bus. For more information, see SB-Messaging Adapter.|
|Updates to the SFTP adapter||SFTP adapter now supports two-factor authentication and provides an option to specify a temporary folder while uploading/downloading large files. You can also select the Encryption cipher value specific to your target server. For more information, see SFTP Adapter.|
|Updates to HL7 Accelerator||HL7 Accelerator now supports the following:
- Provides capability to include free-text data as part of the message that can be processed by the HL7 pipelines.
- 64-bit support for hosting Hl7 adapter.
See What's New in BizTalk Accelerator for HL7.
|BizTalk Health Monitor||BizTalk Health Monitor is a new BizTalk snap-in that helps monitor the health of your BizTalk Server environment. This snap-in can be added to the existing BizTalk Administration Console or can be run individually. Following are the features of BizTalk Health Monitor:
- Generate and view a health report
- Dashboard view for overall health of BizTalk environment
- Send e-mail notifications
- Schedule report collection
- Performance monitor integration with pre-loaded scenario-based performance counters
- Monitor multiple BizTalk environments
- Report management
For more information on BizTalk Health Monitor, see Getting Started with BizTalk Health Monitor and Overview of BizTalk Health Monitor.
|SharePoint SSOM/Web Service adapter||Deprecated||Use the CSOM (Client Side Object Model) option.
Windows SharePoint Services Adapter
Appendix B: Install the Microsoft SharePoint Adapter
|SOAP adapter||Deprecated||WCF-BasicHttp Adapter|
|Old SQL adapter||Deprecated||WCF-based SQL adapter in the BizTalk Adapter Pack|
Some of these deprecated features may be found in newer versions of BizTalk. In these scenarios, consider the following:
- The feature may be used internally within BizTalk and is not meant to be used by customer solutions. It is not supported in customer solutions.
- The interfaces may have been modified by Microsoft and may not be publicly available.
What’s New in BizTalk Server 2013?
The following features are added in BizTalk Server 2013.
BizTalk Server on Azure IaaS
|Configure BizTalk Server on a Microsoft Azurevirtual machine||See Create a BizTalk Virtual Machine in Windows Azure.|
|Create a BizTalk Server Group on a Microsoft Azurevirtual machine||See Create the BizTalk Group Prerequisites and Configure the BizTalk Group.|
BizTalk Server on Premises
|Per Core License Model||BizTalk Server 2013 is per core. SQL Server 2012 is also per core. BizTalk Server 2010 and previous versions are per-processor.
When running BizTalk Server on processors with four cores or less, the license cost remains consistent with BizTalk Server 2010. Core licenses are priced at one quarter the cost of a processor license. When running servers with higher capacity processors, licensing cost are increased due to the increased power of the hardware.
To help determine the number of licenses you may need, a PowerShell cmdlet in C:\Program Files (x86)\Microsoft BizTalk Server 20xx\SDK\Utilities\LicenseUsageTracking is available.
BizTalk Server 2013 Pricing & Editions
Understand BizTalk Server 2013 Licensing
|Support for new Adapters||BizTalk Server provides new adapters to extend connectivity of BizTalk Server applications to Microsoft Azure. BizTalk Server also provides updates to SharePoint adapter that gives users the option of choosing between using the client-side or server-side object model for connecting to a SharePoint server. BizTalk Server includes a new adapter to send and receive messages from an SFTP server.|
|Tracking dependencies between artifacts||BizTalk Server updates the BizTalk Server Administraton console to provide a UI-driven experience to see how different BizTalk Server artifacts such as orchestrations, send ports, receive locations, etc. are dependent on each other. For more information, see Tracking Dependencies Between Artifacts in a BizTalk Server Application|
|Integrated ESB Toolkit||ESB Toolkit is now integrated as part of the BizTalk Server setup. Also, the ESB Toolkit configuration experience is simplified to facilitate quick start time for users. For more information, see Install and Configure the Microsoft BizTalk ESB Toolkit|
|Support for new versions of Windows OS, SQL Server, and Visual Studio||See Hardware and Software Requirements for BizTalk Server 2013 and 2013 R2|
|Updates to the supported EDI schemas||BizTalk Server introduces support for the following EDI schemas:
- X12 – 5040, 5050, 6020, 6030
- EDIFACT – D06A, D06B, D07A, D07B, D08A, D08B, D09A, D09B, D10A, D10B
- HL7 – 2.51 message support added
- SWIFT – 2012 Message Pack
The schemas are included in the BizTalk Server installation package. You can download the installation package from https://go.microsoft.com/fwlink/p/?LinkId=258228.
|Mapper uses XSLCompiledTransform||The Mapper uses the XSLCompiledTransform class. Previous BizTalk Server versions used the XslTransform class, which is obsolete. The XSLCompiledTransform class provides performance enhancements, including:
- Once the Load method completes successfully, the Transform method can be called simultaneously from multiple threads.
- The new XSLT processor compiles the XSLT style sheet to a common intermediate format. Once the style sheet is compiled, it can be cached and reused.
More information at What the Mapper Updates Mean for You and XslCompiledTransform Class.
|Configurable Dynamic Send Port Handler||When creating a Dynamic Send Port, an adapter Send Handler is configurable for every installed adapter. Includes both One-Way and Solicit-Response Dynamic Ports. In previous BizTalk versions, a dynamic send port uses the adapter’s default host.
Dynamic Send Port Handler is Configurable provides more information.
|Ordered Delivery||In previous BizTalk versions with scenarios where ordered delivery uses multiple endpoints, the slowest adapter type is the maximum speed. This behavior directly impacts HL7 solutions. When using the MLLP adapter, acknowledgements (ACK) are required. Delays can occur because an ACK must be received before the next message is sent.
In BizTalk Server, the next message can be sent without waiting for an ACK from the previous message. When the ACK arrives, it is internally correlated/connected with its message.
|Support Tools||Support Tools is automatically installed with BizTalk: C:\Program Files (x86)\Microsoft BizTalk Server 20xx\SDK\Utilities\Support Tools.
- BizTalk Assembly Checker
- MsgBox Viewer
- Internet shortcut to BizTalk Terminator download
|PowerShell Provider||The BizTalk Server PowerShell Provider is in C:\Program Files (x86)\Microsoft BizTalk Server 2013\SDK\Utilities\PowerShell|
|BAM Alerts||If BizTalk Server 2013 uses SQL Server 2012, Database Mail is needed to use BAM Alerts. If BizTalk Server uses SQL Server 2008 R2, SQL Server Notification Services is needed to use BAM Alerts.
BAM Alerts provides more information.
When BizTalk Server and SQL Server are installed on separate computers, Distributed Transaction Coordinator (MS DTC) handles the transactions between the computers. As a result, the SQL Server AlwaysOn feature is not supported with BizTalk Server 2013 R2 and 2013. Starting with BizTalk Server 2016, the AlwaysOn feature is supported. See What's New in BizTalk Server 2016 for the details.