Purposes and Concepts (SAP Library - Enabling Application-to-Application Processes)

Purposes and Concepts

For a quick introduction to the demo examples, this section contains the following:

● A list of the basic purposes of the demo examples and the relevant parts

● A list of the most important concepts of Process Integration and the example integration scenarios and variants that illustrate these concepts

Purpose

The following table provides an overview of the basic purposes of the demo examples and the relevant parts.

Purposes of the Demo Examples

Area of Use	Relevant Part of the Demo Examples
● Understanding the basic structure of design objects ● Understanding the relationship between different object types in the Integration Repository ● Using example solutions for object design in the Integration Repository ● Working with the Integration Builder (Integration Repository)	The design objects required for the demo examples are defined by SAP and shipped. These objects are located in the Integration Repository in the software component SAP BASIS, software component version SAP BASIS 7.00 in the namespaces http://sap.com/xi/XI/Demo/Agency and http://sap.com/xi/XI/Demo/Airline.
● Understanding and using the basic steps for setting up the system landscape ● Learning how to configure and convert XI content (Process Integration content) in the Integration Directory ● Understanding and making adapter configuration settings using examples ● Working with the Integration Builder (Integration Repository)	You make the configuration settings yourself in your system landscape. A detailed configuration guide is available for this purpose. The configuration guide for the demo examples is on SAP Service Marketplace at (http://service.sap.com) under Solution Details. In the navigation area, choose Technology Infrastructure and Services → SAP NetWeaver → SAP NetWeaver in Detail → Process Integration → SAP Exchange Infrastructure → Media Library → Documentation (Document SAP NW 7.0 - Configuration of PI Demo Examples).
● Executing integration scenarios ● Monitoring the processing of XML messages at runtime ● Testing the basic functions and installation of SAP XI	The shipment contains the user interfaces for executing integration scenarios.

More information:

For more information, see Technical Overview.

Concepts

The following table summarizes the important concepts that you can illustrate by using the demo examples. Each concept is implemented in an integration scenario.

Design: Integration Scenarios and Integration Processes

Concept	Implemented in Integration Scenario/Variant
General use of integration scenarios	All integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)
Integration scenario with synchronous connection	Checking Flight Seat Availability (Proxy-to-Proxy)
Integration scenario with asynchronous connection	Booking a Single Flight (Proxy-to-Proxy)
Integration scenario with an executable integration process	Booking Connecting Flights (Proxy-to-Proxy)
Integration scenario with an application component of type Template	Distributing Booking Order Data (Proxy-to-File System)
Integration scenario with multiple component views	Checking Flight Seat Availability
Using an executable integration process	Booking Connecting Flights (Proxy-to-Proxy)

Design: Interface Objects

Concept	Implemented in Integration Scenario/Variant
Synchronous message interfaces	Checking Flight Seat Availability (Proxy-to-Proxy)
Asynchronous message interfaces	Booking a Single Flight (Proxy-to-Proxy)
Abstract message interfaces for an executable integration process	Booking Connecting Flights (Proxy-to-Proxy)
Abstract message interface for an external business partner	Distributing Booking Order Data (Proxy-to-File System)
Message Types	All integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)
Fault message types in synchronous message interfaces	Checking Flight Seat Availability (Proxy-to-Proxy)
Fault message types in asynchronous message interfaces	Booking a Single Flight (Proxy-to-Proxy)
Data Types	All integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)
External Definitions	Distributing Booking Order Data (Proxy-to-File System)
Context Objects	Booking a Single Flight (Proxy-to-Proxy)
Imported Objects RFCs	Checking Flight Seat Availability (Proxy-to-RFC)
Imported Objects IDocs	Booking a Single Flight (Proxy-to-IDoc)

Design: Mapping Objects

Concept	Implemented in Integration Scenario/Variant
Interface mappings in synchronous communication	Checking Flight Seat Availability (Proxy-to-RFC) Booking Connecting Flights (Proxy-to-Proxy)
Interface mappings in asynchronous communication	Booking a Single Flight (Proxy-to-Proxy)
Interface mappings used by the integration process	Booking Connecting Flights (Proxy-to-Proxy)
Message mapping	Booking a Single Flight (Proxy-to-Proxy)
Multi-mappings	Booking Connecting Flights (Proxy-to-Proxy)
Message mapping for mapping data structures with multiple	Distributing Booking Order Data (Proxy-to-File System)
hierarchy levels to a data structure with one hierarchy level
Message mapping with a user-defined function
Message mapping with fixed-value mapping

Design: Adapter Objects

Concept	Implemented in Integration Scenario/Variant
Communication channel templates for a file system	Distributing Booking Order Data (Proxy-to-File System)

Design: Design: Proxy Objects and Other Implementation Objects

Concept	Implemented in Integration Scenario/Variant
Synchronous outbound proxy and synchronous inbound proxy (ABAP)	Checking Flight Seat Availability (Proxy-to-Proxy)
Asynchronous outbound proxy and asynchronous inbound proxy (ABAP)	Booking a Single Flight (Proxy-to-Proxy)
Defining a Web service based on a message interface	Checking Flight Seat Availability (Proxy-to-Web-Service)

Configuration

Concept	Implemented in Integration Scenario/Variant
Using configuration scenarios	All integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)
Configuration with integration scenario as template (integration scenario configurator)	All integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)
Business system service for an SAP system	All integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)
Business system service for a file system	Distributing Booking Order Data (Proxy-to-File System)
Integration Process Service	Booking Connecting Flights (Proxy-to-Proxy)
Receiver determination	All integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)
Routing condition with context object	Booking a Single Flight (Proxy-to-Proxy)
Interface determination	All integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)
Receiver agreement	All integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)
Receiver communication channel for adapter type XI	Booking a Single Flight (Proxy-to-Proxy) Distributing Booking Order Data (Proxy-to-File System)
Receiver communication channel for adapter type RFC	Checking Flight Seat Availability (Proxy-to-RFC)
Receiver communication channel for adapter type IDoc	Booking a Single Flight (Proxy-to-IDoc)
Receiver communication channel for adapter type File	Distributing Booking Order Data (Proxy-to-File System)
Receiver communication channel for adapter type SOAP	Checking Flight Seat Availability (Proxy-to-Web-Service)

Runtime

Concept	Implemented in Integration Scenario/Variant
Sending messages	All integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)
Messages with multiple receivers	Distributing Booking Order Data (Proxy-to-File System)
Monitoring message exchange	All integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)
Executing an integration process	Booking Connecting Flights (Proxy-to-Proxy)
Communication using proxy runtime	Booking a Single Flight (Proxy-to-Proxy)
Communication based on the adapter runtime (RFC adapter)	Checking Flight Seat Availability (Proxy-to-RFC)
Communication based on the adapter runtime (IDoc adapter)	Booking a Single Flight (Proxy-to-IDoc)
Communication based on the adapter runtime (file/FP adapter)	Distributing Booking Order Data (Proxy-to-File System)
Communication based on the adapter runtime (SOAP adapter)	Checking Flight Seat Availability (Proxy-to-Web-Service)