PMWeb Installation Requirements

Typical installation requirements for PMWeb are as follows:

External URL

An external Web URL is required to license PMWeb. (IP addresses will not be licensed)

Operating System Software

Microsoft® Windows Server 2008 R2 or Windows Server 2012

Database Software

Microsoft® SQL 2008 R2 or Microsoft® SQL 2012
Microsoft® SQL 2014
Microsoft® SQL 2016 (in beta) - check for latest approved versions for use with PMWeb
Must be installed using the default collation: SQL_Latin1_General_CP1_CI_AS. Analysis Services collation must match

Reporting Software

Microsoft® SQL Report Server (Included with SQL)

Microsoft Visual Studio

Visual Studio (check for approved versions) must be available on the network for installations where all data is to be retained at the client site

Internet Information Services (IIS)

Enable .Net 4.5
Enable IIS Management Console
Enable All Application Development Features (.NET Extensibility, ASP, ASP.NET, etc...)

Internet Connection - One of the following:

DSL/Cable
Fibre Optic
T1 /T3

Microsoft Internet Explorer is not required as a web browser, but the IE system files must be present in order to install Microsoft Data Access Components (MDAC).

Installation options

The installation options are:

Physical-only infrastructure
Physical/Virtual Hybrid infrastructure
Virtual-Only infrastructure

In each case the actual number of Users that can be served by the system depends on the number of CPUs, CPU speed, memory, etc.

Physical-only infrastructure

The web-code is installed on dual quad-core CPUs with RAID storage, load balanced using either hardware load-balancers or the Network-Load-Balancing capabilities of the Windows OS.

The MSSQL back-end is run on dual quad-core CPUs with RAID or shared storage using SQL-Based clustering for high-availability and load-balancing.

Physical/Virtual Hybrid infrastructure

The web-code is installed in Virtual Machines running on dual quad-core CPUs with RAID storage, load balanced using either hardware load-balancers or the VMWare/Microsoft Virtual infrastructure loadbalancing / failover capabilities (i.e.: vMotion).

The MSSQL back-end is run on dual quad-core CPUs with RAID or shared storage using SQL-Based clustering for high-availability and load-balancing.

Virtual-Only infrastructure

The MSSQL back-end is run in Virtual Machines running on dual quad-core CPUs with RAID or shared storage using SQL-Based clustering for high-availability and load-balancing. A SAN is recommended for this scenario. The interface recommended is Fibre or FCOE.