Difference between revisions of "QPR UI System Requirements"
| Line 32: | Line 32: | ||
* QPR Suite 2015.1 Web Services accessible in the network | * QPR Suite 2015.1 Web Services accessible in the network | ||
| − | In addition, for installation Microsoft .NET Framework 3.5 or newer needs to be enabled on the target | + | In addition, for installation Microsoft .NET Framework 3.5 or newer needs to be enabled on the target computer. |
| − | computer. | ||
| − | Java Runtime (if it does not already exist) and Glassfish server will be installed by the QPR | + | Java Runtime (if it does not already exist) and Glassfish server will be installed by the QPR MobileDashboard installation, but a working instance of Microsoft SQL Server is needed either locally or accessible via the network in order for the installation to succeed. The following configuration is required |
| − | MobileDashboard installation, but a working instance of Microsoft SQL Server is needed either locally or | ||
| − | accessible via the network in order for the installation to succeed. The following configuration is required | ||
for Microsoft SQL Server: | for Microsoft SQL Server: | ||
| − | * If named instances are used, a TCP port needs to be assigned to the instance and the SQL Server | + | * If named instances are used, a TCP port needs to be assigned to the instance and the SQL Server Browser Service needs to be running |
| − | Browser Service needs to be running | + | * Mixed mode authentication or Windows authentication. Note that for Windows Authentication the user performing the installation also needs to have access to SQL Server even if some other account is used for the actual database connection. |
| − | * Mixed mode authentication or Windows authentication. Note that for Windows Authentication the user | ||
| − | performing the installation also needs to have access to SQL Server even if some other account is used | ||
| − | for the actual database connection. | ||
Revision as of 08:40, 7 October 2016
System requirements are mostly the same as those for QPR Suite 2016.1. An exception is that only Microsoft SQL Server supported as a database. For detailed information, refer to QPR Suite 2016.1 system requirements: http://kb.qpr.com/qpr2016-1/index.html?systemrequirements.htm.
Web browser support:
- Internet Explorer 11
- Firefox for Windows (tested on version 46)
- Mobile Safari 8 and 9
- Google Chrome (tested on version 50)
Note: Due to the rapid update schedule of these web browsers, QPR does not specify any specifically supported version but indicates the latest versions that are tested and verified to work. Firefox and Chrome versions newer than the tested versions are likely to work normally, but QPR cannot guarantee their functionality before the next QPR release
Database support:
- SQL Server 2008 or later
Operating system support:
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7 SP1
- Windows 2012 Server R2
- Windows 2012 Server
- Windows 2008 Server R 2
- Windows 2008 Server
In addition, to connect with QPR Metrics or QPR EnterpriseArchitect/ProcessDesigner, QPR Suite 2015.1.1 or later is needed.
Prerequisites
There are four major dependencies for QPR MobileDashboard:
- Java Runtime
- Glassfish server
- Microsoft SQL Server
- QPR Suite 2015.1 Web Services accessible in the network
In addition, for installation Microsoft .NET Framework 3.5 or newer needs to be enabled on the target computer.
Java Runtime (if it does not already exist) and Glassfish server will be installed by the QPR MobileDashboard installation, but a working instance of Microsoft SQL Server is needed either locally or accessible via the network in order for the installation to succeed. The following configuration is required for Microsoft SQL Server:
- If named instances are used, a TCP port needs to be assigned to the instance and the SQL Server Browser Service needs to be running
- Mixed mode authentication or Windows authentication. Note that for Windows Authentication the user performing the installation also needs to have access to SQL Server even if some other account is used for the actual database connection.