Integrationpublic

Integration

Get Involved. Join the Conversation.

This is a public Forum  public

Topic

    Mohana Gopal Selvam
    Internal Server ErrorAnswered
    Topic posted June 16, 2019 by Mohana Gopal SelvamSilver Crown: 22,500+ Points, tagged REST, Web Services 
    322 Views, 23 Comments
    Title:
    Internal Server Error
    Content:

    I have tried to convert the WSDL API into Rest API since OIC VBCS does not support WSDL API. We have followed the steps as mentioned in the forum https://cloudcustomerconnect.oracle.com/posts/18fc9cc15f. Created 2 connection successfully. Created one integration successfully.  But when I hit the Rest API URL, we got the Internal Server Error.

    What might be the cause?

    Thanks,

    Mohan

    Best Comment

    Hemanth Lakkaraju

    1. WSDL should always point to correct endpoint. You may want to check with service owners and get the right wsdl url which will have right endpoint.

    2. Use upload wsdl option by modifying the endpoint. Open the wsdl url in browser. View source and copy the wsdl contents to a file. Update the endpoint to right url. Save the file and use upload option in connection.

    Comment

     

    • Hemanth Lakkaraju

      What is the exact error? From where did you hit the rest API - from VBCS or any tool like postman? 

      Can you provide a screenshot of tracking page of REST flow?

    • Mohana Gopal Selvam

      When I tried the Rest API URL in browser, I got the Internal Server Error. When I tried the same in Postman, I got the 415 unsupported error.

      Thanks,

      Mohan

    • Mohana Gopal Selvam

      Hi Hemanth,

      Please find the error screenshots.

      Thanks,

      Mohan

    • Mohana Gopal Selvam

      Browser Error

      • Hemanth Lakkaraju

        I assume the endpointURL in browser is same as the one in postman. This is error from SOAP Endpoint invocation saying URL not found. Make sure you use right soap endpoint.

    • Mohana Gopal Selvam

      Now received this error in PostMan

       

      { "type" : "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.5.1", "title" : "Internal Server Error", "detail" : "Internal server error. Please contact oracle support for details.", "o:errorCode" : "500", "o:errorDetails" : [ { "type" : "UnMappedFault:execute", "instance" : "\n \n  \n  \n  \n  1 \n  \n  \n \n\n]]>", "title" : "javax.xml.ws.WebServiceException: Error while dispatching SOAP message to the endpoint http://xxxx.Service/:javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Bad response: 404 Not Found from url http://***.Service/\n===== reqeust ========\nContent-Type:text/xml; charset=UTF-8\nContent-Length:658\nSOAPAction:\"\"\n 1 \n:Application Error", "o:errorPath" : "\n  RouteNode1 \n  response-pipeline \n\n]]>", "o:errorCode" : "OSB-380001" } ] }

      • Hemanth Lakkaraju

        This is same as the one from browser call!

        Error while dispatching SOAP message to the endpoint http://xxxx.Service/:javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Bad response: 404 Not Found from url http://***.Service

        The endpoint being called, does not exist. 

    • Mohana Gopal Selvam

      Hi Hemanth,

      When I click the settings on my Integration, I got the below as End Point URL (let say A).

      https://domain.integration.ocp.oraclecloud.com/ic/api/integration/v1/flows/rest/INTEGRATION/1.0/metadata

      When I put the above URL in the browser, I got the message like End Point URL (Let Say B), Swagger, How To Run & Arguments detail.

      If I used, End Point URL A in postman, I got the success message and the response same as the browser detail (End Point URL, Swagger, How To Run & Arguments detail).

      If I used, End Point URL B in postman, I got the 500 Internal server error. 

      Thanks,

      Mohan

       

      • Hemanth Lakkaraju

        1. Are you replacing the query parameter values in endpointURL B before hitting in postman or browser? The URL shown there is just a place holder of actual endpoint.

        2. I suspect the integration is running fine and there is a soap endpoint within it which is failing with bad url. You can verify this in OIC --> Monitoring --> Tracking. Make sure the SOAP Endpoint used in soap connection within the integration is a valid one.

    • Mohana Gopal Selvam

      1. Yes. I replaced the value in Browser & as well as in Postman.

      2. Can you tell me, where we need to define the endpoint url of my SOAP Connection?

      Thanks,

      Mohan

    • Mohana Gopal Selvam

      Hi Hemanth,

      I have configured the SOAP connection with proper WSDL. Where we need to define the endpoint. Can you elaborate it?

      Thanks,

      Mohan

    • Mohana Gopal Selvam

      Hi Hemanth,

      Thanks for your info. If I modify the endpoint in SoapUI, I get the result. 

      Is there any way to modify the endpoint URL in ICS itself. 

      Thanks,

      Mohan

    • Mohana Gopal Selvam

      Hi Hemanth,

      I hope you mentioned the below steps

      Go to the Integrations and check your INTEGRATION.

      See the SOAP Connection used as an invoke in above integration.

      Update the wsdl provided in soap connection with correct endpoint and re-upload or update the connection.

      Deactivate and reactivate the integration.

      In my situation, WSDL is URL, which is received from the customer. Where can I edit the endpoint URL in ICS? 

      Thanks,

      Mohan

      • Hemanth Lakkaraju

        1. WSDL should always point to correct endpoint. You may want to check with service owners and get the right wsdl url which will have right endpoint.

        2. Use upload wsdl option by modifying the endpoint. Open the wsdl url in browser. View source and copy the wsdl contents to a file. Update the endpoint to right url. Save the file and use upload option in connection.

    • Mohana Gopal Selvam

      Hi Hemanth,

      Thanks for your support.

      1. Some customer using the common WSDL, we have to modify the end point url based on the instance(DEV / TEST / PROD)

      2. I have manually modified the end point URL and it is working fine.

      Thanks,

      Mohan

    • Mohana Gopal Selvam

      Modifying the Endpoint URL dynamically, refer the below link.

      https://docs.oracle.com/en/cloud/paas/integration-cloud/soap-adapter/oracle-soap-adapter-concepts.html#GUID-108FBA5E-9509-4E68-83DE-AA6A480D6938__SUPPORTFORDYNAMICENDPOINTS-BB0A9D2D

      Thanks,

      Mohan

     

    community forum