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. 

Adding the Repository  

  1. Right-click the suite, project, or Global Data Sources folder and choose Add New > Data Source.

  2. Choose Repository and click Finish.

The following table describes how to determine the location of the repository data source.

For this goal...Add the data source here...
Using the Data Repository tool to import data into this repository data sourceVirtualize action suite or SOAtest test suite that performs the import
Populating Virtualize message respondersVirtualize responder suite
Populating Virtualize SQL respondersVirtualize responder suite
Populating SOAtest messaging clientsSOAtest test suite
More than one of the above and/or use across multiple suites or projectsProject or global data source

Configuring the Repository

  1. Enter a name for the repository in the Name field. 
  2. You can configure which rows of the repository will be used for the suite or suites in the project. Enable the All option to allow access to all rows in the repository or enable the Range option and specify which rows should be accessible.
  3. Choose one of the following modes from the Connection Mode menu and configure the connection details accordingly:
    • Host/Port:
      1. Enter the Data Repository Server's Host and Port. You can also choose the embedded server or an existing remote server from the menu.
        • If you select the embedded server, the Port, Username, and Password fields will be grayed out. If you select a remote server, the Port, Username, and Password fields will be automatically populated, but these can be adjusted if necessary.
      2. Under Repository name, select or enter the name of the repository you want to use.
      3. Specify your credentials to access the data repository server (if required). To use SSL to connect to the server, enable Use SSL. Click Validate to verify the connection settings.
    • Connection String:
      1. Enter the MongoDB connection string. An example of a connection string that connects to a local server with SSL is shown below. See https://www.mongodb.com/docs/manual/reference/connection-string/ for more information about MongoDB connection strings. 

        MongoDB Connection String Example
        mongodb://localhost:2424/?tls=true&tlsAllowInvalidHostnames=true

        If an authentication database is specified in the connection string, you should use the /defaultauthdb component; only use the ?authsource=defaultauthdb option if credentials are specified in the connection string.

      2. Under Repository name, select or enter the name of the repository you want to use.
      3. Specify your credentials to access the data repository server (if required). You can specify credentials in either the connection string or in the Username and Password fields. If credentials are specified in both, those in the Username and Password fields will take precedence.
  4. Click Validate to verify the connection settings.
     
  5. Specify the data set to which this data source will connect. The data set specified does not need to exist at this point, but it 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.
  6. 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.


  • No labels