You can integrate Broadcom's enterprise Service Virtualization product directly with BlazeMeter by storing MAR files in Blazemeter. MAR files are portable copies of virtual services that are proprietary to Service Virtualization.
You can import a MAR file into the BlazeMeter Asset Catalog so that you have a single place to store any available virtual service. You can then get a basic view of the content in the MAR file and create a Mock Service based on that MAR file that runs in a Virtual Service Environment (VSE).
To deploy a MAR file from the Blazemeter Asset Catalog to a Service Virtualization VSE, you must be on 10.5 and configure a connection to Service Virtualization. For more information, see Integrate with Service Virtualization.
Storing virtual services/MAR files into Blazemeter lets you take the work done in your enterprise deployment of Service Virtualization and leverage it in a shift-left continuous testing platform. Consider the following scenarios when migrating virtual services to Blazemeter would be helpful:
- Service Virtualization customers can store MAR files in a common repository so that a consumer of these assets can find, review, and deploy the needed Mock Service/Virtual Service to a VSE
- You use Blazemeter for performance testing and want to gain the benefit of using Mock Services to enrich performance testing, and want to use Service Virtualization assets as Mock Services
- Service Virtualization supports virtual service types that Blazemeter Mock Services do not yet support. For example, while Mock Services only support HTTP/HTTPS protocols, Service Virtualization supports a much wider range of protocols, and configuring this integration lets you mock those protocols within Blazemeter.
- You want to expose complex virtual services from Service Virtualization to Blazemeter users without requiring them to learn the Service Virtualization product.
You can import any MAR file into Blazemeter, but to deploy a MAR file from the Blazemeter Asset Catalog to a Service Virtualization VSE, you must also configure a connection to Service Virtualization.
Adding MAR Files
- Click the Mock Services tab.
- Click Asset Catalog at the top of the page.
In the Asset Catalog, you should see two tabs: Transactions and MAR Files. If you do not see the MAR Files tab, contact Blazemeter support to request access to the Service Virtualization Integration feature.
- Drag the MAR file into the upload area, or click the area to browse for the file you want. You can upload one MAR file at a time. The file size limit for MAR files is 100 MB.
The Import MAR File dialog opens.
- Select the Service that you want to add the MAR file to. A Service in Blazemeter is a representation of the live service being mocked, and is important for organizing you MAR files in the Asset Catalog. The MAR file name must be unique by Service.
To create a new Service:
- Click Select Service.
- Enter the name for your new Service and click Add Service.
- If you want to assign one or more tags to the file, type the tag name(s) in the Tags field and press Enter.
- Tags make files easier to identify, especially within a large Service.
- Common tags include project data, version/history data, and type of virtual service.
- To enter multiple tags, press Enter after each tag name.
- Click Import.
The MAR file is added to the MAR Files tab as part of the selected service. Expand the entry to view useful information about the MAR file:
From this view, you can update the Service to which you assigned the MAR file, add tags, add a description, and download or delete the MAR file. The rest of the information is read-only data pulled from Service Virtualization to help you understand the underlying Transactions in the MAR file. All of this data is configurable in Service Virtualization. If you need to make any changes, download the MAR file and open it in Service Virtualization.
Here is a summary of the information you can view about the MAR file:
Name: Specifies the name of the MAR file in Service Virtualization. You cannot change this value in Blazemeter.
Transport Protocol: Specifies the transport protocol used by the virtual service. You can import MAR files that include any protocols supported by Service Virtualization, even though Blazemeter Transaction-based Mock Services only support HTTP/HTTPS.
Virtual Service: Specifies the source virtual service name. This information is important if you need to find and view the virtual service within the DevTest Portal.
Transactions: Specifies the number of transactions in the virtual service.
Tags: Displays any Blazemeter tags to help you store and find your assets later.
Think Time Scale: Displays the think time scale setting in Service Virtualization, which controls how long the virtual service waits before acting on a received request. This is similar to the Think Time setting within a Mock Service. Within Service Virtualization, this is a percentage that derives a realistic think time based on recorded data and accounting for any overhead processing time.
Concurrent Capacity: Displays a number that indicates the number of processing threads allocated to handle requests to the virtual service within Service Virtualization. This value typically only applies to virtual services deployed to a VSE in Performance mode.
Group Tag: Displays any group tag values specified in Service Virtualization. The group tag is a value that lets you build groups of virtual services in Service Virtualization.
Stateless Signatures: Lists the stateless requests included in the virtual service. Stateful requests are not shown and must be viewed directly in Service Virtualization. Each stateless request can have a meta matching criteria and several transactions that include different matching criteria in the form of different values for arguments. You can drill into each request to see meta request and response information, and use the arrows to navigate through the individual transactions for that request. This view only shows up to five transactions per request, even if there are more than five in the service. All of this data is read-only, but this view lets you understand the nature of the transactions as you build tests that will call the virtual service.