Problems using SAP SOAP client implementation

[Former Member]

Hello,

I developed a webservice server application that is consumed by a client within SAP EP6. The client is implemented with the SAP SOAP implementation using the eclipse plugin (1.2.0) wizard for creating a webservice client portal service out of a wsdl.

When I deploy the webservice server application within a tomcat, the client works fine within a SAP EP6 Portal Component. When I deploy it on an oc4j (which is the target platform of our customer), the client produces an exception about not wellformed xml.

Comparing the two responses from tomcat and oc4j with a http sniffer shows that oc4j uses chunking of http responses. This means, that the body of the http response body (containig the xml representing the SOAP response message) contains a number at the beginning and the end of the xml, which leads the client to regard this response as not wellformed.

When I don't use the SAP SOAP implementation for the client, but the implementation of jaxrpc from SUN (in which the webservice server part is actually written), things work fine both with tomcat and oc4j.

So my question is: Is there any possibility to configure the SAP J2EEngine in which EP6 runs in a way that chunked http responses are supported for SAP SOAP response parsing?

Since it it is nesseccary to change the prtDefault.properties to get the SUN webservice client running within SAP EP (what might sincerely affect other portal applications), i'd be glad to find a solution to use the SAP SOAP implementation together with oc4j.

Thanks for any hint

Torsten

[former_member222409]

Hi Torsten,

I would like to answer the questions you raised. The SAP web container is HTTP1.1 complaint. It supports receive and decoding of chunked responses. Could you be more specific why you consider that there is problem with chunked responses?

Another thing that you can do is to check whether you are using the latest version of the J2EE engine because some changes were made that concern chunking.

Best regards,

Diyan

[zubev]

Hi Torsten,

The problem for the SOAP Client and support of chunked has been fixed and a future SP will contain it. Ask your supporter for more details.

Best regards,

Alexander

[Former Member]

Hello,

I am facing the same problem in EP6 SP2 Patch 4. I keep on getting exceptions while parsing soap responses, from websphere and other external service providers, and it is always related to chunked responses.

Is there a fix or workaround available ? (obviously not forcing external partners to downgrade to non-chunked..)

Perhaps there is a way to force the soap POST request to stick to POST /uri HTTP/1.0 instead of HTTP/1.1 ?

Thanks in advance

Vitaliano

[zubev]

Hi Torsten,

Seems like the feature is not supported. Please create a CSS message and apply a link to this post to get the implementation in a future service pack.

Best regards,

Alexander

[Former Member]

Hi Alexander,

thanks for your answer. I created an OSS message for this and also asked oracle's support how to configure oc4j's webserver not to use chunking of http responses.

Best regards

Torsten

[Former Member]

Hi,

I consulted the Oracle support about the problem above.

After some "ping-ponging" their research showed the following:

..snip..

SAP state that their web container does support chunking but only for responses made by their container. By extension this means it does not accept it as an input. The RFC standard states

that be HTPT 1.1 compliant it MUST support receive and decoding of chunked responses. Therefore the question to be asked here are one of these:

1/ Is the SAP Web container only HTTP 1.0 compliant?

2/ Is the SAP web container HTTP 1.1 compliant as well? If so why does it not support the RFC standard to the full?

As it looks to us at this time as if the only solution this is to either use only

HTTP 1.0 in your SOAP messages (as HTTP 1.0 does not support chunking) or for SAP to advise whether their container does in fact support HTTP 1.1?

..snip..

Could you please give me an answer to the questions above so i can plan the following actions to do?

Thanks for help.

Best Regards

Torsten

[Former Member]

Hello Torsen

I have solved the problem by applying SAP J2EE Engine 6.20 Cluster Patch 25. This version now supports chunked http/1.1 properly.

Regards

Vitaliano