Tutorial: Developing Content for A2A Processes 

Task

This tutorial contains instructions for developing a simple process integration scenario for an application-to-application process. You will learn the most important development steps that you need to perform when designing a process integration scenario, and you will also learn about all the objects used.

The tutorial is based on the demo examples provided by SAP. It is possible to reuse some of the objects that are already defined in these demo examples (interface and mapping objects, for example).

You use this tutorial to develop the process integration scenario CancelFlightBooking. In this process integration scenario, the travel agency cancels a flight booking that it has made. To do this, the travel agency must change the flight booking order (which it manages) and send a cancellation request to the airline with which it made the booking.

From a business perspective, the process integration scenario CancelFlightBooking is an extension of the process integration scenario SingleFlightBooking, which is part of the demo examples.

Even though from a business perspective the process integration scenario represents a typical use case for a business-to-business process, only concepts from the area of application-to-application processes will be used. For this reason, this tutorial only covers the concepts and guidelines for developing ESR content for application-to-application processes.

For more information about the concepts and guidelines for developing ESR content for business-to-business processes, see Business-to-Business Process Development. 

The figure below illustrates the process flow of this process integration scenario (as a component view):

You create ESR content for two different communication variants of the same process integration scenario.

●      Proxy Variant

Airline communicates with the travel agency by using the proxy runtime.

●      IDoc Variant

Airline communicates with the travel agency by using IDocs (adapter runtime).

Consider the role of the application developer responsible for developing the process integration scenario CancelFlightBooking for a travel agency as follows: You are responsible for developing the travel agency application and have been given the task of enhancing the existing application by adding the process integration scenario CancelFlightBooking.

You also implement the necessary exchange of messages with the airlines. The interfaces for canceling a flight are already available on the airline side: a service interface and an IDoc interface. The application of the travel agency must be able to work with both interfaces.

Result

By the end of this tutorial, you will be able to: 

●      Work with the ES Builder (UI of the Enterprise Services Repository, ES Repository for short)

●      Understand the way the most important objects in the ES Repository are related.

You can compare the result with the process integration scenario SingleFlightBooking, which is shipped by SAP, and then configure and execute the process integration scenario.

For more information:

For detailed information about configuring ESR content, see the Configuration Guide for Demo Examples. When you want to configure and test the process integration scenario you have developed, you can use this document to help you orientate yourself.

Note, however, that this document does not contain configuration instructions that are tailored purely to the process integration scenario CancelFlightBooking. The described procedure only refers to the demo examples shipped by SAP.

More information: Demo Examples

None of the recommendations regarding the configuration that are provided in this tutorial are hard and fast, nor do they constitute the complete procedure for configuring the process integration scenario CancelFlightBooking. You must only use them as an orientation guide.

Therefore, SAP cannot guarantee that the configuration settings you make will result in the error-free execution of the process integration scenario.