Receiver Determination when multiple Product Versions / identical namespace

[Former Member]

Hi,

How would the receiver determination be done when we have multiple product versions with identical namespaces and interface names ?

During development, when we do a release transfer to another product version, the namespaces and interface names remain same as the current objects.

How would XI resolve the correct interface in this case ?

thanks,

Manish

[stefan_grube]

Hi Manish,

the receiver determination does not distinguish between software component versions, so the question in this case would be, how the communication channel is defined for this receiving interface.

As in any application system only one product version can be installed, the receiving system takes the interface from its software component version. Make sure that the mapping is correct for this case.

Regards

Stefan

[Former Member]

I guess the confusing part is that the SLD does not prevent me from selecting 2 software versions for the application system, and these 2 software versions will have identical namespaces and interface names.

But then we should not have 2 software versions for the same application system (does not make sense?). I am curious to know what is XI behaviour when you do select 2 software versions for the application system ?

thanks,

Manish

[stefan_grube]

The XI does not care about the application systems. When a message is received by the application, it knows, what to do with the messages.

The receiver could be an RFC call, an IDOC, an Abap Proxy, here the correlation between interface and Abap code is unique.

The receiver could be a File, or JMS adapter, here the correlation between interface and communication channel is unique as well.

You might reuse IDOCs or RFCs or in rare situations other interfaces in different software components and install them for the same application system. But you can only generate proxies from one interface.

Regards

Stefan