This topic explains how to configure and apply the JSON Data Bank tool in SOAtest and Virtualize. This tool extracts JSON values (e.g., from a request or response message) so that they can be used in another place. Data can also be sent to a Writable Data Source and accessed in the Extension Tool or it can be sent to variables for easy reuse across the test, Responder, or Action suite.
The JSON Data Bank tool was re-implemented in version 9.7. The previous implementations are deprecated: any existing tools will continue to work, but all new JSON Data Banks you add will use the new implementation.
This topic focuses on the current JSON Data Bank implementation.
This tool enables you to extract certain JSON values (e.g., from a request or response message) so that they can be used in another place. The JSON Data Bank tool can be chained to any other tool that outputs JSON. It can extract any information from the JSON and make that information available for later use. For example, you can extract a value from an incoming request and use it to populate an element of the response to be sent when that request is received. You can configure JSON Data Banks automatically when using wizards to create virtual assets from traffic. In addition, you can use the "Use Data Source Wizard" to extract a value and use it as a parameterized value in a response. For Message Responders, you can extract values from the incoming request (body or header); for other tools (e.g., tools used in action suites), you can extract values from another tool in the suite. Another option is to manually add a JSON Data Bank tool (as an output to an existing tool) that extracts the desired data, then configure other tools to use the extracted data.
To use the "Use Data Source Wizard" wizard to configure a JSON Data Bank:
(Not applicable for use with Message Responders) Ensure that you have a test suite or action set with at least two tools.
For Message Responders, select the incoming request message that you want to extract a value from, then specify whether you want to extract values from the message body or message header.Under Expected Message, indicate what element(s) you want to extract, then click Add. The right panel lists the values you have configured for extraction and shows the name of the data source column where each value will be stored (if you keep the default setting).
If you later want to specify additional options (e.g., if you want to change the name of the column used to store the value, you want the value saved to a writable data source, or you want the value stored to an existing variable) —or if you want to modify the referenced element—then select the appropriate element in table on the right and click Modify. Next, configure the options as needed, then click OK.
For details on how to use this dialog to configure additional options, see JSON Selector Reference.
You can also manually chain the JSON Data Bank tool to a tool within the test, Responder, or Action suite. To configure the JSON Data Bank as a chained tool, complete the following:(Not applicable for use with Message Responders)
Ensure that you have a test suite or action set with at least two tools.
Right-click the node for the tool associated with the data you want to extract(e.g., if you want to extract a value from an incoming request or outgoing response, choose the Message Responder that handles those messages), then choose Add Output.
In the Add Output wizard, indicate where you want to extract the value from(e.g., Incoming Request, Transport Header, Incoming Attachment, Outgoing Response, etc), select JSON Data Bank from the list of tools, then click the Finish button. A JSON Data Bank node displays below the tool.
Use the available controls to specify what element you want to extract. To extract an element, select a value from the JSON tree and click the Extract Element button. The value you added displays in the Selected Element list with a Data Source Column name containing the name of the tool the value came from, as well as the extracted value.
The left panel displays the expected JSON response used to create a template from which you can select elements. If JSON Data Bank receives a valid JSON message (e.g., from traffic or as defined in the client tool it is attached to), this panel will be populated automatically. Alternatively, you can copy a sample message into the Literal or Tree tabs. Note that the expected JSON does not get saved by default; if you want to save it, enable the Save Expected JSON option.
If you later want to modify the element referenced by the extraction, click Modify, then modify it as desired. See JSON Selector Reference for details.
After adding and/or modifying the extraction, configure the tool that you want to use the extracted data.
Set the value to Parameterized, and choose the appropriate item from the drop-down. For example, if you saved the value to the "title" data source column, you would select it as follows.
The following options can be configured in the lower portion of the JSON Data Bank tool configuration panel.
XPath: Displays the selected XPath. See JSON Selector Reference for details.
By default, empty and missing elements will not be extracted. This could impact the integrity of the JSON response for use in a Writable Data Source.
For instance, assume you have the following JSON:
Also assume that you want to create an extraction for all
'e' elements. To do this, select the first element, then click Extract Element.
Next, select the new extraction, then click Modify.
In the Modify dialog, change the XPath to extract from
This will extract all three text nodes.
Next, click Data source column and select a writable data source column. When the Data Bank is executed, the writable data source will only contain two rows because the second element is missing text:
ROW 1 = 5
ROW 2 = 6
If you want to write the empty value, change the XPath from
/root/e and ensure that Content Only is enabled.
This way, all three elements are extracted, including their content. You can optionally enable the Extract empty element as option to change the value extracted for the empty value. The Data Bank will now append the empty value to the writable data source:
ROW 1 = 5
ROW 2 =
ROW 3 = 6