cancel
Showing results for 
Search instead for 
Did you mean: 

Difference between XI adapter and HTTP adapter

Former Member
0 Kudos

Hi,

I am not very clear on the exact difference between XI adapter and HTTP adapter.

I want to know, when should we use XI adapter and when to use HTTP adapter.

Regards,

Santosh

Accepted Solutions (0)

Answers (4)

Answers (4)

prateek
Active Contributor
0 Kudos

XI Adapter is used for XI to Proxy communication and vice versa. Also for XI integration server to another XI integration server communication.

HTTP adapter is used for communicating with http clients/applications

Regards,

Prateek

Former Member
0 Kudos

HI

HTTP ADAPTER:

The HTTP Adapter allows connection between the Integration Server and application systems. External systems connect to the Integration Server using the native HTTP interface (HTTP payload without SOAP envelope) which is converted to XI protocol (SOAP with header enhancements). The HTTP Adapter allows synchronous and asynchronous message functionality.

The plain HTTP adapter gives application systems the option of communicating with the Integration Engine and exchanging business data using a plain HTTP connection. Depending on the receiver system, outbound messages can be enhanced with certain information.

XI Adapter:

The communication via web service may have advantages, if you want communicate with non XI systems.

In your scenario, there is direct communication between XI engines, so you can go for XI adapter. The XI adapter which is normally used to configure the exchange of messages with in an Integration Server, can be extended to exchange messages between the two Integration Servers in the scenario.

You can use security settings to sign messages and check the signature. You can encrypt and decrypt message payloads

The XI Adapter is used for communication, via direct XML / HTTP message exchange (no message protocol conversion required)

1. With an Integration Engine (ABAP based). Both XI 2.0 and 3.0 protocols are supported

2. With a party using the Partner Connectivity Kit

3. With an Adapter Engine based either on XI 2.0 or 3.0

The XI Adapter is used with the Proxy Runtime (covered in another chapter) when communicating via ABAP or java proxies.

cheers

former_member182455
Active Contributor
0 Kudos

Hi santosh,

You communicate with the plain HTTP inbound channel of the Integration Engine using an HTTP address. The HTTP body is used as the payload for the message. The payload does not contain an envelope with control data for the message you want to create. You must code the control data in the HTTP address as parameters; these parameters are obligatory to be able to generate a message.

If you want to specify security checks or adapter-specific attributes in the message header for the plain HTTP inbound channel, create a communication channel for the party and service in the Integration Directory. You can configure the security level there. See below under Activities

If you want to specify an increased HTTP security level for incoming messages, perform the following steps:

● Create an adapter of type HTTP and Sender for the plain HTTP inbound channel in the communication channel in the Integration Directory.

The Transport Protocol, Message Protocol, and Adapter Engine are predefined.

● Under Security Check for Incoming Messages, you can specify which HTTP Security Level is to be assumed for incoming messages. You can choose from the following security levels:

○ HTTP (default value)

○ HTTPS without client authentication

○ HTTPS with client authentication

and XI adapter is used in proxies

Former Member
0 Kudos

Hi,

We use HTTP Adapter in case of the Application is trying to post the HTTP Request message to XI and able to receive the HTTP Message from XI also.

While using the HTTP as Sender , HTTP Sits on ABAP Stack and can able to communicate with the Integration Server Directly, No need of any Adapter here, it is adapterless communication

In Case of Client Proxies

Source application can directly interact with the XI by executing the report in SAP R/3 & will be able to send the XML data to IS,

So no need of the XI Adapter in this case to post xml to XI.

In Case of Server Proxies

Now XI has to post the xml data to the Target Application, here some thing shld be there to establish the medium with the Target System. So we use XI adapter here.

In the receiver case, we need XI Adaper to communicate XI integration Server with the Local Integration Engine( Which we made in SAP R/3's Business system as local IE) to post the data

Basically XI adapter will be used in normal scenarios also to communicate Adapter Engine with Integration Server internally while delivering the msg.

Check this Msg Flow how the XI Adapter is used in Normal Scenarios

REgards

Seshagiri