Service Virtualization

  • Private Community

  • 1.  Suggestions require for Virtual service

    Posted Jun 20, 2017 12:28 PM

    Given Url ;- https://***.com/cart/activity/mobileBaggageProcess.action

     

    Given Request 1 ;- fdb73003-57a1-4353-89d8-fd126792fc93

    Reponse1 ;- json format 

     

    Given Request 2 ;- 3c0875f3-f264-4afa-9c0c-396a7d65b68f

    Reponse2 ;- json format 

     

     

     

    Cachekeysuffix:- fdb73003-57a1-4353-89d8-fd126792fc93

    Reponses are well formatted.

     

    for the above Rest Api Request do I need to frame the request doc as

    Req 1

    GET /cart/activity/mobileBaggageProcess.action
    cacheKeySuffix:fdb73003-57a1-4353-89d8-fd126792fc93

    Req 2

    GET /cart/activity/mobileBaggageProcess.action
    cacheKeySuffix:3c0875f3-f264-4afa-9c0c-396a7d65b68f

     

    do I need to consider the fdb73003-57a1-4353-89d8-fd126792fc93 as header or body or argument

     

    when used as argument its not working

    how this can be implemented .Any suggestions please

    Attachment(s)

    zip
    request2.json.zip   178 B 1 version
    zip
    Response2.json.zip   369 B 1 version
    zip
    response1.json.zip   465 B 1 version
    zip
    request1.json.zip   178 B 1 version


  • 2.  Re: Suggestions require for Virtual service

    Broadcom Employee
    Posted Jun 20, 2017 12:48 PM

    Hi Sri, Please open a support ticket and we can help you with your issue in a WebEx.



  • 3.  Re: Suggestions require for Virtual service
    Best Answer

    Broadcom Employee
    Posted Jun 20, 2017 03:16 PM

    Sri opened ticket 00775705 and support helped him resolve the issue.

     

    cacheKeySuffix:3c0875f3-f264-4afa-9c0c-396a7d65b68f is in the Meta data, support recommended to use "Request Data Manager" DPH and Move/Copy the cacheKeySuffix from Meta data to Request Data Argument which resolved the issue.