System Landscape Directory: All the technical systems of system landscape are entered in the SLD. This includes the host names and other technical attributes as well as information on the Software component installed on a server.Assign a system name to each technical system .This business system is required for scenario configaration as the name for the sender and receiver Systems.
Integration Builder: A client-server framework for accessing and editing two stores of Shared Collaboration knowledge. It has two parts, which are fat clients to SLD where we can import the objects and use them locally. The basic reason for separating Integration Repository from Integration Directory is because by separating design time activities from configuration time activities, SAP can ship content from the Integration Repository, which each customer can implement for their specific landscape in the Integration Directory.
Integration Repository: It is used for the design and development of interface, Process and Mapping objects that are used to implement Integration Scenarios. Usually they contain static objects, which can be used for different landscapes by defining the routing rules in Integration Directory.
Integration Directory: They contain dynamic objects where in we configure scenarios using the objects from Integration Repository and route the messages between systems.
Integration Server: This component provides run time for XI. This is central processing engine of XI.
Business Process Engine: Business Process Engine enables SAP Netweaver with BPM capability by processing integration processes at runtime. BPE uses functions of the workflow engine and generates workflow from integration process at runtime.
Components of Sap xi
Integration Engine: Integration engine enables processing of XML messages that are exchanged between applications in heterogeneous system landscapes. Using adapters such as IDoc, http, it can process IDocs(Intermediate documents), http requests and Remote Function Calls. It is runtime environment of SAP Exchange Infrastructure, which has the task of receiving, processing and forwarding XML messages. Processing is done with the evaluation of Collaboration agreements, by determination of receivers and execution of mapping programs.
Adapter Engine: Adapter engine is used to connect Integration Engine to SAP systems and external systems. Various types of adapters are provided to convert XML and HTTP based messages to the specific message protocol and format required by the partner systems and vice-versa. It is based on adapter framework, in turn based on SAP J2EE Engine (as part of the SAP Web Application Server) and J2EE Connector Architecture (JCA).
1 comments:
May 2, 2014 at 7:34 PM
nice post from Sankar
Post a Comment