Supported Configurations and System Requirements

Note: This product has been discontinued. Technical Guidance ends July 15th 2018.

This document describes Pivotal Web Server supported configurations and system requirements.

Supported Configurations

The following table shows all supported configurations for Pivotal Web Server.

The table indicates if the supported configuration is for production or development. Generally, Production support means you can run your production application on the platform; Developer support means you can develop on the platform but you should not run your production application on it.

Table 1. Pivotal Web Server 6.2 Supported Configurations
Operating System Processor Package Format Production or Developer Support?
Red Hat Enterprise Linux (RHEL) 7

Oracle Linux 7

CentOS 7

x86_64 (64 bit) Self-extracting ZIP (.zip.sfx) or RPM Production
Red Hat Enterprise Linux (RHEL) 6

Oracle Linux 6

CentOS 6

x86 (32 bit), x86_64 (64 bit) Self-extracting ZIP (.zip.sfx) or RPM Production
Red Hat Enterprise Linux (RHEL) 5

CentOS 5

x86 (32 bit), x86_64 (64 bit) Self-extracting ZIP (.zip.sfx) or RPM Production
SUSE Linux Enterprise Server (SLES) 12

SUSE Linux Enterprise Server (SLES) 11

x86_64 (64 bit) Self-extracting ZIP (.zip.sfx) Production
Oracle Solaris 11

Oracle Solaris 10

  • amd64 (64 bit)
  • UltraSPARC III+ (64 bit)
Self-extracting ZIP (.zip.sfx) Production
Ubuntu 16.04 LTS

Ubuntu 14.04 LTS

Ubuntu 12.04 LTS

x86_64 (64 bit) Self-extracting ZIP (.zip.sfx) Production
Microsoft Windows Server 2012 x64 (64 bit only) Self-extracting ZIP (.zip.exe) Production
Microsoft Windows 8+ x64 (64 bit only) Self-extracting ZIP (.zip.exe) Developer

System Requirements

TCP/IPv6 is required on all platforms. Modern platforms have this support installed already. It is not necessary to configure IPv6 adapters; simply install the IPv6 socket support drivers and associated libraries. Vendor OS patch sets recommended for compatibility with the current vendor release of Java should be also be applied for all Pivotal Web Server installations. The operating system flaws that affect sockets and multi-threaded services for Java similarly affect Pivotal Web Server and its support libraries.

Windows PowerShell Requirement

  • You must use Windows PowerShell 2.0 to execute the Pivotal Web Server scripts on Windows computers. Most recent Windows versions have PowerShell installed by default, but some older versions of Windows do not. To check whether your version of Windows has PowerShell installed, go to Start > All Programs > Accessories and check for Windows PowerShell in the list.

    If Windows PowerShell 2.0 is not installed on your Windows computer, download and install it from the Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0) Web page on the Microsoft Support.

  • If necessary, enable Windows PowerShell for script processing; by default, script processing is disabled.

    1. Start PowerShell from the Start Menu as an Administrator by opening Start > All Programs > Accessories > Windows PowerShell, then right-clicking on Windows PowerShell and selecting Run as Administrator. A PowerShell window starts.
    2. Check the current PowerShell setting by executing the following command:

      PS prompt> Get-ExecutionPolicy 
      

      If the command returns Restricted, it means that PowerShell is not yet enabled. Enable it to allow local script processing at a minimum by executing the following command:

      PS prompt> Set-ExecutionPolicy RemoteSigned 
      

      You can choose a different execution policy for your organization if you want, as well as enable PowerShell using Group and User policies. Typically, only the Administrator will be using the Pivotal Web Server scripts, so the RemoteSigned execution policy should be adequate in most cases.