Service Virtualization

Expand all | Collapse all

Copybook Parsing Error

  • 1.  Copybook Parsing Error

    Posted 12-17-2015 10:21 AM

    Hi ,

     

    I am getting the same error while using Copybook Data Protocol .I had created Copybook bundle from Dev test portal . Workstation log getting error message "[AWT-EventQueue-0] WARN  com.itko.util.copybook.PayloadProcessor - Couldn't find a payload mapping, "

     

     

     

    <copybook-payload>

      <rawHeader>30303137373030303433303031393930202020202020202020202020202020202020343330302020202020</rawHeader>

    </copybook-payload>

     

     

    Regards,

    -Ankush



  • 2.  Re: Copybook Parsing Error

    Posted 12-17-2015 10:27 AM

    This message means that the request message couldn't be matched to a copybook definition file.  If you up the logging level from INFO to DEBUG in logging.properties you will get more information in your Workstation log file regarding the parsing of the message.  If you need even more information TRACE will churn out a lot of information and show you down to a field level how things are being parsed.  There is likely either a mistake in your payload mapping file or the req/rsp messages you've specified don't align to a specific copybook definition you have available.



  • 3.  Re: Copybook Parsing Error

    Posted 12-17-2015 10:49 PM

    Hi Ankush,

     

    Adding to Josh point, i will suggest, go bit by bit process,

     

    Like first try to parse your request only by proving payload mapping file with single payload details like below

     

    Payloads

          Payload name=operation-req type=request key=abcdxyz

          Section

                Copybookfile

     

     

    Your key is important and it should be available in the request.

     

    This error sometime comes due to if there is no match in key properly.

     

    If still you get error, might b try to check if your copybook file parsing into Xml is happening properly.



  • 4.  Re: Copybook Parsing Error

    Posted 04-09-2018 03:08 PM

    @ AnkushSharma62132828 , how did you managed to rectify this issue?