Database Reference
In-Depth Information
the sender and recipient using XML-based communication via HTTP by employing either of
these approaches:
◾
Direct communication via proxies that are generated into the application system based on
descriptions in the corresponding WSDL
◾
Communication via adapters enabled by creating exchange interfaces in the application
system
The combination of disparate system is primarily enabled by the fact that the sender and recipi-
ent exchanging messages via the Integration Server are effectively decoupled from each other.
Moreover, consequently, every system that can exchange messages with the Integration Server can
automatically exchange messages with all other systems connected to the Integration Server (see
note on page 280 of this chapter).
The normal processing on the Integration Server is
stateless
, which means that the Integration
Server is usually not aware of the semantic correlation between different messages, that is, the
context of the messages. But one can describe the logical dependencies between the messages
as well as additional conditions for defining the message flow, thus enabling the modeling and
maintenance of cross system business process with SAP XI. Business processes are objects stored
in the Integration Repository or Integration Directory along with other objects like message
interfaces. During the design phase, the business process can be defined using the graphical pro-
cess editor within the Integration Builder (in the Integration Repository). During the configura-
tion phase, the recipient determination for the business process can be set using the Integration
Directory of the Integration Builder. At runtime, the business processes can be run using the
Business Process Engine.
Similarly, in the case of collaborative processes, all the integration-related information in its
entirety is stored and accessible centrally in SAP XI:
◾
Objects during the design phase are stored in the Integration Repository.
◾
Objects during the configuration phase are stored in the Integration Directory.
The costs of development and maintenance of distributed systems are effectively reduced by the
centralized storage and access to knowledge on business processes.
10.4.3.2 SAP Business Process Management (BPM)
SAP BPM extends SAP XI to include
stateful
processing of messages by enabling persistence
of business processes on the Integration Server. As a result, business processes can be made to
wait indefinitely or according to a schedule of messages or send the messages after grouping
them in a specific manner or process the messages within a business process further recursively
or so on.
10.4.4 Application Platform
The SAP NetWeaver Application Server (AS) provides a complete development environment for
developing, deploying, and running platform-independent, resilient, and scalable applications.
SAP NetWeaver AS enables a homogenous infrastructure for both ABAP and J2EE-based
applications. The development environments of ABAP Workbench and SAP NetWeaver
