Defining an Integration Process
An integration process defines which messages are processed and how. The definition, configuration, execution, monitoring of an integration processes are all integrated in SAP Exchange Infrastructure.
Message Interfaces and Message Mappings
At design time, you first define the messages that are to be processed by an integration process. For this purpose, define the required message interfaces in the Integration Repository (see also: Developing Message Interfaces).
If the integration process is to transform messages (for example bundle multiple messages into one message), you also need to define the required multi-mapping.
Integration Process: Step Types, Container Elements, Correlations
Finally, define the integration process by using the graphical process editor in the Integration Builder of the Integration Repository.
When defining an integration process you define the individual processing steps. The process editor has step types for sending, receiving, and transforming messages, as well as control-relevant step types, for example, for defining a loop or a switch.
The individual steps of an integration process can either supply or demand data. This data is managed in containers. A container comprises individual container elements (variables). Before you can use data in a step, you must first define the corresponding container elements (see also: Defining the Data of a Process in Containers).
At runtime, multiple instances of an integration process can be active. To ensure that a message is assigned to the correct instance of the integration process at runtime, you must correlate messages that belong together (see also: Correlating Messages).
You have the option of defining an integration scenario for an integration process (see also: Designing Integration Scenarios). This then enables you to use the integration scenario configurator to configure the integration process in the Integration Directory later on.
At configuration time, in the Integration Directory, create a service without a party for the integration process itself and for each business system from the integration scenario. Next, define an integration scenario that references the integration scenario in the Integration Repository. You can then call the integration scenario configurator from the integration scenario to help you through all further steps in the configuration process.
An integration process is started when a message is received. You have different options for monitoring processing:
· XI Runtime Cache (see also: Analyzing an Integration Process in the XI Runtime Cache)
· Monitoring the Business Process Engine (Transaction SXMB_MONI_BPE)
· Message Monitoring (see also: Monitoring XML Messages)
· Central Monitoring (see also: CCMS Alert Monitor)
Furthermore, an integration process can generate alerts for Alert Management.
For an example of an integration process, in the Integration Repository, choose SAP BASIS → SAP BASIS 6.40 in the namespace http://sap.com/xi/XI/Demo/Agency under MultipleFlightBookingCoordination (see also: Example: Integration Process for Connecting Flight Bookings).