spaghetti of proprietary interfaces integration broker (eai/b2b) enterprise service bus crm
TRANSCRIPT
ERP/LOB, ESB and Azure AppFabric Integration
Harsha Karunaratne, Jeff JohnsonIntegration SpecialistsMicrosoft
Agenda> A changing landscape
> Enterprise Platform and Applications> Extending ERP/LOB through this
landscape> ESB – Enabling Business Integration
Infrastructure> Reach for the cloud with Azure
“SPAGHETTI” OF PROPRIETARY INTERFACES
INTEGRATION BROKER (EAI/B2B)
ENTERPRISE SERVICE BUS
The Changing LandscapeEnterprise Integration Domain
E-COMMERCE
CRM
HR
ERP
E-COMMERCE
CRM BUSINESS PARTNER
HR
ERP
HR ERP
CRM
BUSINESS PARTNER
E-COMMERCE
CLOUD SERVICES
E-COMMERCE
CRM
HR
ERP
CLOUD SERVICES
Reach
Agility
Expose
Compose
Consume
Devices& People
Web 2.0
Trading Partners& CloudData
CRM
CustomApps
Legacy
Provision New Hire
Order to Cash
EngineeringChange Request
Portal
ERP
Create Work Order
Ship Product
Create Opportunity
Delete P.O.
The Changing LandscapeApplication Domain
BizTalk Server 2009
Extend ERP with BizTalk Demo > Goods Receiving into
SAP > Time Sheet Entry into
SAP
Composite Applications
OfficeBusiness
Applications
Customer Example – Major Oil & Gas Co
Documents associated with Work Order. Fetched from Documentum
Customer Example – NHS CUI
> And now..
ESB and AppFabric Service Bus
> BizTalk 2009 ESB Feature Highlights> Itineraries> Resolvers> Demo
> Extend to the Cloud> AppFabric Service Bus Overview> Connect to Cloud via BizTalk> Demo
> Contact: [email protected]
“SPAGHETTI” OF PROPRIETARY INTERFACES
INTEGRATION BROKER (EAI/B2B)
ENTERPRISE SERVICE BUS
The Changing LandscapeApplication Integration Domain
E-COMMERCE
CRM
HR
ERP
E-COMMERCE
CRM BUSINESS PARTNER
HR
ERP
HR ERP
CRM
BUSINESS PARTNER
E-COMMERCE
CLOUD SERVICES
E-COMMERCE
CRM
HR
ERP
CLOUD SERVICES
Benefits of ESB
Service Consumer
Service Consumer
Service Consumer
Service Provider
Service Provider
Service Provider
Invocation & Orchestration
Transport ProtocolConversion
Data Format Transformation
Location & VersionTransparency
Message InteractionsSupport
En
terp
rise S
erv
ice B
us
Error Handling & Repair
BizTalk Server
Static Receive Port
Static Send Port
Hard Coded Map Name
Static Schema
WSDL Schema
Static Schema
WSDL Schema WSDL SchemaWSDL SchemaWSDL Schema
Static Receive Port
Static Send Port
Hard Coded Map Name
Static Schema
Static Schema
Static Receive Port
Static Send Port
Hard Coded Map Name
Static Schema
Static Schema
Static Receive Port
Static Send Port
Hard Coded Map Name
Static Schema
Static Schema
Static Receive Port
Static Send Port
Hard Coded Map Name
Static Schema
Static Schema
All decisions are made and locked in at Design Time or at Deployment!
Change is often a re-development or a system re-configuration!
We’ve allowed the easy to use tools to define how we leverage the BizTalk features!
BizTalk ESB – Example ScenarioDeclarative, Meta-data, Policy and Configuration –Driven.
Transform ServiceRouting Process Orchestration
ProtocolAdaptation
End Point ResolutionPub/Sub ServiceService Consumers Service Providers
1.Message arrives on-ramp2. Itinerary resolution3.Transformation determined
at runtime4.Routing determined at
runtime5.Process the message
On Ramp Off Ramp
External Services: Transform my message
External Services: Resolve a service end point address
BizTalk ESB
Itinerary injection Resolve
endpoint
Resolve mapping
Key concepts: Itineraries, Resolvers
Itinerary – Transform & Route
> Transform using rules resolver
> Runtime lookup of map
> Runtime lookup of endpoint
> Route using static resolver
Core Web Services
Resolver Web Service
Transformation Web Service
UDDI Web Service
Exception Web Service
Operations Web Service
BizTalk Send Ports
Off-Ramps
BizTalk Receive Ports
On-Ramps
BizTalk ESB Toolkit Architecture
Exception Management
Store
ESB Management Portal
Provisioning Framework
Reports
Alerts
ESB Toolkit Core Itinerary Services
Exception Management Framework
Exception Logger
Exception Handler
Fault Processor
Resolver-Adapter Provider Framework
Resolvers (…)
Adapter Providers(…)
UDDI 3.0 BAM Generic SOAPSend
Generic WCFSend
Generic JMSSend
CustomSend
Pipeline
Pipeline
Pipeline
Custom Pipeline
ItineraryStore
Generic SOAPReceive
Generic WCFReceive
Generic JMSReceive
CustomReceive
Pipeline
Pipeline
Pipeline
Custom Pipeline
Route Service
Custom Service
Transform Service
Transformation Engine
Business Rules Engine
Orchestration Engine
BizTalk Pub/Sub Engine
Introduction Itinerary, Routing and Transformation
Demo
On-Ramp – Selects itinerary
BizTalk ESB connected to Azure AppFabric Service Bus
Demo
AppFabric Service Bus
> Challenges in connectivity> Integrate on-premise ESB, apps via cloud> Bidirectional communication at Internet
scope not trivial> Security
> Service Bus> Federated Identity and access control> Federated Naming> Dynamic Service Registry> Robust Messaging Fabric
BizTalk Cloud - Demo Architecture
App FabricService Bus
Receiver (EchoServi
ce)
Echo Client(Sender)
Backend Naming, Routing Fabric
Outbound connect one-way net-tcp
TCP/SSL
808/828
Msg
TCP/SSL 828
Route
Subscribe
Frontend Nodes
BizTalk ESB
Itinerary Routing, dynamically transforms and resolves endpoint
sb://biztalk-uk-conf.servicebus.windows.net/EchoService
Outbound connect bi-directional socket
Start the service, visible in registry
• Start the service• Outbound bidi connection established• Service visible in Azure Service Registry
Connect via Client Application
> Connect via BizTalk> Transform lookup
using Business rules engine
> Resolve on-ramp and route
> Send message to cloud
BizTalk Service Bus Send Port
> BizTalk send port> WCF Custom
Binding
Summary
> Extend the reach of ERP and LOB applications – composite applications
> More agility and flexible infrastructure with ESB approaches and patterns
> Extend to cloud and off-premises with BizTalk and Azure AppFabric Service Bus
> Download & enjoy
© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.