Figure 3: Integration scenario 􀁸 The process flow and its

(design time view; left) and separation into individual process

assignment of process components components (integration scenario
to systems of and
the actual system landscape further process models to be
(configuration time view; right) discussed later-on)
As an example, the figure shows 􀁸 The interfaces that determine the
the systems of the actual system data exchange between process
landscape where the business logic components
of 􀁸 The detailed structure of the data
process components 1 and 2 is – of the messages – that is being
implemented: Process component exchanged
1 is deployed on systems 1a and 􀁸 The mapping or transformation of
1b, data structures on both sides of a
whereas process component 2 is connection
deployed on systems 2a, 2b, and The following figure gives an
2c. Resulting from this, the overview of these entities. On the
communication between two left side it shows a complete
process components is broken integration
down to communication between scenario spanning a huge set of
the systems process components and
mentioned above at runtime, connections; on the right side, the
whereas the communication is details of one
mediated by an integration broker. single connection between two
The three phases introduced here process components are shown:
can be considered to be phases of
an integration project: They form
the
basic framework for the detailed
description of the concepts in this
handbook.
2.4.1 Design Time
At design time, an integration
developer designs the integration-
relevant aspects of a business
application at
an abstract level, independent from
any implementation-relevant
details.
The following aspects of a business
process can already be specified at
design time: