BizTalk Server
Availability
| Product Version and Edition | Date Available |
|---|---|
| BizTalk Server 2020 Enterprise (Core License) | February 2020 |
| BizTalk Server 2020 Standard (Core License) | February 2020 |
| BizTalk Server 2020 Branch (Core License) | February 2020 |
Use Rights
| License Terms: Universal License Terms | Product-Specific License Terms: Standard and Branch editions | Prior Version: BizTalk Server 2016 |
| Additional Software: All editions | Client Software: All editions (includes Additional Software) | Disaster Recovery: All editions |
| Included Technologies: Windows Software Components | License Mobility: Yes |
Additional Terms for BizTalk Server Standard and BizTalk Server Branch
Use Limitation
Customer may not use the server software, including the Master Secret Server, on a Server that is part of a networked cluster or in an OSE that is part of a networked cluster of OSEs on the same Server.
Office Web Component
Customer may use the Office Web Component only to view and print copies of static documents, text and images created with the software. Customer does not need separate licenses for copies of the component.
Additional Terms for BizTalk Server Branch
Customer may use Running Instances of the software on Licensed Servers only at the endpoint of its internal network (or edge of its organization) to connect business events or transactions with activities processed at that endpoint. The Licensed Server may not:
- act as the central node in a “hub and spoke” networking model;
- centralize enterprise-wide communications with other Servers or devices; or
- automate business processes across divisions, business units, or branch offices.
Licensing Use of Host Integration Server (HIS)
Customer may use HIS server software and Additional Software under the terms and conditions of the Per Core (Applications) License Model using BizTalk Server core licenses. Customer may use HIS Additional Software (e.g., HIS Client) only in conjunction with its licensed use of HIS server software. The rights applicable to this use are determined by which edition and version of BizTalk Server licenses Customer assigns to the Server (e.g., unlimited virtualization rights require BizTalk Server Enterprise licenses). Use of HIS server software is limited to branch office deployments if used under the BizTalk Server Branch Edition licenses).
Additional Software
| Administration and Monitoring Tools | ADOMD.NET | BizTalk Server Related Schemas and Templates |
| Business Activity Monitoring (“BAM”) Client | BAM Alert Provider for SQL Notification Services | BAM Event APIs and Interceptors and Administration Tools |
| Business Activity Services | Business Rules Component | Development Tools |
| HTTP Receive Adapter | Master Secret Server/Enterprise Single Sign-On | MQHelper.dll |
| MQSeries Agent | MSXML | SOAP Receive Adapter |
| Software Development Kit(s) | SQLXML | UDDI |
| Windows Communication Foundation Adapters | Windows SharePoint Services Adapter Web Services |
License Model
Per Core (Applications)
For Products under the Per Core (Applications) License Model, Customer must choose either licensing by Physical Core on a Server or licensing by Individual Virtual OSE. The terms for each are set forth below.
Server Licenses (per core) – Licensing by Physical Core on a Server
- Customer may use the server software on a Licensed Server, provided it acquires sufficient Licenses as described below.
- The number of Licenses required equals the number of Physical Cores on the Licensed Server subject to a minimum of four per core Licenses per Physical Processor.
- For enterprise editions, Customer may use any number of Running Instances of the server software on the Licensed Server in the Physical OSE and/or any number of Virtual OSEs.
- For other editions Customer may use any number of Running Instances of the server software only in the Physical OSE on the Licensed Server.
Server Licenses (per core) – Licensing by Individual Virtual OSE
- Customer may use any number of Running Instances of the server software in any Virtual OSE on the Licensed Server, provided it acquires sufficient Licenses as described below.
- The number of Licenses required equals the number of Virtual Cores in the Virtual OSE, subject to a minimum of four License per Virtual OSE.
- If any Virtual Core is at any time mapped to more than one Hardware Thread, Customer needs a License for each Hardware Thread to which it is mapped.