Using CA Continuous Application Insight › VS Traffic to CA Application Insight Companion

VS Traffic to CA Application Insight Companion

The VS Traffic to CA Application Insight Companion pushes data to the CAI database to generate virtual services and visibility into the application. When you add this companion to a virtual service model, it performs the following actions:

• Captures the requests that the model processes and their corresponding responses.
• Saves the requests in the CAI database as transaction frames.

This companion supports HTTP, JMS, and WebSphere MQ models.

Prerequisites

• Messages from an application are captured by the VSE Recorder.
• A virtual service model file was created. See Using CA Service Virtualization for more information about creating a virtual service model.

Follow these steps:

1. Open the virtual service model.
2. In the right panel, select Companions and click Add.

   The Companions menu opens.

3. Select Virtual Service Environment, VS Traffic to CA Application Insight Companion.
4. Save the virtual service model.
5. Right-click the virtual service and select Deploy/Redeploy to VSE@default. See Using CA Service Virtualization for more information about deploying a virtual service.

   A message indicates that the virtual service was deployed to the VSE@default VSE server.

6. Invoke the virtual service.

   The transaction frame is created.

   Note: The transaction frames that are created by this companion display in the DevTest Portal with a virtualized label at the end of the name. An example of a component name for an HTTP transaction is POST/itkoExamples/EJB3AccountControlBean(virtualized). See the Path Graph topic for more information about component names.

7. Go to the DevTest Portal and create the baseline test. See the Creating Baselines topic for more information about creating baselines for HTTP, JMS, and WebSphere protocols.
8. Create a DevTest test from the baseline.
9. Verify the test in DevTest Workstation.