Request Data Manager Data Protocol
The Request Data Manager data protocol lets you alter lvse requests during recording or playback.
The Request Data Manager data protocol lets you alter
VSErequests during recording or playback.
Data Protocolswindow, select Request Data Manager for a data protocol. When your recording is complete, the following window opens:
Fundamentally, this protocol lets you apply a list of actions against a request. You can add the following actions in the
ActionListsection of the window:
- CopyCopies a piece of data in the request to another part of the request.
- MoveMoves a piece of data in the request to another part of the request.
- DeleteDeletes (or clears) a piece of data from the request.
- KeepKeeps a piece of data in a request while deleting anything else in that group for the data value.
All actions can be applied to the request operation, any argument, attribute, or metadata entry, or the request body. For example, when virtualizing Java (which ends up with XML documents as arguments), you can move or copy the value of an argument into the request body, so other data protocols can process the argument.
Keepaction is most meaningful for arguments, attributes, and metadata. If you specifically keep a value from one of these three groups, any other value in that group that is not referenced by any action in the list for the data protocol is deleted. If you keep one argument, other arguments are removed unless they were the target of a move or copy. This technique is a good way to remove meaningless arguments.
Each action can also be limited to apply only to requests whose operations match a specified regular expression.
In the recording wizard or the model editor containing a Request Data Manager data protocol, add a
Deleteaction, or both. Select
argument/attribute/meta dataand specify a regular expression to match as the name. You must also change the cell that reads
matches. When the data protocol is run, it keeps or deletes all items in the argument, attribute, or metadata list with a name that matches the pattern. Leaving the operation matching pattern for an action empty affects all requests.
From this list of transactions, double-click a transaction to open a dialog showing the content of the transaction.
Use the Request Data Manager Data Protocol to set JMS and MQ Message Properties
After the recording is finished, use the
Request Data Managerwindow to add the targeted JMS message properties to the request arguments. The JMS message properties can be found under the request Meta Data with a
msg.prefix for standard JMS properties, such as correlation ID, and a
msg.props.prefix for custom message properties. To copy a property to the request arguments, select
argumentfrom the drop-down list:
WebSphere MQ works the same way.
To set the stateful session key instead of an argument, select
session keyfrom the drop-down instead.
You can use a single Request Data Manager data protocol to set any number of arguments and the session key simultaneously.