Blazemeter can integrate with Broadcom's enterprise Service Virtualization product to help serve the following use cases:

• Allow Service Virtualization customers to store MAR files in an Asset Repository so that they can find, review, and deploy the needed Mock Service/Virtual Service to a VSE.
• Provide support for use cases 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.

BlazeMeter can use your MAR-based assets by either deploying to a BlazeMeter Virtual Service Environment or to your on-premise VSE:

Deploying to a BlazeMeter Virtual Service Environment

If using BlazeMeter Virtual Service Environment, you do not require a connection to your on-premise VSE to spin up and down VSE environments.

Deploying to an on-premise VSE

Blazemeter integrates with your on-premise VSE by establishing a connection with the Service Virtualization Enterprise Dashboard. Using this connection, Blazemeter can remotely deploy MAR files as Mock Services by connecting to Service Virtualization and deploying to a Virtual Service Engine (VSE).

The creation and management of these virtual services remains in Service Virtualization, but the deployment and orchestration of the MAR file-based Mock Service occurs in Blazemeter. This procedure describes how to set up the integration required to deploy MAR files as virtual services.

Note: Only Blazemeter users with administrator privileges for a given workspace can access the features required to fully configure the integration between Blazemeter and Service Virtualization. If you are an administrator and you cannot see the pages described in this procedure, contact Blazemeter support and request access to the Service Virtualization Integration feature.

We recommend that you install the BlazeMeter agent and SV bridge co-located with your DevTest install (at a minimum in the same data center). With a co-located installation, the bridge can communicate with DevTest without any firewall in between and only requires outbound access to blazemeter.com.

Configure the Service Virtualization Integration

1. Click the Cog icon at the top right of the page.
2. Click Private Locations under Workspaces.
   If you don't see this option, you don't have the appropriate credentials. Either request to become an admin in your workspace, or work with an administrator to create the private location.
3. Click the Add new private location button.
   
   See Creating an On Premise Environment for full information about creating a private location. This procedure only contains the required configuration information for Service Virtualization integration.
4. Create a private location to integrate with Service Virtualization. 
   The location can be Shared or Dedicated depending on whether you want it to perform other functions.
   On the Functionalities tab, make sure you enable Service Virtualization Bridge.
   Note: The Mock Services entry is not required for Service Virtualization integration; however, you can enable it if you want to run any Transaction-based Mock Services using the location.
   
5. Add an agent to the private location, and install it within the same network as the DevTest Server.
   Note: We recommend that you install the BlazeMeter agent co-located with your DevTest install (at a minimum in the same data center).
6. Expand Workspaces, and click Credentials.
7. Click the Add button.
   The Create a New Credential dialog opens.
   
8. Click the Enterprise Dashboard entry under Service Virtualization Credentials.
   You have to be account admin to create Enterprise Dashboard credentials.
   
9. Add a name, the Enterprise Dashboard URL, and administrator credentials. You can give the credential a unique name to help you identify it in Blazemeter. Click Create Credential when done.
   The new credential appears on the Manage Credentials page with a Type of Enterprise Dashboard.
10. Expand Workspaces and click SV ED Connections.
11. Click the Add button.
    The Add New SV Enterprise Dashboard Connection dialog opens.
    
12. Select the Private Location Agent that you associated with the private location you created, select the Enterprise Dashboard credentials you created to connect with Service Virtualization, and click Add Connection.
    You now have a connection established between a Blazemeter on premise agent and your Enterprise Dashboard.
13. Click the Play button next to the newly created connection.
    When the Status of the connection is Running, that means the agent has deployed the necessary components to be able to deploy virtual services to a VSE from the Mock Services tab.
    

Add Service Virtualization End User Credentials

To deploy a virtual service to a VSE from the Blazemeter Mock Services tab, valid Service Virtualization user credentials are required. 

You can manage Service Virtualization credentials in Blazemeter in either of the following ways:

• Any user who needs to deploy a MAR file-based Mock Service can enter their Service Virtualization credentials and mark them as private. This approach ensures the security of each user's login information. 
• You can configure a public Service Virtualization credential that all users can leverage when deploying MAR file-based Mock Services.
• If a user only has one credential in place (including public credentials), the VSE list is filtered based on any Service Virtualization resource groups assigned.

1. Click the Add button again on the Credentials page.
   The Create a New Credential dialog opens.
   
2. Click the other entry under Service Virtualization credentials to configure end user credentials.
   An admin account is not required to configure end user Service Virtualization credentials.
   
3. Give the credentials a unique name, and enter the credentials you use to log in to Service Virtualization as a user. Leave the Private Credentials box checked if you want to hide these credentials from other users in the workspace. This approach ensures that your private login information is protected, but it requires each user to enter their own Service Virtualization credentials. If you want to avoid entering multiple credentials, work with your Service Virtualization administrator to configure a public credential that you can add here without making it private.
4. Click Create Credential when done.
   The new credential appears on the Manage Credentials page with a Type of Service Virtualization.

Next Steps

This completes the Service Virtualization integration process. After this point, you can do the following:

• Import MAR files into the Blazemeter Asset Catalog. The MAR files are stored in Blazemeter, and you can view information about their transactions directly from the Asset Catalog.
• Create and deploy Mock Services from a stored MAR file. The Mock Services uses the host VSE to deploy the virtual service associated with the MAR file.