difference between central adapter engine and decentral adapter engine?

[Former Member]

Hi, experts i am fresher to XI. can you please explain the difference between central adapter engine and decentral adapter engine?

[Former Member]

HI

1.When Xi is installed we get the defaukt Adapter Engine(i.e) central adapter engine.

2. For load balancingand to share the load for better performance we use decentral engine.

3. Central Adapter Engine is on Integration server and decentral adapter engine is outside Integration Server.

cheers

[Former Member]

Hi,

Central AE: uses UME with ABAP (J2EE with Add-In option), i.e.UME of this engine is configured against the coresponding ABAP stack automatically during installation)

Decentral AE: uses UME with DB only (default) or UME with ABAP (su01, PFCG; roles visible as groups; CUSTOM INSTALLATION); decision at installation time!

1. when Xi is installed we get default adapter (i.e) central adapter engine.

2. For load balancing we use decentral engine.

3. central adapter engine is on Integration server and decentral adapter engine is outside IS.

Adding a decentralized adapter engine can create load balancing for the integration server.

For messages going to decentral adapter use channel XI with specified URL, for incoming messages you don't need a channel.

Every XI installation will install a default adapter engine and these are called as the Central / Local Adapter Engines. Most of the times this one Adapter Engine is more than sufficient.

At times, when the load on your server is going to be high , you can install a Decentral Adapter Engines and these are nothing but seprate instances of your Adapter Engine that can pick data and send it to your Integration Engine.

The need for a decentral Adapter Engine also arises when you have security restrictions, DMZ , etc in the landscape where one adapter engie is used for one particluar DMZ and another acts as the local adapter engine etc.

Refer

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/03fd85cc-0201-0010-8ca4-a32a119a...

The main advantage is load balancing and reducing risk of "single point of failure" so if something is wrong with central system or network then atleast your message will persist for later processing.

Another practical advantage is related to maintenance, every decentral AE is independent of other so maintenance will affect small set of interfaces not others.

Reward Points if it helps

Thanks

Vikranth

Edited by: Khimavath Vikranth on May 28, 2008 9:11 PM

[Former Member]

Hi,

Adding a decentralized adapter engine can create load balancing for the integration server.

For messages going to decentral adapter use channel XI with specified URL, for incoming messages you don't need a channel.

Every XI installation will install a default adapter engine and these are called as the Central / Local Adapter Engines. Most of the times this one Adapter Engine is more than sufficient.

At times, when the load on your server is going to be high , you can install a Decentral Adapter Engines and these are nothing but seprate instances of your Adapter Engine that can pick data and send it to your Integration Engine.

The need for a decentral Adapter Engine also arises when you have security restrictions, DMZ , etc in the landscape where one adapter engie is used for one particluar DMZ and another acts as the local adapter engine etc.

Refer

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/03fd85cc-0201-0010-8ca4-a32a119a...

The main advantage is load balancing and reducing risk of "single point of failure" so if something is wrong with central system or network then atleast your message will persist for later processing.

Another practical advantage is related to maintenance, every decentral AE is independent of other so maintenance will affect small set of interfaces not others.

Thanks

Swarup

Edited by: Swarup Sawant on May 28, 2008 9:06 PM