The Integration Server is the SAP Exchange Infrastructure runtime component for receiving messages and controlling how these messages are forwarded. During configuration of the XI system landscape, an SAP Web AS client is assigned the role of Integration Server. The following two engines work together in this client to control the message flow:
· The Integration Engine is responsible for central Integration Server services, for example, routing and mapping.
· The Business Process Engine is responsible for executing and persisting integration processes.
Furthermore, the majority of the adapters run on the central Adapter Engine, which is installed on the J2EE Engine of the SAP Web AS, and which can take over inbound and outbound processing on the Integration Server from the Integration Engine. In this way, the central services of the Adapter Engine (for example, persistence), can be used by all adapters.
See also: Connectivity.
Special Features of the Integration Engine
The Integration Engine can be deployed in various roles in different business systems. It comprises the following parts:
· A messaging logic, which implements the XI message protocol. The messaging logic receives messages and forwards them on. In the process, it ensures that the services that are defined by the protocol, such as quality of service and status management, also apply to messages (including processing of acknowledgments).
· An integration logic, which is used to describe the central services of the Integration Engine: Logical routing, technical routing, mapping, and adapters.
The application logic in the application systems should be kept separate from these components of the Integration Engine. Application logic includes the selection of application-specific data or the updating of requests in a business system, for example. For example, the application program can use proxies to exchange messages by means of SAP Exchange Infrastructure in a cross-system process. Proxy objects belong to the application logic.
You can only use the integration logic of the Integration Engine if you have assigned the role of central Integration Server to the Integration Engine in exactly one client. The following is an example of proxy communication by using the Integration Server:
You do not have to configure the Integration Engine as the Integration Server in client 010. This is just an example.
In other clients, you can configure the Integration Engine in such a way that its task is simply to send and receive messages. If no other client of the SAP Web AS sends or receives messages, the entire SAP Web AS is seen as the Integration Server, although technically speaking only the engines of a client actually take on this role.
The messaging logic for proxy communication is part of the SAP Web AS on either the sender or receiver business system. In adapter communication with the Integration Server, messaging is part of the Adapter Engine.
No comments:
Post a Comment