Generation in Sproxy of inbound and outbound MI

[former_member737583]

I've synchronous communication with WS. Everything is configured in XI. Sproxy is generated for Outbound MI. Everything is working. I'm able to send and receive messages. Now comes the question. Should I generate Sproxy object for Incoming MI too? Helps this with something?

Why incoming MI are displayed in sproxy and when they are used for?

[bhavesh_kantilal · Accepted solution]

You generate outbound interfaces as proxies when SAP acts as the initiator of the interface or the source.

In the case of outbound, you generate the proxy for the outbound interface and then have a report that populates the data and triggers the call to XI.

Inbound proxies are used when you want to SAP to be the recipient of data from XI. The Inbound proxy would receive the data and the implementation of the Proxy Interface would / should have the code to deal with the data that is received from XI.

In your case if I understand right, you are using SAP as the initiator and hence you need to create a proxy for the outbound interface, but you would have to do this when SAP acts as the receiver!

Regards

Bhavesh

[Former Member]

Hi,

As Bhavesh said correctly, you need to create the inbound proxy (incoming MI) only when R3 is a receipient. In your case, if you further want to post some data into R3 (returned by WS) then you should create the inbound proxy.

Regards,

Sarvesh

[former_member737583]

Thanks for reply. This is how I understood inboud and outbound concept of MI. I was asking about that, because I've seen development where SAP (XI) was initiator of communication and even then developer has generate sproxy for inboud MI. I guessed that maybe this has any good impact to performance.

Btw. I' noticed that when I'm sending the message using one MI to webService, for the first time it take XI a really long to send the message. Next message are send really quicker!