16 Replies Latest reply: Aug 4, 2008 5:28 PM by Brian Fernandes RSS

TechnicalException: Deserializing WSDL stream, Invalid Response Code: (500)

Brian Fernandes
Currently Being Moderated

I am creating a Composite Application, which consumes a Enterprise Serivce from the Service Registry.

 

I have created the destination and also done the mapping.

 

But when I test the service in WSNavigator I get the following error

 

Caused by: com.sap.engine.services.webservices.espbase.query.exceptions.TechnicalException: Deserializing WSDL stream http://<host>:8000/sap/bc/srt/xip/sap/ECC_SALESORDER009QR? failed

at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.getWSDLDefinitions(WSQueryImpl.java:512)

at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.initialize(WSQueryImpl.java:311)

at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.findWSEndpoints(WSQueryImpl.java:167)

at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImpl.getEndpointConfigurations(DestinationsHelperImpl.java:966)

... 81 more

Caused by: com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException: Invalid Response Code: (500) Internal Server Error. The requested URL was:"http://<host>:8000/sap/bc/srt/xip/sap/ECC_SALESORDER009QR?, used user to connect: dev01"

at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:140)

at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:91)

at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:80)

at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.getWSDLDefinitions(WSQueryImpl.java:510)

... 84 more

Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (500) Internal Server Error. The requested URL was:"http://<host>:8000/sap/bc/srt/xip/sap/ECC_SALESORDER009QR?, used user to connect: dev01"

at com.sap.esi.esp.service.server.query.discovery.WSTransportSettingsResolver.resolveEntity(WSTransportSettingsResolver.java:376)

at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:127)

... 87 more

 

 

 

 

Is it a problem with the Destination settings or some Server problem, or some problem with coding.

 

