It is a strange year, and for the first time since 2013, we didn’t have face to face INTEGRATE event. Instead, due to the COVID-19 pandemic, this year we had to go with an online event. Despite all of that, it was a great event. Nevertheless, I miss that social interaction we use to have and see friends that I usually only see once a year in this event.
The good part for me in being an online event was that I was able to attend (or view) the sessions at my on rhythmic. Having three small kids at home can be a challenge, and it was a little difficult to attend in real-time to all the sessions, so once they went to bed, I could see the sessions that I miss out during the day without having to wait two months for them to be available online.
About my session
Session Name: BizTalk Server 2020: Migration Path
Session Overview: The goal of this session to demystify and clarify the BizTalk Server migration process and help both implementation teams as decision-makers to be aware of all the considerations that need to be taken into account when planning your migration to BizTalk Server 2020 and hopefully helping you carry out these tasks.
BizTalk Server 2020: Migration Path Slides
You can find and download the slide deck on SlideShare here: https://www.slideshare.net/SandroPereira3/integrate-2020-sandro-pereira-biztalk-server-2020-migration-path
BizTalk Server 2020: Migration Path Video
Like previous years, the event was recorded, so if for any reason you could not be present at these events, or if you want to review it again, you can now do it here:
3 thoughts on “BizTalk Server 2020: Migration Path | INTEGRATE 2020 Remote | Slides and Video Available”
HI I have a BizTalk 2016 Application with a fairly large amount of generated SQL schemas that use the WCF Custom Adapter. Will I need delete each of existing generated Schemas and Regenerate each one of the schemas again for BizTalk 2020 migration?
Hi Pedro. For BizTalk 2016 SQL generated schemas that have to be regenerated, do the newly generated bindings for the send/receive port have to be used or can the previous bindings (generayed in 2016) that were used to create these ports still be used?