BPM, Workflow, and Case

 View Only
  • 1.  Call External Web Service Error

    Posted Tue March 21, 2023 10:16 AM

    Hello,

    We tried to call a web service in ibm baw. We have called this web service since February. But, now we got an error. The error message is 

    CWTBG0019E: Unexpected exception during execution. Exception information: 'An exception occurred in activity "Script Task" of "Service Flow" with name "WServer". Task instance id "Task.". Details: "javax.xml.stream.XMLStreamException: An invalid XML character (Unicode: 0x35) was found in the prolog of the document.".'.

    Is there anybody knows the solution of that error? Please help.



    ------------------------------
    YASEMİN ALADI
    ------------------------------


  • 2.  RE: Call External Web Service Error

    Posted Tue March 21, 2023 03:05 PM

    Hi Yasemin,

    What could have happened is that the code could have been pasted from a system or editor with a different encoding. Look through whatever is in the server script called "Script Task" in the WServer service flow. Unicode: 0x35 is the digit 5, so I would also look to see if this is showing up in any unexpected area of the XML document, perhaps in the schema declaration.



    ------------------------------
    Rex Townsend
    Salient Process
    ------------------------------



  • 3.  RE: Call External Web Service Error

    Posted Tue March 21, 2023 03:26 PM

    Hi Rex,

    Web service is our customer web service and our customer states there is no change in web service. But on february, web service call is successful. I did not see any detailed log in bpm log. Can we change log level or detailed log? Thanks for your help.



    ------------------------------
    YASEMİN ALADI
    ------------------------------



  • 4.  RE: Call External Web Service Error

    IBM Champion
    Posted Wed March 22, 2023 07:42 AM

    Hi Yasemin,

    Sounds like it's a problem from the web service, not from BAW.

    Have you tried calling it from SOAP? 

    Regards 



    ------------------------------
    Thong Huynh
    Sydney NSW
    ------------------------------



  • 5.  RE: Call External Web Service Error

    Posted Wed March 22, 2023 07:46 AM

    Hello,

    I called from SOAP and returned success and data. So, I think the problem is not from web service.



    ------------------------------
    YASEMİN ALADI
    ------------------------------



  • 6.  RE: Call External Web Service Error

    IBM Champion
    Posted Wed March 22, 2023 08:07 AM

    Hi Yasemin,

    Then go and identify the differences between SOAP and BAW when BAW makes the call. See if you can find what could have tampered with the XML in your BAW project.

    Regards 



    ------------------------------
    Thong Huynh
    Sydney NSW
    ------------------------------



  • 7.  RE: Call External Web Service Error

    Posted Wed March 22, 2023 08:13 AM

    Hello,

    How can I identify BAW request? I created external service and called it.



    ------------------------------
    YASEMİN ALADI
    ------------------------------



  • 8.  RE: Call External Web Service Error

    IBM Champion
    Posted Wed March 22, 2023 09:38 AM

    Hi Yasemin,

    Maybe it would be more helpful if you can describe in more detail with screenshots how you did it?

    Cheers

     



    ------------------------------
    Thong Huynh
    Sydney NSW
    ------------------------------



  • 9.  RE: Call External Web Service Error

    Posted Thu April 13, 2023 09:11 AM

    Hi Yasemin,

    The error indicates there are invalid characters (not allowed in xml documents) in response SOAP message.  This response was sent by remote service.   The investigation should be done from service provider side.

    Can you please investigate in this regard please ?

    We have Other Cases where the issue has occurred where SAP is WS provider trying to contact other WS provider, are you using SAP as WS provider, and is it a JEE application ?

    and

    This error and it's variants (different Unicode value) all stem from one of two reasons.

    1. You are setting an invalid header or header value
    2. You are not sending a complete SOAP message

    The prolog refers to the headers of the SOAP message. When the headers are parsed, normally on a reply but possibly on a request, if there is an error or bad data, this exception is thrown. https://www.w3.org/TR/xml/#charsets. Thus this S is not expected or the data after is not set.

    If you look at the http://en.wikipedia.org/wiki/List_of_HTTP_header_fields , you can see few use a capital S:

    • Server
    • If-Modified-Since
    • If-Unmodified-Since
    • Set-Cookie
    • Status
    • Strict-Transport-Security
    • X-XSS-Protection
    • Content-Security-Policy

    Note that not all are acceptable for all messages. If you set one of these, check to make sure the spelling is valid, it is valid for this message, and the content with it is valid. In one case, there was a POST header that was valid, however, there was nothing past the headers in the SOAP message due to a code error. This threw the same exception on the P in POST since it could not locate the data to post.

    Therefore, make sure your headers are well formed, correctly spelled, valid, and the message is complete.



    ------------------------------
    Sriram Bharadwaj Sampathkumar
    ------------------------------