SOAP Adapter Sender PI7.1: 400 Bad HTTP request

[Former Member]

Hello,

I have a problem with a SOAP adapter sender communication channel.

I'm trying to migrate a scenario from XI 3.0 to PI7.1 SP6 (PI_BASIS 2006_1_710 SAPKIPYN06).

I can send messages successfully to the old system using the URL

http://host:port/XISOAPAdapter/MessageServlet?channel=:BC_Name:CC_SOAP_Sender

On PI7.1 I get

400 Bad HTTP request

Error: -21

Version: 7010

Component: HTTP_PLG

Module: http_plgrt_mt.c

Line: 5226

Error Tag:

Detail: illegal request version

I have created a Sender Agreement, generated the wsdl from that and tried the URL in there.

Surprisingly it has the old format, namely

http://host:port/XISOAPAdapter/MessageServlet?senderParty=&senderService=BC_Name&receiverPar...

although the 7.1 documentation describes the ?channel=party:service:channel style only.

Anyway, the result remains the same.

I tried some other approaches like escaping the colons in the URL without success.

The user has the role SAP_XI_DEVELOPER_J2EE assigned.

Any idea what's wrong here?

Thanks in advance

Rainer

[Former Member · Accepted solution]

Hey

The difference in can see in your URL's is that in the first URL,you are posting to the adapter engine of XI system.

in the second one you are posting to Integration engine of PI system.

Any reason for this change? While creating WSDL did you click on "Propose URL" button?

Thanks

Aamir

[Zilch · Accepted solution]

Hi Aamir,

like I wrote: The first URL is the one that works on XI3.0, the second is the one that was generated from the Sender Agreement.

I have tried the first URL with both ports, ABAP and Java, with the same result.

Yes, I have clicked the "Propose URL" button to generate the wsdl.

In RWB the channel appears as "started but inactive".

Regards

Rainer

Edited by: Rainer Zilch on May 29, 2009 1:07 PM

[Former Member · Accepted solution]

>>In RWB the channel appears as "started but inactive".

Yeah,it will be like that because you are posting messages directly to Integration server."Propose URL" does that.You are bypassing the adapter engine when you use the URL generated by "Propose URL" button.

/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine

The above blog gives the reason for this,if you want to bypass the adapter engine,then generate the URL as given in the above blog

/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services

This blog explains how to post message to adapter engine,here you need to change the URL,don't click on "Propose URL" button.You can monitor SOAP adapter in RWB only if you generate the URL as given in second blog

The URL which is working for you in XI 3.0 is posting messages to adapter engine,so generate the URL in PI 7.1 in the same way,by following the second blog i have mentioned.

Thanks

Aamir

[Former Member]

In SOAP UI tool, change the HTTP settings as 1.0/1.1.

And also maintian the Request compression as None.

[Zilch]

Hi All,

thanks a lot for your input.

The problem was that the client I was using for my tests (soapUI) was using HTTP 0.9.

I have now changed the preferrences so that it uses HTTP 1.0, now it works.

Best regards

Rainer

[stefan_grube]

> The problem was that the client I was using for my tests (soapUI) was using HTTP 0.9.

Sometimes the cause of an error is far away from any possible imagination

[Former Member]

Hi Rainer,

in PI 7.1 in ID from sender agreement, from menu - display WSDL and then your WSDL will be displayed in a new window.........just copy this WSDL URL and use it in your sender SOAP application...........

Regards,

Rajeev Gupta

[stefan_grube]

Apply the latest SPS for Sp6, as there are some bugs in that version.

The ?channel= version should work.

Check host/post/mdt/channelmonitorservlet for errors as well.

Regards

Stefan

[Zilch]

Hello Stefan,

is that

Support Packages and Patches" SAP NetWeaver" SAP NETWEAVER" SAP NETWEAVER PI 7.1" Entry by Component" Process Integration

1. XI ADAPTER FRAMEWORK 7.10

o #OS independent

SAPXIAF06_25-20001975.SCA SP06 for XI ADAPTER FRAMEWORK 7.10

?

Thanks & regards

Rainer

[stefan_grube]

Hi Rainer,

Yes, that is right, this is SPS 25 for SP 6.

But on the other side, as Aamir mentioned, the error message comes from the ABAP stack. So verify the in the address server:port that the port number is the same as in the SLD or RWB page.

Regards

Stefan