How To Install Q-Pulse Web Reporting

Prerequisites: 

• Q-Pulse v5.95 (or higher)  installed
• Q-Pulse licence file with Web Reporting enabled
• Q-Pulse Web Service API should be installed and configured as per the relevant installation guide.
• IIS 7 or greater with ASP.NET v4 installed
• Web Reporting content ZIP file downloaded

Installation steps:

1. Extract the contents of the zip file into c:\inetpub\wwwroot\reporting
2. Run Internet Information Services (IIS) Manager
3. Right click on Application Pools> Add Application Pool…

4. Type “WebReportingAppPool” into the Name box and choose .NET Framework version 4 and Integrated pipeline mode. Click OK.

5. Under the Default Web Site right click the 'reporting' folder and Convert to Application

6. Select the WebReportingAppPool then Ok
7. 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

8. 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 Q-Pulse login screen of the database you wish to report into.

• QPulseUsername – The username of the Q-Pulse 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 Q-Pulse 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 - Q-Pulse 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 Q-Pulse 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 Q-Pulse 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 Q-Pulse 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 Q-Pulse 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"…

9. Test on the server using the URL http://localhost/reporting as this will display any error details in the event of a configuration problem.