Use JDBC 4 compliant drivers for better performance
Valid from Pega Version 7.1.7
For better performance, ensure that you are using JDBC 4-compliant drivers. For more information on supported and non-supported JDBC drivers, please reference the Platform Support Guide.
Use Tomcat 7 for better performance
Valid from Pega Version 7.1.7
For better performance with a Tomcat web server, use Tomcat 7.
Tomcat 6 has a limitation that causes 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 and use a JDBC 4-compliant driver.
Engine will not start if the incorrect JDBC driver is used
Valid from Pega Version 7.1.7
The engine will not start up if the incorrect JDBC driver is used. The following configurations are unsupported:
- Using a Multi-tenant Oracle system with one of the Oracle JDBC drivers with issues (see the chart in the Platform Support Guide)
- Using a Multi-tenant system with a JDBC 3 compliant driver, OR with Tomcat 6 (for more information on using tomcat with Pega 7.1.7, see Use Tomcat 7 for best performance)
- Using Microsoft SQL Server with a JDBC 3 compliant driver, OR with Tomcat 6 (for more information on using tomcat with Pega 7.1.7, see Use Tomcat 7 for best performance)
When any of these unsupported configurations are encountered, Pega 7 will not start. Before this change, the engine would appear to start up properly, but would encounter issues during other parts of the engine startup or during actual use of the system.
IBM WebSphere Application Server V8: Edit the URL for Enabling System Management Application
Valid from Pega Version 7.1.7
WebSphere 8 does not correctly resolve the URL to enable System Management Application. As a workaround, when you configure the application server, you can do either of these actions:
-
Enter the full URL in the format:
http://hostname:port/prsysmgmt/getnodes.action - Set the com.ibm.ws.webcontainer.redirectcontextroot property to true.
Open ports required for cluster communication
Valid from Pega Version 7.1.7
In a Pega 7 system, there can be multiple servers, or nodes, and each node can contain multiple JVMs. In Pega 7.1.7, the port range 5701-5800 needs to be left open for cluster communication. The number of available ports in this range needs to be greater than or equal to the greatest number of JVMs on any one node in the cluster. So for example, if there are 3 JVMs on one node, and 7 JVMs on another node, there need to be at least 7 ports available. By default, the system will begin with port 5701, and then look for the next port in the sequence (5702, followed by 5703).
If these ports are not available, you will see the following error:
ERROR - PegaRULES initialization failed. Server: ABCDEF123
com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed
< . . . Java dump here . . . >
Caused by: com.hazelcast.core.HazelcastException: ServerSocket bind has failed. Hazelcast cannot start! config-port: <port>, latest-port: <port>
Recommended heap sizes
Valid from Pega Version 7.1.7
The heap is a storage area in the Java virtual machine (JVM) allocated for both short-term and long-term (shared) object storage. If the server does not have enough memory allocated to run Pega 7, the system can hang without an error message. If this occurs, your values need to be higher than the recommendations based on your server hardware and the number of other applications on the server.
Pegasystems recommends using these settings:
- Initial Heap Size (Xms): 1 GB
- Maximum Heap Size (Xmx): 12 GB (8 GB minimum)
If your application server is using the Oracle JVM, also add the PermSize and MaxPermSize settings:
- PermSize (-XX:PermSize): at least 256MB
- MaxPermSize (-XX:MaxPermSize): at least 512MB
Set the JVM memory options to increase the amount of system memory allocated to the application server running Pega 7 by selecting and then selecting a listed node.
See the Pega 7.1.7 Installation Guides for more information about how to make these setting changes.
The System Management Application is supported only on Microsoft Internet Explorer
Valid from Pega Version 7.1.7
Microsoft Internet Explorer (IE) is required for the System Management Application (SMA). No other browser is supported.
Create and modify tenants only from the Tenant Management landing pages or SOAP operations
Valid from Pega Version 7.1.7
When creating or modifying tenants, do not use any of the following methods:
- Creating a new tenant definition from the Data-Admin-Tenant list
- Using the Save As feature to create a tenant from an existing tenant
- Creating a tenant from the rule form from the menu
Although these methods might appear to work, the resulting tenants have no associated metadata and are not valid. Always use landing pages or SOAP operations to create or modify tenants.
Work attachment indexing fails with IBM SDK Java 6
Valid from Pega Version 7.1.7
Indexing of work attachments fails when you use IBM SDK Java 6 with Pega 7.1.7 through Pega 7.2. The workaround is to switch to IBM SDK Java 7 or Oracle JDK Java 1.6. You can also disable attachment indexing from the Search landing page; however, if you do this, you are not be able to search the content of attachments.