Use this page to specify error handling options.
To specify error handling settings
Select Error Handling. Review the following.
Group | Description |
---|---|
Error Handling | |
Stop test after first error |
Default setting for a new jobs. Terminates the test when a server error occurs. |
Stop job after first test error |
Terminates the job when a server error occurs. |
Thresholds | |
Stop job if Memory usage exceeds |
Instructs Benchmark Factory to stop the job if memory usage exceeds this threshold. |
Note: If you create a new repository in Benchmark Factory 5.5 or later, earlier versions of Benchmark Factory will not work against this repository.
The repository is a database where all of the test results are stored. Benchmark Factory inserts test results into the repository and provides an easy way to access all test results data.
By default, the Repository is a SQLite database that resides on the same machine as Benchmark Factory. The Repository can reside on another database server if required. To change the database, select the Data Source Name of the ODBC connection for the new database. To migrate data from one database to another, click Data Migration to open the Data Migration Wizard.
Note: By default in Benchmark Factory 7.1.1 or earlier, a MySQL database is created and used as the Repository, unless you selected the SQLite option during installation. In Benchmark Factory 7.2 or later, by default a SQLite database is created and used as the Repository.
If you plan to store a large amount of test data in the repository, you might want to consider using a more robust database than SQLite.
The Repository Settings page allows you to edit the DSN, perform ODBC administration, and test the connection. Benchmark Factory also provides a Repository Manager and Data Repository Migration wizard to assist you with other repository management functions.
Note: If the database structure does not exist on the selected database, Benchmark Factory prompts you to create the structure.
The supported database types are:
To specify Repository settings
Select Repository. Review the following for additional information:
Data Source Name | Data Source name of the ODBC connection used to connect to the repository database. |
User Name | The User Name used to log into the selected database. |
Password | The Password associated with the user name used to log into the database. |
Edit DSN | Click to edit the selected Data Source Name. |
ODBC Administrator | Click to open the ODBC Data Source Administrator dialog. Use this to add a DSN or ODBC connection. |
Test Connection | Tests the defined connection. |
Data Migration | Click to open the Data Migration Wizard. See Data Repository Migration Wizard for more information. |
You can use this page of the Settings dialog to specify default values for the statistics collection options.
Note: If you modify the default settings in the Settings dialog, the changes apply to new jobs only, not to existing jobs.
To specify Statistics settings
Specify statistics collection options. Review the following for additional information:
Save results to Repository |
Select to save test information to the Repository. Then select one or more of the following options:
|
To specify Real-Time Counter settings
Tip: You can over-ride the default settings and specify statistics collection options per job. In the New/Edit Job Wizard, select a test under Workload and then select the Performance Counters tab (under Job Setup tab).
Use this page of the Settings dialog to do the following:
To specify Agent settings
Select Agent. Review the following for additional information:
Setup New User Agent |
Click to setup a new agent or to install a remote agent on Windows or Linux.
|
List of agents |
Displays the list of agents that have been set up in the console.
Use this area to specify the default agent machines to use by selecting the check box for each default agent. Also, specify the number of agents. These default settings are used when you create a new job. If you do not select a default agent, the local agent is automatically selected when you create a new job in the New Job wizard. Note: When you run a job using one or more local agents, if Agent utilization of resources on the local machine is too high, errors could occur. |
Remove | Click to remove the selected agent. |
Verify Selected Agent | Verifies that the selected agent starts and communicates with console. |
Error Handling |
Stop job when agent cannot be started/connected—Cancels job if agent does not start or connection is lost. Do not select this option if you want to run a job using multiple agents AND you want the job to run even if one or more agents do not start. |
Agent communication timeout | Specify timeout duration in seconds. |
Agent refresh interval | Specify how often each agent should refresh its status. |
Tips:
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center