Integration

Get Involved. Join the Conversation.

Topic

    VR
    External Service BIP WS
    Topic posted September 13, 2019 by VRBlue Ribbon: 750+ Points, tagged Cloud, ERP Cloud, Integration, Orchestration, PaaS, SOAP, xml 
    138 Views, 19 Comments
    Title:
    External Service BIP WS
    Content:

    External webservice for BIP report fetches only part of the report but entire response is fetched from soap UI.

    <COUN  ******* Payload Truncated ******* is received in the response for part of the report.

    The data size is around 3MB from SOAP UI with around 8000 records. Kindly let me know why the data fetch is partial in OIC. I have provided datachunk size as -1.

    Comment

     

    • Hemanth Lakkaraju

      <COUN  ******* Payload Truncated ******* is received in the response for part of the report.

      Where do you see this? in OIC Tracking UI or Logs? Then it may be your assumption that the service is returning part of report.

      • VR

        Hi Hemanth, I see it in the OIC tracking Payload. The stage file write and read actions after this also display truncated data. 

        • Hemanth Lakkaraju

          Thanks! I think, it is an unnecessary panic. The display is truncating the payload if it exceeds certain size, but in actual it should work fine.

          • VR

            Hemanth.. I would not have asked the query if it was only in the display and entire data set was available in the following stage file actions. But I do not see it.

            If I set 1000000 in the chunk download size field instead of -1, I was able to get that many characters in the response. So is there any configuration which limits to only 512KB or anything of that sort? 

             

            “Payload exceeds the configuration size, hence not logging the payload even if tracing is enabled.”

             

            Solution

            The solution is to install the following patch from the console:

            Patch: 18.3.5.180918.1047-15760

            ACTION PLAN:
            1) Login to the Oracle Integration Classic Service Console and check to see if you have "One or more patches are available" to install for your OIC-C service instance.
            2) Click on the link and confirm if Patch "18.3.5.180918.1047-15760" is listed
            3) First run the PreCheck, and if successful, install the patch.
            4) Test the integration to see if the payload is shown with trace logging.

            This patch will allow the first 512 KB of the payload to be shown.

            If your OIC-C version is greater than the 18.3.5, then you already have this feature.

             

            • Hemanth Lakkaraju

               would not have asked the query if it was only in the display and entire data set was available in the following stage file actions.

              Can you explain how exactly you determined that is is not available for following stage file actions?

              If I set 1000000 in the chunk download size field instead of -1, I was able to get that many characters in the response.

              Are you sure the 1000000 number of characters are having a size > 512KB?

              • VR

                Hemanth, again these are my queries and looking for answers..  I am not providing a solution or reaching conclusions..

                I have attached screenshots of the process and truncated payload message in the conversations below. Just trying to find out if its a valid issue and anything looks amiss with the configurations I have done.. 

                 

                 

                • Hemanth Lakkaraju

                  I'm trying to validate your question first to tell you answers.

                  Kindly let me know why the data fetch is partial in OIC

                  There is NO partial fetch in OIC unless your query has a filter criteria. I'm 100% sure for the same request in SoapUI whatever response you see, the same will be seen in OIC too. The truncated payload in tracking screen is expected, as I told if it exceeds certain size - This is needed to avoid *frequent* rotation of logs and make sure maximum instance data is retained in the history.

    • Prateek Parasar

      We use the same service from another third party and never seen an issue with this

    • Monish Munot

      We were able to extract full, large data in OIC and did not see any issue. Can you share the request payload xml from logs and one you are using in SOAP UI?