You can use CA Continuous Application Insight to virtualize a process in TIBCO ActiveMatrix BusinessWorks. When the virtual service is deployed, it substitutes the behavior of process activities with the responses collected in the service image.
The following approaches are supported:
- Virtualize from DevTest Workstation. You use the Virtual Service Image Recorder to capture traffic and generate the virtual service. You do not need to enable CAI.
- Virtualize from the DevTest Portal. You generate transactions that appear in the DevTest Portal. At any time afterward, you can use the transactions to create the virtual service. CAI must be enabled. This approach provides more flexibility, but has greater overhead than the first approach.
You can generate virtual services that are stateful or stateless. Stateless is recommended. You can control this setting from the Virtual Service Image Recorder and the DevTest Portal.
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.
These procedures assume that the DevTest Java Agent was installed and configured on TIBCO ActiveMatrix BusinessWorks.
For detailed information about installing and configuring the DevTest Java Agent, see
For detailed information about using the Virtual Service Image Recorder and deploying virtual services, see
Using CA Service Virtualization
To virtualize TIBCO ActiveMatrix BusinessWorks from DevTest Workstation:
- Go to DevTest Workstation and start the Virtual Service Image Recorder.
You are prompted to provide basic information.
- Specify the names of the service image and virtual service model.
- Set the transport protocol to Java.
- Click Next.
You are prompted to select the Java classes to virtualize.
- Select the agent and move it into the Connected Agents list.
- Expand the Protocols arrow and move the TIBCO BW protocol into the right pane.
- Click Next. If necessary, trigger the execution of the TIBCO processes that you want to record. As the processes run, the agent records the activities.
- When the recording has completed, click Next and perform the remaining steps in the Virtual Service Image Recorder. You do not need to select a data protocol.
A service image and virtual service model are created.
- Deploy and start the virtual service model.
To virtualize TIBCO ActiveMatrix BusinessWorks from the DevTest Portal:
- Trigger the execution of the TIBCO processes.
- Add a TIBCO transaction frame to the shelf. You can virtualize the entire conversation by selecting the leftmost frame. You can virtualize a specific activity by selecting the frame that includes the activity name.
- Open the shelf.
- Click Create VS.
To change the default name, select the name and make your edits, then click to save.
- If you want all transactions to be treated as stateless, ensure that the check box is selected.
- Configure the response for unknown requests.
- To view the consolidated transactions, click
- To delete a consolidated transaction, click
- Click Create.
- Select the project where the virtual service will be created.
- (Optional) Edit name prefix. The default prefix is the user name.
- Select an option to keep or delete the transactions in the shelf once the VS is created.
- Click Create.
Example: Virtualize an Add User Process
The following graphic shows a process definition in TIBCO Designer. The process contains the following activities: File Poller, JMS Queue Sender, Confirm, and End.
The File Poller activity monitors a text file. When the file is changed, the activity starts the process.
The JMS Queue Sender activity sends a message to the specified queue.
The following graphic shows a service image that the Virtual Service Image Recorder generated. A conversation with four nodes appears in the Transactions tab. The four nodes correspond to the four activities in the process definition.
Each node in the conversation includes an operation field. The value of this field consists of the fully qualified process name and the activity name. In the preceding graphic, the value for the selected node is Tibco:VSE/Processes/AddUser.JMS Queue Sender.
The virtual service model is the default for the Java transport protocol.