Technical Overview 

This section describes the demo examples shipped by SAP from a technical perspective. It focuses on explaining the technical concepts of Process Integration in the context of the demo examples.

Example Applications for Travel Agency and Airline

The demo examples comprise two example applications: a travel agency application and an airline application. Both applications are implemented in SAP Web Application Server (SAP NetWeaver 7.0) and are therefore available in every SAP system that is based on SAP Web AS (SAP NetWeaver 7.0).

Applications that use Process Integration to communicate are usually part of different products and run on different SAP systems.

From a logical perspective, the travel agency and airline applications can therefore be considered as separate applications. However, from a technical perspective, both applications are implemented together in SAP Web Application Server (SAP NetWeaver 7.0). This makes it possible to access and use the demo examples on all SAP systems.

To emphasize the separation from the logical perspective, the respective program objects have been created as independently from one another as possible and belong to different packages in the SAP system.

The travel agency application has a user interface (as a Business Server Page application), which you use to execute the demo examples.

The airline application has a user interface, which you use to access current data in the flight database tables.

The example applications are designed as teaching examples and are not intended for productive operation.

Design Objects in the Integration Repository

The design objects that are required to integrate the travel agency and airline applications are defined by SAP and are part of the shipment. Examples of such objects are integration scenarios, an integration process, message interfaces, messages, and data types, as well as interface and message mappings.

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.

The Integration Repository reflects the logical separation of the travel agency application and the airline application described above. All the design objects that belong to the travel agency application are in the namespace http://sap.com/xi/XI/Demo/Agency, and those that belong to the airline application are in the namespace http://sap.com/xi/XI/Demo/Airline.

It is not always possible to assign cross-system design objects (such as integration scenarios, integration processes, and mapping objects) uniquely to one of the communication parties. The demo examples are based on the assumption that the airline application provides certain services, which only form a complete integration scenario together with the travel agency application. Therefore, all cross-system design objects are defined in the travel agency namespace.

The available design objects form the basis for executing the demo examples for test purposes. The design objects also illustrate the following:

●      How content is structured in the Integration Repository

●      How the various object types in the Integration Repository are structured and used

●      The dependencies between the design objects in the Integration Repository

The design objects in the demo examples are designed as teaching examples and are not intended for productive operation.

Configuration Objects in the Integration Directory

The configuration objects required to integrate the travel agency and airline applications are not shipped by SAP and you must define them yourself in the Integration Directory.

Some of the settings (business system services and communication channels) are cross-integration-scenario settings. For more information, see General Configuration Steps.

For information about the standard SAP configuration (see General Configuration Steps), see the detailed instructions for the configuration steps for the demo examples, which are provided in a separate document.

For detailed instructions about configuring the demo examples, see SAP Service Marketplace at http://service.sap.com/solutions ®  SAP NetWeaver  ®  SAP NetWeaver in Detail  ®  Process Integration  ®  SAP Exchange Infrastructure  ®  Media Library  ®  Documentation (Document SAP NW 7.0 - Configuration of PI Demo Examples).

You must configure the demo examples in the Integration Directory before you can execute them. The design objects also illustrate the following:

●      How the design objects in the Integration Repository are related to the configuration objects in the Integration Directory

●      How content is structured in the Integration Directory

●      How the various configuration object types in the Integration Repository are structured and used

●      The dependencies between the configuration objects in the Integration Directory

●      How message processing is controlled by the configuration objects at runtime

Runtime

You can use the runtime of Process Integration to execute the demo examples for test purposes. This enables you to do the following:

●      Use a simple example to check whether you have configured the usage type Process Integration correctly and whether it is functioning correctly

●      Use monitoring to monitor messages at runtime and track the steps that are processed