Layer7 API Management

Expand all | Collapse all

Non-SOAP XML

  • 1.  Non-SOAP XML

    Posted 05-29-2018 06:27 AM

    Hi Team,

     

    I have a requirement is to identify "submit" in root tag (Line no : 2), some times we get other values like Update/Delete etc. Based on that we are trying to route request to different target hosts.

     

    I have tried using Non-SOAP XML element verification but could not required result.

     

     

    <?xml version="1.0" encoding="UTF-8"?>
    <perform_erics_m5x_submit_rma result_name="">
    <parameters>
    </parameters>
    </perform_erics_m5x_submit_rma>



  • 2.  Re: Non-SOAP XML

    Posted 05-29-2018 07:05 PM

    Not sure what are you trying to achieve, are you trying to check if a particular tag exists in the xml ?

    If yes, xpath assertion or regular expression assertion should help.



  • 3.  Re: Non-SOAP XML

    Posted 12-17-2018 12:28 PM
      |   view attached

    Good morning,

     

    I believe you are looking to evaluate the base element perform_erics_m5x_submit_rma, perform_erics_m5x_update_rma, perform_erics_m5x_delete_rma, etc then based on the action make routing decisions. If this is the case, I've attached a very simple policy building on previous post that will extract out the submit, update, delete and assign it to a context variable ${elementRoute} which can be used in say a Map value to compare and assign another variable ${routingURL} to be used in your HTTP Routing assertion.

     

    Sincerely,

     

    Stephen Hughes

    Broadcom Support

    Attachment(s)