Understanding Intelligence Reporting on Terminal Servers
Intelligence Reporting licensing can be tricky, especially given the different license types and the possible network configurations. In this tip we’re going to look at the case of Citrix and or Terminal Server environments and consider the different options available. This includes Terminal Server, Citrix XenApp / XenDesktop, load balanced and single server environments. We’ll start by describing the different Intelligence Reporting licenses and then take a look at the various scenarios.
Intelligence Reporting uses a workstation licensing model whereby licenses are assigned to machines which need access to the Intelligence Reporting modules. Four license types exist, each giving a different level of access:
| Connector license: | This is a site license and gives all workstations access to the Connector module. It also includes one Report Manager and one Report Viewer license. Additional Report Manager or Report Viewer licenses are required if you would like to launch more instances of those modules simultaneously. |
| Report Manager license: | This is a workstation license and gives access to the Report Manager and Report Viewer. |
| Report Viewer license: | This is a workstation license and gives access to the Report Viewer only. |
| Report Designer license: | This is a site license and will allow all workstations
connected to the Intelligence Repository access to the Report
Designer module. |
Scenario 1 – Single Server Citrix / Terminal Services Environment
In a single server environment, whether Intelligence is included as part of your accounting package (an integrated install) or as standalone, all modules are installed, configured and licensed on the application server. Purchasing a single Connector and Report Designer license is recommended. This will give all users access to the Connector module and Report Designer functionality while allowing one user at a time to access the Report Manager or Report Viewer. If multiple users need to access the Report Manager or Viewer simultaneously then further Report Manager or Viewer Licenses will need to be bought.
Note: In this case, Terminal Services could also be setup on the application server instead of the gateway server.
Scenario 2 – Separate Application and Database Server Citrix / Terminal Services Environment
In this case, whether integrated or standalone, all modules are installed, configured and licensed on the application server. It is recommended that the Intelligence Repository be setup on the database server and that a single Connector and Report Designer license be purchased. This will give all users access to the Connector module and Report Designer functionality while allowing one user at a time to access the Report Manager or Report Viewer. If multiple users need to access the Report Manager or Viewer simultaneously then further Report Manager or Viewer licenses will need to be bought.
Note: Like with the above case, Terminal Services could also be setup on the application server instead of the gateway server.
Scenario 3 – Load Balanced Citrix / Terminal Services Environment
In a load balanced environment, whether integrated or standalone, all modules are installed, configured and licensed on each application server. The Intelligence Repository is setup on the database server. It is recommended that a Connector license and Report Designer license be purchased for each server that Intelligence Reporting is installed on. This will give all users access to the Connector module and Report Designer functionality regardless of the application server they connect to. This will also ensure that one user at a time can access the Report Manager or Report Viewer regardless of the server they connect to. To allow multiple users to access the Report Manager or Viewer simultaneously then further Report Manager or Viewer licenses will need to be bought for each application server in the environment. It is recommended that the same number of licenses be bought for each.
Note: As with the above cases, Terminal Services could also be setup on each application server instead of the gateway server.
Related Articles
Sharing Report Shortcuts using Intelligence Reporting
Problem When you create a report shortcut, it creates and points to a file within the AppData directory of the user that created the shortcut, which in turn points to the BICore.exe on the machine. When another user tries to run the report shortcut, ...Downloading and Installing Intelligence Reporting
1. Download Intelligence Reporting To download your version of Sage Intelligence, visit our website and choose the appropriate version. a) Visit our website here: https://www.alchemex.com.au/intelligence-reporting/#alchemextrial b) Choose the ...Replicating Auto-Connection Details on Terminal Server Profiles
Problem: You are trying to replicate the auto-connection details on load balanced terminal servers or across multiple user profiles without requiring to send out all the details to the users. Solution: Configure the auto-connection on an ...Does Intelligence Reporting and CData support TLS 1.2?
Question A recent upgrade from Microsoft has marked End of Life for TLS 1.0 and 1.1. I am using Intelligence Reporting and/or Cdata drivers selled by Alchemex and need to upgrade my servers. How will it affect my Reporting? Support for Intelligence ...Using Velixo Reports in Citrix/Terminal Server enviroments
Overview This is a best practices guide for installing and configuring Velixo Reports in a Citrix or Terminal Server environment. The document applies to standalone Citrix/Terminal servers and to Citrix server farms. MSI-Based Installation ...