Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2023.1

...

  1. Right-click the VirtualAssets project and choose Add New> New > Virtual Asset (.pva) file.
  2. Specify a file name , then and click Next.
  3. Select Choose Recorded Database Queries, then  and click Next.
  4. Complete the Recorded Database Queries wizard page as follows:
    1. For Server, select the Virtualize Server where the database recording file is located.
    2. For Databases, select the appropriate data source from the list of JDBC URLs. This list is populated based on the available recordings; the available URLs will direct Virtualize to the appropriate set of files that captured the recording.
    3. For Responder Data Source Type, select enable Data Repository.
    4. (Optional) If you want date fields automatically replaced with wildcards, enable Wildcard Date Fields. If this option is enabled and a query takes a date as a parameter, Virtualize won’t require the dates to match exactly. We recommend enabling this option when a query takes the current time or a changing data as input, but you want a consistent response from Virtualize (ignoring changes in the date field).
    5. Click Next.
  5. In the Parasoft Data Repository Settings page, specify which data repository should store the data used to parameterize the SQL Responder, then click Next.
    • From the Server box, specify which server you want to connect to (either the embedded server or a remote server).  If 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).
    • 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.
    • When defining a repository connection, you can check the connection by clicking Validate.

  6. Click Finish.

...

  • A SQL Responder with parameterized query templates, result sets, and parameters will be added.
  • A SQL data set will be added to the SQL Data Sets area of the selected repository. If this repository did not already exist, it will be created. Applicable record types will be added to the repository.
  • A repository data source will be created for each added data set and the SQL Responder will be configured to use this data source.
  • A .pva will be deployed to the local Virtualize server  at at /virtualDb.

    Info
    titleConfiguring Deployment Settings

    For details on deployment settings, see Configuring Individual Virtual Asset Deployment Settings.

...

  1. Choose the Recorded Database Queries option in one of the available creation wizards.

    For details on accessing the wizards, see Adding Projects, Virtual Assets, and Responder Suites.
  2. Complete the Recorded Database Queries wizard page as follows:
    1. For Server, select choose the Virtualize Server where the database recording file is located.
    2. For Databases, select choose the appropriate data source from the list of JDBC URLs. This list is populated based on the available recordings; the available URLs will direct Virtualize to the appropriate set of files that captured the recording.
    3. For Responder Data Source Type, select enable .csv files.
    4. (Optional) If you want date fields automatically replaced with wildcards, enable Wildcard Date Fields. If this option is enabled and a query takes a date as a parameter, Virtualize won’t require the dates to match exactly. We recommend enabling this option when a query takes the current time or a changing data as input, but you want a consistent response from Virtualize (ignoring changes in the date field).
    5. Click Finish.

...

  • A SQL Responder that is configured with the appropriate JDBC URL, SQL Template, and Parameter Criteria.
  • One or more ResultSet files stored within the database_recorded_data folder inside the VirtualAssets Project.
  • A .pva will be deployed to the local Virtualize server  at at /virtualDb.
Info
titleConfiguring Deployment Settings

For details on deployment settings, see Configuring Individual Virtual Asset Deployment Settings.

...