Process Integration Scenario with an Application Component of type Template.

The receivers are file systems. These are represented by the application component AgencyReporting. This is a storage location and not an application (a product). Therefore, you use an application component of type Template.

Abstract Service Interfaces

You define a service interface to represent the file format expected by the file system. This is an abstract service interface, since the interface is not implemented (unlike in an SAP system, for example).

External Definitions

The file format expected by the file system is described by an XSD file, which was defined independently of the ES Builder.

This description was imported to the Enterprise Services Repository as an external definition BookingOrderDataInformation and must not therefore be recreated manually.

The message type BookingOrderDataInfo defined in the XSD file is referenced in the service interface BookingOrderDataInformation_Ext.

Message mapping to map data structures with multiple hierarchy levels to a data structure with one hierarchy level.

The Template scenario uses the message mapping BookingOrderDataInfo_Agency2AgencyReporting. This mapping maps a data structure with multiple hierarchy levels (the message sent by the travel agency) to a data structure with a single hierarchy level (the message expected by the file system). (For details, see the test case defined in message mapping.)

Message mapping with a user-defined function

The message mapping uses the user-defined function countByTemplate. This function duplicates field values of the AgencyID and the OrderNumber, if they are required in multiple item entries.

Message mapping with fixed-value mapping

The message mapping uses the function FixValues to map fixed values (flight class: from codes to meaningful names).

Communication channel template

In the communication channel templates XIDemoChannel_FileXML and XIDemoChannel_FileCSV, the required communication channels are preconfigured.

Using configuration scenarios in the Integration Directory

All configuration data for the process integration scenario is grouped into a configuration scenario in the Integration Directory.

Communication Component

You define a communication component of type Business System Service for the travel agency system in the Integration Directory.

You define a separate communication component for each file system in the Integration Directory. These communication components can be either of type Business Component or Business System.

Communication components enable you to address the application systems as the sender/receiver of messages.

Receiver Determination

A receiver determination defines the receiver of the booking order data. This can be one or more file systems.

Messages sent by the travel agency are sent to all configured receivers. Therefore, you do not need to specify any routing conditions.

Interface Determination

Interface determinations define the inbound interface and the operation mapping used.

Receiver Agreement and Communication Channels

The travel agency sends the message in XI message format. Therefore, a sender agreement to specify inbound processing in more detail is not necessary.

You define a receiver agreement for each file system. The receiver agreement defines the technical details for outbound processing of the message by means of its assigned communication channel.

Since the receivers are file systems, you assign a communication channel with the adapter type File to the receiver agreement.

You define further details in the communication channel, for example file directory, file name, and file format (XML format or CSV format (Comma Separated Values)).

When using communication channel templates when assigning communication channels (configuration of a connection)

You create the required communication channels when assigning the receiver communication channels (adapter type File) for the connection. To do this, use the communication channel templates XIDemoChannel_FileXML and XIDemoChannel_FileCSV from the Enterprise Services Repository as templates.

Messages with multiple receivers

If multiple file systems are used, the messages are sent to multiple receivers.

To do this, a message split is performed during message processing.

Communication based on the adapter runtime (file/FTP adapter)

The SAP system of the travel agency is based (in the standard configuration) on AS ABAP 7.10. Therefore, you can use ABAP proxies to connect it to the Integration Server.

You connect the file system to the Integration Server using the file/FTP adapter. In the SAP standard configuration, this file system is localized on the server on which the SAP system of the travel agency (and the Integration Engine) is also installed.