Skip to content
DevTest Solutions - 8.0.1
Documentation powered by DocOps

Create Virtual Services from EJB Transactions

Last update January 22, 2015

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

All methods of the same EJB are 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 an EJB 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 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: EJB User Control Bean

The following graphic shows a path graph that includes EJB components. The Shelve All Occurred Transactions action has been applied to one of the getUser() components.

Screen capture of a path graph with EJB nodes.

The following graphic shows the service image that was generated. The service image contains a stateless transaction. Notice that multiple methods are virtualized.

Screen capture of a service image.

In the virtual service model, the Virtual Java Listener step contains the agent name and the EJB name.

Was this helpful?

Please log in to post comments.