Issue in Proxy to SOAP scenario with standard Webservice from EP

[Former Member]

Hi Experts,

I have designed the scenario from Proxy to SOAP in PI 7.11. The scenario is files contained in ECC system has to be placed into collaboration room in EP through PI system.

The standard EP repository framework webservice is working fine in WSNavigator and same webservice is working in PI by published in the SR then inbound and outbound interfaces are getting results properly.

The issue is while we are running end to end scenario in PI system for SOAP adapter for calling webservice and got the below error.

Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Unsupported Media Type

If I configured the Message transfer bean in module tab for SOAP adapter

Transform.ContentType=======text/xml;charset=utf-8

XMBWS.NoSOAPIgnoreStatusCode====true

I can see the request and response messages was successfully in PI but in response message there is no payload.

Please suggest if any idea and I will appreciate your help?

Thanks,
Narasimha

[former_member184681]

Hi,

It looks like your receiver's web service doesn't accept the content type "text/xml". Check what should be the correct content type and use that one in the message transform bean - for instance, maybe application/xml will work fine for you. Since you're saying it is working fine in WS Navigator, you can also check the content type used there, and use the same one in PI.

Regards,

Grzegorz

[RameshGulipall]

Hi Gregorz,

Thanks for your reply!!

Still no luck after change to content type. After changed in SOAP receiver adapter now request and response messages processed successfull but there is no file in target EP system. One more thing processed successfully response message no payload. Please give you inputs for this issue

Regards,

ramesh

[baskar_gopalakrishnan2]

HTTP 415 is content type incompatible issue. Thats the reason you dont see the payload. You might want to check with target system and see what content type they are sending. Accordingly you can decide.  For example say if the target system requires  content type Application/soap+xml. In this case we can't use standard soap adapter and we need to use soap axis adapter.   The similar discussion I see it in this thread  http://scn.sap.com/thread/1703687

[RameshGulipall]

Hi Baskar,

Thanks for your response!!

After adding Transferbena http 415 error got solved. Now am getting the http 500 internal error , via tested from the Runtime workbench. I was successfully test in SOAP UI. Please provide your inputs

The error details below.

SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error

MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAd

Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Errorapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error

Please find the below test message from RWB.

<?xml version="1.0" encoding="utf-8"?><n0:createDocument xmlns:n0="urn:RepositoryFrameworkWSVi"><n0:parentCollectionRid>/room_extensions/cm_stores</n0:parentCollectionRid><n0:childName>TAX_File_ECC2EP111111</n0:childName><n0:orderPosition><n0:type></n0:type></n0:orderPosition><n0:overwriteEnforced>true</n0:overwriteEnforced><n0:lockDescriptor><n0:depth></n0:depth><n0:scope></n0:scope><n0:timeout></n0:timeout><n0:type></n0:type></n0:lockDescriptor><n0:properties></n0:properties><n0:content></n0:content><n0:fetchGroup><n0:generateGuid></n0:generateGuid><n0:includeContentMetadata></n0:includeContentMetadata><n0:includeProperties></n0:includeProperties><n0:includeUrls></n0:includeUrls></n0:fetchGroup></n0:createDocument>

Please find the test message from SOAPUI:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:RepositoryFrameworkWSVi" xmlns:urn1="urn:com.sap.netweaver.bc.rf.ws.namespace" xmlns:urn2="urn:com.sap.netweaver.bc.rf.ws.lock" xmlns:urn3="urn:com.sap.netweaver.bc.rf.ws.property" xmlns:urn4="urn:com.sap.netweaver.bc.rf.ws.content" xmlns:urn5="urn:com.sap.netweaver.bc.rf.ws.lookup" xmlns:lang="urn:java/lang">

   <soapenv:Header/>

   <soapenv:Body>

      <urn:createDocument>

         <urn:parentCollectionRid>/room_extensions/cm_stores</urn:parentCollectionRid>

         <urn:childName>HD_File_SK_301</urn:childName>

<urn:orderPosition>

           <urn1:type></urn1:type>

         </urn:orderPosition>

<urn:overwriteEnforced>true</urn:overwriteEnforced>

<urn:lockDescriptor>

            <urn2:depth></urn2:depth>

            <urn2:scope></urn2:scope>

            <urn2:timeout></urn2:timeout>

            <urn2:type></urn2:type>

         </urn:lockDescriptor>

<urn:properties>

         </urn:properties>

<urn:content></urn:content>

<urn:fetchGroup>

           <urn5:generateGuid></urn5:generateGuid>

            <urn5:includeContentMetadata></urn5:includeContentMetadata>

            <urn5:includeProperties></urn5:includeProperties>

            <urn5:includeUrls></urn5:includeUrls>

</urn:fetchGroup>

</urn:createDocument>

   </soapenv:Body>

</soapenv:Envelope>

Regards,

Ramesh

[baskar_gopalakrishnan2]

HTTP 500 internal server might be due to many reasons. Please check whether target system sends the response that does not match your target response message structure. Please check any namespace or namespace prefix you expect different from the WSDL response given. This could be even due to invalid data that comes from the response of target system. Please test end to end and see the results. Also see whether you find any differences between soapui and end to end in the response structure..