Page tree

Versions Compared


  • 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 the following chapters for additional details: Adding a New .tst File to an Existing Project and Adding a New Test Suite.

    Adding Projects, Virtual Assets, and Responder Suites.

  2. Specify the following information in the Traffic wizard and click Next:
    1. Specify the location of the traffic file.
    2. Change the character encoding if needed
    3. 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 - SOAtest for details about creating and using templates in SOAtest and Using Configuration Templates to Reuse and Share Wizard Settings - Virtualize1 for details about creating and using templates in Virtualize.

  3. In the Parasoft Data Repository Settings page, specify which data repository should store the data used to parameterize the test clients or message responders and click Next

    • In the Server field, specify which server you want to connect to (either the embedded server or a remote server). If you select the embedded server, the PortUser, and Password fields will be grayed out. If you select a remote server, the Port, User, and Password fields will be automatically populated and can be adjusted as needed.

    • 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. Configure the settings in the Message Formatand Grouping Strategy screen:

    1. Verify that Request message format and Response message format are set to the correct format. If not, select the appropriate format.SOAtest and 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 that same file are expected to have one format. The request format may be different than the request 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 one of the message grouping options:

      • Based on operation/type: Group messages based on the operation or message type. This is useful for service traffic that contains messages that are distinctly identifiable either by operation or by the format's message type (i.e., the name of the element under the SOAP Body, the name of the root element in plain XML messages, or the message type of a specified message format). A responder is generated for each operation/type discovered within the traffic file.If you select this option, Virtualize will recommend grouping heuristics to apply, based on its analysis of the traffic file. You can change the pre-selected heuristics. To learn more about the heuristics, see Understanding Heuristics for Grouping by Operation - Type.

      • Based on similar requests: Group messages based on request message structure. This tells Virtualize to analyze the request message structures and group the request/response into responders so that each responder will contain responses that correlate with requests that have a similar structure. Messages are considered "similar" when they have an identical DOM tree model, even if they have different values. This option is used to optimize and simplify the rules for correlating requests to responses within each Message Responder.
      • Based on similar responses: Group messages based on response message structure. This tells Virtualize to analyze the response message structures and group the request/response pairs into responders so that each responder will contain responses that have a similar structure. Messages are considered "similar" when they have an identical DOM tree model, even if they have different values.

      • None: No grouping. A responder is generated for each response message in the traffic file. Use this option if you want every request/response pair in separate Message Responders.

  5. Click Next and review the information about the operations and messages in the Message Grouping Review screen. 
    1. The columns included are based on the grouping strategy applied. 
    2. 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. 
    3. The correlation criteria will be processed in the order in which they appear in the table (from top to bottom). 

      URL paths and parameters will be parameterized against a field from the record type. The fields will have an automatically-generated name and will be visible in the Data Reuse page (later in the wizard).

      For details on how these groupings were created, see Understanding Heuristics for Grouping by Operation - Type.

    1. Add, modify, reorder, and remove grouping criteria using the available controls. See Customizing Grouping Criteria SOAtest1 for details on configuring grouping criteria in SOAtest.

      See Customizing Grouping Criteria Virtualize for details on configuring grouping criteria in Virtualize.

      If you change the criteria, be sure to click Regroup before proceeding.

    2. If all the Autoconfig boxes are checked and you want Virtualize to automatically configure Message Responders for the specified groups, you can skip this step.

      If you want to perform any of the following tasks, disable Autoconfig for each message group you want to customize, click Next, then configure the request mapping as described in Customizing Request Matching and Correlations:

      • Customize which parameter values should be used to determine the response messages of the virtual asset 
      • Modify the automated request/response pair matching 
      • Specify a WSDL or Schema

      Auto-configuration is typically available when there are multiple requests within a message group and there are differences in the paths, the parameters, or the body. If the Autoconfig box is grayed out, this means that autoconfiguration is not available for this group; for more details on why a specific group cannot be automatically configured, see the tooltip for that item.

      For more details on any of the items listed at the top of the panel (processed pairs, unprocessed pairs, messages that don’t match groups, etc.), click the associated hyperlinks.

      To review the messages associated with a particular responder—and/or to change the responder and data set name—click the related row in the Count column.

      If you want to specify a WSDL/schema, enable Configure WSDL/Schema, then specify the appropriate values in the next page.

      titleShould you specify a WSDL or Schema?

      Advantages of specifying the WSDL or schema include:

      The generated Form Input model will be based on that WSDL/Schema, which provides type richness when you are editing and maintaining the resulting Form Input.

      Change Advisor (described in Change Management) is available to help you keep your assets in sync with evolving services and changing environment conditions.

      If you notice that the generated Form Input and its data parameterizations do not match the original messages, this is a sign that the messages do not fully match the WSDL/Schema or that mapping the raw messages failed. If you are experiencing such issues, you should omit the WSDL/Schema to ensure that the generated Form Input model fully matches the traffic messages.

  6. Click Next and configure the settings in the Request Matching screen.

    1. Click the Request/Response pairs tab and verify that the correct correlations have been made. You can click and drag the points connecting the requests and responses to change the match.
    2.  Click the Request Correlation tab choose a Responder mode from the drop-down menu. 
  7. and configure how the imported traffic should be reused or how it should affect existing data in the Data Reuse screen.
    1. 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 from the data tree in this page. 
    2. The tree indicates identity fields with green arrow icons. Existing data sets are noted with annotations.
    3. You can control how new data from the traffic file will extend and/or update existing repository data sets. 

      Replace: Erase existing data then add the new data

      Append: Adds new records without first erasing the existing data.

    4. You can also control whether matching data (data that matches existing record types, as determined by the identity) reuses existing record types or updates an existing record. The Reuse option enables you to reuse/share the existing records that match. The Update option enables you to update the existing records’ corresponding fields with data from the traffic and add new records for new record types.

      titleVirtualize Only Options

      Replace: Erase existing data then add the new data.

      Merge: Import new data without modifying existing data.

      Update: Update matching records with new data and create new records as needed.

      Overwrite: Update matching records (with matching keys) with new data, do not create any additional records.

      Additional details about specifying identities and choosing among the available data reuse/updating options in SOAtest is available at Configuring Data Reuse and Updating SOAtest. For Virtualize, see Configuring Data Reuse and Updating Virtualize1.

    5. The Infer constraints from option enables the Virtualize to determine the characteristics of the data stored in the repository. You can infer constraints based on the data or a service definition.
  8. Click Next and specify any additional configurations in the Final Options screen:
    1. You can configure the wizard to create messages in Form or Literal mode. These modes present a Form Input view (see Form Input) or a Literal view (see Literal View Options_SOA).   
    2. You can enable the Export configuration data into a reusable template option and specify a file name and location to save the settings you used in this wizard as a template. 

      (MQ and JMS only) Specify your connection settings in the next SOAtest wizard page. These settings will be applied to the tools created from this traffic. For details, see Configuring MQ Optionsand Configuring JMS Options.

      See Using Configuration Templates to Reuse and Share Wizard Settings - Virtualize1 and Using Configuration Templates to Reuse and Share Wizard Settings in SOAtest for details about creating and using templates.

      If you are creating the .pva in the Virtual Assets folder, which results in automated deployment, complete the Deploy Virtual Asset wizard page by specifying the desired name and deployment path for the virtual asset that will be created and click Next. The virtual asset will be deployed at the listed endpoint. For details, see Configuring Individual Virtual Asset Deployment Settings.

    3. Click Finish.

The following items will be created and configured:


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:

Completing the SOAtest Wizard: Advanced Topics

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

Scroll pdf ignore

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

In this video you'll learn how to create a virtual asset from traffic recorded with a message proxy.