LEADER 03292nam 2200625 450 001 9910792930103321 005 20200520144314.0 010 $a1-5015-0601-3 024 7 $a10.1515/9781501506086 035 $a(CKB)3710000001403486 035 $a(DE-B1597)479465 035 $a(OCoLC)992454292 035 $a(DE-B1597)9781501506086 035 $a(Au-PeEL)EBL4880140 035 $a(CaPaEBR)ebr11399432 035 $a(CaONFJC)MIL1015535 035 $a(OCoLC)991179095 035 $a(CaSebORM)9781501506017 035 $a(MiAaPQ)EBC4880140 035 $a(EXLCZ)993710000001403486 100 $a20170717h20172017 uy 0 101 0 $aeng 135 $aurcnu|||||||| 181 $2rdacontent 182 $2rdamedia 183 $2rdacarrier 200 10$aUpgrading and migrating to BizTalk server 2016 /$fMark Beckner, Dylan Jones 210 1$aBoston, [Massachusetts] ;$aBerlin, [Germany] :$cDe|G Press,$d2017. 210 4$dİ2017 215 $a1 online resource (156 pages) $cillustrations 300 $aIncludes index. 311 $a1-5015-1507-1 311 $a1-5015-0608-0 327 $tFrontmatter -- $tAcknowledgements -- $tIntroduction -- $tAbout the Author -- $tContents -- $tChapter 1: Preparing for Your Upgrade -- $tChapter 2: Migrating Your Solution -- $tChapter 3: Visual Studio and Maps -- $tChapter 4: Orchestrations and C# -- $tChapter 5: Migrating to Azure -- $tAppendix: Managing Your Migration -- $tIndex 330 $aThere are a variety of considerations you'll need to take into account when migrating your solutions to BizTalk 2016. In this book, you'll find detailed information about how to migrate your components "as-is", as well as recompile them with the latest version of Visual Studio. You'll look at ways to improve your components pre-migration, as well as troubleshoot issues within these components. You'll learn how to make intelligent mapping updates, especially with XSLT, and how to simplify your overall architecture. Additionally, working with BizTalk 2016 in an Azure environment and building BizTalk Azure Services are covered. Readers will look at migrating maps, orchestrations, .NET assemblies, database components, EDI parties and configurations, and other artifacts found in BizTalk solutions. They will also be able to quickly come to an understanding of what will be involved in a migration and what will be required for resourcing and costs associated with a migration. Readers will find information that will cover virtually every aspect of their upgrade to BizTalk 2016, and should come away with a simpler solution once that migration is complete. 606 $aClient/server computing 606 $aBusiness$xComputer programs 610 $aBizTalk. 610 $aEnterprise Application Integration. 610 $aEnterprise Software. 610 $aIOMS. 610 $aMiddleware. 610 $aServer. 615 0$aClient/server computing. 615 0$aBusiness$xComputer programs. 676 $a004.36 700 $aBeckner$b Mark$0872333 702 $aJones$b D$g(Dylan), 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9910792930103321 996 $aUpgrading and migrating to BizTalk server 2016$93689071 997 $aUNINA