Running a Mock Service makes it available for you to test against. Running a Mock Service is a simple two step process:

• Run the Mock Service
• Connect your application to the running Mock Service

Run a Transaction-based Mock Service

1. Find your Mock Service on the Mock Services tab and click Run Mock Service.
   
   The Status changes to Running, and the endpoint for the running Mock Service appears.
2. Copy the endpoint for the Mock Service and redirect your application to point to the Mock Service instead of the real Service.
   This configuration occurs on the application itself, not within Blazemeter, and how you do it depends on the application. It's often as simple as changing a value in an application properties file from the live service to the Mock Service endpoint. After you redirect your application, an application restart might be required.

Run a MAR File-based Mock Service

1. Find your Mock Service on the Mock Services tab and click Run.
   The Select Credentials dialog opens.
   
   Note: If there is only a single Service Virtualization credential available, Blazemeter attempts to use that credential without opening this dialog. If there are no credentials defined, an error displays that directs you to the page for adding Service Virtualization credentials.
2. Select the valid Service Virtualization credentials for the VSE to which you are deploying the Mock Service, and click Apply.
   Blazemeter uses the specified credentials to deploy the virtual service represented by the MAR file to the VSE that you selected in the Location field.
3. Use the DevTest Portal to monitor the virtual service in Service Virtualization.
   You can perform edit operations and manage the virtual service in the DevTest Portal. In Blazemeter, if you click the Stop button, the virtual service is undeployed in Service Virtualization.
4. Copy the endpoint or endpoints (a MAR file-based Mock Service may have more than one endpoint) for the Mock Service and redirect your application to point to the Mock Service instead of the real Service.
   This configuration occurs on the application itself, not within Blazemeter, and how you do it depends on the application. It's often as simple as changing a value in an application properties file from the live service to the Mock Service endpoint. After you redirect your application, an application restart might be required.

Configure SSL Connection to Mock Service

BlazeMeter can configure HTTPS connections to Mock Services over TLS/SSL. When you run a Mock Service over HTTPS, verify that your application can connect to the Mock Service. You can connect your application using the SSL certificate that we provide.

Cloud Deployment

When you deploy a Mock Service to a Cloud location, it uses a certificate signed by the Let's Encrypt certificate authority.

If the application or browser you're using to access a Service Mock does not trust certificates issued by Let's Encrypt, then you will need to configure it to trust the following certificates:

• Let’s Encrypt Authority X3 intermediate certificate
• DST Root CA X3 root certificate, which is used to cross-sign at the previous certificate

Refer to your application, language, or operating system documentation for details on how to import these certificates.

OPL Deployment

When you deploy a Mock Service to an on-premise location (OPL), the HTTPS endpoint is based on the IP address of the agent that deployed the Mock Service. No FDQN resolution occurs by default.

Use the following self-signed certificate to connect to a Mock Service deployed to a private location:

-----BEGIN CERTIFICATE-----
MIIC4jCCAcqgAwIBAgIEXSSpbDANBgkqhkiG9w0BAQsFADAgMR4wHAYDVQQDDBUq
Lm1vY2suYmxhemVtZXRlci5uZXQwHhcNMTkwNzA5MTQ0OTE2WhcNNDYxMTIzMTQ0
OTE2WjAgMR4wHAYDVQQDDBUqLm1vY2suYmxhemVtZXRlci5uZXQwggEiMA0GCSqG
SIb3DQEBAQUAA4IBDwAwggEKAoIBAQCoePRBvFbV5We4CmR/68AddxloEeH3oLeg
ylZpZuPbQt0kEg93mYo4j1xvrTThS4gqCWg1bg7eh4pvVeNTUvTZf/BvCq4RGohG
dfodFzHSuSNMVAhCrMmlUi+T3M4nrBjCj41ZgDB7bijMSbYhb5oOAqXHxLSNCgO/
3UDlUwdbyTzlag0p5iu8spI6IoS6XtWR44h8Jm+WOkBSp7PIc8SMQC2xj5DWHrxx
NlTTj9dC099jvvsR4ncelYNwQGEM5xj6HqTFdD6NGYkyV7r2egjl25uBbruC+M7k
1k4k5BgzuR4g/M1D9y0Yw1ezUvYMaT5g4aCSU5RV3ha4IBJaItZTAgMBAAGjJDAi
MCAGA1UdEQQZMBeCFSoubW9jay5ibGF6ZW1ldGVyLm5ldDANBgkqhkiG9w0BAQsF
AAOCAQEARRPDOPPHQgZCmNqamVcC4rjuG6Q5uDrOejg9uoI2iYHa4ScD8WZxKUy/
7FTzYMBkBSb6NbhEJfIP/D7PL+MWG115080LM01WDdYN8Avjqx4ZlmyQyAwTsdKt
hkGErTVqwiBjuDxjNosFi/0w1XeYIRdZ41iE5x9wqy0qio9pVyc30rwAimIbFFDc
aKtLTEom3yAhj4vpBojN35YyEY6jnTkpQBcd4bnarwtqYvTbqiSIbMJivmTHl88e
eWsSBE53G/u2aDPOyx+Lg24Rqh6I+ssgRVmNDZIc4Vj8cvEeTmihMVY6DTpwPls5
yuLi+DPQq6qM479piqLVP7LPV5vs/A==
-----END CERTIFICATE-----

If you want to generate a hostname for the HTTPS endpoint, add an entry to your operating system's  host file that lists the IP address followed by a host name that ends with mock.blazemeter.net.

Example: 

10.1.1.100 testmock.mock.blazemeter.net