Glenn kicked off with the evolution of enterprise integration: from brokers and service bus towards Winodws Azure BizTalk Service.
Glenn gave a really good introduction to WABS for EAI & B2B scenarios. He ended up with connecting his (already famous) SAP-in-a-box with a WPF client by using Service Bus Relay, WABS & WABS Adapter service! If Glenn is doing this session again, don’t hesitate and attend!!
7. What Microsoft heard
Reduce transaction
cost by 25-50%
incurred through low
server utilization
We want to cut-down
the on-boarding time
from weeks to a
matter of days
OOB SaaS
connectivity
Need a config-driven
experience for
exchange of
information
We would like out-of-
box capabilities like
archiving built into
the platform
We need a self-
service solution
14. Trading Partner Management
➔ Set up agreements between parties
➔ AS/2 support
➔ X12 & EDIFACT support
➔ Portal Experience
➔ Transformation, validation, routing
➔ Route incoming messages to different endpoints
➔ Web Service
➔ Blob Storage
➔ Azure BizTalk Bridge
20. Advanced Messaging –
Extending BizTalk Service
Message Inspectors
C# Scripting
Functoids
Custom WCF
Bindings
Bridge
Pipeline
V E T E
Messages
Sources
FTP/S
HTTP
SFTP
Destinations
Service Bus
Web Service
Blob
21. BizTalk Adapter Service
Server Explorer
(Visual Studio)
PowerShell
CmdLets
Management
Service REST API
Lob Relay
(Service Host)
BizTalk Adapter Service
Bridge
Pipeline
V E T E
Messages
Sources
FTP/S
HTTP
SFTP
Destinations
Service Bus
Web Service
FTP/S
HTTP
Blob
27. Lessons Learned
27
➔ Good for B2B scenarios
➔ Good for basic ‘pipeline’ capabilities as a service
➔ Extensibility is key in integration
➔ Configuration & tracking needs attention
➔ Combination with Service Bus is really
important
28. The FUTURE of Microsoft Integration
2 year major release cycle
minor releases every alternate year
on-prem is real and here to stay
JSON, SFTP, Healthcare,….
quarterly updates ADD Integration
pull from LOB adapters
JSON support workflow
adapter extensibility
29. Thank you!
Keep in touch.
Call or mail us. Ask questions. Happy to help.
LinkedIn
blog
.codit.eu codit.eu NewsletterTwitter
Pay us
a visit
Hinweis der Redaktion
Cloud has introduced a whole new paradigm-- Huge scale-- Social networks-- Big Data-- Access from EverywhereThink “global”
How and when to “move to the cloud” is the wrong way to look at it. Microsoft’s strategy with the cloud is to bring computing resources to your enterprise to extend your capabilities.
Toextendsthosecapabilitiesthere are following building blocksavailable, the onlythingthat was missing was anintegration part andthis is wherebiztalk services comesintoplace
So, whatdidmicrosofthear…. Reduce, cut-down, oobsaas….
Another key way to use the cloud is though integration. Windows Azure provides a great environment for running web apps and public facing services. Also a great “DMZ” for connecting with partners. Full story with BizTalk Server on-prem forbusiness process management, transactions, etc.
Is an on-premise Service hosted in IISAllows LOB Relays and LOB Targets to be created using REST APIsFor Development, there is a VS Server Explorer extensionFor Management, there are PowerShell ScriptsLOB RelaysRepresents a connection to the cloud using a Service Bus RelayCan host multiple LOB TargetsLOB TargetsRepresents an on-premise LOB system that is exposed to the cloudIs hosted inside an LOB Relay and identified by a unique sub path
Biztalk server: on prem is real andheretostayMajor release every 2 years, minor realeasesalternateyearsOn the roadmap for the quarterly updates for Windows Azure BizTalk Services are following features: ADD integration, pull from LOB adapters, JSON support, BPMN, Adapter extensibility, AS2 enhancements and custom EDI codes….