Demo Examples 

Purpose

The demo examples demonstrate the basic communication scenarios of Process Integration (PI) and guide you through the technical concepts and tools step-by-step.

You use the demo examples to do the following:

·        Learn about the technical concepts of Process Integration

The demo examples teach you about the basic concepts.

·        Test the basic functions of Process Integration

The demo examples enable you to perform simple checks to assess whether SAP NetWeaver for usage type Process Integration is configured correctly and whether it is functioning as required.

The demo examples are designed to be used as teaching and test examples for Process Integration. They are not intended for productive operation.

 

The demo examples are very useful if you want to learn about the concepts of Process Integration and how they fit together all in just one example.

 

Features

The features of the demo examples include several complete integration scenarios and comprise the following parts:

·        Design objects in the Integration Repository

The design objects are defined and shipped by SAP.

·        Configuration objects in the Integration Directory

You must create the configuration objects yourself. SAP provides comprehensive recommendations to help you.

·        Example applications

SAP has implemented example applications for the communication parties involved. These example applications also contain user interfaces. You use these to execute the demo examples.

·        Configuration guide

Detailed configuration instructions for the standard configuration recommended by SAP are available for the demo examples. These describe all the steps required to configure the demo examples in detail. A basic knowledge of Process Integration is sufficient to be able to make the relevant configuration settings.

·        Documentation

Besides the detailed configuration instructions, additional documentation is also available. This also describes how to use the individual demo examples and explains the technical concepts addressed.

Documentation Structure

The documentation consists of a general cross-integration-scenario section and separate sections for the individual integration scenarios.

The general cross-integration-scenario section contains the following information:

·        Purposes and Concepts

Contains an overview of the ways that you can use the demo examples and the concepts that they impart. For each concept there is a reference to a demo integration scenario that enables you to illustrate the concept.

·        Business Overview

A description of the business application case of the demo examples.

·        Technical Overview

An overview of the demo examples from a technical perspective. It contains information on the objects that are shipped with the demo examples and how to use them.

·        General Configuration Steps

An overview of the most important cross-integration-scenario configuration steps with references to the detailed descriptions in the configuration guide for the demo examples.

In the integration-scenario-specific sections you will find the following information for each integration scenario.

·        A short business description of the integration scenario

·        The configuration variants of the integration scenario (referred to simply as "variants") that are currently supported

The sections on the variants contain the following:

¡        A description of the concepts addressed by the integration scenario

¡        A short overview of the configuration process flow

¡        Information about the execution of the integration scenario (in the respective variant)

The application case for the demo examples is the communication between a travel agency and airlines with regard to flight bookings. Four integration scenarios are currently available. The table below lists the integration scenarios and their variants:

Available Integration Scenarios with Variants

Integration Scenario	Variants	Remarks
Checking flight seat availability    (CheckFlightSeatAvailability)	ABAP proxy runtime to ABAP proxy runtime ABAP proxy runtime to RFC runtime ABAP Proxy Runtime to Web-Service	Synchronous communication
Booking a single flight    (SingleFlightBooking)	ABAP proxy runtime to ABAP proxy runtime ABAP proxy runtime to IDoc runtime	Asynchronous communication
Booking connecting flights    (MultipleFlightBooking)	ABAP proxy runtime to ABAP proxy runtime	Asynchronous communication with an executable integration process
Distributing booking order data    (DistributeBookingOrderInformation)	ABAP proxy runtime to file system	Asynchronous communication with a file system as receiver