Installation of Report Visualizer

It is required to have an installed .Net Framework 4.0. on the computer where the visualizer will be installed.

Also, perform the following actions for the web interface to function:

• Install Internet Information Services:

  If you are going to install the Report visualizer on the same computer as WebInterface, skip this step

  To do that, open Windows Features:

  • For Windows 10: press Win+R and enter OptionalFeatures in the window and click OK
  • For earlier Windows versions: Start > Control Panel > Programs > Turn Windows features on or off.

  Select Internet Information Services
  
  Enable ASP.NET support:
  
  Now, you need to register IIS for ASP.NET. You can do it using aspnet_regiis.exe registration program. It is located in the NET Framework 4.0 folder, the usual path is: C:\Windows\Microsoft.NET\Framework64\v4.0.30319. See more details on the program on the official site.
  Run aspnet_regiis.exe via the Command Prompt with the -i parameter.
  

If 

Fig. 2. Enabling and disabling Windows features

1. If deployment is performed on the same computer as WebInterface, skip this step. Register IIS for ASP.NET using the registration program (aspnet_regiis.exe) that is in the folder NET Framework 4.0 (Usually this is C:\\Windows\Microsoft.NET\Framework64\v4.0.30319).

(You can also get familiar with it here: http://msdn.microsoft.com/ru-ru/library/k6h9cz8h(v=vs.100)).

For this purpose, launch aspnet_regiis.exe in the console with the specified parameter –i (see Fig. 3):

Fig. 3. Example of launching aspnet_regiis.exe from the console

This is used when installing the selected ASP.NET version and updating the IIS configuration at the root level for the purpose of using this version of ASP.Net.

1. If deployment is performed on the same computer as WebInterface, skip this step.But do not skip it if you use the Deploy (installer). Install the Web Deployment tool (the distribution package can be found in 'deploy' folder of the archive; install it considering your OS bitness. If the package is missing from the archive, download it from the official Microsoft website http://technet.microsoft.com/ru-ru/library/dd569059(v=ws.10).aspx );
2. If you deploy a build, you should copy the r_framearchive contents to the pre-created folder intended for the app. The folder is usually created in the IIS directory: C:\inetpub\wwwwroot\. If you use the Deploy (installer), run the file <BUILD NAME>.deploy.cmd in the console with the specified parameter "/y"
3. Launch the IIS manager from the execution dialog. To do this, proceed as follows:

1) From the Start menu, select sequentially All programs, Standard and Execute.

2) In the Open field, enter "inetmgr", and click "OK" (see Fig. 4).

Fig. 4. The Execute window

In the IIS manager, the application pool should use the .Net Framework 4.0 environment.

Fig. 5. IIS services manager application pool

1. Create an app in IIS.

 

Fig. 6. Creating the WebInterface in IIS.

Double click the relevant website (if required, you create a new website) and select "add the app..." (see Fig. 7. In the window that appears (see Fig. 6), fill in the Alias field (what the app will be called in the browser address bar), the App Pool field and the physical path to the folder containing the app.

 

Fig. 7. Adding the r_frame app to IIS.

1. Launch the website having the web interface in the IIS manager:

Fig. 8. Launching a website from the IIS manager

1. In the process of interaction between the app and the Feature Server, it is periodically required to have access to the directory C:\Windows\Temp. Therefore, you should set access rights to this folder. To do so, right click the folder and select Propertiesin the menu (see Fig. 9). In the window that appears, select the Security tab. Here you should select the user that runs IIS and press the Change button. Next, you grant this user the read\write\change right.

Fig. 9. The Properties window of the directory C:\Windows\Temp

1. Now let us check the web interface operability: open the browser and use the address http://localhost/r_frame(Fig. 10):

Fig. 10. Application Display in Browser.

1. To ensure the correct operation of the report visualizer (r_frame), you should change the settings in the R-Keeper manager section. Go to the menu Extensions->Web Menu. Next, you will see the window containing a report tree. Each report has the URL property (see Fig. 11). It should be changed to the one that matches the URL deployed on your computer. For example, if the r_frame application has the address http://localhost:789/r_framein the IIS settings, this address should be saved in the R-Keeper settings having changed the localhost to your computer IP, i. e. you should save http://192.168.34.123:789/r_frame, for example. To save the settings in R-Keeper, press the floppy disk icon.

Fig. 11. Summary Report Properties in R-Keeper.

1. In the"web.config" file, change the version_plugin parameter (see Fig. 1): set the Feature Server version as its value. If there is a version mismatch error, take the version from the error text and save it as the value of this parameter.

Fig. 12. Changing the Version_Plugin Parameter

* If a report is in a report group (for example, Analytical Reports), it is enough to indicate a url for the group instead of indicating it for each individual group report.

* WebInterface and r_frame can be installed on separate computers.

Possible issues: if Skype is launched, forbid the port 80 for the app. Run it and check it is working properly.

 Configuring Web Interface and Dashboard  Configuring integration with Grafana