Weird error with SOAP sender scenario

[Former Member]

Hello

I got very weird error.

I've completed a SOAP --> Xi --> proxy scenario. Tested it and worked fine.

Then I configured another scenario SOAP --> XI --> proxy for another service interface with same sender system and receiver system. Since it's the same sender, thus both scenarios use the same sender SOAP communication channel.

However if now I test the first scenario, the PI tries to process it using the second scenario configuration.

Basically it assume the incoming message is for interface of the second scenario.

I used wsnavigator for testing, in the HTTP log I can clearly see log:

POST /XISOAPAdapter/MessageServlet?senderParty=&senderService=FMS&receiverParty=

&receiverService=&interface=SI_Interface1_A&interfaceNamespace=http://myinterface HTTP/1.1

as you see the interface is SI_Interface1_A and interfacenamespace is also the one of the first scenario. But PI just assume the incoming interface is SI_Interface2_A and namespace of the second scenario. In the result HTTP log I see:

com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.ConfigException: No sender agreement configured that matches the message's header fields (sender party: "", sender service: "FMS", interface: "http://interfacenamespace2 SI_Interface2_Out_A", receiver party: "", receiver service: "")

Note: I deleted the sender agreement of the second scenario.

Anybody has similir error before?

What the hell is it?

Thanks

Jayson

[Former Member · Accepted solution]

Hi Jayson

Are you on PI 7.1?

If yes then we found this an issue. Like 7.0 you need to create one more CC for another NS. reason was not known but its not working.

conceptually when Default interface has been removed from Sender Soap CC then it should work irrespective of interface but it didnt.

You can search a thread raised by Venkat on this and no solution came up.

Thanks

Gaurav

[Former Member · Accepted solution]

Thank you all for the information.

I created separate soap CC for each interface, now it's working.

However I still think it's not right to need to define a soap CC for each interface, because in sender agreement, we already defined the incoming interface, PI has all the information to determine the interface. In addition, the CC will be the same for every interface, then why need to repeat the same thing over and over? Anyway, this is up to SAP whether to change.

Issue closed.

[bhavesh_kantilal]

To me the need to make 2 Sender SOAP adapter makes sense.

You have 2 Separate Interface calls and each of these are to be used in 2 separate Sender SOAP adapters with 2 sender agreements.

Each of these will have their own WSDL from the Sender Agreement and so on.

I think you have already done this or like others have pointed out , are you using a single SOAP sender adapter?

Regards

Bhavesh

[prateek]

As per the naming convention, I think you are using PI 7.1.

In case of SOAP adapter till PI 7.0, the behaviour deferred from standard behaviour of other adapters in retrieving the sender interface details from sender agreement. To comply with behaviour of other adapters, SOAP adapter was changed in PI 7.1.

Since it's the same sender, thus both scenarios use the same sender SOAP communication channel.

Try to configure separate channels for separate interfaces.

Regards,

Prateek