To deploy your MAR-based Mock Services on a containerized VSE, install a BlazeMeter Virtual Service Environment. 

• System Requirements
• Install the BlazeMeter Virtual Service Environment on Docker
• Enable Performance Mode

All you need is a BlazeMeter Private Location (OPL). As long as you enable the correct options during (OPL) creation, a BlazeMeter Virtual Service Environment is installed on a Docker container at the same time as the BlazeMeter Agent installation.

BlazeMeter Virtual Service Environments spin up on demand when you deploy a Mock Service to them. Otherwise, the container does not use resources when not needed.

Note: This feature is not available by default. If you are interested in using BlazeMeter Virtual Service Environments, contact BlazeMeter Support.

System Requirements

Ensure that the server on which you are installing the BlazeMeter Virtual Service Environment adheres to all Docker installation requirements on the Private Location System Requirements page.

Note: We do not support sharing of private locations across Workspaces for BlazeVSE. It is recommended that a new private location is created for each BlazeVSE within a workspace.

Install the BlazeMeter Virtual Service Environment on Docker

1. Click the Gear icon at the top right of the BlazeMeter UI.
2. Click Private Location 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 button.
4. Name the private location, choose Shared run type, and click Next.
   
5. Select Mock Services and Service Virtualization Bridge under Functionalities, and click Create.
   
6. Click Add Agent.
   
7. Name the agent and click Create Agent.
   
   A window appears that includes a Docker command for running the agent. 
8. Copy the Docker run command to a text file.
9. (Optional) If needed, add a PREFERRED_LOCATION property to the Docker command with a value specifying the network interface you want to use for network traffic from Mock Services.
   Example: --env PREFERRED_INTERFACE=eth0
   For more information, see Configure Crane Agent to Ensure Mock Service Deployed on Private Location is Reachable.
10. Open a terminal on the system where you want to install the agent and run the Docker command that you copied in Step 8.
    As long as you chose the correct options during Private Location creation, the agent installation will also install the images for a BlazeMeter Virtual Service Environment.
11. Verify that the agent is running on the Private Locations page.
    
    Note: The Idle status indicates the agent is ready to accept commands. For more information, see Using Private Locations.
12. Click Mock Services and click the Environments page.
    Your installed BlazeMeter Virtual Service Environment should appear on this page.
    
    Note: The VSE will only run when MAR Mock Services are deployed to it. A stopped status indicates no MAR Mock Services are running on that VSE.
    If your agent installation was successful but you do not see an entry on the Environments page, verify that the BlazeMeter Virtual Service Environment feature is enabled in your workspace.

Enable Performance Mode

By default, all newly created Virtual Service Environments have performance mode disabled (ie. they are in functional mode).

BlazeMeter Account Administrators and Workspace Mangers are able to enable performance mode. Changing the performance setting will be tracked according to your Service Virtualization Performance VSE entitlement.

To enable performance mode:

Prerequisite: You are an Account Administrators or a Workspace Manger.

1. Navigate to Mock Services, Environments tab to see the list of all currently installed BlazeMeter Virtual Service Environments.
2. Expand the VSE.
3. Toggle the Performance Mode button. 
   
   An Update message opens.
   
4. Click Update.

You enabled the performance mode for the VSE. For more information about tracking VSE metrics, see Mock Services Analytics.