Installation and Upgrade Guide
Application Pool Timeouts
Configuring a Mail Server
Managing Your License
Moving the Enterprise Tester Data folder
Secure Channel - Using an SSL Certificate
Server Performance Test
Updating the logging.config File
- Updating the web.config File
- Application Pool Timeouts
Upgrading Enterprise Tester
Managing Your Organization
Users and Groups
Managing Picklist Values
Migrating Enterprise Tester from one server to another
Versioning & Version Control
Screen Field Configuration
- Installation and Upgrade Guide
Searching & TQL
Earlier Versions of this Documentation
Changes to the web.config file can leave Enterprise Tester inoperable. We advise taking a backup of your web.config file and database prior to making changes.
Some configuration settings in Enterprise Tester are not yet exposed in the User interface. You can apply custom settings to some features in the appSettings section in the web.config file.
In the appSettings section, you can add key/value pairs which can be used to control features of Enterprise Tester .
|avatars.storage.path||The path to avatar images used on the website||c:\Enterprise Tester\data\Avatars\|
Storage method to use, either InDatabase or FileSystemCas - defaults to FileSystemCas.
Set to true to disable garbage collection or false to enable garbage collection.
true or false
Minutes between garbage collections, should generally be set to an hour or more.
Path to where attachments are stored, defaults to \Data\Attachments|f:\et-attachments.
The maximum size for attachments (in bytes) to be included in any exported baseline, if not set it will default to 4mb.
If true (the default) then at startup we check to see if any projects are "uncached" and require a refresh lookups sync to be executed, if so we trigger an update at startup.
true or false
How often custom field metadata is updated, defaults to 00:00:00
00:00:00 ( disabled)
Time to wait after completing a defect synchronization pass across all projects, before checking again.
Turns the issue collector on or off. Default is set to on (true).
true or false
Disables displaying / calculating the existing elements report for requirements EA import/sync. This report can be very costly (half hour +) to calculate for large EA projects where there may be tens of thousands of requirements. Default for 4.2 and above is "false"
true or false
Defaults to 1000 database transactions per batch. When exporting a large amount of data from ET you can reduce the number of transactions per page to improve the performance of the export.
If true (the default) then after creating a link the lookup refresh process will be triggered to refresh of all the cached custom/inbuilt field info. The refresh process will only work if the defect tracker is also enabled.
true or false
The timeout when submitting ExtJS forms (in seconds).
The timeout for ajax requests (in milliseconds).
The ajax update timeout for requests (in seconds).
Defaults to "Open", but can be set to either a single value i.e. "Closed" or multiple options, separated by commas i.e. "Open, Ready, Awaiting Review" - in which case each value in the list will be tried until we can find a match - useful if you have different projects which have different sets of statuses.
This setting specifies the number of JIRA issues to retrieve per page when synchronizing with JIRA. The default setting is 1000. This can be useful when the number of JIRA issues retrieved causes timeout issues.
The date format used for rendering ET date fields to strings, as required by JIRA - defaults to "dd/MMM/yy hh:mm a".
dd/MMM/yy hh:mm a
When refreshing loops using the JIRA 5.2+ plugin, by default it will attempt to "Sample" each JIRA project for examples issues of each issue type, to discover additional custom fields which are only displayed on the edit screen. This feature was introduced in ET 4.10, and for very large JIRA instances may be quite slow - if all the custom fields you wish to map appear on the create screen in JIRA, then you can skip the time-consuming sampling process by changing this setting.
The prefix added to the start of relationship names when synchronized to JIRA as remote links, it defaults to "ET: " - to disable the prefix, you can switch it a blank value, or distinguish between ET instances by setting it say "ET-Prod: " and "ET-Dev:".
The max time it can take to close a connection to the JIRA soap service, defaults to 00:02:00 (2 minutes - prior to v3.3 this was fixed at 1 minute)
The max time it can take to open an http connection to the JIRA soap service, defaults to 00:02:00 (2 minutes - prior to v3.3 this was fixed at 1 minute)
The max time it can take to receive data from the JIRA soap service, defaults to 00:15:00 (15 minutes - prior to v3.3 this was fixed at 10 minutes)
The max time it can take to send a request to the JIRA soap service, defaults to 00:02:00 (2 minutes - prior to v3.3 this was fixed at 1 minute)
The time to wait between successive screen-scraping requests when fetching options for custom fields, for low-spec JIRA servers you might need to adjust this to give the server a chance to "breathe" between requests, to avoid degradation in performance for other users. Defaults to 1 second delay. For high-spec JIRA servers, you can set this value at 0 seconds, to have no delay between scraping requests
Generates a stable server key even if the MAC address changes over time.
When upgrading ET, by default the logging.config file is overwritten to remove debugging settings that can effect the performance of ET. You can select not to have the logging.config file overwritten by selecting a new location to store the config file.
c:\Program Files (x86)\Catch Limited\Enterprise Tester\data\logging.config (default)
|MinimumPasswordStrength||Enables a minimum password strength to be enforced for users logging directly into Enterprise Tester. The system default for new installations is Medium.|
Poor, Weak, Medium, Strong, or VeryStrong
Note the capitalisation of the first letter for each setting.
The name of the provider class used for applying database migrations.
Enables support for multiple query results being returned from Oracle in a single round-trip. This should be enabled for all ET installations which use an Oracle database, to improve performance.
Support on version 4.9.1 and above of Enterprise Tester only.
The maximum number of notifications to record per user, once the limit is reached older notifications will be discarded for newer ones.
The separator character used for display requirement/script paths - defaults to "|" in v4.2 and above
(the default is “/” in V4.1 and earlier) .
The path to the set of baselines which are used as project templates available when creating a new project.
The value can be specified as either a number e.g. 5 - which would be 5 seconds, or formatted as what's called a timspan e.g. "hh:mm:ss" - so 5 minutes would be specified as 00:05:00.
The maximum number of steps allowed for a script - default is 100.
The path to the indexes folder (in v4.0 and later, if not specified, this defaults to the \Data\Indexes folder of the installation directory.
The time between commit changes to the search index.
The time to wait before waking up again processing search index changes (changes in ET will also trigger the worker process to "wake up").
The time the index worker processor will wait for the queue to empty - currently used in unit tests.
The time to wait before aborting the reindexing process when waiting for the index queue to flush - 5 minutes by default.
Defaults to false, if set to true then "all relationships" are indexed, which will results in a much larger set of re-indexing occurring after each change within the application.
true or false
Root URL to use for the site when generating external links for applications such as defect trackers, this can be useful when ET uses the wrong address when generating links.
Configures how absolute URL's are generated by the ET application, you may need to change this setting when exposing Enterprise Tester from behind a reverse proxy.
For full details on each of the values, and what it does to the generated absolute URLs please see the addendum at the bottom of this page..
Defaults to false, but if set to true then when synchronizing if a file is found that has the same file name and file size as a previously synchronized file, it will be skipped - useful if you want to avoid attachments which have been duplicated by another synchronization process or user error.
true or false
Enable the sending of anonymous trial statistics to allow Catch Software to monitor the quality of the installation and initial project setup experience for users with an Enterprise Tester trial license applied.
Setting a Key
To set a key:
- Open the web.config file in a text editor.
- Locate the section starting with <appSettings>
- Add the new entry, in the format off: <add key="key-name" value="value" />
- Save changes
- Refresh ET in browser, it should reload with the new settings applied.
Example - before adding new values:
Example - after adding new values:
Here are the values that the appSetting site.root.url.scheme can be configured as.
Forces base URL to http when processing OAuth requests.
Forces base URL to https when processing OAuth requests.
Uses same scheme (Http/https) as the request's URL.
This is equivalent to how ET used to work for v4.5 and below.
Checks for the x-forwarded-scheme header, if present, will use the value specified there, if header not present, will revert back to the "Same as request" behaviour
This is the new default for v4.6 and above.
When refreshing lookups in the JIRA (REST based plugin - JIRA 5.2 and above), if this option is set to true (the default) it will use both create screen meta and a technique of sampling issues of each issue type in a project and getting their edit screen metadata to compile a list of all available custom fields. This does require that the project contains issues to sample in the first place, and will still not detect fields that are neither on the edit or create screen ( e.g. transition screens).
Sampling may be slow for instances with very large numbers of issue types. If performance is slow, it may be necessary to turn this value to false. Note that this does mean any field that you wish to map for synchronization must appear on the create screens for those issue types/screen schemes.
If enabled, and the logging level is "INFO" or "DEBUG" then when doing a refresh lookups, you will see this in the log file:
Which allows you to see how much time is being spent retrieving getting custom field information by sampling issues and getting their edit meta data.
Additionally, if the feature is set to "off" (false) and the log level is "DEBUG" then in the logs you will see this message:
So you can be assured that sampling of issue edit metadata is not occurring.