Versions Compared

Key

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

...

  1. Choose the Traffic> Generate Parameterized Messages option in one of the available creation wizards. See Adding Projects, Virtual Assets, and Responder Suites for basic information about adding responders.  

  2. Specify the following information in the Traffic wizard:
    1. Specify the location of the traffic file.
    2. Change the character encoding if needed
    3. (Optional) Specify the service definition file. Providing a service definition helps Virtualize create better message groupings and data source correlations.
    4. If you want to populate the wizard with a previous group of settings saved in a template, enter the location of that template. See Using Configuration Templates to Reuse and Share Wizard Settings 1- Virtualize for details about creating and using templates in Virtualize.

  3. Click Next and specify a data repository for storing the data in the Parasoft Data Repository Settings screen:
    • In the Server field, specify whether you want to connect to a remote server or the embedded server. If you select a remote server, the Port, User, and Password fields will be automatically populated and can be adjusted as needed.
    • If you choose Embedded Server, the PortUser, and Password fields will be grayed out. 

    • In the Repository name field, 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

  4. Click Next and configure the settings in the Message Format and Grouping Strategy screen.

    1. Verify that Request message format and Response message format are set to the correct format. Virtualize will attempt to identify the message format of the request and response based on the first message in the traffic file. All requests in a single traffic file are expected to have one format, and all responses in the same file are expected to have one format. The request format may be different than the response format. If the message format is not detected, Plain Text will be selected.

    2. Conversion options are available for some formats, such as EDI or custom formats. Click the Conversion Options button and make the desired changes. 

    3. Choose a message grouping option. See Message Grouping Options for details.

    4. If you specified a service definition or template file, you can enable the Constrain option in the Message Group Creation Options section. If this option is enabled, only the message groups defined in either the template or service definition file will be grouped. All other messages will be ignored. If this option is disabled, Virtualize will group all messages that appear in the traffic file. If a service definition and template file are provided and this option is enabled, groupings will be constrained according to the template file prior to being constrained by the service definition. As a result, a message will be ignored if it is defined in the service definition but not in the template file. The Constrain option is enabled by default.
  5. Click Next and review the information about the operations and messages in the Message Grouping Review screen. See Message Grouping Review Screen for details.
  6. Click Next. If the Autoconfig option for each group was enabled, the Data Reuse screen will open and you can skip the next step.
  7. If the Autoconfig option was disabled in the previous screen, you will need to manually configure the request matching options in the Request Matching screen. See Configuring Request Mapping Options
  8. Configure how the imported traffic should be reused or how it should affect existing data in the Data Reuse screen. See Configuring Data Reuse Options for details.  
  9. Click Next and specify any additional configurations in the Final Options screen:
  10. Click Finish.

...

The columns in in the Message Grouping Review screen are based on the grouping strategy applied. Each table row represents the criteria for defining a group. One group will be generated for each table row. One responder will be generated for each group. Complete information for using this screen is in the Customizing Grouping Criteria Virtualize section. 

The correlation criteria will be processed in the order in which they appear in the table (from top to bottom). For details on how these groupings were created, see Understanding Heuristics for Grouping by Operation - Type.

...

The defined record identity is used to determine which data is new and which new records match existing records. If it has not already been specified for this data set, the identity can be added/modified in the data tree. The tree indicates identity fields with green arrow icons. Existing data sets are noted with annotations. Complete details about configuring reuse are discussed in the Configuring Data Reuse and Updating 1Virtualize chapter. 

You can control how new data from the traffic file will extend and/or update existing repository data sets. 

...

If the .pva was created in the Virtual Asset folder, the virtual assets is automatically deployed to the local Virtualize server as the wizard completes. Otherwise, you can deploy it to local or remote servers whenever you are ready. For a more detailed discussion of deployment procedures and options, see Deploying Virtual Assets - Overview Virtualize.

Customizing the Virtual Assets

...

The following topics provide additional details that will help you complete the wizard:

Video Tutorial: Creating Virtual Assets from Traffic Recorded with a Message Proxy

...