Header validation for incoming request and route the traffic to sub transaction

[vikramreddy anthireddygari]

Hello 

I have a virtual service with two transactions (two different endpoints).

I have a requirement to validate the header for incoming requests and route to the correct end point and also if the header missing virtual service need to throw a error . The challenge here is that each transaction has a different set of header validations, and header validation is a must.

Transaction 1, below are the sample headers that need to be validated

gatewayid

duplicatecheck

key

Transaction 2-- only gatewayid id need to be validated and route to associated transaction.

Any suggestion on this scenario ?

[Danny Saro]

Hi Vikram,

The exact flow that you need to implement is not completely clear to me.
There cannot be something like 1 virtual service with 2 endpoints. Maybe
you can document with a high-level sequence diagram? An important
requirement will be whether or not the second endpoint (the one you need to
route the transaction to in case of a specific gatewayid) is also virtual
in your test environment?

Anyways, an initial part of the solution will be that the required header
values that are needed for differentiating between the 2 different
transactions are moved from metadata arguments to request arguments within
the lisa_vse_request object. That can be done using the RDM DPH (Request
Data Manager Data Protocol Handler). Add this DPH to the Listen step in and
add the necessary move-actions.

If you are not familiar with configuring the RDM DPH then try to create the
initial VSM and VSI with a couple of request-response pairs. In the
workstation recording wizard you can add the RDM DPH and graphically
construct the move-actions.

Cheers,

Danny Saro

Client Services Consultant

Broadcom Software


-------------------------------------------------

--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.