Skip to content
DevTest Solutions - 8.0.1
Documentation powered by DocOps

Create Virtual Services from webMethods Transactions

Last update January 22, 2015

Use the following procedure to create a virtual service from a set of webMethods Integration Server transactions in the CAI database.

webMethods Integration Server includes the concepts of a flow service and a pipeline. A flow service lets you encapsulate a group of services and manage the flow of data among them. The pipeline is a data structure that contains the input and output values for a flow service. You can add steps to a flow service to perform such actions as invoking services and changing data in the pipeline.

The flow service is the unit that is virtualized.

A virtual service includes the responses that are sent for unknown conversational requests and unknown stateless requests. When you create a virtual service, you can configure the body of these responses. The following list describes the options:
  • Report "No Match"
    Causes an exception to be raised in the virtualized application.
  • Bypass Virtual Service
    Allows the original request to pass straight through, as if the class and method were not virtualized at all.

Follow these steps:

  1. Add a webMethods Integration Server transaction frame to the shelf.
  2. Open the shelf.
  3. Click Create VS.
  4. To change the default name, select the name and make your edits, then click save button to save.
  5. If you want all transactions to be treated as stateless, ensure that the check box is selected.
  6. Configure the response for unknown requests.
  7. To view the consolidated transactions, click .
  8. To delete a consolidated transaction, click Remove from Virtual Service listing button.
  9. Click Create.
  10. Select the project where the virtual service will be created.
  11. (Optional) Edit name prefix. The default prefix is the user name.
  12. Select an option to keep or delete the transactions in the shelf once the VS is created.
  13. Click Create.
Note: For more information about consolidated transactions, see Consolidation of Transactions When Creating Virtual Services.

Example: Update User

The following graphic shows a path graph that includes webMethods Integration Server frames. The flow service in this example is named updateUser. The purpose is to send updated information for a user to a database.

Screen capture of path graph with WebMethods frames.

Note: If you select any of the webMethods Integration Server frames, you can view the pipeline data in the transaction detail dialog.

When a path graph has multiple webMethods Integration Server frame, you must select one frame for virtualization. The decision of which frame to select depends on the system under test. This example could result in the following decisions:

  • To ensure that your software interfaces with a webMethods process, select the leftmost webMethods Integration Server frame.
  • To remove the database, select the webMethods Integration Server frame that directly calls the database.
Was this helpful?

Please log in to post comments.