The Benchmark Factory Licensing dialog allows you to enter a new license key, modify a license, or modify the virtual user pack.
The active license or licenses in Benchmark Factory determine the available features, including the ability to connect to certain types of databases. Benchmark Factory supports multiple licenses. This can enable multiple license-dependent features.
Note: If you delete an active Trial key from the Licensing dialog, any features enabled by the Trial key and not included in one of the remaining active licenses will be disabled.
To access the licensing dialog
From this dialog you can:
To enter a new license key
If required, you can modify your Benchmark Factory license key.
To modify the license key
Benchmark Factory comes with 100 virtual users. Benchmark Factory Freeware comes with 20 virtual users. To add up to an unlimited number of virtual users, enter a virtual user key.
To modify the Virtual User Pack
License keys compatible with Benchmark Factory 5.8.1 (or earlier) are no longer supported.
To upgrade your license key
Go to Help | Licensing to find your license number in your current version of Benchmark Factory. If not explicitly listed, it may be included as part of the Site Message associated with your key.
Example: ACCOUNTNAME-nnn-nnn-nnn
If you need help finding your license number or an upgrade key, please contact the License Administration team: https://support.quest.com/licensing-assistance.
The Benchmark Factory Licensing dialog allows you to enter a new license key, modify a license, or modify the virtual user pack.
The active license or licenses in Benchmark Factory determine the available features, including the ability to connect to certain types of databases. Benchmark Factory supports multiple licenses. This can enable multiple license-dependent features.
Note: If you delete an active Trial key from the Licensing dialog, any features enabled by the Trial key and not included in one of the remaining active licenses will be disabled.
To access the licensing dialog
From this dialog you can:
To enter a new license key
If required, you can modify your Benchmark Factory license key.
To modify the license key
Benchmark Factory comes with 100 virtual users. Benchmark Factory Freeware comes with 20 virtual users. To add up to an unlimited number of virtual users, enter a virtual user key.
To modify the Virtual User Pack
License keys compatible with Benchmark Factory 5.8.1 (or earlier) are no longer supported.
To upgrade your license key
Go to Help | Licensing to find your license number in your current version of Benchmark Factory. If not explicitly listed, it may be included as part of the Site Message associated with your key.
Example: ACCOUNTNAME-nnn-nnn-nnn
If you need help finding your license number or an upgrade key, please contact the License Administration team: https://support.quest.com/licensing-assistance.
Benchmark Factory comes with 100 virtual users by default. Benchmark Factory Freeware comes with 20 virtual users. Virtual users simulate the load against the system-under-test. Each virtual user is a separate thread, acting independently of the other virtual users, with its own connection to the system-under-test. Each virtual user tracks its own statistics that includes transaction times and the number of times a transaction executes.
Benchmark Factory can scale up to an unlimited number of concurrent load users. Additional virtual users allow you to:
To request additional concurrent load users, please contact your Quest Software representative, or visit the Benchmark Factory Web site.
Benchmark Factory provides a REST API that allows you to access the functionality of Benchmark Factory, but without the need to interact with the Benchmark Factory graphic user interface. A REST API is an application program interface (API) that uses HTTP requests to GET, POST, PUT, and DELETE data. Through the REST API, you can use a script, command-line tool, or custom application to automate your load testing tasks using Benchmark Factory.
You can use the Benchmark Factory REST API with the Benchmark Factory console application or BMFServer.exe. BMFServer.exe is a non-UI application included in the Benchmark Factory installation. See BMFServer.exe for more information.
Why Integrate Benchmark Factory
Integrating Benchmark Factory into your continuous testing / continuous improvement process allows you to test the scalability of changes before committing those changes to your production environment. Different Benchmark Factory tests can be used to validate scalability and performance.
To interface with Benchmark Factory using the REST API, use the following URI format:
http://{server}:{port}/api/{resource}
Where {server} is the Benchmark Factory host server, {port} is the port number, and {resource} is the name of the resource.
Example: http://localhost:30100/api/jobs
Use the applicable REST API port number for the Benchmark Factory application you are using.
GET - Retrieves a list of resources
POST - Creates a new resource based on the data provided in the request body
PUT - Updates the resource to the value/values provided in the data supplied in the HTTP data area
DELETE - Deletes the resource
Benchmark Factory must be running to use the REST API. Start the Benchmark Factory console or BMFServer.exe prior to sending requests via the REST API.
Note: You cannot run the Benchmark Factory console and BMFServer.exe on the same machine at the same time.
Both XML and JSON are supported request and response formats. Specify the response format in the Accept header of the request. Indicate the request format in the Content-Type header of the request.
When you create a resource, such as a job or connection, the new resource is assigned a zero-based index. This number can be used to identify the resource. However, the index number attached to the resource will change as users remove and add resources. For best results, define a name for the resource and then use the resource name in your requests.
If a resource (such as a connection or a job) is created, the response header usually contains the URL for the newly-created resource.
These are the expected response codes returned. In addition, some other status codes may be returned if either an internal error occurs or there are other issues.
| Code | Description |
|---|---|
| 200 | Success |
| 201 | Success. Resource created. |
| 204 | Success. No content returned. |
| 400 | The request failed. |
| 404 | The specified resource was not found. |
| 405 | The method is not supported for the specified resource. |
Each job state or status has a code. These are the codes returned when you get the job status. Use these codes to change a job’s status (e.g., start a job, stop a job).
| Code | Status | Action when included in a request |
|---|---|---|
| 1 | Complete | Stops a running job. |
| 2 | Running | Runs a job, if possible. |
| 3 | Ready | Readies a job to run on schedule. Stops a running job. |
| 4 | Hold | Prevents a job from running. Stops a running job. |
| 5 | Stop | Stops a running job. |
© ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center
