What's New in BizTalk Server 2013 and 2013 R2
The release notes for the BizTalk Server 2013 and 2013 R2 release contain the following information:
What’s New in BizTalk Server 2013 R2?
BizTalk Server supports the following platform stack:
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:
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:
SharePoint SSOM/Web Service adapter
Use the CSOM (Client Side Object Model) option.
Old SQL adapter
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: |
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 Windows Azure virtual machine
Create a BizTalk Server Group on a Windows Azure virtual machine
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.
Support for new Adapters
BizTalk Server provides new adapters to extend connectivity of BizTalk Server applications to Windows 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
Updates to the supported EDI schemas
BizTalk Server introduces support for the following EDI schemas:
The schemas are included in the BizTalk Server installation package. You can download the installation package from http://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:
For more information on the XSLCompiledTransform class, go to 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.
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 is automatically installed with BizTalk: C:\Program Files (x86)\Microsoft BizTalk Server 20xx\SDK\Utilities\Support Tools.
The BizTalk Server PowerShell Provider is in C:\Program Files (x86)\Microsoft BizTalk Server 2013\SDK\Utilities\PowerShell.
For previous BizTalk versions, there’s a CodePlex PowerShell Provider at http://psbiztalk.codeplex.com/.
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. The SQL Server AlwaysOn feature does not support MSDTC transactions.|
© 2014 Microsoft Corporation. All rights reserved.