Dynamic interface in SOAP Sender Adapter

[Former Member]

Hi all,

for a specific business scenario we provide several web services using PI 7.11. We would like to use one communication channel (configured as SOAP Sender) for the client application, the interface (namespace) provided in the endpoint URL should be used for the inbound processing:

In the SOAP sender channel we have configured the following parameters:

The endpoint URL is used according to SAP Note 856597 in the form:

https://host:port/XISOAPAdapter/MessageServlet?senderParty=&senderService=...&interface=...&interfac...

We tried the following variants without success:

No sender agreement

Without a sender agreement we get the error: Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=TestSystem;TS=;AN=TestOut;ANS=urn:test;

One generic sender agreement (with * in interface/namespace)

The SOAP adapter throws an error: Bubble configuration error: parameter 'XI.InterfaceNamespace' is missing

Several specific sender agreements (one for each interface)

With specific sender agreements the SOAP adapter processes the messages without exceptions, but alsways uses the interface and namespace of the first message after the channel start. Other values for interface and namespace are ignored.

Is it at all possible to have one SOAP sender communication channel for multiple interfaces???

Thanks for your comments!

Hans

[MichalKrawczyk · Accepted solution]

Hi,

>>>Several specific sender agreements (one for each interface)

as far as I remember I've used the same scenario in one of my projects and it was working

so this shouldbe the way to work with that - if any,

Regards,

Michal Krawczyk

[Former Member · Accepted solution]

Hi,

thank you for your reassurance, I will set up some test scenarios again.

Unfortunately in my last tests today, only the first interface was recognized and then somehow cached. The second message was identified with the same interface, although the URL parameters were set differently.

Regards,

Hans

[baskar_gopalakrishnan2]

Few cents.. Technically it is possible to have one communication channel to handle multiple interfaces.

If you are dealing with same sender system and multiple operations,  You might want to consider having each interface as seperate operation or method in the same sender service interface. This way you maintain multiple operations in one scenario and using one sender communication channel. You need to use Stateless interface pattern not stateless (XI 3.0) interface pattern. You might get some basic idea about designing multiple operations using the same outbound interface with this blog

http://scn.sap.com/people/abhishek.salvi/blog/2009/07/31/using-service-interfaces-now-reuse-one

[Former Member]

Thank you for your input!

We already use multi-operation services, also in the described scenario. But still I have many services (with several operations each) and not one mega-service with all operations possible and would like to combine the call from one client in one sender communication channel, because it is one direction (sender), one adapter (SOAP), one qos (EO) and the same overall process logic.

Regards

Hans