BizTalk Server 2020

Microsoft recently announced that BizTalk Server 2020 will be available as of January 15, 2020.
Here are some of the great new features it offers:

Group Managed Service Accounts (gMSA):

Extends windows GMSA support to BizTalk operations and service. New installations of BizTalk Server may be configured with gMSA by running BizTalk Server Custom Configuration (not available with a Basic Configuration).

Note for BizTalk 2016 users: You cannot use these accounts during installation. Instead, use a temporary account and update the account after installation.

The following table shows the BizTalk Server features that support gMSA:

Azure Blob Adapter:

Send and receives messages to/from Azure Blob Storage.
The Azure Blob storage receive adapter supports high availability. You can add multiple host instances in the same Azure Blob storage adapter. The receive handler receives from the same blob container simultaneously. Blob leasing is used as a lock to avoid the same blob being received by multiple host instances. Accordingly:

• Blobs leased by other processes won't be received by Azure Blob storage adapter.

• Blobs being received by the Azure Blob storage adapter can't be updated while in a leased state.

The Azure Blob storage send adapter, like most send adapters, provides high availability for the sending host by utilizing multiple host instances in the same send host.

Logic App Adapter:

Starting with BizTalk Server 2020, the Logic App adapter and BizTalk Adapter Pack (BAP) is included with the BizTalk Server installation.

Note for BizTalk 2016 users: We use the LogicAppAdapter.iso to run the LogicApp Adapter.msi file for install.

Audit Log:

Makes BizTalk even more secure by maintaining audit trails of all management operations. Administrators can configure BizTalk Server to generate audit trails for management operation on application artifacts such as send ports, receive ports, receive locations, orchestrations, and resources. Auditing of suspend/resume/terminate operations on service instances is also possible.

Read Only Operator Role:

Facilitates dev ops model, where access to production stamp is provided without the ability to update anything.

XSLT 3.0:

New extensible model for runtime map execution, out-of-box wiring to work with Saxon XSLT3.0.

BizTalk's default XSL transform engine implementation is based on .Net Framework XSLT Transformations. This support is limited to XSLT 1.0. Use this property to configure other XSL transform engines at map level. This makes it possible for BizTalk server maps to support newer versions of XSLT. Registered Saxon users can readily use XSLT3.0.

BizTalk Configuration:

This feature applies to BizTalk Server 2020 is newer and allows for the configuration of REST APIs and BizTalk TMS.

Note for BizTalk Server 2016 Feature Pack 1 users: A Windows PowerShell script to install the above REST APIs is available.

Additional updates:

• New long-term supported Microsoft OLEDB Driver for SQL Server.

• Support for SSO Affiliate applications in SFTP adapter.

• SQL Availability Group support for BAM DTS Package via SSIS Catalog.

• Partially disabled receive locations.

• Improvements to Dynamic Send Ports with Ordered Delivery throughout.

Deprecated & Removed List:

If you are considering an upgrade, please CLICK HERE for our scorecard for migration and FAQs.
CONTACT US for an in-depth analysis and review of your migration or new BizTalk implementation.

Implement or Migrate to Microsoft BizTalk Server 2020

The Aidant team recently got hands-on experience with BizTalk 2020. They completed a POC for an existing customer who will be now migrating from BizTalk 2016 R2. The target was an aggressive five* days! 

A lot has changed in BizTalk 2020. However, Microsoft is keeping the promise it made in 2015 to keep BizTalk on-premise alive while adding features to bring it closer to Azure (a.k.a. Cloud). 

FAQ! Here are some frequently asked questions for those considering migrating to, or starting brand new, with BizTalk 2020.

*Five days does not include installation, configuration, and end to end testing. Includes unit testing.

Q1: What are the software requirements/support for BizTalk 2020?

A. Windows 10, Windows Server 2016 or 2019 

B. SQL Server v.2016 SP2, v.2017, v.2019

C. Visual Studio 2019 (.NET Framework 4.7)

D. Office Excel 2016 or 2019

E. SharePoint (optional) 2016, 2019 or SharePoint Services Online

F. IBM MQ Series version 8 and 9 supported (if used)

Q2: Will my existing BizTalk integrations work, or is there a lot to retrofit?

Answer: YES

However, there are some variations depending on your current setup. Based on Aidant’s extensive
experience with BizTalk migrations, we can grade each of the following scenarios on a scale of 1 to 10,   1   being the easiest and shortest migration, and  10  being the longest and hardest.

2 - Currently running BizTalk 2013 or higher

In-place migration possible, but not recommended.

