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 process 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 Enterprise Services Repository Using example solutions for object design in the Enterprise Services Repository Working with the Enterprise Services Builder	The design objects required for the demo examples are defined by SAP and shipped. These objects are located in the Enterprise Services Repository in the software component SAP BASIS, software component version SAP BASIS 7.10 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 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 (see: General Configuration Steps).
Executing process integration scenarios Monitoring the processing of XML messages at runtime Testing the basic functions and installation of SAP NetWeaver Process Integration	The shipment contains the user interfaces for executing process integration scenarios.

See also:

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 a process integration scenario.

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

Design: Interface Objects
Concept	Implemented in Process Integration Scenario/Variant
Synchronous service interfaces	Checking Flight Seat Availability (Proxy-to-Proxy)
Asynchronous service interfaces	Booking a Single Flight (Proxy-to-Proxy)
Abstract service interfaces for an executable integration process	Booking Connecting Flights (Proxy-to-Proxy)
Abstract service interface for an external business partner	Distributing Booking Order Data (Proxy-to-File System)
Message types	All process integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)
Fault message types in synchronous service interfaces	Checking Flight Seat Availability (Proxy-to-Proxy)
Fault message types in asynchronous service interfaces	Booking a Single Flight (Proxy-to-Proxy)
Data types	All process 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 Process Integration Scenario/Variant
Operation mappings in synchronous communication	Checking Flight Seat Availability (Proxy-to-RFC) Booking Connecting Flights (Proxy-to-Proxy)
Operation mappings in asynchronous communication	Booking a Single Flight (Proxy-to-Proxy)
Operation 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 hierarchy levels to a data structure with one hierarchy level	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 Process Integration Scenario/Variant
Communication channel templates for a file system	Distributing Booking Order Data (Proxy-to-File System)

Design: Proxy Objects and Other Implementation Objects
Concept	Implemented in Process 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 service interface	Checking Flight Seat Availability (Proxy-to-Web Service)

Configuration
Concept	Implemented in Process Integration Scenario/Variant
Using configuration scenarios	All process integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)
Configuration with process integration scenario as template (model configurator)	All process integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)
Business system component for an SAP system	All process 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 component	Booking Connecting Flights (Proxy-to-Proxy)
Receiver determination	All process 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 process integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)
Receiver agreement	All process 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 Process Integration Scenario/Variant
Sending messages	All process 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 process 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/FTP 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)