Page History

...

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. This is optional if a Definition file has been entered.
   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 - Virtualize for details about creating and using templates in Virtualize.
      Image RemovedImage Added

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 Port, User, 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. 

     Info
     title Locking the Repository Until the Wizard Completes
     When you’re working with a remote (e.g., not embedded) Data Repository server, the repository that you specify here will be locked until the wizard completes. If you want the lock to display as "locked by [your_username]" rather than "locked by [tmp]", check Configure authentication for locking, then specify the URL of the CTP server that you use, as well as your username and password for that CTP server. To learn more about locking, see Locking and Unlocking Repositories in CTP.

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

   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. If you specified a service definition or template file, you can enable the Empty groups option in the Message Group Creation Options section. When this option is enabled, groups will be created based on a service definition or template file even if the traffic file does not contain messages that match the group criteria. When this option is disabled, groups without messages will not be created. The Empty Groups option is set to false by default if a traffic file is specified alongside a service definition or traffic template. The Empty Groups option is set to true by default if no traffic file is specified.
   6. Click Next and review the information about the operations and messages in the Message Grouping Review screen. See Message Grouping Review Screen for details.
5. Click Next. If the Autoconfig option for each group was enabled, the Data Reuse screen will open and you can skip the next step.
6. 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. 
7. 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.  
8. Click Next and specify any additional configurations in the Final Options screen:
   • Enable the Form or Literal option in the Payload section to configure the wizard to create messages in Form or Literal mode. See Form Input or Literal View Options_SOA for details.   

   • 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. See Using Configuration Templates to Reuse and Share Wizard Settings - Virtualize for details about creating and using templates.

9. Click Finish.

...