EAR support for JBoss EAP 6
Valid from Pega Version 7.1.5
PRPC deployment in JBoss EAP 6 as an EAR archive is now supported.
If you need to deploy the JBoss EAR file, go to My Support Portal and submit a Support Request. GCS can assist you with the procedure.
Small distribution kit
Valid from Pega Version 7.1.5
A new “small” release distribution format for Maintenance Levels (ML) is now available, designed to significantly increase adoption via:
- Minimal package size and faster download time
- Minimal install time via tactical changes to the upgrade implementation and process
This kit contains streamlined installers (both UI and command-line installers) and specialized error handling for ML updates (for example, a “small” kit will only work if an existing version of the same release is already installed).
The kit assembly has also been automated, which includes the construction of a PRPC_Rules.jar archive containing cumulative rules since the GA release.
A “small” kit will work for any prior ML release within a major release (for example, the “small” ML5 distribution kit will update any customer on 7.1 ML1 through 7.1 ML4).
Improved data page performance
Valid from Pega Version 7.1.5
Improvements have been made with queueing and processing of asynchronously-loaded data pages to reduce the number of calls to the database and avoid generating performance problems because of unneeded asynchronous requests.
Restricted SMA access
Valid from Pega Version 7.1.5
System Management Application (SMA) remote connections are not supported on JBoss EAP 6.x. This means SMA users may only monitor locally connected systems. Ensure that the "Local JVM Connection..." option is selected when configuring PRPC nodes:
DB2-LUW database logfile size increase
Valid from Pega Version 7.1.5
To avoid running out of logfile space due to large transaction sets during the rule base load of a Pega 7.1.x install, upgrade, or maintenance level update, systems supported by a DB2-LUW database platform should increase the LOGFILSIZ parameter to at least 4096 pages from the default size of 1000 pages.
After the size has been increased, restart the database to ensure that the new setting is loaded into the database correctly.
Adaptive Decision Manager installation changes to support delayed learning
Valid from Pega Version 7.1.7
To support delayed adaptive learning, Adaptive Decision Manager (ADM) has been enhanced with database schema changes and no longer relies on Hibernate. This change has an impact in the way ADM is set up in the Decision Management service layer: the jdbc/admDataSource resource is now superseded by jdbc/adm7DataSource.
Additionally, Pega 7.1.7 further simplifies the ADM deployment by providing a single enterprise application or web archive:
- Single EAR deployment archive that can used when deploying ADM on IBM WebSphere and Oracle WebLogic
- Single WAR deployment archive that can be used when deploying ADM on Tomcat and JBoss
Improved full text search
Valid from Pega Version 7.1.7
In Pega 7.1.7, Elasticsearch is used to provide full-text search functionality for rules, work, and data content, replacing the existing Lucene search functionality. In addition to providing search results two to five times more quickly than with Lucene Search, Elasticsearch is more scalable: with multi-threaded bulk and incremental indexing, it provides enhanced information about the search queue, the ability to host index files on multiple nodes, a more robust and expressive search parser, the ability to configure thresholds for alerts and search query time-outs, and automatic handling of replication and failover.
The search management user interface, where you can see length of queue and age of entries, which node hosts the search index, and where it is located.
After upgrading to Pega 7.1.7, the system administrator must manually migrate search functionality from Lucene Search to Elasticsearch. Note that during the switch-over and until the indexes are rebuilt, Lucene search continues to function and there is no interruption in search functions. For more information, see the Pega 7.1.7 Upgrade Guide.
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.