Skip to main content

Confused in understanding SAP Process Orchestration ?

SAP Process Orchestration (PO) is a comprehensive solution that brings together various components and flows to handle multiple scenarios of requests.



Advanced Adapter Engine Extended:

  1. Configuration of Integration Content:


    • Components Involved: Integration Directory, Integration Builder, Configuration Content.
    • Flow: Integration Expert connects with the Advanced Adapter Engine to set up the rules (Configuration Content) via the Integration Directory and Integration Builder.
    • Use Case: Imagine setting up rules for a game. This part defines how the game should be played, ensuring all players follow the same rules.

  2. Design of Integration Content:

    • Components Involved: Enterprise Service Repository (ERS), ERS Content, RS Builder.
    • Flow: The design is created and stored in the ERS, connecting with the Advanced Adapter Engine.
    • Use Case: Think of this as designing the game board itself, with all the paths and components in place, ready for the players.

Business Process Management Category:

  1. Process Modeling:
    • Components Involved: Process Composer, Model Service, Process Models.
    • Flow: The Process Composer connects to the Advanced Adapter Engine to create business processes (the workflows), including model services and process models.
    • Use Case: This is like planning how a project should be completed in a company, setting up the steps and guidelines.

Additional Connections:

  • Advanced Adapter Engine and Runtime Cache: Receive inputs from Integration Builder, serving as a memory to store recent actions.
  • Advanced Adapter Engine to BPM Runtime: Connects different events and automated activities.
  • ERS Content to Model Service: Shares design information.
  • Integration Builder to ES Builder: Allows cooperation between different builders.

Overall System Connections:

  • Noncentral AAE: Secondary Adapter Engine that supplements the main one.
  • Business System (with any protocol): Represents the various technologies that can be connected.
  • System Landscape Directory: Keeps track of all systems and their information.

A Simplified Analogy:

Imagine a big orchestra (your organization). The Advanced Adapter Engine acts as the conductor, coordinating all the musicians (components). Each musician has a specific role (task), and they must work together to create harmonious music (smooth integration).

  • Integration Expert: Chooses the musical pieces (Design) and sets the rules (Configuration).
  • Integration Content: The musical pieces themselves.
  • Business Process Management: The way the orchestra practices and performs.

Other connections like the Noncentral AAE, Business System, and System Landscape Directory act as support staff, ensuring the smooth operation of the whole performance.

The complexity lies in coordinating all these elements to produce the desired result, whether it's an orchestral performance or an efficiently running business system.


  1. Different Flows:

    • Integration Flow: Enables complex integration requirements.
    • Operational Process Flow: Covers daily operation tasks.
    • Administration Process Flow: Manages administrative aspects.
    • Monitoring Process Flow: Monitors all the processes.

  2. Handling Scenarios:

    • Synchronous Communication: Request and response in the same call.
    • Asynchronous Communication: Request and response as separate calls.
    • Stateless Sequence: No need to retain interaction sequence.
    • Stateful Sequence: Interaction sequence is remembered.

SAP PO accommodates various patterns and can be tailored to suit business needs.


Let's break down the components of SAP Process Orchestration (PO) into more understandable terms for someone not familiar with technical jargon:

  1. Integration Repository (IR):

    • What It Does: It's like a library where rules for handling messages are created.
    • How It Connects: Works with the Integration Directory to make the rules functional.
    • Why It's Needed: Helps businesses define how messages are processed, like a translator between different languages.
  2. Integration Directory (ID):

    • What It Does: It sets up the paths that messages follow.
    • How It Connects: Works with the Integration Server to guide messages along the right paths.
    • Why It's Needed: Ensures that messages get to the right place, like a traffic cop directing traffic.
  3. System Landscape Directory (SLD):

    • What It Does: Keeps a record of all the systems and software.
    • How It Connects: Informs other components about the available systems.
    • Why It's Needed: Helps keep track of what’s where, like a directory in a big office building.
  4. Integration Server:

    • What It Does: The central place where messages are processed.
    • How It Connects: Uses rules and paths from IR and ID and works with adapters to send messages.
    • Why It's Needed: Manages all the conversations between different systems, like an operator at a switchboard.
  5. Business Process Engine:

    • What It Does: Handles the business tasks and workflows.
    • How It Connects: Works with the Integration Server to make messages part of business tasks.
    • Why It's Needed: Makes sure tasks follow the right order and rules, like a manager organizing work.
  6. Adapters:

    • What It Does: Connects different technologies.
    • How It Connects: Works with the Integration Server to handle specific connections.
    • Why It's Needed: Lets different kinds of technology talk to each other, like different types of plugs and sockets.
  7. Integration Flows:

    • What It Does: Sets up the journey of messages from start to finish.
    • How It Connects: Uses other components to make a complete connection between systems.
    • Why It's Needed: Ensures a smooth and organized flow of information, like a travel guide planning a trip.

