Biztalk Integration, Thinking like an Integration Person Biztalk360
•Download as PPTX, PDF•
0 likes•2,432 views
Biztalk Integration, Thinking like an Integration Person Biztalk360, there are different ways to implement a BizTalk (integration) solution. The solution you choose will depend on various aspects,strategies, patterns, technical decision makings etc. Here are some of the common scenarios •Some technologies are more expensive to integrate than others, •Some technical issues are more difficult to solve than others, and •Some critical situations could be solved in easy way. It's not always possible to learn about these challenges in books or in internet. Most of the time, it comes from years of personal experience. In this session Nino Crudele will provide a real guidance based on personal experience, referring to all topics of previous European sessions but covering the most important aspects in BizTalk Summit 2014, London March 03-04 Brought to you by BizTalk360
Recommended
More Related Content
Similar to Biztalk Integration, Thinking like an Integration Person Biztalk360
Similar to Biztalk Integration, Thinking like an Integration Person Biztalk360 (20)
More from BizTalk360
More from BizTalk360 (20)
Recently uploaded
Recently uploaded (20)
Biztalk Integration, Thinking like an Integration Person Biztalk360
- 1. brought to you by Thinking like an Integration Person NINO CRUDELE
- 2. A person? NO my definition? are dangerous animals thinking in debatching mode and in unrecoverable interchange mode too
- 3. Microsoft Integration MVP 7 Years Blog: ninocrudele.me Who am I - Since BizTalk 2002 - 7 YEARS MVP - Microsoft VTS - Integrated:Sap,Siebel,AS400, Tibco,IBM World, databases engines and more… - Used: HL7-EDI-RFID-SWIFT- Rosettanet-RFID and more.. - Missions: Assessment, Development, Health check, Troubleshooting
- 4. My big passion: Kayak
- 6. BizTalker Evolution1 BizTalk Server 2002 BizTalk Server 2004 BizTalk Server 2006 BizTalk Server 2006 R2 BizTalk Server 2009 BizTalk Server 2010 BizTalk Server 2000 Messaging XML tools XLang Deployment Tools XSD EAI (partner adapters) Vertical B2B VS + .NET Messaging + Orchestration BRE Routing BAM Scale-out Simplified configuration Adapters in box Runtime+ BAM+ EDI/AS2 RFID WCF support Adapter Pack Adapter SDK HIS 2006 BAHS ALM Support B2B+ RFID Mobile Adapter Pack 2.0 Hyper-V Support HIS 2009 BAHS 2.0 Mapper UI enhancements Fine-grained Manageability Trading Partner Management Secure FTP Cloud Connect Updated Swift and HIPAA HIS 2010 BizTalk Server 2013 Hybrid Applications Configuration Cloud- scale ESB Visual Studio 2013
- 7. Evolution1 BizTalk Admin BizTalk Developer
- 10. Bad perception
- 11. 2.1 Not equilibrate 26 simple BizTalk Flows X
- 12. Extremism 86 functoids in map
- 13. Insanity
- 15. Developement3 Project1 Orchestration Transformation Schema Pipeline Transformation Schema Pipeline Common1 Orchestration Transformation Schema Pipeline Project2 Orchestration Transformation Schema Pipeline BTS Admin Receive Ports Send Ports Receive Locations Common2 Orchestration Transformation Schema Pipeline
- 16. Developement4 Two environments Test pipeline , Deploy, Debug Put file, simulate, drop file, check directory, call , send email
- 17. Strategies3 Naming convention Project structure Artifact ready Templates Reflection Injection Dynamic Atomicity Abstraction Automation Best pratces Documentation Reccomendations
- 18. Other strategies3 Extend & Invest User Experience applied to developers In other words
- 19. Improvise, Adapt, Overcome (Gunnery Sgt. Tom Highway )
- 21. Core3 + =
- 22. The challenge (Demo) 4 Months Every evening, in the toilet too Sleeping together with .net,VS,BizTalk internal friends
Editor's Notes
- Who is the most complicate system? Who the most complicate accelerators? Who the most complicte adapter? From what could depend how much is complicate an adapter or accelerator or system? (from its features for adapter, from the structure for accelerator, from interfaces for the system)
- Who is the most complicate system? Who the most complicate accelerators? Who the most complicte adapter? From what could depend how much is complicate an adapter or accelerator or system? (from its features for adapter, from the structure for accelerator, from interfaces for the system)
- The perception is the most important thing, all of the solution depend from this A lot of technologies in play, more of them are common: .Net, SQL, BizTalk, XSL We percept the technologies as a TAGs cloud, some more important than other, this is bad
- The perception is the most important thing, all of the solution depend from this A lot of technologies in play, more of them are common: .Net, SQL, BizTalk, XSL We percept the technologies as a TAGs cloud, some more important than other, this is bad
- The perception is the most important thing, all of the solution depend from this A lot of technologies in play, more of them are common: .Net, SQL, BizTalk, XSL We percept the technologies as a TAGs cloud, some more important than other, this is bad
- The perception is the most important thing, all of the solution depend from this A lot of technologies in play, more of them are common: .Net, SQL, BizTalk, XSL We percept the technologies as a TAGs cloud, some more important than other, this is bad
- The perception is the most important thing, all of the solution depend from this A lot of technologies in play, more of them are common: .Net, SQL, BizTalk, XSL We percept the technologies as a TAGs cloud, some more important than other, this is bad
- The perception is the most important thing, all of the solution depend from this A lot of technologies in play, more of them are common: .Net, SQL, BizTalk, XSL We percept the technologies as a TAGs cloud, some more important than other, this is bad