4 - Currently running BizTalk 2010

.NET framework and deprecated functions in C# or VB .NET to be re-written. Adapters need to be switched. Testing with external partners is key.

6 - Currently running BizTalk 2006, 2006R2, 2009

In-place upgrade not recommended and not fully supported anymore. However, the migration is less painful compared to “Grade 9” below.

9 - Currently running BizTalk 2002 or 2004

We need to evaluate inventory of integrations running and create a migration checklist. Our team has developed tools to access and auto-migrate maps. This type of migration is accelerated using the Aidant DI.Platform.

Q3: Will I be able to leverage old and existing code?

Answer: YES

We take what you have, migrate it over, and improve the implementation in the process before testing.

Q4: Will there be special training required for existing BizTalk staff?

Answer: NO

Special training is not required. The look and feel remains similar, so teams usually adapt easily and quickly. The Aidant team specializes in cross-training and highlighting what needs to be focused on going forward.

Q5: Will we be Cloud-ready after implementing BizTalk 2020?

There are exceptional new features in this version that will bring you closer to Cloud or Azure implementations. However, Microsoft has done a great job of keeping the choice with the customer. You’ll be able to decide how much you want to be on Cloud versus on-premise. We recommend a hybrid approach based on individual needs.

Microsoft BizTalk Support Lifecycle

*BizTalk Version includes all editions viz. Developer, Standard, Enterprise, Branch, Partner, DataCenter.

If you are using 2013R or earlier – it’s time to investigate an upgrade.
Aidant has compiled an easy-to-reference summary of the support available for BizTalk versions.

X Critical X
This is a highly critical situation and creates a high risk for business continuity and prevents growth. BizTalk Support is not the only one that has ended. Microsoft Server OS and other development tools such as Visual Studio, SQL Server and other support tools like Covast, etc. are also not supported anymore. Information security is compromised as a result of unpatched and unsupported software.

! Getting Critical !
The normal support for BizTalk has ended and Microsoft is under extended support (see definition below). If the BizTalk version used is in extended support, the customer must start planning (and budgeting) for an upgrade. The following should be incorporated into an upgrade strategy:

• Lower the infrastructure footprint

• Decrease the total cost of ownership

• Re-architecting data integrations and EDI platforms for current and future needs

• Develop cloud strategy

💡 This is the perfect opportunity to explore options for partners and platforms that can guide the transition.

✔ Current ✔
There is nothing to worry about regarding the end of the support cycle from Microsoft. If a company is considering moving an older EDI platform (generally non-Microsoft) to BizTalk/Azure, there are still other challenges to tackle and will require roadmapping and rethinking on EDI. Data integration can be leveraged and moved closer to the business and create value add.

💡 Considerations for migration:

• Master data migration (x-ref, party configuration)

• User impact – technical and business users

• Data quality – scope for improvement to avoid IT overhead

• Migration testing and validation

• Trading partner impact

• Re-architect for cloud and next-generation readiness

• Information security compliance and considerations

• Reducing infrastructure footprint

• The lower total cost of ownership

• Bring business closer to EDI and create self-servicing options for businesses to create efficiency and lower their dependency on IT/EDI Teams for trivial/day-to-day questions

Mainstream Support: Hotfixes will be issued if any major bugs are found including security patches. Microsoft will issue these updates and hotfix at no cost. Service packs will be provided along with the product warranty at no cost. Microsoft support will be provided at no charge.

Extended Support: Microsoft will support issue patches and hotfix for a fee with non-security type issues found. Security related patches will be provided in special cases. However, no security updates, warranty, feature updates or service packs will be provided. Normal support and research may be charged by Microsoft.

What else happens after extended support ends?

1. No updates will be available. Any critical or non-critical bugs will be user liability.

2. Security patches and vulnerability, along with keeping up information security becomes customer responsibility.

3. Platform upgrades for Windows Server and other Developer tools not supported.

4. Microsoft Server lifecycle needs to be monitored and once Windows Server Operating Systems is out of support BizTalk Server as an application becomes unreliable.

5. The top reason Microsoft supports BizTalk in extended support mode, is to give customers enough lead time to plan, develop and execute BizTalk Migration to next platforms before Server OS becomes unsupported.

Running BizTalk Version 2006 or prior and using EDI Accelerators like Covast? – Contact us for streamlined, low impact migration services.

Stay up to date with your EDI Platforms and realize full return of investment and achieve peace of mind, along with confidence to grow and support your business leveraging EDI platforms of the future.

For reference: https://support.microsoft.com/en-us/lifecycle