QPR Knowledge Base 2016.1

Other Requirements

Other Requirements

Previous topic Next topic No directory for this topic  

Other Requirements

Previous topic Next topic Topic directory requires JavaScript Mail us feedback on this topic!  

See the requirements for different miscellaneous or optional components below:

 

SVG Requirements

 

QPR 2016.1 supports SVG graphics in QPR Portal with Microsoft Internet Explorer (built-in from version 9 onwards) and Mozilla Firefox built-in viewers. However, the built-in SVG is not supported for Microsoft Internet Explorer in the Compatibility Mode.

 

Note that the server computer needs to be set to use the default 100% font size. Larger sizes may cause display issues with SVG views.

 

Note: You can use also Microsoft Silverlight (see requirements below) instead of SVG.

 

 

Silverlight Requirements [Deprecated in release 2016.1.0]

 

QPR 2016.1 supports Microsoft Silverlight. See the table below for notes about browser compatibility:

 

Browser

Supported Versions

Microsoft Internet Explorer 11

Tested with 5.1

 

Note that the server computer needs to be set to use the default 100% font size. Larger sizes may cause display issues with Silverlight views.

 

Note: You can use SVG (see requirements above) instead of Microsoft Silverlight.

 

 

.NET Requirements

 

Microsoft .NET Framework 4.5.1 is required for using QPR Web Services Foundation and QPR Add-In for Microsoft Office 2010/2013. If you select either of the features to be installed and you do not have the framework installed, it is installed during the QPR 2016 installation. However, the .NET Framework installation requires an Internet connection, so without a connection you need to acquire the framework by other means. If you wish to install the framework before installing QPR 2016, you can acquire it from http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=0a391abd-25c1-4fc0-919f-b21f31ab88b7.

 

Microsoft .NET Framework 2.0 or later is required for using QPR Metrics Client and QPR Web Application Server. QPR 2016 installation will install Microsoft .NET Framework 2.0 SP2 if it is not present on the computer and QPR Metrics Client and/or QPR Web Application Server is selected to be installed.

 

 

Office Requirements

 

Using the QPR Add-In for Microsoft Office 2010/2013/2016 requires Microsoft Word 2010, Microsoft Word 2013, or Microsoft Word 2016 and Visual Studio Tools for Office runtime 4.0. The VSTO runtime is installed during the QPR Add-In for Microsoft Office 2010/2013/2016 installation in the case they are not present on the machine.

 

 

VB Script Requirements

 

In the case Visual Basic Scripting (VBScript) is used, the supported version is 1.0.

 

 

OLAP Requirements

 

With OLAP (Online Analytical Processing), only Microsoft SQL Server is supported.

 

 

LDAP Requirements

 

If LDAP (Lightweight Directory Access Protocol) is used for authentication, the following implementations are supported:

Windows Active Directory

OpenLDAP 2.3

 

 

Hard Drive Requirements

 

In order for the installation to succeed, the hard drive should have at least 300 megabytes of free space.

 

 

Integration Kit Requirements

 

Using the QPR Metrics Integration Kit requires that Microsoft SQL Server is used. See more details about the supported versions in the Supported Databases chapter.

 

 

Localization Requirements

 

In multilingual environments you may need to install additional fonts to computers running QPR Modeling Client and/or QPR Metrics Client. On Windows 7 and newer systems the necessary fonts are usually installed by default. This can be done in Control Panel -> Regional and Language Options -> Languages -> Supplemental language support. Note that you will have to reboot the computer after installing the additional language support files.

 

 

 

The system requirements provided herein do not extend to situations where a defect or an error has been recognized in a third party vendor software product listed herein as a supported product. Such errors are e.g. all errors that the third party vendor has acknowledged by releasing a service pack or a new version addressing the issue, or errors which are in some other way publicly acknowledged by the vendor.