Pega 7: Platform Support Guide
Pega 7: Platform Support Guide
Pega 7: Platform Support Guide
September 2019
© 2019
Pegasystems Inc., Cambridge, MA
All rights reserved.
Trademarks
For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All other trademarks or service
marks are property of their respective holders.
For information about the third-party software that is delivered with the product, refer to the third-party license
file on your installation media that is specific to your release.
Notices
This publication describes and/or represents products and services of Pegasystems Inc. It may contain trade
secrets and proprietary information that are protected by various federal, state, and international laws, and
distributed under licenses restricting their use, copying, modification, distribution, or transmittal in any form
without prior written authorization of Pegasystems Inc.
This publication is current as of the date of publication only. Changes to the publication may be made from
time to time at the discretion of Pegasystems Inc. This publication remains the property of Pegasystems Inc.
and must be returned to it upon request. This publication does not imply any commitment to offer or deliver
the products or services described herein.
This publication may include references to Pegasystems Inc. product features that have not been licensed by
you or your company. If you have questions about whether a particular capability is included in your
installation, please consult your Pegasystems Inc. services consultant.
Although Pegasystems Inc. strives for accuracy in its publications, any publication may contain inaccuracies or
typographical errors, as well as technical inaccuracies. Pegasystems Inc. shall not be liable for technical or
editorial errors or omissions contained herein. Pegasystems Inc. may make improvements and/or changes to
the publication at any time without notice.
Any references in this publication to non-Pegasystems websites are provided for convenience only and do not
serve as an endorsement of these websites. The materials at these websites are not part of the material for
Pegasystems products, and use of those websites is at your own risk.
Information concerning non-Pegasystems products was obtained from the suppliers of those products, their
publications, or other publicly available sources. Address questions about non-Pegasystems products to the
suppliers of those products.
This publication may contain examples used in daily business operations that include the names of people,
companies, products, and other third-party publications. Such examples are fictitious and any similarity to the
names or other data used by an actual business enterprise or individual is coincidental.
Pegasystems Inc.
One Rogers Street
Cambridge, MA 02142-1209
USA
Phone: (617) 374-9600
Fax: (617) 374-9620
www.pega.com
Pega Platform
Our expectation is that Pega Platform can be deployed successfully in tandem with any
combination of environmental and infrastructure components from this document – including
hybrid heterogeneous combinations of dissimilar servers. It is also our expectation, gained from
experience, that with such deployments there are many details to take into consideration, and
that the first such deployment should only be undertaken by experienced engineers who have
the necessary skills to ensure smooth and complete installation and reliable and performant
operation.
In addition:
2. Pega Platform and applications built on it are designed to run on any combination within
each category of the published Platform Components in the Platform Options section,
including a mixed deployment of different application server, database, or browser
technology. Consult your Pegasystems representative to determine whether the desired
platform combination has been deployed in production before, and to discuss risk
mitigation strategies.
3. To obtain new features and capabilities, customers may be required to upgrade to newer
versions of Pega Platform products, which may have different or additional prerequisites.
Note also that updated versions of Platform Components (including bug fix releases of
such Components) may themselves impose different or additional prerequisites.
4. Pegasystems will make commercially reasonable efforts to offer support in its products
for a new release or version of the Platform Components listed in this document, within
12 months of that version becoming Generally Available (as differentiated from an alpha
or beta version of the product). This support will normally be made available in a new
release.
If you choose to upgrade Platform Components to the latest releases, but want to stay on
older releases of Pega Platform, you may enter support requests for any problems
encountered. However, if the root cause of these problems stems from the fact that the
older versions of PRPC were not designed to handle functionality in the newer
Components, Pegasystems may request that you upgrade your PRPC version to a Pega
Platform release that directly supports that newer Component, as listed in this Guide.
Pegasystems Inc. will support customers who run Pegasystems Inc. products on supported
Operating Systems, irrespective of whether they are running in virtualized environments or not.
Virtualization vendor products support a set of certified Operating Systems and Hardware, and
the customer and vendor will be responsible for any interactions or issues that arise at the
Hardware or Operating System layer as a result of their use of such products.
Pegasystems Inc. will not require clients to recreate and troubleshoot every issue in a non-
virtualized environment; however, Pegasystems Inc. does reserve the right to request our
customers to diagnose certain issues in a native certified Operating System environment,
operating without the virtual environment. Pegasystems Inc. will only make this request when
there is reason to believe that the virtual environment is a contributing factor to the issue.
Any time spent on investigation of problems that may, in the sole opinion of Pegasystems Inc. be
related to a virtualization product, will be handled in the following fashion:
1. Pegasystems Inc. will provide standard support to all Pegasystems Inc. products.
3. Regardless of the problem type or source, time spent on investigation and resolution will be
covered as part of regular maintenance, and support will be provided as usual.
• The following Platform Options have all been tested by Pegasystems in at least one
combination; however, not every combination of all of these options has been tested.
• Any compatible combination should work; but there may be specific setup or configuration
requirements for a particular combination.
• Not all features may be available on all platforms.
• Decision Strategy Manager (DSM) supports all the platforms supported by Pega Platform –
except for WebSphere “classic” on z/OS or WebSphere Liberty on z/OS.
• Some Industry Applications have refinements on the list of platforms in this Guide.
For specific details, please reference the Installation Guides/Release Notes on the PDN for
the application in question.
Please contact your Pegasystems representative if you have questions about any option.
Server Hardware
IBM System p (“pSeries”) or IBM Power Systems
IBM Mainframe System z (“zSeries”) with zAAP, zIIP processor 1 or IFL (Integrated Facility
for Linux)
Wintel (with Intel or compatible chip – includes IBM System x and Lenovo System X)
1
Requires a minimum of one IBM System z Application Assist Processor (zAAP) or IBM System z Integrated
Information Processor (zIIP). Consult the installation guide and PDN for the latest set-up options.
NOTE: These databases are not supported for the main relational database for the Pega Platform, but should
only be used for DDS data sets.
Cassandra 2.1.14 is included in the Pega Platform, and is supported as an “internal” setup with the Decision
Data Store dataset type.
Alternatively, if customers already have a Cassandra cluster (“external” setup), that can be used instead of the
internal shipped database. For an external setup, Pega applications can connect to any Cassandra version
higher than 2.1.
Load Balancers
F5 BigIP versions 10.x.x, 11.x.x 2
Beginning in Pega Platform, production systems may take advantage of high-availability features.
Customers using this high-availability functionality must use a load balancer that supports:
• session affinity
• pool management (enable, disable, remove servers)
• server monitoring for crash detection
For details, please refer to the High Availability guide on the PDN.
Cloud Deployments
Pega Cloud
Pega Cloud provides industry-leading infrastructure, enterprise-grade services, and operational
excellence for Pega Platform Platform and strategic application solutions in the cloud. For details
on the Pega-managed cloud solution, please see the Pega Cloud landing page on the PDN.
2
Must include the Local Traffic Manager (LTM) module
• Microsoft Azure
For details on all the Cloud Choice options, please see the Cloud Choice article on Pega
Community.
Operating systems
Pega Pega Pega
Pega 7.2 7.2.1 7.2.2 Pega 7.3 7.3.1 Pega 7.4
(Feb 8, (Jun 27, (Dec 6, (Jun 30, (Oct 16, (April 13, IMPORTANT
2016) 2016) 2016) 2017) 2017) 2018) NOTES
See important note
about Pega Applications
IBM AIX v7.1 supported supported supported supported supported supported below.
Oracle Enterprise
Linux v7 supported supported supported supported supported supported
Oracle Solaris 10
(SPARC and Intel
edition) supported supported supported supported supported supported
Oracle Solaris 11
(SPARC and Intel
edition) supported supported supported supported supported supported
Microsoft
Windows 2008 supported supported supported supported supported supported
Microsoft
Windows 2012 supported supported supported supported supported supported
• The websites of Platform Options vendors may contain additional information about how they
work with other hardware or software options on this list. If vendors state a particular
combination will not work or is not supported, that combination will not be supported by
Pegasystems.
• Applications built on Pega Platform may not function correctly if run on platforms which are not
approved for Pega Platform.
• Prior versions of Pega Platform may not work with the most recent Platform Options.
• Pegasystems Strategic Applications may not yet be certified on Pega Platform. Please reference
the System Requirements for Pegasystems Solution Frameworks and Product Components
document on the PDN for product details.
Application Servers
Requires Fixpack
Version 8.5.5.2 or later
to avoid Java Verify
errors when using Java
7. Please see Known
Issues with JVMs.
IBM WebSphere 9
(Classic)
(using IBM Java 8) supported supported
IBM WebSphere
Liberty v16.0.0.4
(using IBM Java 8) supported supported
IBM WebSphere
Liberty v17.0.0.3
(using IBM Java 8) supported
IBM WebSphere
Liberty v18.0.0.1
(using IBM Java 8) supported
Oracle WebLogic
Server 11g
(10.3.6 and
higher) (using
Oracle Java 6 or 7) supported supported
Oracle WebLogic
As of Pega 7.4, Java 7 is
Server 12c
no longer supported, so
(12.1.2) (using this application server is
Oracle Java 7) supported supported supported supported supported no longer supported.
Oracle WebLogic
Server 12c R3
(12.1.3) (using
Oracle Java 7 or 8) supported supported supported supported supported supported
Oracle WebLogic
Server 12.2.1
(using Oracle Java
8) supported supported supported
• None of the “Community Editions” of these application servers (such as JBoss or WebSphere)
have been tested with Pega Platform; therefore, these “Community Editions” are not supported
with Pega Platform.
• Beginning in Version 7.4, the Pega Platform will no longer support Java 7, so the following
application server versions will no longer be supported:
− IBM WebSphere 8.5
− Oracle WebLogic Server 12c (12.1.2)
− JBoss Redhat EAP 6.1.x
− JBoss Redhat EAP 6.2.x
− JBoss Redhat EAP 6.3.x
− JBoss EWS (Enterprise Web Server) v2.0
supported supported
for WAR for WAR
PostgreSQL 9.1.x installations installations
Community Edition only only
Postgres Plus
supported supported supported supported supported supported
Standard Edition
for WAR for WAR for WAR for WAR for WAR for WAR See important
(Enterprise DB) installations installations installations installations installations installations PostgreSQL notes
9.3.x only only only only only only below.
Postgres Plus
supported supported supported supported supported supported
Standard Edition
for WAR for WAR for WAR for WAR for WAR for WAR See important
(Enterprise DB) installations installations installations installations installations installations PostgreSQL notes
9.4.x only only only only only only below.
Postgres Plus
supported supported supported supported
Standard Edition for WAR for WAR for WAR for WAR See important
(Enterprise DB) installations installations installations installations PostgreSQL notes
9.5.x only only only only below.
supported supported supported
for WAR for WAR for WAR See important
PostgreSQL 9.6.x installations installations installations PostgreSQL notes
Community Edition only only only below.
Postgres Plus
supported supported supported
Standard Edition
for WAR for WAR for WAR See important
(Enterprise DB) installations installations installations PostgreSQL notes
9.6.x only only only below.
Amazon Aurora
PostgreSQL 9.6.x supported
Microsoft
SQL Server 2012 supported supported supported supported supported supported
For Pega 7.2.2 and prior:
Adaptive Decision
Manager (ADM – an
optional module of
DSM) is not supported
on SQL Server. (In 7.3,
ADM is no longer
separately deployable,
so it will support
Microsoft whatever the Pega 7
SQL Server 2014 supported supported supported supported supported supported Platform supports.)
Microsoft
SQL Server 2016 supported supported supported
For details on using
Microsoft Azure, please
see the Deploying Pega
Platform on Microsoft
Microsoft Azure Azure article on the
SQL database supported supported supported PDN.
1. Please note: none of the “Express” or “Personal” versions of these databases have been tested
with the Enterprise version of Pega Platform; no express/personal version of a database is
supported with Pega Platform.
2. IBM has announced the end of support for Db2 for LUW version 10.1 as of September 30, 2017:
http://www-01.ibm.com/support/docview.wss?uid=swg22001885 Therefore, beginning
in Version 7.4, Pega Platform will no longer support this version of the database.
3. IBM has announced the end of support for Db2 for z/OS version 10 as of September 30, 2017:
http://www-
01.ibm.com/software/support/lifecycleapp/PLCDetail.wss?synkey=Z736916P90323T50-
N374421N08939B79-A375709J95876F78 Therefore, beginning in Version 7.4, Pega
Platform will no longer support this version of the database.
4. PostgreSQL is only supported for the Tomcat webserver, or JBoss with WAR installations only.
6. PostgreSQL version 9.6.1 requires the latest PostgreSQL JDBC driver to avoid issues - this
should be postgresql-9.4-1212.jar or later.
Java Versions
When running
WebSphere on z/OS in
Java SDK 8 Pega 7.2.1, the z/OS
DB2 jar db2jcc4.jar must
(WebSphere Liberty)
be at level 4.19.56 or
(7.2.1 only – higher (prior levels do
WebSphere 8.5.5.9) supported supported supported supported supported supported not work).
Notes on Java Virtual Machines (JVMs): Pega Platform requires Java to be installed on the
application server.
1. Pega Platform requires the use of the Java 7 or Java 8 specification (depending upon the version
of Pega Platform, as shown in the charts above). Each of the Java vendors will routinely issue
maintenance that addresses security, performance, and stability issues in the JDK.
Pegasystems recommends that this maintenance be applied on a periodic basis; customers’
JDKs should never be more than a year behind current JDK maintenance levels.
2. The last public release of Java 7 is Oracle Java 7 update 79 – 7u79 (subsequent updates are
available if a support offering is purchased from Oracle). All users of Java 7 should have update
79 or a later paid support update.
4. Oracle stopped providing public updates to Java 6 in February 2013. Therefore, beginning in
Pega Version 7.1.7, Oracle Java 6 is no longer supported by Pega Platform.
5. Beginning in Pega 7.2.1, IBM Java 6 is no longer supported by Pega Platform. This means that
the WebSphere 7.0 and 8.0 application servers will no longer be supported, and other
application servers using IBM Java (such as Websphere 8.5 and 8.5.5) will only be supported on
IBM Java 7 (or IBM Java 8, if that is supported by the application server).
6. Pega Platform recommends 64-bit JVMs on the platforms your application server supports.
Please refer to the support matrix of your application server, and choose one of the Java
versions supported by both your application server and Pega Platform.
7. When installing Pega Platform on a server with a 64-bit operating system, be sure to install the
64-bit JVM.
8. Pegasystems recommends that your verbose GC options be enabled, even in production (this
adds negligible overhead).
9. For WebSphere, use the latest approved JVM provided by IBM for that version and patch level of
the application server (unless it is specifically stated that it does not run with Pega Platform). Be
For IBM WebSphere Network Deployment, the Deployment Manager, the Node Agent, and the
application servers must all be on the same IBM JDK.
10. For WebLogic, Pega has tested both “Hotspot” (Sun/Oracle) JVM and JRockit; either may be used.
11. Tomcat does not bundle a JVM in its application. Pega recommends using either Oracle or IBM
Java 8, at the Java vendor’s latest patch level (unless it is specifically stated that that patch level
does not run with Pega Platform).
12. JBoss does not bundle a JVM in its application. Pega recommends Oracle Java 8, at the latest
level (unless it is specifically stated that that level does not run with Pega Platform).
13. The amount of additional memory required for DSM services (what is required in addition to the
recommendations for Pega Platform, found in the Install Guides) will depend upon your
application’s use of ADM and VBD. Contact Pega Support for specialized sizing
recommendations.
14. Per IBM, when using the Windows platform, the IBM JDK will only support the WebSphere
application server. On the Windows platform, use an Oracle JDK for all application servers
other than WebSphere.
Existing Pega Platform systems running earlier versions of WebSphere can avoid the risk by
turning on a JIT switch for Idiom Recognition. The JVM argument is:
-Xjit:disableIdiomRecognition
2. IBM reported a bug with IBM Java 7 version 1.7.0 SR2: http://www-
01.ibm.com/support/docview.wss?uid=swg1IV30057 This issue manifests as a “Wrong
Method Type Exception” error in the Service Wizard.
Do not use SR2. All IBM Java 1.7.0 users should be on SR3 or later.
The following are issues with WebSphere and the IBM Java versions. To avoid these issues, new
installs of Pega Platform should use the following WebSphere Fixpack versions (or later) available from
IBM:
*Pega 7.1.7 will require WAS 7 fix pack 25 and above. Due to a bug in older versions of
WebSphere, the introduction of Elasticsearch causes WAS 7 to fail on startup: http://www-
01.ibm.com/support/docview.wss?uid=swg1IZ67813
**The version of Java 1.7 shipped with WebSphere 8.5.5.1 reports a Java Verify error when
loading classes for assembled rules. This appears to be related to an Eclipse bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=381172
The VerifyError does not appear to occur with the Java 1.7 SR6 release. See also:
https://www.ibm.com/developerworks/community/forums/html/topic?id=7f616d94-a4ec-
4e32-9ccc-3406ee063a6f
Operating Systems
Developer Client Pega Pega Pega IMPORTANT
Software - OS Pega 7.2 7.2.1 7.2.2 Pega 7.3 7.3.1 Pega 7.4 NOTES
NOTE: Touch-screen-based laptops are not supported for Pega Platform until Pega 7.2.1.
End-User Browsers
1. Pega Platform is certified on the latest version of these supported browsers at the time a given
version of Pega Platform is released. Reasonable efforts are made to test previous versions of
the browsers. If you have an issue with Pega Platform guardrail-compliant UI in a particular
version of a supported browser type, please contact Pega Support, and we will make
commercially-reasonable efforts to resolve the issue.
2. Internet Explorer 64-bit browsers are supported beginning with Pega 7.1.5.
3. Beginning in Pega 7.3, ActiveX controls are deprecated (see Microsoft Client Side Technologies
Support section below). You should migrate to HTML5-based solutions for increased
performance, better security, and reduced compatibility issues.
Limited support will be provided for issues with ActiveX, although several compatibility issues
cannot be addressed. For details, please see the PDN article Deprecation of Microsoft ActiveX
controls in the Pega Platform.
4. Microsoft® ended support for Internet Explorer 9 and 10 (IE9 and IE10) in January 2016.
Instead, Microsoft points customers to more recent browsers, like Internet Explorer 11. See
https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support for more
information.
For full details on Pega’s support for Internet Explorer browsers, please see Support for Internet
Explorer (IE) V11 on the PDN.
6. Version 42.0 of the Google Chrome browser blocks Silverlight (an NPAPI plugin) by default. (For
details on which Pega tools are affected by Silverlight, please see the PDN article Client-side
technologies in Pega 7.2.1.) For details on re-enabling Silverlight, see
https://support.microsoft.com/en-us/kb/3058254 .
Chrome version 45.0 or later fully removes Silverlight support – use IE, Firefox or Safari instead.
See http://www.chromium.org/developers/npapi-deprecation for more information; also,
please reference the PDN article End of support for Netscape Plugin API in Google Chrome 45.
8. The System Management Application (SMA) will only work with Microsoft Internet Explorer. No
other browser is supported.
As of May 2017, all ActiveX controls in Pega Platform are marked as "deprecated." A deprecated
control will continue to "work" (assuming no other changes are introduced on the customer's
Windows desktop), but they should not be used, and technical support for issues related to these
controls will be limited. Here’s why:
Compatibility risks
While Pega 7.3 ActiveX controls will still run in IE11, you may experience compatibility issues
between these ActiveX controls and the newest software on your desktop, such as Windows 10
or Microsoft Office 365. If your Pega application relies on ActiveX, you may wish avoid
upgrading to Windows 10 or Office 365.
Security risks
ActiveX controls contain significant security vulnerabilities and are no longer supported in the
Microsoft Edge browser on Windows 10. Pega strongly recommends that customers migrate
ActiveX-based functionality towards HTML5-based, cross-browser solutions.
For details, please see the PDN article Deprecation of Microsoft ActiveX controls in the Pega
Platform.
Microsoft has committed to supporting Silverlight 5 through October 2021. There are several
optional runtime features that leverage Microsoft Silverlight technology (NPAPI plugins) and
these will continue to be supported. (For details on which Pega tools are affected by Silverlight,
please see the PDN article Client-side technologies in Pega 7.3.)
Flash Support
Adobe is planning to end-of-life Flash, and will stop updating and distributing the Flash Player at
the end of 2020. https://theblog.adobe.com/adobe-flash-update/ The Pega Platform team will
replace or remove all the Flash-based developer productivity tools in the Pega Platform in a
future release. These tools include Reference Rules, the Declarative Network Analyzer, and a few
other charts accessible from the Designer Studio. This work will be done before Adobe officially
ends support for the Flash Player in 2020.
DESIGNER
STUDIO/
DEVELOPER Pega Pega Pega IMPORTANT
PORTAL Pega 7.2 7.2.1 7.2.2 Pega 7.3 7.3.1 Pega 7.4 NOTES
See Important Browser
Note #5 below for IE9 &
IE10.
1. We support current and future versions of Safari, Chrome, and Firefox to the extent possible.
Pega will make reasonable efforts to continue to support future versions of each browser –
barring any major architectural or backward compatibility changes from the browser vendors,
we will support users on those platforms.
2. In Pega versions prior to 7.1, Designer Studio functionality depended entirely on Internet
Explorer browsers. Starting with Pega 7.1, the vast majority of development activities can be
accomplished using Chrome, Firefox, or Safari. A few optional features continue to require
Internet Explorer. For a complete listing of these features, please refer to the following article
on the PDN: Client-side technologies in Pega 7.3
4. Version 42.0 of the Google Chrome browser blocks Silverlight (an NPAPI plugin) by default. (For
details on which Pega tools are affected by Silverlight, please see the PDN article Client-side
technologies in Pega 7.3.) For details on re-enabling Silverlight, see
https://support.microsoft.com/en-us/kb/3058254 .
Chrome version 45.0 or later fully removes Silverlight support – use IE, Firefox or Safari instead.
See http://www.chromium.org/developers/npapi-deprecation for more information; also,
please reference the PDN article End of support for Netscape Plugin API in Google Chrome 45.
5. Microsoft® ended support for Internet Explorer 9 and 10 (IE9 and IE10) in January 2016.
Instead, Microsoft points customers to more recent browsers, like Internet Explorer 11. See
https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support for more
information.
For full details on Pega’s support for Internet Explorer browsers, please see Support for Internet
Explorer (IE) V11 on the PDN.
7. The System Management Application (SMA) will only work with Microsoft Internet Explorer. No
other browser is supported.
Starting with Pega 7.1.8, Designer Studio integration points with Microsoft Office have been
steadily replaced with simple import/export paradigms that don’t require ActiveX or Silverlight.
Specific areas of Designer Studio may behave differently based on your exact version of Pega.
For details on which tools are affected and the required third-party components, please see the
PDN articles below.
Note on Office 365: There are two different types of Office 365 that are available:
• Click-to-install
• Click-to-run
Click-to-install is the traditional “InstallShield wizard” installation that most users are familiar
with – they click on an installation file, and Office is installed on their local desktop. Click-to-
install is supported by Pega Platform applications.
Click-to-run is a new Microsoft virtualization technology that helps users run multiple (usually
older) versions of Office on the same computer. Click-to-run is not supported by Pega
Platform applications.
Microsoft Visio
Beginning in Version 7.1, Microsoft Visio will no longer be used for flow editing. For customers
upgrading older versions of PRPC who have flows created in Visio, the first time those flows are
edited, they will automatically be upgraded to use Process Modeler, and will save as Process
Modeler flows.
Visio is still required for Entity Relationship Diagrams. In versions of Pega Platform prior to Pega
7.1.8, Visio is required to generate and also view ERDs. For supported versions of Microsoft Visio,
please reference the Legacy Support chart below.
In Pega 7.1.8 and later, documentation generation is being done on the server, which creates
.vdx files. This type of file can be viewed by a Visio Viewer, and does not require a full Visio
installation (although that will work). Any version of Visio Viewer which supports the .vdx file
format can be used.
NOTE: Due to the large number and diversity of physical Android devices on the market, it is not
possible to test each and every device. This matrix is intended to be a guide, rather than an
exhaustive list of supported devices. Your experience on your mobile device may differ from
results indicated in this matrix.
1. User interfaces built using layouts that use the new "Flexbox" setting will not render
correctly in the Pega Mobile Client running on Android versions prior to 4.4. This issue
does not occur on the Chrome browser on these versions of Android.
2. Windows 10/Client for Windows supports desktop, laptop, and tablet devices running x86
and x64 Windows 10.
3. In Pega 7.3, you can build a deployable binary inside our hosted server for Pega Mobile
Client, but this is not yet supported for Client for Windows. If you want to build a
deployable binary for Client for Windows, please contact your Pega representative for
help in doing this manually, or reference the PDN article Building a Pega Client for Windows
Application.
Decision Strategy Manager (DSM) supports all the platforms supported by Pega 7 – except SQL Server, as
noted.
Some Industry Applications have refinements on the list of platforms in this Guide. For specific details, please
reference the Release Notes on the PDN for the application in question.
Please contact your Pegasystems representative if you have questions about any option.
Server Hardware
IBM System p (“pSeries”)
IBM System x (“xSeries”)
Lenovo System x (“xSeries”)
IBM Mainframe System z (“zSeries”) with zAAP, zIIP processor 3 or IFL (Integrated Facility
for Linux)
Oracle Sun Server (SPARC and Intel processors)
Wintel (with Intel or compatible chip)
HP 9000 series
HP Integrity servers (Itanium)
Cisco Unified Computing System (UCS)
Load Balancers
F5 BigIP versions 10.x.x, 11.x.x 4
Beginning in Pega 7, production systems may take advantage of high-availability features. Customers using
this high-availability functionality must use a load balancer that supports:
• session affinity
• pool management (enable, disable, remove servers)
• server monitoring for crash detection
For details, please refer to the High Availability guide on the PDN.
3
Requires a minimum of one IBM System z Application Assist Processor (zAAP) or IBM System z Integrated Information
Processor (zIIP). Consult the installation guide and PDN for the latest set-up options.
4
Must include the Local Traffic Manager (LTM) module
Microsoft
Windows 2008 supported supported supported supported supported supported
Microsoft
Windows 2012 supported supported supported supported supported supported
Oracle WebLogic
Server 12c R3
(12.1.3)
(WL 12.1.3 supports
Java 7) supported supported
Pivotal tc Server
2.8.2 This web server runs only
(supports Java 6 or with Pega 7 deployed in a
7) supported supported supported supported supported supported servlet container (WAR).
Please note: none of the “Community Editions” of these application servers (such as JBoss or WebSphere) have
been tested with Pega 7; therefore, these “Community Editions” are not supported with Pega 7.
IBM Db2 for z/OS v10 supported supported supported supported supported supported
PostgreSQL is NOT
supported for zLinux.
PostgreSQL is NOT
supported for zLinux.
Postgres Plus
Standard Edition supported for Enterprise
(Enterprise DB) 9.3.x supported supported installations
Microsoft
SQL Server 2008 R2 supported supported supported supported supported supported
Adaptive Decision Manager
Microsoft (ADM – an optional module
of DSM) is not supported
SQL Server 2012 supported supported supported supported supported supported on SQL Server.
Microsoft
SQL Server 2014 supported supported
Please note: none of the “Express” or “Personal” versions of these databases have been tested with the
Enterprise version of Pega 7; no express/personal version of a database is supported with Pega 7.
Important Notes:
• The websites of Platform Options vendors may contain additional information about how they work with
other hardware or software options on this list. If vendors state a particular combination will not work or
is not supported, that combination will not be supported by Pegasystems.
• Applications built on Pega 7 may not function correctly if run on platforms which are not approved for
Pega 7.
• Prior versions of Pega 7 may not work with the most recent Platform Options.
• Pegasystems Strategic Applications may not yet be certified on Pega 7. Please reference the System
Requirements for Pegasystems Solution Frameworks and Product Components document on the
PDN for product details.
• For better performance, ensure that you are using JDBC 4-compliant drivers.
• For better performance with a Tomcat webserver, use Tomcat 7 or higher. Tomcat 6 has a limitation that
will cause the server to treat the JDBC driver as if it were a JDBC 3-compliant driver, even if the system is
using a JDBC 4-compliant driver. Customers using Tomcat will see better performance if they upgrade to
Tomcat 7 or higher, and make sure to use a JDBC 4 compliant driver.
• The engine will not start up if the incorrect JDBC driver is used. The following configurations are
unsupported:
o Using a Multi-tenant Oracle system using one of the Oracle JDBC drivers with issues (see chart
above)
o Using a Multi-tenant system with a JDBC 3 compliant driver, OR with Tomcat 6 (see above
Tomcat note)
o Using Microsoft SQL Server with a JDBC 3 compliant driver, OR with Tomcat 6 (see above
Tomcat note)
When any of these unsupported configurations are encountered, Pega 7 will not start.
Notes on Java Virtual Machines (JVMs): Pega 7 requires Java to be installed on the application server.
1. Pega 7 requires the use of the Java 6 or Java 7 specification, or the Oracle Java 8 specification (depending
upon the version of Pega 7, as shown in the charts above). Each of the Java vendors will routinely issue
maintenance that addresses security, performance, and stability issues in the JDK. Pegasystems recommends
that this maintenance be applied on a periodic basis; customers’ JDKs should never be more than a year
behind current JDK maintenance levels.
2. For systems with multiple nodes/servers, all JVMs on the nodes in the system must use the same Java
version. This will ensure that our system will be able to depend on a consistent set of services from the
installed Java platform the Pega products depend on, ensuring trouble-free operation. Mixed Java versions
within a system (e.g., some nodes using Oracle Java SE 6 and other nodes using Oracle Java SE 7) may result
in unpredictable connection failures within the cluster.
3. Oracle stopped providing public updates to Java 6 in February 2013. Therefore, beginning in Pega Version
7.1.7, Java 6 will only be supported with WebSphere.
4. The last public release of Java 7 is Oracle Java 7 update 79 – 7u79 (subsequent updates are available if a
support offering is purchased from Oracle). All users of Java 7 should have update 79 or a later paid support
update.
6. When installing Pega 7 on a server with a 64-bit operating system, be sure to install the 64-bit JVM.
7. Pegasystems recommends that your verbose GC options be enabled, even in production (this adds negligible
overhead).
8. For WebSphere, use the latest approved JVM provided by IBM for that version and patch level of the
application server (unless it is specifically stated that it does not run with Pega 7). Be sure to check the JVM
Known Issues section on the next page to avoid issues with certain JVM versions.
9. For WebLogic, Pega has tested both “Hotspot” (Sun/Oracle) JVM and JRockit; either may be used.
10. Tomcat does not bundle a JVM in its application. Pega recommends using either Oracle or IBM Java 7, at the
Java vendor’s latest patch level (unless it is specifically stated that that patch level does not run with Pega 7).
11. JBoss does not bundle a JVM in its application. Pega recommends Oracle Java 7, at the latest level (unless it
is specifically stated that that level does not run with Pega 7). See Note #3 above for information on the latest
Oracle Java 7 levels.
12. The amount of additional memory required for DSM services (what is required in addition to the
recommendations for Pega 7, found in the Install Guides) will depend upon your application’s use of ADM
and VBD. Contact Pega Support for specialized sizing recommendations.
1. Pega 7 (version 7.1.6 and prior) supports the 64-bit Sun Java 6 JVM at update 10 or later. Earlier versions of
the Sun Java 6 JVM will not function correctly due to a Java 6 bug. All Java 6 users should be on the last
public release (Update 45) or a later paid support update.
2. Oracle reported a bug with Java 6 (Hotspot) Update 29: it does not work with Microsoft SQL database drivers:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7105007 This bug prevents Pega 7 from
starting (the system just hangs). All Java 6 users should be on the last public release (Update 45) or a later
paid support update.
Existing Pega 7 systems running earlier versions of WebSphere can avoid the risk by turning on a JIT switch
for Idiom Recognition. The JVM argument is:
-Xjit:disableIdiomRecognition
4. The JBoss version 6.1, 6.2, and 6.3 application servers support Java versions 6 and 7. When using Pega’s
System Management Application (SMA) tool, there is an issue for JBoss 6.x and Java 7. With this
combination, you must use a JDK update of 1.7.0_39 or lower, as Update 40 (1.7.0_40) and above does not
work.
*Pega 7.1.7 will require WAS 7 fix pack 25 and above. Due to a bug in older versions of WebSphere, the
introduction of Elasticsearch causes WAS 7 to fail on startup: http://www-
01.ibm.com/support/docview.wss?uid=swg1IZ67813
**The version of Java 1.7 shipped with WebSphere 8.5.5.1 reports a Java Verify error when loading
classes for assembled rules. This appears to be related to an Eclipse bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=381172
The VerifyError does not appear to occur with the Java 1.7 SR6 release. See also:
https://www.ibm.com/developerworks/community/forums/html/topic?id=7f616d94-a4ec-4e32-9ccc-
3406ee063a6f
End-User Browsers
END-USER Pega Pega Pega Pega Pega
CLIENT Pega 7.1 7.1.5 7.1.6 7.1.7 7.1.8 7.1.9 IMPORTANT NOTES
Internet Explorer 8 Pega 7.1.9 WILL NOT
32-bit supported supported supported supported supported WORK with IE8.
Internet Explorer 9
32-bit supported supported supported supported supported supported
Internet Explorer 10
32-bit supported supported supported supported supported supported
Internet Explorer 11
32-bit supported supported supported supported supported
Pega 7.1.9 WILL NOT
Internet Explorer 8 WORK with IE8.
64-bit supported supported supported supported
1. Pega 7 is certified on the latest version of these supported browsers at the time a given version of Pega 7 is released.
Reasonable efforts are made to test previous versions of the browsers, with particular attention paid to Internet
Explorer 9, 10, and 11. If you have an issue with Pega 7 guardrail-compliant UI in a particular version of a
supported browser type, please contact Pega Support, and we will make commercially-reasonable efforts to resolve
the issue.
2. Internet Explorer 64-bit browsers are supported beginning with Pega 7.1.5. A few optional features continue to
require ActiveX controls, which do not work in a 64-bit Internet Explorer browser. For a complete listing of these
features, please refer to the following articles on the PDN:
Client-side technologies in Pega 7.1.1 through 7.1.7
Client-side technologies in Pega 7.1.8
3. Beginning with the release of Pega 7.1.9, Internet Explorer 8, as well as non-HTML5 user interfaces, is no
longer supported. Microsoft is no longer updating Internet Explorer 8, and instead points customers to Internet
Explorer 10 or 11.
Internet Explorer 8 continues to work with older versions of Pega 7, with the caveat that Internet Explorer 8 is
known to cause client-side performance issues when operating in Standards Mode. Some screens, especially grids
and lists which display large amounts of data, may experience sub-optimal performance with Internet Explorer 8.
For the older 7.1 versions, we strongly recommend using another browser which does not have these performance
issues, such as Internet Explorer 11, Chrome, Safari, or Firefox. For full details, please reference the PDN article
End of support for Internet Explorer 8 and "quirks mode" applications in Pega 7.1.9.
4. Version 52.0 of the Mozilla Firefox browser blocks Silverlight (an NPAPI plugin) by default. (For details on
which Pega tools are affected by Silverlight, please see the PDN article End of support for Microsoft Silverlight in
Mozilla Firefox 52.) For a limited time, Mozilla is offering a 64-bit Extend Support Release (ESR) of Firefox 52.0
that will support Silverlight through early 2018. For more information, see
https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/.
5. Version 42.0 of the Google Chrome browser blocks Silverlight (an NPAPI plugin) by default. (For details on which
Pega tools are affected by Silverlight, please see the PDN article Client-side technologies in Pega 7.2.1.) For
details on re-enabling Silverlight, see https://support.microsoft.com/en-us/kb/3058254 .
Chrome version 45.0 or later fully removes Silverlight support – use IE, Firefox or Safari instead. See
http://www.chromium.org/developers/npapi-deprecation for more information; also, please reference the PDN
article End of support for Netscape Plugin API in Google Chrome 45.
DESIGNER
STUDIO/
DEVELOPER Pega Pega Pega Pega Pega Pega
PORTAL 7.1 7.1.5 7.1.6 7.1.7 7.1.8 7.1.9 IMPORTANT NOTES
Internet Explorer 8 Pega 7.1.9 WILL NOT WORK with
32-bit supported supported supported supported supported IE8.
Internet Explorer 9 For IE9 and IE10, Pega 7 will no
longer support the IE8 “compatibility
32-bit supported supported supported supported supported supported mode” (EmulateIE8). Browsers in IE8
compatibility mode will not display
Internet Explorer correctly.
10 32-bit supported supported supported supported supported supported
Internet Explorer
11 32-bit supported supported supported supported supported
Internet Explorer 8 Pega 7.1.9 WILL NOT WORK with
64-bit supported supported supported supported IE8.
Internet Explorer 9
64-bit supported supported supported supported supported
Internet Explorer
10 64-bit supported supported supported supported supported
Internet Explorer
11 64-bit supported supported supported supported supported
In Pega versions prior to 7.1,
Designer Studio functionality
depended entirely on Internet
Explorer browsers. Starting with
Pega 7.1, the vast majority of
Firefox supported supported supported supported supported supported development activities can be
accomplished using Chrome, Firefox,
or Safari. A few optional features
continue to require Internet Explorer.
For a complete listing of these
features, please refer to the
following article on the PDN: Client-
side technologies in Pega 7.1.8.
1. We support current and future versions of Safari, Chrome, and Firefox to the extent possible. Pega will make
reasonable efforts to continue to support future versions of each browser – barring any major architectural or
backward compatibility changes from the browser vendors, we will support users on those platforms.
3. Version 42.0 of the Google Chrome browser blocks Silverlight (an NPAPI plugin) by default. (For details on which
Pega tools are affected by Silverlight, please see the PDN article Client-side technologies in Pega 7.2.1.) For
details on re-enabling Silverlight, see https://support.microsoft.com/en-us/kb/3058254 .
Chrome version 45.0 or later fully removes Silverlight support – use IE, Firefox or Safari instead. See
http://www.chromium.org/developers/npapi-deprecation for more information; also, please reference the PDN
article End of support for Netscape Plugin API in Google Chrome 45.
4. Beginning with the release of Pega 7.1.9, Internet Explorer 8, as well as non-HTML5 user interfaces, is no
longer supported. Microsoft is no longer updating Internet Explorer 8, and instead points customers to Internet
Explorer 10 or 11. Therefore, Pegasystems cannot address these client-side performance issues reported with
Internet Explorer 8. Customers should consider carefully before using Internet Explorer 8 as the target browser
with v7.1.
Internet Explorer 8 continues to work with older versions of Pega 7, with the caveat that Internet Explorer 8 is
known to cause client-side performance issues when operating in Standards Mode. Some screens, especially grids
and lists which display large amounts of data, may experience sub-optimal performance with Internet Explorer 8.
For the older 7.1 versions, we strongly recommend using another browser which does not have these performance
issues, such as Internet Explorer 11, Chrome, Safari, or Firefox. For full details, please reference the PDN article
End of support for Internet Explorer 8 and "quirks mode" applications in Pega 7.1.9.
In Pega 7 for versions 7.1.1 through 7.1.7, the Designer Studio authoring environment contains several integration
points with Microsoft Office that leverage browser plugins (ActiveX, Silverlight). These plugins allowed developers
the ability to perform tasks such as:
• Edit large decision rules using Excel
• Edit large data tables using Excel
• Edit requirements and large text files using Word
Starting with Pega 7.1.8, Designer Studio integration points with Microsoft Office have been steadily replaced with
simple import/export paradigms that don’t require ActiveX or Silverlight. Specific areas of Designer Studio may
behave differently based on your exact version of Pega. For details on which tools are affected and the required third-
party components, please see the PDN articles below.
As of May 2017. ActiveX controls are deprecated, and support for their use will become limited. We recommend
updating to the latest version of Pega 7 for an ActiveX-free development experience. This allows developers to
generally use any version of Office that can read and write .docx, .xlsx, and .csv files.
For these older versions of Pega 7, the following versions of Microsoft Office are supported.
Microsoft Visio
Beginning in Version 7.1, Microsoft Visio will no longer be used for flow editing. For customers upgrading older
versions of PRPC who have flows created in Visio, the first time those flows are edited, they will automatically be
upgraded to use Process Modeler, and will save as Process Modeler flows.
Visio is still required for Entity Relationship Diagrams. In versions of Pega 7 prior to Pega 7.1.8, Visio is required to
generate and also view ERDs. For supported versions of Microsoft Visio, please reference the Legacy Support chart
below.
In Pega 7.1.8 and later, documentation generation is being done on the server, which creates .vdx files. This type of
file can be viewed by a Visio Viewer, and does not require a full Visio installation (although that will work). Any
version of Visio Viewer which supports the .vdx file format can be used.
NOTE: Due to the large number and diversity of physical Android devices on the market, it is not possible to test each
and every device. This matrix is intended to be a guide, rather than an exhaustive list of supported devices. Your
experience on your mobile device may differ from results indicated in this matrix.