Think of SAP PO as a complex travel system, with airports, control towers, traffic cops, translators, and guides ensuring that every passenger (message) gets to the right destination, taking the best route, and understanding local languages. It makes sure everything in a business talks to everything else, smoothly and without confusion.

What are the points that are worth noting ?

  1. Process Orchestration:

    • Offers an integrated tool infrastructure for designing business processes.
    • Encompasses process flow, activity sequence, interfaces, and data types connecting SAP and external systems.
    • Configures business processes for specific system landscapes.
  2. Core Components:

    • Advanced Adapter Engine Extended (AEX):
      1. Enterprise Services Repository:
        • Designs integration content like service interfaces and mappings.
      2. Integration Directory:
        • Configures integration content.
        • Specifies business communication between systems and Process Integration & Orchestration.
        • Establishes connectivity between BPM process and Process Integration runtime.
      3. Advanced Adapter Engine:
        • Processes XML messages.
  3. Additional Components:

    • Business Process Management and Business Rules Management Engines:
      • Models business processes.
      • Executes and monitors BPM-based applications at runtime.
  4. Installation and Technical Details:

    • AEX and BPM components installed on the same technical system.
    • Java stack is involved.
    • Process Composer of SAP BPM used for business process modeling.
    • Enterprise Services Repository defines integration content.
    • Integration of ES Repository content into Process Composer for a loose integration.
    • Integration Directory configures BPM processes and integration content.
    • Defines communication channels for connectivity with external business systems.
    • Business systems as communication components, represented in SLD.
    • Business components represent external partners.
    • Interfaces used by BPM process assigned to business component manually.
  5. Communication and Runtime:

    • Technical communication between BPM process and Advanced Adapter Engine (AAE) via SOAP communication channels.
    • AAE serves as message hub for runtime communication.
    • All AAE adapters available for use.
    • Monitoring via SAP BPM and AEX's capabilities.
    • Non-central AAE can connect to Process Orchestration hub, but separate BPM usage type can't be installed on non-central AAE system.

Comments

Post a Comment

You might find these interesting

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system.  These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477.  These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system?  In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with

sapstartsrv is not started or sapcontrol is not working

 What is sapstartsrv ? The SAP start service runs on every computer where an instance of an SAP system is started. It is implemented as a service on Windows, and as a daemon on UNIX. The process is called  sapstartsrv.exe   on Windows, and   sapstartsrv   on UNIX platforms. The SAP start service provides the following functions for monitoring SAP systems, instances, and processes. Starting and stopping Monitoring the runtime state Reading logs, traces, and configuration files Technical information, such as network ports, active sessions, thread lists, etc. These services are provided on SAPControl SOAP Web Service, and used by SAP monitoring tools (SAP Management Console,  SAP NetWeaver  Administrator, etc.). For more understanding use this link : https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/enUS/b3/903925c34a45e28a2861b59c3c5623/content.htm?no_cache=true How to check if it is working or not ? In case of linux , you can simply ps -ef | grep sapstartsrv In case of windows, you need

HANA System Replication - Prerequisites & Setup

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out operation & replication modes in hana system replication. If you haven't gone though that blog, you can checkout  this link In this blog we will be talking about the prerequisites of hana replication and it's setup. So let's get started. When we plan to setup hana system replication, we need to make sure that all prerequisite steps have been followed. Let's have a look at these prerequisites. HANA System Replication Prerequisites: Primary & secondary systems should be up & running HDB version of secondary should be greater than or equal to Primary database sever But, for Active/Active(read enabled config), HDB version should be same on both sites. System configuration/ini files should be identical on both sides Replication happe

ST03N : The chapter for all BASIS Admins

