Skip to content
DevTest Solutions - 8.0.1
Documentation powered by DocOps

Consolidation of Transactions When Creating Virtual Services

Last update January 22, 2015

When creating virtual services for transactions with the same category, CAI consolidates the transactions into one virtual service per category. For example, if there are three Web HTTP transactions, only one virtual service is created. You can view all the transactions that were consolidated into a virtual service in the Shelf. Only single and merged transactions can be consolidated. All occurred transaction frames cannot be consolidated.

The consolidated virtual service name is the category name when all the transactions are consolidated into one virtual service.

When all the category frames for one agent are consolidated, the consolidated virtual service name is the category name and the agent name.

To display the transactions that were consolidated into the single virtual service, from the shelf click Create VS and click .

The following graphic displays a consolidated Web HTTP virtual service in the Shelf dialog:

Notice that the transactions /lisabank/createaccount.do, /lisabank/buttonclick.do, and /lisabank/buttonclick.do were consolidated into one virtual service.

Note: You have the option of deleting any of the consolidated Web HTTP transactions before creating the virtual service.

The following protocols are supported for consolidation when creating a virtual service:

  • REST: one virtual service
  • All SOAP: one virtual service
  • All HTTP: one virtual service
  • EJB: one virtual service per agent
  • JDBC: one virtual service per agent
  • JCA: one virtual service per agent
  • TIBCO: one virtual service per agent
Note: JMS and SAP protocols are not supported.
Was this helpful?

Please log in to post comments.