Wrong interface used in sender agreement

[former_member185171]

Hallo,

We set up a service with SAP as provider. The configuration does not give any errors. In the WSDL we use this URL:

https://<host:port>/XISOAPAdapter/MessageServlet?channel=:Z_OZ_Lirias_GetData_CC:Z_OZ_Lirias_GetData... .

When we want to test this webservice PI is always using a wrong interface. Within the namespace there are five interfaces and always the same one is used. It seems to be sort of a default interface.

Is there a way to detect how that 'default' is chosen? Or has anyone any idea what we might do wrong?

To test the service we use SoapUI 3.5. I found some treads in SDN talking about possible problems with determining the sender interface when using SoapUI. Is this correct?

Are there any good and simple alternatives for testing webservices?

Thanks for any possible help.

Regards.

Kris

[stefan_grube · Accepted solution]

Try this URL:

http://host:port/XISOAPAdapter/MessageServlet?senderParty=FP&senderService=FS&interface=IF&receiverParty=TP&receiverService=TS&interfaceNamespace=IFNamespace

According to SAP Note 856597 this URL should be preferred.

[former_member200962]

In the WSDL we use this URL

The URL format seems fine for sending a SOAP message to PI (SOAP_Sender --> PI). make use of %5E instead of ^ and check.

When we want to test this webservice PI is always using a wrong interface.

PI will use the interface which is specified in the URL...i hope the interface name is proper....is the same interface maintained everywhere....in Sender Agreement, in Sender Channel (if PI7.0)

I found some treads in SDN talking about possible problems with determining the sender interface when using SoapUI. Is this correct?

I heard that Altova XML spy has issues....personally never faced an issue while using SAP SOAP Client.

Regards,

Abhishek.

[former_member185171]

Thanks for the reply.

The interface mentioned in the URL is correct and even when replacing the '^' it won't work.

Regards.

Kris

[former_member200962]

Did you try with the option of Test Configuration in ID?

[former_member185171]

Yes, we tested it in the configuration. And there everything goes as it should. Everything looks very well ok, that is what makes it so bizarre.

Kris

[former_member200962]

Quite Strange....I aslo use the same URL format and it works for me:

http://<IPAddress OR ServerName>:<PORT_No>/XISOAPAdapter/MessageServlet?channel=:<SenderBusinessService>:<SenderSOAPCC>&version=3.0&Sender.Service=<SenderBusinessService>&Interface=<SenderInterfaceNamespace>%5E<SenderMI>

can you do one thing..re-create the Sender Agreement Manually?

[former_member185171]

Hallo,

I tried this already several times and now again. But it made no difference.

Afterwards I deleted the sender agreement he seems to find: so I make the call with the mendioned interface, and this is what I got:

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: "Z_OZ_Lirias_GetData_CC", interface: "http://webservice.kuleuven.be/Lirias/GetData addData_OUT", receiver party: "", receiver service: "").

He keeps asking for the wrong interface.

Something is very wrong and I don't find the clue!

Kris