...
- Choose the Traffic> Generate Fixed Messages option in one of the available creation wizards.
- For details on accessing the wizards, see Adding Projects, Virtual Assets, and Responder Suites.
- Complete the first page of the Traffic wizard as follows:
- Specify the location of the traffic file.
- Change the character encoding if needed.
- Specify the desired message grouping option (see Messaging Group Options), then click Next.
- (MQ and JMS only) Specify your connection settings in the next wizard page, then click Next.
- Complete the Deploy Virtual Asset wizard page as follows:
- Specify the desired name and deployment path for the virtual asset that will be created. It will be deployed at the listed endpoint. For details, see Configuring Individual Virtual Asset Deployment Settings.
- Click Next.
- Complete each Request Parameter Selection page as follows:
- Use the available controls to specify which parameter values should be used to deter-mine the response messages of the virtual asset. You do not need to configure these selections; you can leave the default automatic selection enabled, if desired. See Completing the Request Parameter Selection Wizard (below) for details.
- Click Next.
- (Optional) If you want to set up dynamic messages (using data extracted from the incoming message to parameterize the response message or header elements), complete the Configure Dynamic Messages page for each operation that you want to parameterize. Upon completion of each wizard page, click Next to advance to the page for the next operation.
- For details on how to configure dynamic messages, see Completing the Configure Dynamic Messages Wizard (below).
- Click Finish.
...
You can specify the following messaging group options.
| None | No grouping. A responder is generated for each response messages in the traffic file. Use this option if you want every request/response pair in separate Message Responders. |
|---|---|
| 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. |
| 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. This option is used in order to generate Message Responders that are optimized for data source parameterization. Since all responses within a Message Responder are similar, a data source can be generated more easily for each responder to create data-source-driven assets. |
| Anchor | ||||
|---|---|---|---|---|
|
...
For a more detailed discussion of deployment procedures and options, see Deploying Virtual Assets Virtualize.
Customizing the Virtual Assets
...