Uses EO Queues
Will always be BE
In case of connection failures, we don't know if it was processed
PI is responsible for errors
Sender waits for a response
Uses EO Queues
Can be QoS = BE
Sender can continue working after message is sent
Restart is possible only if sender and receiver support
Sender waits for a response
Stateless
Stateful
It is BE so interface patterns are not possible.
TUCC
Stateless
Stateful
Interface patterns are always possible.
TUCC
Stateless XI 3.0 Compatible
True
False
System
Read
Application
ABAP proxies
Java Proxies
Integration Processes
Some adapters
SWCVs
ABAP proxies
Java Proxies
Integration Processes
Some adapters
SWCVs
Structure mapping
XSLT
ABAP-XSL
ABAP-CLASS
Value Mapping
Structure Mapping
Value Mapping
XSLT
No need to map
Is realized as Integration Process Communication Component
Is realized as a Configuration Scenario
Is mandatory in async scenarios
Is same as a PCIM
Outbound interface
Message
Inbound Interface
Adapters
Receiver
Decentral
Sender
Proxy
True
False
Adapters
Sender proxies
Receiver proxies
None of the above
Based on SOAP
Has the payload in the last attachment
Has extra SAP proprietary tags
Has no SOAP body
The HTTP_AAE adapter
Is the Central Pipeline URL
Does not exists
HTTP ABAP adapter
True
TRUE
Si
1
0
It will not fail but will be slow
ABAP central pipeline Technical Routing
ABAP central pipeline Logical Routing
Mapping
=
Not =
EX (Exists)
In Table
CP
True
False
Wait!
Here's an interesting quiz for you.