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.
      

3. Click Next and choose one of the following modes from the Connection Mode dropdown 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 drop-down 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. Select or enter the name of the repository you want to use in Repository name. If you enter the name of a new repository, that repository will be created.
     3. Specify your credentials to access the data repository server (if required).
     4. To use SSL to connect to the server, enable Use SSL.

   •  Connection String: 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.
     

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

     Info
     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.

     

4. Click Validate to verify the connection settings.

5. 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. 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.
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:
   • 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.

10. Click Finish.

...