8/2/2017
Concepts
Concepts Use Process Orchestration provides an integrated tool infrastructure to model and design business processes - from the overall process flow and the sequence of activities through to the interfaces and data types that are needed to integrate SAP systems and external systems. In addition, it provides the tools to configure business processes for specific system landscapes. The package is based on the following components: Components of the Advanced Adapter Engine Extended (AEX), in particular: Enterprise Services Repository Enables you to design integration content like service interfaces and mappings, for example. Integration Directory Configuration tool that allows an integration expert to configure integration content, in particular: One the one hand, to specify the business communication between business systems and the Process Integration Integration & Orchestration Package and, on the other, to specify specify the connectivity between the BPM process and the Process Integration runtime. Advanced Adapter Engine Process Integration runtime component that allows you to process XML messages. More information on this installation option: Advanced Adapter Engine Extended Business Process Management and Business Rules Management engines Allows an integration expert to model business processes and to execute and monitor the business processes (BPM-based applications) at runtime. More information: Business Process Management , Management , Business Rules Management The involved components are illustrated in the figure below.
1/3
8/2/2017
Concepts
Interaction of the Components As shown in the figure above, the components interact in the following way: During installation time, the components of the AEX and of Business Process Management (BPM) (usage types PI-AEX and BPM) are installed on the same technical system (same system ID). Note That means, that, technically, only the Java stack is involved. At design time, an integration expert uses the Process Composer of SAP BPM to model the business process (BPM process). The Process Composer is part of SAP NetWeaver Developer Studio. More information: Concepts (Process Composer) Using the Enterprise Services Repository (ES Repository), an integration expert defines the relevant integration content, for example, data types, service interfaces and mappings. More information: Interface Objects Mapping Objects To make these ES Repository content available also for a BPM process, service interfaces and mappings defined in the ES Repository can be imported into the process composer. This option enables a loose integration between the ES Repository and the Process Composer. 2/3
8/2/2017
Concepts
In order to configure the BPM process and the integration content for usage in a specific system landscape, an integration expert uses the Integration Directory as central tool. In the Integration Directory, the relevant communication channels are defined in order to specify the connectivity with the (external) business systems. The business systems themselves are represented as communication components. Business systems that are defined in the System Landscape Directory (SLD) are represented as business system components, whereas external partners (typically used in business-to-business communication) are represented by business components (and optionally communication parties). Applications that are implemented as BPM process are represented as business components. The interfaces that are used by the BPM process are assigned to the business component manually in Integration Directory. The technical communication between the BPM process and the AAE is specified by communication channel with adapter type SOAP. As with regard to Process Integration capabilities the AEX is used, integrated configurations are used to specify routing, mapping, and sender and receiver channels. More information: Configuration Time At runtime, the Advanced Adapter Engine (AAE) is used as runtime engine (message hub) to enable the communication between business systems and Process Orchestration. Therefore, all adapters that are part of the AAE can be used. More information: Advanced Adapter Engine The “internal” communication between the AAE and the BPM runtime is based on the XI 3.0 protocol (using a SOAP communication channel). More information: AEX and BPM Runtime Integration At runtime, a business process is monitored using the monitoring capabilities of SAP BPM and AEX (not shown in the figure). Note As shown in the figure, a non-central AAE can also be connected to the Process Orchestration hub. However, a separate BPM usage type cannot be installed on the system of the non-central AAE.
More Information For more information on the security-relevant aspects of Process Orchestration, see Security Aspects of Process Orchestration Note This documentation also provides more details regarding the interaction of the components at runtime.
3/3
