Setup reporting service and management web application

You have set up a database, and Bandwidth Splitter has started to write the stats to a database. Now you can install the reporting service, which will produce reports from that data, and also IIS web application for management via web interface.

You should have already chosen the server where these 2 modules will be installed. Make sure Internet Information Services (IIS) and .NET Framework 2.0 are already installed on the server. (In Windows Server 2000/2003, only World Wide Web Service component is required in IIS installation. In Windows Server 2008, open Administrative Tools > Server Manager > Roles. Add role Web Server (IIS), if it is not installed. Also, in this role install ASP.NET, Windows Authentication, and IIS 6 Metabase Compatibility role services.)

Look again into BWStats folder on ISA Server computer where you installed Bandwidth Splitter. There are 2 installation modules: BWReportsSvc.msi and BWReportsWebApp.msi. Copy them to a server where you want to install them, and run one and then another.

Bandwidth Splitter reporting service does not provide you any options during installation, so it is straightforward.

Bandwidth Splitter management web application lets you choose the Site and Virtual directory where it will be installed. Selecting the site is useful if you have several web sites hosted on the server. If you want to install web application into the root of the web site, clear out the Virtual directory field. This will install web application under http://localhost/ instead of http://localhost/BWReports/.

After you install reporting service and web application, use a new link placed on your desktop to open the reports management web interface. Only members of local Administrators group are allowed to access it. If it asks you for authentication, enter valid credentials of account which is a member of local Administrators group.

When you first open this web interface, you will see a message saying you must configure database connection settings before you can manage any reports. Go to Configuration page, and specify the valid database connection settings. Usually they should be the same as the ones you specified in Bandwidth Splitter settings in ISA Management console.

However, if you use MSDE database on ISA Server computer, and you installed the reporting service with management web application on another server, you can’t specify (local)\MSFW as MSDE/SQL Server name here. Instead you should use the server name or IP address in this case, for example: 192.168.0.1\MSFW.

If, on the other hand, you use MSDE and installed the reporting service with management web application on ISA Server computer, use (local)\MSFW as MSDE/SQL Server name.

Note. Specifying the instance name (for example, \MSFW) after server name is required if you use local MSDE database. If you use remote SQL Server, and SQL Server port number is specified (not equal to 0), then it is not necessary to specify SQL Server instance name in "MSDE/SQL Server" parameter.

You can specify 0 as SQL Server port number, for example if your SQL Server is configured to use dynamic ports. Then if you use named instances of SQL Server, you must specify the SQL Server instance name, and SQL Server Browser service must be running.

Use Test button to check that database settings were set up correctly. Then click Apply Changes button to save the settings.

Also on this page you can configure SMTP settings. They are used if you want to send reports via email. However, it is optional, and you can setup it later, if you wish.

Note. If you installed reporting service with management web application on ISA Server computer, and want to use the web interface remotely, don’t forget to configure ISA Server access rules to allow HTTP(S) connections from remote computers to ISA Server.

See also
Using bandwidth usage reports
© BNTC Software. All rights reserved.