...

The XML Data Bank tool enables you to extract certain XML values (e.g., from a request or response message) so that they can be used in another place. The XML Data Bank tool can be chained to any other tool that outputs XML. It can extract any information from the XML and make that information available for later use.

For example, you can configure a test suite that tests a bank’s Web service transactions. Test 1 of that test suite can log on to the service using a User ID, then the SOAP response would return a session ID back to Test 1. Test 2 of that test suite can be configured to use the session ID from Test 1 to perform transactions. You can configure any of the tests in a test suite to use SOAP response parameters as SOAP request parameters.

Users typically configure an XML Data Bank by accessing the "Use Data SourceWizard" while parameterizing a value in a tool such as the SOAP Client or Messaging Client tool. This provides a quick, intuitive, and largely automated way to extract data from one tool and use it another. You simply go to the tool where you want to insert extracted data, then use a wizard to specify what data (e.g., from what tool) you want to extract. This is the usage model demonstrated in the Storing Results to Be Used in Subsequent Tests tutorial. This same method can be used to extract data that is used to set a variable. Alternatively, you can manually configure an XML Data Bank tool to extract data from one tool, then manually configure other tools to use the extracted values.

For example, you can configure a test suite that tests a bank’s Web service transactions. Test 1 of that test suite can log on to the service using a User ID, then the SOAP response would return a session ID back to Test 1. Test 2 of that test suite can be configured to use the session ID from Test 1 to perform transactions. You can configure any of the tests in a test suite to use SOAP response parameters as SOAP request parameters.

Users typically configure an XML Data Bank by accessing the "Use Data SourceWizard" while parameterizing a value in a tool such as the SOAP Client or Messaging Client tool. This provides a quick, intuitive, and largely automated way to extract data from one tool and use it another. You simply go to the tool where you want to insert extracted data, then use a wizard to specify what data (e.g., from what tool) you want to extract. This is the usage model demonstrated in the Storing Results to Be Used in Subsequent Tests tutorial. This same method can be used to extract data that is used to set a variable. Alternatively, you can manually configure an XML Data Bank tool to extract data from one tool, then manually configure other tools to use the extracted values.

You can also extract a value from an incoming request in Virtualize, for example, and use it to populate an element of the response to be sent when that request is received. You can configure XML 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 an XML Data Bank tool (as an output to an existing tool) that extracts the desired data, then configure other tools to use the extracted data.

For example, you can You can also extract a value from an incoming request in Virtualize, for example, and use it to populate an element of the response to be sent when that request is received. You can configure XML 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 an XML Data Bank tool (as an output to an existing tool) that extracts the desired data, then configure other tools to use the extracted data.

...

Configuring XML Data Bank Using the Data Source Wizard

Anchor
Configuring XML Data Bank Using the Data Source Wizard Configuring XML Data Bank Using the Data Source Wizard

...

• Custom column name: Specifies the name of the data source column in which to store the value. Values are stored in an internal data source unless you specify otherwise (e.g., if you select Writable data source column or Variable). This is the name you will use to reference the value in other places. For example, if it is stored in a data source column named My Value, you would choose My Value as the parameterized value. You could also reference it as ${My Value} in literal or multiple response views.

  
  
  
  

• Writable data source column: Enables storing the value(s) in a writable data source column (see Configuring a Writable Data Source for details). This allows you to store an array of values within a single column. Other tools can then iterate over the stored values.

• Write to all columns that match: Enables storing the value(s) in all columns whose name contains the specified string. When extracting multiple values from a message, the values will be written in a single row across all columns that match, with each value put into a different column. If more values are extracted than there are columns that match, some values will not be written since there are fewer matching columns than values. In contrast, if you pick a single writable data source column (the above option), then the values will be written down the column across multiple rows.

• Variable: Enables saving the value in the specified variable so that it can be reused across the current Responder, Action, or test suite. The variable must already be added to the current suite as described in Defining Variables in SOAtest or Defining Variables in Virtualize.Defining Variables in SOAtest.Defining Variables in Virtualize. Any values set in this manner will override any local variable values specified in the Responder, Action, or test suite properties panel.

...