🔗

Understanding Process Integration and Orchestration

Mar 19, 2025

Process Integration and Process Orchestration

Course Overview

  • Objective: Understand process integration, process orchestration, and the differences between them.
  • Structure: Initial theory followed by hands-on exercises.
  • Key Terms: PI (Process Integration), PO (Process Orchestration), EAI (Enterprise Application Integration), ESB (Enterprise Service Bus).

Introduction to SAP PI

  • Part of SAP NetWeaver suite.
  • An EAI platform to integrate SAP and non-SAP applications.
  • Acts as an ESB providing a governed means of integrating applications.

Why PI is Needed

  • Avoid Spaghetti Model: Direct connections between systems lead to complex, unmanageable landscapes.
  • Centralized Integration: PI provides a cleaner, maintainable architecture.

Key Concepts

  • A2A Integration: Application to Application within a corporate landscape.
  • B2B Integration: Business to Business, across corporate boundaries.

Components of SAP PI

1. System Landscape Directory (SLD)

  • Acts as a directory listing all systems in the landscape for PI to connect.
  • Comparable to a telephone directory.

2. Enterprise Services Repository (ESR)

  • Design Time Component: Where interface design occurs, including data and mapping definitions.

3. Integration Directory

  • Configuration Time Component: Where interfaces are configured using design-time objects.

4. Integration Server

  • Runtime Component: Processes messages through three engines:
    • Central Adapter Engine: Connectivity layer.
    • Integration Engine: Main pipeline execution.
    • Business Process Engine: Executes ccbpm (Cross Component Business Process Management).

Monitoring Framework

  • Runtime Workbench & PI Monitoring: Tools for message monitoring and tracking.

Tools and Access

  • System Landscape Directory: Accessed via browser.
  • Enterprise Service Repository & Integration Directory: Java web start-based client (Integration Builder) or NetWeaver Developer Studio.

Managed vs Basic Web Services

  • Managed Web Services: Use PI for controlled, structured integration.
  • Basic Web Services: Direct access, leading to potential unstructured landscapes.

Architecture Options

Dual Stack PI

  • Combination of ABAP and Java stack.

Single Stack PI

  • Java-only, called Adapter Engine Extended (AEX).

Process Orchestration (PO)

  • Combines three products:
    • Java-only PI (AEX)
    • Business Process Management (BPM)
    • Business Rules Management (BRM)

Differences Between PI and PO

  • Process Integration: Primarily for integration tasks.
  • Process Orchestration: Includes PI capabilities and adds BPM and BRM.

Summary

  • PI provides structured application integration avoiding chaotic landscapes.
  • Essential components: SLD, ESR, Integration Directory, Integration Server.
  • PI can be deployed as dual stack or single stack.
  • PO enhances PI with additional BPM and BRM capabilities.

Next Steps

  • Hands-on with SLD and beginning with interface building.

End of Session: Move to next session for practical exercises.