A repository data source is a "wrapper" for the repository data source that allows you to consume it in Parasoft messaging tools—in the same manner as you would consume data from an Excel data sheet, CSV file, or other supported data source. For more details about repository data sources, see “Repository Data Source”, page 617.
To create a repository data source:
1. Do one of the following:
|For this goal...||Add the data source here...|
|Using the Data Repository tool to import data into this repository data source||Virtualize action suite or SOAtest test suite that performs the import|
|Populating Virtualize message responders||Virtualize responder suite|
|Populating Virtualize SQL responders||Virtualize responder suite|
|Populating SOAtest messaging clients||SOAtest test suite|
|More than one of the above and/or use across multiple suites or projects||Project or global data source|
2. Select Repository, then click Finish.
Specify the repository to which this data source will connect.
a. From the Server box, specify which server you want to connect to (you can select the embedded server or an existing remote server—or you can specify a new server to be created). If you select the embedded server, the Port, User, and Password fields will be grayed out. If you select a remote server, the Port, User, and Password fields will be automatically populated (these can be adjusted if needed).
b. Under Repository name, select or enter the name of the repository you want to use. If you enter the name of a new repository, that repository will be created.
Specify the data set to which this data source will connect. Since you’re importing data, it’s okay to specify a data set that does not yet exist. However, that data set will need to exist (and contain data) by the time you start applying tools to use this data source.
If you are creating a data source for use in Virtualize’s SQL Responder tool, be sure to change the data setting from Data Set to SQL Data Set:
If the data source’s Enable caching option is disabled (the default), updates to the repository data will be immediately reflected in any deployed virtual assets which use that data. If you enable caching, virtual assets will need to be redeployed in order for the repository data changes to take effect at runtime. Enabling caching for load testing is recommended for performance optimization.