8. Governance Design-Time ‘Model’ Service Definitions Outside-In Design: 1st: interface first 2nd: implementation Library of artefacts Change control etc. Run-Time Focus on Control Usage metering & billing Enforce policies Service Discovery – UDDI Performance monitoring etc. More info: http://www.infoq.com/presentations/SOA-Governance-Development-Deployment-Runtime
10. ESB Enterprise Service Bus “Your SOA Middleware” Facilitates implementation of an SOA at run-time and design-time PI is SAP’s ESB
11. Standards… WS-* Soup of standards of various quality WS-I Basic Profile is pretty much all that counts to be honest Too many, complex standards without wide support Take a look yourself: http://en.wikipedia.org/wiki/WS-*
16. PI = Process Integration SAP’s Middleware product Message-Oriented Middleware + ESB (Enterprise Service Bus) Design-time governance features Many adapters from SAP and third parties Orchestration of different services across systems Monitoring, metering, etc.
17. Some Use Cases Suppliers send Invoices to ERP via XML (B2B) CRM triggers Refunds to customers in ERP via web service (SOA) PI aggregates many production stats messages and sends 1 big IDoc to ERP (orchestration) ERP HR updates Access Control system by writing into its database (A2A)
18. Design-Time Run-Time NetWeaverWebAS Java & ABAP Runtime Workbench Monitoring, alerting, etc. Enterprise Services Repository Global Data Types, Schemas, processes, mappings, etc. Enterprise Services Registry (UDDI v3) Integration Builder Routing rules, connections Integration Server Execution Environment System Landscape Directory System information, connection information, etc. Components More on the next slide!
22. High-Level Runtime Features Sync & Async XML-centric integration Supports the popular WS-* standards Supports ‘hub & spoke’ and federated deployment Out-of-the-box integration with SAP systems Different transformation technologies (drag & drop, XSLT, Java, ABAP) 1-to-1 and 1-to-n processing, message splits, multi-stage mappings, etc. Loosely-coupled development object model to facilitate reuse Stateful orchestration (avoid if possible)
24. Use at Post Single PI 7.11 system 3 Java nodes, 60GB RAM, IBM “Big Iron” 39 Interfaces 150,000 messages on an average day Peak load 1.2 million/day in about 3 months