1. Introduction
   
   
2. Requirements
   
   
3. Important Note for Customers Upgrading
   
   
4. Installing the Web Reports Module
   
   
5. Configuration
   • Configuring the Web Reports Administration Console
   • Configuring the IIS Session Timeout
   • Configuring the Report Scheduler Service Controller
   • Configuring the SupportDesk Setup Console
   • Report Settings
   • Navigator Reports
     
     
6. Running reports from SupportDesk
   
   
7. Using the Web Reports Module
   • Logging In
   • The Main Window
     • Quick Reports View
     • User Defined Reports View
     • Report Templates View
     • Report Scheduling View
   • Adding a New User-Defined Report
   • Loading a Report
   • Exporting a Report
   • Printing a Report
     
     
8. Scheduling Reports from the Web Reporting Module
   • Report Scheduling – Step by Step Instructions
     • Add Report
     • Configure Report
     • Specify Report Criteria
     • Specify Navigator (CMDB) Criteria
     • Schedule the Report
   • Editing, Deleting and Cloning Tasks
     
     
9. Scheduling Reports from the Setup Console
   
   
10. Customising the Web Reports Module
    
    
11. Modifying a Report’s SQL query
    
    
12. The Error Console
    
    
13. Crystal Reports Compatibility
    
    
14. Recent Report Additions

Configuring the Web Reports Administration Console

The web reports module shares the same initial setup application as the SupportDesk Self Service Portal. This application is used to configure the initial database connectivity for the application and in the case of the web reports module, the path to the SupportDesk report template directory. This directory contains the distributed Crystal Reports (.rpt) files and can be placed anywhere on your network providing that the chosen web server has read access to it.

Note: There are separate settings for the Self Service Portal and Web Reporting Module (circled below).

Figure 1: Web Reports Administration

Figure 2: Self Service Portal Administration

To configure the settings for the Web Reporting Module:

1. Click on Start à All Programs à Richmond Systems à SupportDesk Web Interfaces à Self Service Portal à Self Service Portal & Web Reports Administration

2. The Web Admin application will appear. At this point, the main options will be disabled as you are required to browse for the web reports modules’ configuration file called Web.config. This is an XML file which contains all application settings for the system.
   
   Note
   the application will attempt to load Web.config automatically when it is started. If this does not happen then the file can be found in the root directory of the web reports website (i.e. C:/InetPub/wwwroot/… )

3. In the Database Connection Settings frame, enter the required SQL Server and database name.
   
   
4. Click on the Test button. If the test is successful; you will receive a confirmation message. In the event that you receive an error, you must ensure that you have entered a valid SQL Server and database name and that the machine you are attempting to connect from is able to connect to the required SQL Server database.
   
   
5. The Advanced Database Options allow you to fine-tune the database connection pool and should only be changed if you are expecting more than 100 concurrent users to be connected to the system simultaneously. If this is the case, you should increase the value of the Maximum Pool setting by the required amount.
   
   Warning
   Setting the Maximum Pool to a value which is too low could result in users experiencing database connectivity problems and so it is recommended that the default value of 100 is used for most installations.
   
   
6. Once you are satisfied with the settings, click on the Save button to update the configuration file and exit the application.
   
   Note
   The settings specified with the Web Admin application are only loaded when the Web Reports Module is started. If changes are made whilst the web application is running then it will be necessary for you to restart it before the new settings are applied. This will cause any active user sessions to be lost.

Configuring the IIS session timeout >>>