This blog is targeted to BASIS ADMINS Transaction for workload analysis statistical data changed over time are monitored using transaction code ST03 , now ST03N (from SAP R/3 4.6C) . With SAP Web AS 6.4 the transaction ST03 is available again. From time to time ST03 and ST03N has seen many changes but later in SAP NW7.0 ST03N has reworked in detail specially processing time is now shown in separate column. Main Use of ST03N  is to get detailed information on performance of any ABAP based SAP system. Workload monitor analyzes the statistical data originally collected by kernel. You can compare or analyze the performance of a single application server or multiple application server. Using this you start checking from the entire system and finding your way to that one application server and narrowing down to exact issue. By Default :- You see data of current day as default view , you can change the default view. Source of the image : sap-perf.ca Let's discuss the WORKLOAD MONITOR By D

How to resolve Common Error : Standard Template "sap_sm.xls" missing

Hey everyone, putting forward a common error we usually face when we have “ Excel inplace” functionality enabled in our SAP system. This error occurs when validity of the signature of SAP standard templates expired or were incorrectly delivered via support packages. We can reproduce the error by doing as below.. Click on “spreadsheet” icon after any SAP ALV grid view of data is on screen to make this data to export into excel directly from SAP.

HANA hdbuserstore

The hdbuserstore (hana secure user store) is a tool which comes as an executable with the SAP Hana Client package. This secure user store allows you to store SAP HANA connection information, including user passwords, securely on clients. With the help of secure store, the client applications can connect to SAP HANA without the user having to enter host name or logon credentials. You can also use the secure store to configure failover support for application servers in a 3-tier scenario (for example, SAP Business Warehouse) by storing a list of all the hosts that the application server can connect to. To access the system using secure store, there are two connect options: (1)key and (2)virtualHostName. key is the hdbuserstore key that you use to connect to SAP HANA, while virtualHostName specifies the virtual host name. This option allows you to change where the hdbuserstore searches for the data and key files. Note

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory :  Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory :  If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used.  Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory. You can set

ABAP Dumps Analysis

Ever now and then have you heard about ABAP Dumps, We also have a joke everything in temporary in life except ABAP dumps for SAP Consultants. Lets try to understand ABAP dumps from perspective of a SAP BASIS Consultant. Dumps happen when an ABAP program runs and something goes wrong that cannot be handled by the program We have two broad categories of Dumps , In custom program Dumps and SAP provided program Dumps. Dumps that happen in the customer namespace ranges (i.e. own-developed code) or known as Custom Program , can usually be fixed by the ABAP programmer of your team. Dumps that happen in SAP standard code probably need a fix from SAP. You do not have to be an "ABAPer" in order to resolve ABAP dump issues. The common way to deal with them is to look up in ST22 How to correct the error ? Hints are given for the keywords that may be used to search on the note system. Gather Information about the issue  Go to System > Status and Check the Basis SP level as well as info

Complete Guide : XPI Inspector Tool

Content of this blog :           What is an XPI Inspector Tool ? Why XPI Tool is used ? XPI standard URL How to check XPI Tool version ? How to Install/Update XPI version using TELNET How to Use XPI Tool ? References – SAP Notes What is XPI Inspector tool ?          -    XPI Inspector is a diagnostics web application developed by SAP that collects logs and debug traces from various PI components in a very simple way and is useful for SAP PI consultants, developers, and administrators to get more insights on an issue. Why XPI is used  – 1.  Used to collect traces and logs from Messaging system or XI module. 2. Used to collect the related information to solving the issues or improving the PI or PO systems’ performance. 3. Using XPI Inspector application you will be able to collect a lot of information about your system that will help you to learn about problems in the past, to analyze new and detect such at an early stage. 4. Performs certain number of configuration checks, such as SSL c

SAP HANA System Replication - Operation Mode & Replication Mode

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out what is hana system replication and how it basically works. If you haven't gone through that blog, you can checkout link In this blog we will be talking about the replication modes and operation modes in hana system replication. So let's get started. When we setup the replication and register the secondary site, we need to decide the operation mode & replication mode we want to choose for replication. For now we won't focus on setting up replication as we'll cover it in our next blogs.  Operation Modes in Hana System Replication: There are three operation modes available in system replication: delta_datashipping, logreplay and logreplay_readaccess. Default operation mode is logreplay. 1. Delta_datashipping: In this operation mode initially one full data shipping is done as part of replication setup and then a delta data shipping takes place occasionally in addition to cont