Intro to SAP PI
…and SOA in the SAP World
SOA
http://geekandpoke.typepad.com
Service-Oriented Architecture
Business + Technology!
Expose app functionality via services
A is for Architecture
Usually focus on reusability
Governance
http://geekandpoke.typepad.com
The Business Side of SOA
Think Processes, not Departments
This is hard!
Business Process focus, technology later
IT comes into play here
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
http://geekandpoke.typepad.com
ESB
Enterprise Service Bus
“Your SOA Middleware”
Facilitates implementation of an SOA at run-
time and design-time
PI is SAP’s ESB
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-*
ES Workplace
http://esworkplace.sap.com
SAP’s “yellow pages” of standard web services
There are 2,600+ service operations
Public website, no login required
SAP PI
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.
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)
NetWeaver WebAS Java & ABAP
Enterprise Services Repository
Global Data Types, Schemas,
processes, mappings, etc.
Integration Builder
Routing rules, connections
Enterprise Services Registry
(UDDI v3)
Integration Server
Execution Environment
Runtime Workbench
Monitoring, alerting, etc.
System Landscape Directory
System information, connection information, etc.
Design-Time Run-Time
Components
More on the
next slide!
Integration Server in Detail
Stand-alone Java-
only install with PI
7.3
© SAP AG 2009. All rights reserved. / Page 20
JEE AAE ABAP IE
any
Adapter
Module
Processor
XI Msg.
Handler
Msg.
Sys.
IDoc
Adapter
Bus.Proc
Engine
XI
Adapter
Route Map
Pipeline
DB DBhttp
… to
JEE AE ABAP IE
Integration Server (central AE plus IE)
any
Adapter
Module
Processor
XI Msg.
Handler
Msg.
Sys.
IDoc
Adapter
Bus.Proc
Engine
XI
Adapter
Route Map
Pipeline
DB DBhttp
Route Map
Runtime Picture: From…
• 3-4 persistence steps
• 2 times rendering / parsing
for http transport incl. user
authentication, process
switch
• 1 persistence step
SAP NetWeaver PI 7.1: From Adapter &
Integration Engine to Advanced AE (AAE)
PI Performance
Tuning
XI/PI Overview
Integration Server
Overview
Adapter Framework
Overview
Adapter Framework
Tuning
Scaling and
Quicksizing
Integration Server
Tuning
PI Performance
Tuning
XI/PI Overview
Integration Server
Overview
Adapter Framework
Overview
Adapter Framework
Tuning
Scaling and
Quicksizing
Integration Server
Tuning
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)
Future Roadmap
Java-Only deployment
Robustness & Scalability improvements
Tight integration with NetWeaver BPM
Better JMS integration
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
REST
…but that’s a whole new session
Contact Info
Sascha Wenninger
sascha@wenninger.name
@sufw
The slides are available on http://slideshare.net/sufw

Sap Process Integration

  • 1.
    Intro to SAPPI …and SOA in the SAP World
  • 2.
  • 3.
  • 4.
    Service-Oriented Architecture Business +Technology! Expose app functionality via services A is for Architecture Usually focus on reusability Governance
  • 5.
  • 6.
    The Business Sideof SOA Think Processes, not Departments This is hard! Business Process focus, technology later
  • 7.
    IT comes intoplay here
  • 8.
    Governance Design-Time ‘Model’ Service Definitions Outside-InDesign: 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
  • 9.
  • 10.
    ESB Enterprise Service Bus “YourSOA Middleware” Facilitates implementation of an SOA at run- time and design-time PI is SAP’s ESB
  • 11.
    Standards… WS-* Soup ofstandards 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-*
  • 12.
    ES Workplace http://esworkplace.sap.com SAP’s “yellowpages” of standard web services There are 2,600+ service operations Public website, no login required
  • 15.
  • 16.
    PI = ProcessIntegration 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.
    NetWeaver WebAS Java& ABAP Enterprise Services Repository Global Data Types, Schemas, processes, mappings, etc. Integration Builder Routing rules, connections Enterprise Services Registry (UDDI v3) Integration Server Execution Environment Runtime Workbench Monitoring, alerting, etc. System Landscape Directory System information, connection information, etc. Design-Time Run-Time Components More on the next slide!
  • 19.
    Integration Server inDetail Stand-alone Java- only install with PI 7.3
  • 20.
    © SAP AG2009. All rights reserved. / Page 20 JEE AAE ABAP IE any Adapter Module Processor XI Msg. Handler Msg. Sys. IDoc Adapter Bus.Proc Engine XI Adapter Route Map Pipeline DB DBhttp … to JEE AE ABAP IE Integration Server (central AE plus IE) any Adapter Module Processor XI Msg. Handler Msg. Sys. IDoc Adapter Bus.Proc Engine XI Adapter Route Map Pipeline DB DBhttp Route Map Runtime Picture: From… • 3-4 persistence steps • 2 times rendering / parsing for http transport incl. user authentication, process switch • 1 persistence step SAP NetWeaver PI 7.1: From Adapter & Integration Engine to Advanced AE (AAE) PI Performance Tuning XI/PI Overview Integration Server Overview Adapter Framework Overview Adapter Framework Tuning Scaling and Quicksizing Integration Server Tuning PI Performance Tuning XI/PI Overview Integration Server Overview Adapter Framework Overview Adapter Framework Tuning Scaling and Quicksizing Integration Server Tuning
  • 21.
    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)
  • 22.
    Future Roadmap Java-Only deployment Robustness& Scalability improvements Tight integration with NetWeaver BPM Better JMS integration
  • 23.
    Use at Post SinglePI 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
  • 24.
    REST …but that’s awhole new session
  • 25.
    Contact Info Sascha Wenninger sascha@wenninger.name @sufw Theslides are available on http://slideshare.net/sufw