SAP PI and SOA Overview


Published on

A high-level overview of some SOA concepts and of SAP PI, presented as part of the BCO6181 course at Victoria University

Published in: Technology

SAP PI and SOA Overview

  1. 1. Intro to SAP PI<br />…and SOA in the SAP World<br />
  2. 2. SOA<br />
  3. 3.<br />
  4. 4. Service-Oriented Architecture<br />Business + Technology!<br />Expose app functionality via services<br />A is for Architecture<br />Usually focus on reusability<br />Governance<br />
  5. 5.<br />
  6. 6. The Business Side of SOA<br />Think Processes, not Departments<br />This is hard!<br />Business Process focus, technology later<br />
  7. 7. IT comes into play here<br />
  8. 8. Governance<br />Design-Time<br />‘Model’ Service Definitions<br />Outside-In Design: <br /> 1st: interface first<br /> 2nd: implementation<br />Library of artefacts<br />Change control<br />etc.<br />Run-Time<br />Focus on Control<br />Usage metering & billing<br />Enforce policies<br />Service Discovery – UDDI<br />Performance monitoring<br />etc.<br />More info:<br />
  9. 9.<br />
  10. 10. ESB<br />Enterprise Service Bus<br />“Your SOA Middleware”<br />Facilitates implementation of an SOA at run-time and design-time <br />PI is SAP’s ESB<br />
  11. 11. Standards…<br />WS-* Soup of standards of various quality<br />WS-I Basic Profile is pretty much all that counts to be honest<br />Too many, complex standards without wide support<br />Take a look yourself:*<br />
  12. 12. ES Workplace<br /><br />SAP’s “yellow pages” of standard web services<br />There are 2,600+ service operations<br />Public website, no login required<br />
  13. 13.
  14. 14.
  15. 15. SAP PI<br />
  16. 16. PI = Process Integration<br />SAP’s Middleware product<br />Message-Oriented Middleware +<br /> ESB (Enterprise Service Bus)<br />Design-time governance features<br />Many adapters from SAP and third parties<br />Orchestration of different services across systems<br />Monitoring, metering, etc.<br />
  17. 17. Some Use Cases<br />Suppliers send Invoices to ERP via XML (B2B)<br />CRM triggers Refunds to customers in ERP via web service (SOA)<br />PI aggregates many production stats messages and sends 1 big IDoc to ERP (orchestration)<br />ERP HR updates Access Control system by writing into its database (A2A)<br />
  18. 18. Design-Time<br />Run-Time<br />NetWeaverWebAS Java & ABAP<br />Runtime Workbench<br />Monitoring, alerting, etc.<br />Enterprise Services Repository<br />Global Data Types, Schemas, <br />processes, mappings, etc.<br />Enterprise Services Registry<br />(UDDI v3)<br />Integration Builder<br />Routing rules, connections<br />Integration Server<br />Execution Environment<br />System Landscape Directory<br />System information, connection information, etc.<br />Components<br />More on the next slide!<br />
  19. 19. Integration Server in Detail<br />Stand-alone Java-only install with PI 7.3<br />
  20. 20. IDoc<br />Adapter<br />IDoc<br />Adapter<br />Bus.Proc<br />Engine<br />Bus.Proc<br />Engine<br />XI<br />Adapter<br />XI<br />Adapter<br />… to<br />JEE AAE<br />ABAP IE<br />XI Msg.<br />Handler<br />Pipeline<br />Module<br />Processor<br />Route<br />Route<br />Map<br />Map<br />any<br />Adapter<br />http<br />DB<br />DB<br />Msg.<br />Sys.<br />Runtime Picture: From…<br />JEE AE<br />ABAP IE<br /><ul><li> 3-4 persistence steps
  21. 21. 2 times rendering / parsing </li></ul> for http transport incl. user <br /> authentication, process <br /> switch<br />XI Msg.<br />Handler<br />Pipeline<br />Module<br />Processor<br />Route<br />Map<br />any<br />Adapter<br />http<br />DB<br />DB<br />Msg.<br />Sys.<br />Integration Server (central AE plus IE)<br /><ul><li> 1 persistence step</li></ul>SAP NetWeaver PI 7.1: From Adapter & Integration Engine to Advanced AE (AAE)<br />
  22. 22. High-Level Runtime Features<br />Sync & Async XML-centric integration<br />Supports the popular WS-* standards<br />Supports ‘hub & spoke’ and federated deployment<br />Out-of-the-box integration with SAP systems<br />Different transformation technologies (drag & drop, XSLT, Java, ABAP)<br />1-to-1 and 1-to-n processing, message splits, multi-stage mappings, etc.<br />Loosely-coupled development object model to facilitate reuse<br />Stateful orchestration (avoid if possible)<br />
  23. 23. Future Roadmap<br />Java-Only deployment<br />Robustness & Scalability improvements<br />Tight integration with NetWeaver BPM<br />Better JMS integration<br />
  24. 24. Use at Post<br />Single PI 7.11 system<br />3 Java nodes, 60GB RAM, IBM “Big Iron”<br />39 Interfaces<br />150,000 messages on an average day<br />Peak load 1.2 million/day in about 3 months<br />
  25. 25. REST<br />…but that’s a whole new session<br />
  26. 26. Contact Info<br />SaschaWenninger<br /><br />@sufw<br />The slides are available on<br />