Optimising the Ideagen Quality Management Legacy Web Interface
Summary
You may encounter errors when trying to perform certain tasks or encounter performance issues when using Ideagen Quality Management web. This article will guide you through optimising the web interface to ensure the best possible performance
Solution
There are 3 configurations that can be made to the web interface configuration to ensure optimal performance:
- Setting/Increasing the SQL Command Timeout value
- Increase the Maximum File Upload Size Supported by ASP.NET and IIS
- Increase the Amount of time that a Request can Execute
Set/Increase the SQL Command Timeout
All of the Ideagen Quality Management data is held in a SQL database. When the information displayed in Ideagen Quality Management is changed, the application will automatically perform SQL operations to update the data on the SQL server. While this is being performed, the default SQL timeout options will determine how long these operations will run for.
Increasing the timeout is recommended if:
- There is a large geographical distance between the application server and database server which may result in a delay carrying out tasks
- The SQL server hosts various other databases which may result in slower performance
- The user will be carrying out actions that require complex calculations to be performed (e.g. restructuring large managed lists)
To set the SQL command timeout:
- On the application server, browse to the Ideagen Quality Management web folder. By default, this will be C:\inetpub\wwwroot\QPulse5Web
- Locate and open web.config with Notepad
- Add a new entry to the <appSettings> section:
<add key="SqlCommandTimeout" value="120"/>
- Save the web.config.
| Benefits of Configuration | Details |
|---|---|
| Control Over SQL Timeout | The time allowed for SQL commands to be performed can be controlled by IT. |
Increase the Maximum File Upload Size Supported by ASP.NET and IIS
When using the web interface you may need to add a chabge request attachment or add attachments to records. You may need to increase the maximum file upload size if there is the need to upload files that are larger than 4Mb.
If you regularly need to upload large files then you will have to increase the maxRequestLength attribute under the HttpRuntime element in your web.config file. This attribute indicates the maximum file upload size for ASP.NET. This by default can be found at C:\inetpub\wwwroot\QPulse5Web. By default, this attribute is set to 4096kb. To increase this, do the following:
- Open your Web.Config file and locate <system.web> element.
- Add the following line UNDER <system.web>:
<httpRuntime maxRequestLength="10240">
- The example above increases the maxRequestLength to 10MB
If you need to upload files greater than 28.6MB then as well as increasing the maxRequestLength, you will have to increase the maxAllowedContentLength attribute under the requestLimits element in your Web.config file. This attribute indicates the maximum content length in a request that can be handled by IIS. By default this attribute is set to 30000000 bytes (28.6MB). To increase this, do the following:
- Open your Web.Config file and locate <system.webserver> element.
- Add the following UNDER <system.webserver>:
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="60000000"/>
</requestFiltering>
</security> - The example above increases the maxAllowedContentLength to 57.2MB
Increase the Amount of Time That a Request Can Execute
If your requests are timing out through the web interface then you will need to increase the executionTimeout attribute under the httpRuntime element. This attribute specifies the maximum number of seconds a request has to execute before being shut down. By default, this is set to 90 seconds. To increase this, do the following:
- Open your Web.Config file and locate <system.web> element.
- Add the following to the httpRuntime element:
<httpRuntime maxRequestLength="10240" executionTimeout="300"/>
- The example above increases the execution timeout to 300 seconds.