Thanks

   -Brian

  • Re: TechnicalException: Deserializing WSDL stream, Invalid Response Code: (
    Yasar Pala
    Currently Being Moderated

    Hi Brian,

     

    Please check if the service endpoint (for ECC_SALESORDER009QR?) is configured properly in the backend in the given path (http://<host>:8000/sap/bc/srt/xip/sap/). If you configured the destinations pointing the "WSIL" (WSIL of the Soap Runtime Registry), you can try to reactivate this service in the backend.

     

    Hope this helps,

     

    Yasar

    • Re: TechnicalException: Deserializing WSDL stream, Invalid Response Code: (
      Brian Fernandes
      Currently Being Moderated

      Hi Yasar,

      Thanks.

       

      I have tested the Endpoint in the Service Registry(in WSNavigator) it works fine without any input.

       

      So while creating the destination,

      http://<addr>:8000/sap/bc/srt/xip/sap/ecc_salesorder009qr?sap-client=400&wsdl=1.1&mode=sap_wsdl 

      is the location of my wsdl on my ECC.

       

      and within the wsdl I have

      http://<addr>:8000/sap/bc/srt/xip/sap/ECC_SALESORDER009QR?sap-client=400
      

        as " soap:address location "

       

      So while creating the destination, I have put "soap:address location " as the destination(wsdl type, I havent used wsil)

       

      I believe I have done the right thing while creating destinations, if not plz tell me .

       

       

      When do we get this error generally, Invalid Response Code : 500  ???

       

       

      Thanks Brian .

  • Re: TechnicalException: Deserializing WSDL stream, Invalid Response Code: (
    Yasar Pala
    Currently Being Moderated

    Hi Brian,

     

    If you search in WS Navigator for the destination that you configured, can you find the service interface for your enterprise service or is searching throwing an error?

     

    One thing you can do is, give the binding URL of the Service as URL in the destination.

     

    Regards,

     

    Yasar

    • Re: TechnicalException: Deserializing WSDL stream, Invalid Response Code: (
      Brian Fernandes
      Currently Being Moderated

      Hi Yasar,

      Thanks for the response.

       

      I have tested the Endpoint in the Service Registry(in WSNavigator) it works fine without any input.

       

       

      In Service Registry, I have tested the Service, by going to the endpoints tab and then clicking on Test button, which opens WSNavigator and allows me to test this service.

      My service is working fine there.

       

      So next I imoprt it in CAF, and expose it as a Web Service, and create destinations, this is where I get the Deserialization error.

       

      So while creating the destination,

       

      http://<addr>:8000/sap/bc/srt/xip/sap/ecc_salesorder009qr?sap-client=400&wsdl=1.1&mode=sap_wsdl

       

      is the location of my wsdl on my ECC.

       

      and within the wsdl I have

      http://<addr>:8000/sap/bc/srt/xip/sap/ECC_SALESORDER009QR?sap-client=400

       

      as " soap:address location "

       

      So while creating the destination, I have put "soap:address location " as the destination(wsdl type, I havent used wsil)

       

      I just want to confirm from where do I get the url for creating the Destination in nwa >> SOA Mgmt > Destination

  • Re: TechnicalException: Deserializing WSDL stream, Invalid Response Code: (
    Yasar Pala
    Currently Being Moderated

    Hi Brian,

     

    For example, if you have configured the endpoint of the enterprise service in the services registry with this WSDL URL:

    http://hostname:portnumber/sap/bc/srt/wsdl/bndg_XXXXXX/wsdl11/allinone/ws_policy/document?sap-client=001

     

    you can use the same URL as the destination URL on NWA SOA Management --> Destination Template Management.

    For destination you should give the URL and System (ABAP or Java).

     

    After configuring the destination on External Service Configuration of Composite Application Framework, map the deployed composite service (that you exposed) with this destination.

     

    Best regards,

     

    Yasar

    • Re: TechnicalException: Deserializing WSDL stream, Invalid Response Code: (
      Brian Fernandes
      Currently Being Moderated

      HI Yasar,

       

      Thanks for taking time to respond to my queries.

       

      I would like to summarize the steps I have performed:

      - Imported the wsdl from my Local Service Registry.

      - Performed default mapping.

      - Created an additional operation to narrow down the variables I want to output.

      - Exposed this operation in my Appl Service as a Web Service.

      - Created a destination in nwa*

      - Done the mapping in host:port/CAF

       

      All the steps I have performed fall in line with what you stated, but even then I am unable to attain the desired output.

       

      *In setting the destination, I have taken the url from Service Registry,

         On searching the service, in the endpoints tab, I have selected the Target Adress.

       

      Also another point I would like to make is that, I successfully created a standalone Java client to consume the same ES.

      So I assume the inputs are correct.

       

      Is there any other possiblity for getting the Deserialization error.

       

      Also when I try to manually open the Target url in a browser, I get the following content

      - - <soap-env:Fault>
             <faultcode>soap-env:Server</faultcode> 
                  <faultstring xml:lang="en">SRT: Wrong Content-Type and empty HTTP-Body received</faultstring> 
                - <detail>
                     - <ns:SystemFault xmlns:ns="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/">
                       <Host>undefined</Host> 
                       <Component>COREMSG</Component> 
                          - <ChainedException>
                            <Exception_Name>CX_SOAP_CORE</Exception_Name> 
                            <Exception_Text>SRT: Wrong Content-Type and empty HTTP-Body received</Exception_Text> 
                            </ChainedException>
                       </ns:SystemFault>
                  </detail>
             </soap-env:Fault>

       

      Is this content expected within the target url for any Enterprise Servic. I am not very confident because this is what we enter in the Destination in nwa.

       

       

      Is it possible for me to hold a NetMeeting, so that you can view the confiigurations I have made ?

       

      Thanks for all the help

       

      --- Brian

       

      Edited by: Brian Fernandes on Jul 14, 2008 8:02 PM

  • Re: TechnicalException: Deserializing WSDL stream, Invalid Response Code: (
    Yasar Pala
    Currently Being Moderated

    Hi Brian,

     

    The destination URL should not be the target adress of the endpoint from services registry.

     

    *In setting the destination, I have taken the url from Service Registry,

    On searching the service, in the endpoints tab, I have selected the Target Adress

     

    The destination URL should be the "Binding WSDL" of the Endpoint from the services registry.

     

    Regards,

     

    Yasar

    • Re: TechnicalException: Deserializing WSDL stream, Invalid Response Code: (
      Brian Fernandes
      Currently Being Moderated

      Hi Yasar,

       

      I tried using the Binding url

      and I received this error

      Caused by: com.sap.engine.services.webservices.espbase.query.exceptions.ObjectNotExistsException: {urn:sap-com:document:sap:soap:esr/document}ECC_SALESORDER009QR_Document 
      at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.findWSEndpoints(WSQueryImpl.java:195) 
      at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImpl.getEndpointConfigurations(DestinationsHelperImpl.java:966) 
      

       

      I havent found any help pertaining to this error on sdn.

       

      Are there any indications from the last line of the error

      service.server.query.discovery.DestinationsHelperImpl.getEndpointConfigurations  that the error is with the Destination ?

       

      Caused by: com.sap.esi.esp.service.server.query.discovery.ExtendedServiceException: com.sap.engine.services.webservices.espbase.query.exceptions.ObjectNotExistsException: ECC_SALESORDER009QR_Document&#xD;

           at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImpl.getEndpointConfigurations(DestinationsHelperImpl.java:977)&#xD;

           at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImpl.getWSDLUrl(DestinationsHelperImpl.java:401)&#xD;

           at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.getWSDLUrl(GenericServiceFactory.java:222)&#xD;

           at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:192)&#xD;

           at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:175)&#xD;

           at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:160)&#xD;

           at com.sap.caf.rt.connectivity.ws.WSExecuteManager.executeWS(WSExecuteManager.java:106)&#xD;

           ... 75 more&#xD;

      Caused by: com.sap.engine.services.webservices.espbase.query.exceptions.ObjectNotExistsException: ECC_SALESORDER009QR_Document&#xD;

           at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.findWSEndpoints(WSQueryImpl.java:195)&#xD;

           at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImpl.getEndpointConfigurations(DestinationsHelperImpl.java:966)&#xD;

           ... 81 more&#xD;

      </nestedStackTraceString><stackTraceString>com.sap.caf.rt.exception.CAFServiceException: com.sap.engine.services.webservices.espbase.query.exceptions.ObjectNotExistsException: ECC_SALESORDER009QR_Document&#xD;

           at com.sap.caf.rt.bol.da.remote.GenericOperationExecutor.execute(GenericOperationExecutor.java:56)&#xD;

           at com.wipro.get_sales_order.modeled.appsrv.ecc_salesorder009qr.ECC_SALESORDER009QRBean.SalesOrderERPBasicDataByElementsQueryResponse_In(ECC_SALESORDER009QRBean.java:34)&#xD;

           at com.wipro.get_sales_order.modeled.appsrv.ecc_salesorder009qr.ECC_SALESORDER009QRBeanImpl.getSalesOrder(ECC_SALESORDER009QRBeanImpl.java:44)&#xD;

           at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)&#xD;

           at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)&#xD;

           at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)&#xD;

           at java.lang.reflect.Method.invoke(Method.java:585)&#xD;

           at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)&#xD;

           at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(Ab

      1000

      stractInvocationContext.java:166)&#xD;

       

       

       

      Thanks

      --- Brian

       

      Edited by: Brian Fernandes on Jul 15, 2008 12:07 PM

       

      Edited by: Brian Fernandes on Jul 15, 2008 12:14 PM

  • Re: TechnicalException: Deserializing WSDL stream, Invalid Response Code: (
    Yasar Pala
    Currently Being Moderated

    Hi Brian,

     

    Are you able to test the exposed web service from NWDS CAF Perspective. Is it also throwing the same exception there?

     

    After redeploying your CAF Project, you have to  re-map the destination with the exposed web service on external service configuration.

     

    If you already performed this step, try to undeploy and redeploy the CAF project.

     

    Regards,

     

    Yasar

  • Re: TechnicalException: Deserializing WSDL stream, Invalid Response Code: (
    Yasar Pala
    Currently Being Moderated

    Hi Brian,

     

    from your Log I can say the error seems to be a problem about the endpoint of your enterprise service.

     

    Are you sure that the WSDL binding of the endpoint is still valid.

     

    If on the SOAMANAGER --> Web Service Administration of the backend, the endpoint for the enterprise service interface is re-configured (delete and re-create) the WSDL binding of the service interface will be changed. In that case your destination URL could be invalid if you configured it with the URL of the old WSDL binding.

     

    Could you please check on "Web Service Administrator" (you can start it with transaction SOAMANAGER) of the  backend system, if the endpoint WSDL binding is the same as the URL you configured your destination?

     

    Regards,

     

    Yasar

  • Re: TechnicalException: Deserializing WSDL stream, Invalid Response Code: (
    Yasar Pala
    Currently Being Moderated

    Hi Brian,

     

    If you have access to the backend system of your enterprise services,then execute the transaction "SOAMANAGER". This will open the "SOA Management" tool of the backend system on your web browser. On that select the tab "Business Administration". There clickon "Web Service Administration". In this part you can search for service interfaces for your enterprise service. Find the service interface, and create an endpoint for the service interface. This will generate a binding URL for the enterprise service, that you can use as WSDL URL for your destination. This will be then the valid configuration of your destination.

     

    Regards,

     

    Yasar

  • Re: TechnicalException: Deserializing WSDL stream, Invalid Response Code: (500)
    Swarnaprakash A
    Currently Being Moderated

    Hello Brian,

     

     

    Can you please tell me how did you resolve the issue? I am facing the similar issue.

     

    com.sap.engine.services.webservices.espbase.query.exceptions.TechnicalException: Deserializing WSDL stream http://aaaaa.xxxx.com:8002/sap/bc/srt/xip/sap/ecc_prodbillofmaterial001qr?sap-client=300&wsdl=1.1&mode=sap_wsdl failed

     

    Regards,

    Swarna Prakash.

Actions