New article
Recently updated
How To Install Web Reporting
Who is this article for?IT Personnel performing an installation of Ideagen Quality Management 7.
An understanding of Windows infrastructure is required.
Important: This article is part of a series of articles covering the Ideagen Quality Management installation process. Please visit How to Install Ideagen Quality Management to view the entire process.
The Web Reporting Portal (also known as Web Reporting) is an optional feature that needs to be purchased. Web Reporting allows a lightweight web interface for submitting Occurrence reports into the Ideagen Quality Management Occurrences module.
These records can then be reviewed and accepted/rejected, creating an Incident for investigation.
1. Prerequisites
In order to run Web Reporting you must first confirm the following prerequisites have been met:
- You are running Ideagen Quality Management v5.95 (or higher)
- You have an Ideagen Quality Management licence file with Web Reporting enabled
- You have Ideagen Quality Management Web Service APIs installed on your server
- You have IIS 7 or greater with ASP.NET v4 installed
- You have the Web Reporting installation files
2. Installation steps
- Extract the contents of the zip file into c:\inetpub\wwwroot\reporting
- Run Internet Information Services (IIS) Manager
- Right click on Application Pools> Add Application Pool…
- Type “WebReportingAppPool” into the Name box and choose .NET Framework version 4 and Integrated pipeline mode. Click OK.
- Under the Default Web Site right click the 'reporting' folder and Convert to Application
- Select the WebReportingAppPool then Ok
- Browse to c:\inetpub\wwwroot\reporting and give the IIS_IUSRS group the following access:
- Full control on the Uploads folder
- Modify on the Resources folder
- Modify on the Content folder
- Open the Web.Config file in c:\inetpub\wwwroot\reporting and set the following configuration:
- QPulseDatabaseDisplayName – This should be set to the name displayed on the Ideagen Quality Management login screen of the database you wish to report into.
<add key="QPulseDatabaseDisplayName" value="Default"/>
- QPulseUsername – The username of the Ideagen Quality Management user that will be used to submit unauthenticated reports. This user should have the full occurrence access and read access to all other modules (to allow reference list retrieval). If access to occurrence forms is set to use job roles this account must have all relevant job roles applied within the people module.
- QPulsePassword – The password for the above user.
- QPulseAPIEndpoint – This should be configured with the location of the Ideagen Quality Management web services API along with the two endpoints within the client element.
- Authentication Mode – Should be set to ON to enable authenticated mode. To run with unauthenticated mode set to OFF.
- AdminUsers - Ideagen Quality Management usernames with access to the admin area of the portal can be specified in a comma separated list e.g. Admin, ColinD.
- CacheRefreshURL – This URL should be amended to match the virtual directory where Ideagen Quality Management Web Reporting has been deployed. This is required to trigger the cache refresh action of the application.
- If your API is configured for iPad reporting you will need to update the endpoint as follows: address=http://localhost/QPulse5WebServices/services/Occurrence.svc/soap
- If the Ideagen Quality Management web services are not installed on the same machine as the web reporting portal all the endpoints will need to have localhost updated to the IP address or machine name where they reside.
- If the Ideagen Quality Management web services are setup to use SSL the mode attribute on the security elements will need to be changed to Transport e.g. <security mode=”Transport” />
- If multiple instances of Ideagen Quality Management Web Reporting are setup on the same server you should ensure that each has a unique value specified for the name attribute on the forms element. This is to avoid conflicts with authentication cookies. E.g. <forms name=".ASPXAuth_QP1"…
- Test on the server using the URL http://localhost/reporting as this will display any error details in the event of a configuration problem.