Installing QPR ProcessAnalyzer Server: Difference between revisions
Line 34: | Line 34: | ||
# Implement scheduled maintenance tasks for the database according to SQL Server best practices, e.g. backups and regular defragmenting of indexes. | # Implement scheduled maintenance tasks for the database according to SQL Server best practices, e.g. backups and regular defragmenting of indexes. | ||
== Install Server Roles and Features | == Install IIS Server Roles and Features == | ||
The following '''Server Roles and Features''' should be enabled for '''Microsoft Internet Information Services''' (IIS): | The following '''Server Roles and Features''' should be enabled for '''Microsoft Internet Information Services''' (IIS): | ||
#On the taskbar, click '''Server Manager''', and then click the '''Manage''' menu, and then click '''Add Roles and Features'''. | #On the taskbar, click '''Server Manager''', and then click the '''Manage''' menu, and then click '''Add Roles and Features'''. | ||
Line 49: | Line 48: | ||
#On the '''Confirm''' installation selections page, click '''Install'''. | #On the '''Confirm''' installation selections page, click '''Install'''. | ||
#On the '''Results''' page, click '''Close'''. | #On the '''Results''' page, click '''Close'''. | ||
== Install QPR ProcessAnalyzer Server == | == Install QPR ProcessAnalyzer Server == |
Revision as of 18:35, 8 May 2022
This page describes, how to install .Net 6 -based QPR ProcessAnalyzer.
Introduction
This page describes how to install QPR ProcessAnalyzer Server. Installation steps are:
- See the System Requirements, and acquire a compatible Windows server and SQL Server.
- Setup an SQL Server database.
- Install and configure Roles and Features for IIS.
- Install QPR ProcessAnalyzer Server.
- Activate QPR ProcessAnalyzer server license. The activation occurs online automatically during the server startup if there an internet access. If not, the activation needs to be done manually using the Activation Utility).
- Configure IIS and .Net for QPR ProcessAnalyzer.
- Go through and set settings in QPR ProcessAnalyzer Server web.config file and change them if needed.
- Go through the environment settings stored to the PA_Configuration table and set them if needed.
- Setup the Scripting Sandbox.
- Setup https and certificate to IIS.
- If using Snowflake processing, install the Snowflake ODBC driver and set the SnowflakeConnectionString setting. For more information, see Snowflake Connection Configuration.
Notes:
- If you are updating an existing installation, please follow the update instructions.
- QPR ProcessAnalyzer Server activates itself automatically, if there is an internet connection in the server. If there is no internet connection in the computer where QPR ProcessAnalyzer Server is installed, you need to use manual activation method.
- If you are installing multiple QPR ProcessAnalyzer Server to the same machine, follow instructions in Installing Multiple QPR ProcessAnalyzer Servers. Note that the instances need to be completely separate and use different QPR ProcessAnalyzer database.
- If you have any problems with the installation, check Troubleshooting QPR ProcessAnalyzer Server Installation.
Create and Initialize Database
QPR ProcessAnalyzer needs an SQL Server database for storing data managed by the system. Also another database is needed to run SQL scripts, which is instructed later in section Scripting Sandbox. It's possible to connect to SQL Server either using Windows authentication (Windows account) or SQL Server authentication.
Follow these steps to create and initialize the database:
- Open SQL Server Management Studio and create a new database. You can use for example name QPR_ProcessAnalyzer. You must select <default> for the collation, so that the database collation will be same as the server collation. As QPR ProcessAnalyzer also uses the tempdb (which is using server collation), the collations between the QPR ProcessAnalyzer database and tempdb need to match.
- Create a login in Security > Logins > New Login....
- In the User Mapping tab, assign the login to the QPR ProcessAnalyzer database. For an easy setup, check the db_owner role, or for advanced setup, use the hardened configuration.
- Run database setup scripts initializedb.sql and optimizedb.sql, available in the PA_Deploy.zip package. The initializedb.sql script creates database tables, primary and foreign keys, indexes and default configuration data. The optimizedb.sql script take into use snapshot isolation (https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/sql/snapshot-isolation-in-sql-server) and simple recovery model (https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/recovery-models-sql-server).
- Optionally, increase the Initial Size and Autogrowth settings of the database datafiles for better performance (in Database Properties > Files).
- Implement scheduled maintenance tasks for the database according to SQL Server best practices, e.g. backups and regular defragmenting of indexes.
Install IIS Server Roles and Features
The following Server Roles and Features should be enabled for Microsoft Internet Information Services (IIS):
- On the taskbar, click Server Manager, and then click the Manage menu, and then click Add Roles and Features.
- In the Add Roles and Features wizard, click Next. Select the installation type and click Next. Select the destination server and click Next.
- In the Server Roles section, select the following components:
- Common HTTP Features: Default Document, Directory Browsing, HTTP Errors, Static Content, HTTP Redirection (please do not install WebDAV Publishing because its handler mappings are not directly compatible with QPR ProcessAnalyzer)
- Health and Diagnostics: HTTP Logging
- Performance: Static Content Compression
- Application Development: .Net Extensibility 4.8, Application Initialization, ASP.NET 4.8
- In the Features section, select the following components:
- .Net Framework 4.8 Advanced Services: ASP.NET 4.8
- Windows Powershell: Windows Powershell 5.1 (or newer) (if available)
- On the Confirm installation selections page, click Install.
- On the Results page, click Close.
Install QPR ProcessAnalyzer Server
- If setting up QPR ProcessAnalyzer under the IIS Default Web Site, create a directory C:\inetpub\wwwroot\QPRPA\.
- Extract the contents of the QPR ProcessAnalyzer server installation package to the created directory.
- In IIS Management Console, create an application pool QPRPA (in Application Pools -> Add Application Pool...). Use .NET Framework version 4.0 and set Managed pipeline mode to Integrated.
- Go to Sites and find the web site for QPR ProcessAnalyzer (e.g. the Default Web Site). Select the previously created QPRPA directory and select Convert to Application. In the dialog, select the previously created application pool and also select Enable Preload.
- Make sure that there is an https binding set to the IIS web site for QPR ProcessAnalyzer (found in Edit Bindings...). If you don't have a valid SSL certificate, a self-signed certificate can be used.
- Create a directory C:\ProgramData\QPR Software\QPR ProcessAnalyzer\Logs\ for log files. Note that this directory is later set to the web.config file.
- If data is extracted from SAP using the RFC interface, install the SAP connector.
Installing SAP NetWeaver RFC Library
Extracting data from SAP using the SAP RFC interface requires SAP NetWeaver RFC Library 7.50 which can be installed with the following steps:
- Microsoft Visual C++ Redistributable Package 2013 is required and can be downloaded from https://support.microsoft.com/en-us/topic/update-for-visual-c-2013-redistributable-package-d8ccd6a5-4e26-c290-517b-8da6cfdf4f10. Restart the computer after the Microsoft Visual C++ Redistributable Package installation.
- For storing the SAP NetWeaver RFC Library dll files, create folder C:\SapNwRfcLib (you may also use another location, but do not store the files in the same place as the QPR ProcessAnalyzer Server application files).
- Download and extract SAP NetWeaver RFC Library 7.50 package by following the instructions in https://launchpad.support.sap.com/#/notes/2573790 (SAP login credentials and permissions needed).
- In the extracted files, go to folder nwrfcsdk\lib, and copy all .dll files (icudt50.dll, icuin50, icuuc50.dll, libicudecnumber.dll, libsapucum.dll, sapnwrfc.dll) to the folder C:\SapNwRfcLib.
- Make sure that the dll files are not in the blocked state as follows: Open the each dll files Properties and in the General tab in the Security section, check the Unblocked checkbox (if that checkbox exists). (Downloaded files may be blocked by default by Windows, preventing their code from executing.)
- Make sure that the user account running the IIS application pool for QPR ProcessAnalyzer Server has read access to the folder C:\SapNwRfcLib.
- Include the folder C:\SapNwRfcLib to the Windows PATH environment variable (more information: https://superuser.com/questions/284342/what-are-path-and-other-environment-variables-and-how-can-i-set-or-use-them).
IIS Configuration
All the IIS configurations instructed in this chapter needs to be in place for QPR ProcessAnalyzer Server to work correctly.
Set Application Pool Always Running
- Open Internet Information Services (IIS) Manager and click Application Pools in the left side hierarchy.
- Select QPR ProcessAnalyzer application pool and click Advanced Settings....
- Set (General) > Start Mode to AlwaysRunning. Click OK.
Enable Application Preloading
- Open Internet Information Services (IIS) Manager and in the left side hierarchy under Sites select the QPR ProcessAnalyzer application.
- Click Advanced Settings... on the right pane.
- Set Preload Enabled to True. Click OK.
Disable Application Pool Idle Timeout
When the IIS application pool that runs QPR ProcessAnalyzer Server shuts down, all loaded models are dropped and script running is stopped. By default, idle application pools (i.e. QPR ProcessAnalyzer hasn't been used for some time) are shut down automatically after a certain time. To disable application pool idle timeout:
- Open Internet Information Services (IIS) Manager and click Application Pools in the left side hierarchy.
- Locate QPR ProcessAnalyzer application pool, select it and click Advanced Settings....
- Set Process Model -> Idle Time-out (minutes) to 0. Click OK.
Disable Application Pool Regular Recycling
When the IIS application pool that runs QPR ProcessAnalyzer Server shuts down, all loaded models are dropped and script running is stopped. By default, application pools are restarted (recycled) regularly. To disable application pool regular recycling:
- Open Internet Information Services (IIS) Manager and click Application Pools in the left side hierarchy.
- Locate QPR ProcessAnalyzer application pool, select it and click Advanced Settings....
- Set Recycling -> Regular Time Intervals (minutes) to 0. Click OK.
Disable Application Pool Overlapping Recycle
If using regular application pool recycling, e.g. at specific times, it's recommended to disable the overlapping recycles. When using overlapping recycles, a new instance is started before shutting down the previous, which will take much more memory. Disable the overlapping recycling as follows:
- Open Internet Information Services (IIS) Manager and click Application Pools in the left side hierarchy.
- Locate QPR ProcessAnalyzer application pool, select it and click Advanced Settings....
- Set Recycling -> Disable Overlapping Recycle to True. Click OK.
IIS Application Pool User Profile Loading
To enable user profile loading:
- Open Internet Information Services (IIS) Manager and click Application Pools in the left side hierarchy.
- Click QPR ProcessAnalyzer application pool and click Advanced Settings....
- Set Process Model > Load User Profile to True. Click OK.
The user profile loading allow access to their cryptographic store and environment variables (such as %TEMP%). Additional information can be found from Compatibility Issues with Application Pool Identities.
Disable Application Pool Pinging
Application pool pinging is a mechanism in IIS to monitor that applications are responding normally. In QPR ProcessAnalyzer, application pool pinging may cause issues when there are long running analysis calculations, because during them the application pool might not respond to a ping. As a result, IIS shuts down QPR ProcessAnalyzer application pool (that IIS considers unhealthy), and models are dropped from the memory which degrades performance.
To disable application pool pinging:
- Open Internet Information Services (IIS) Manager and click Application Pools in the left side hierarchy.
- Locate QPR ProcessAnalyzer application pool, select it and click Advanced Settings....
- Set Ping Enabled to False. Click OK.
More information about IIS Application Pool Pinging: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc725836(v=ws.10)