on 06-27-2008 4:32 AM
Hi,
what is meant by local integration engine . it exists in R/3 application system.
Diff b/w local integration engine and central integration engine.
Hello Praveen,
A business system can be configured as an Integration server or Application system:
Ø Integration Server
The Integration server executes only integration logic available Integration Builder. They can also be identified as Pipe Line Steps. It receives XML message, determines the receiver, executes the mappings, and routes the XML message to the corresponding receiver systems. Thus configured Integration Engine is identified to be Central Configured Integration engine.
Note: Only one client of SAP system can be configured as Integration Server.
Ø Application system
The Application system will not execute the integration logic. It in turn calls the integration server to execute the integration logic if required. It acts as sender or receiver of XML messages. So, the Application system with a local Integration Engine requires the Integration server to execute the integration logic.
Regards,
Prasad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
This local adapter engine can be installed on any WAS and then while creating the Adapter in the Integration Directory you can select the adapter engine from your central or local adapter engine.
ofcourse all the installation activities like registring the adapter engine , etc should be done before you will be able to see the adapter engine listed in the integration directory as well.
Thnaks
VIKRANTH
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The Integration Engine, as a runtime component of SAP Exchange Infrastructure, has the task of receiving, processing, and forwarding XML messages. During message processing, collaboration agreements are evaluated, the receivers are determined, and mapping activities are executed.
The individual processing steps are called pipeline services and are defined in pipelines. It is the task of the Integration Engine to process these pipelines correctly and consistently.
Thus The Local Integration is configured on the Sender Or Receiver R/3 system, that could be able to talk with the central Integration Engine under the layre of WAS.
Norammly while dealing with ABAP proxy, you need the local Integration engine that will communicate to the central integration engine.
In your R/3 system, it has a local integration engine (6.20 or higher) is the local integration engine connecting to XI's integration Engine via using an HTTP destination or URL to XI's pipeline UR.
Refer
http://help.sap.com/saphelp_nw04/helpdata/en/a5/1b5342d8a7be30e10000000a155106/frameset.htm
Thanks
Swarup
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The Central Integration Engine receives XML messages, determines the receiver, executes mappings, and routes the XML messages on to the corresponding receiver systems and is not able to execute application logic.
But,
Application system with a local Integration Engine that requires the Integration Server to execute the integration logic (the Integration Server can run in another client of the same SAP system)
The system can act as a sender or receiver of XML messages, but it does not contain any integration logic. Therefore, neither routing nor mapping can be executed locally. Instead they must be executed by the Integration Server, which is called by the application system.
Although integration logic is only offered in ABAP-based business systems, the sender/receiver role of an Integration Engine can also be made available in other business systems.
There are pipelines for a local Integration Engine in the sender or receiver system, or for a central Integration Engine that is configured as the Integration Server, for example.
The individual processing steps that an XML message must pass through when it is processed are called pipeline elements. Each pipeline element calls exactly one pipeline service.
Thanks
Swarup
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.