Pega File Listener process changes
Valid from Pega Version 7.2.2
Beginning with Pega 7.2.2, File Listener processes files in a different way:
- File movement in directories – Previously, files were processed from the Work directory. In Pega 7.2.2, files are processed from the source location. Files move to the Work directory only if the initial processing fails and Recovery is disabled.
- New file processing – Previously, File Listener would process all files in the source location, even if the files were added during the processing. In Pega 7.2.2, files added to the source location during processing are read the next time the File Listener starts.
For more information, see File Listener data instances.
Functionality of the pyInvokeRESTConnector rule and the pxDeferenceEndpoint rule moved to core engine
Valid from Pega Version 7.2.2
The functionality of the pyInvokeRESTConnector rule and the pxDeferenceEndpoint rule has been moved into the core engine code of the Pega 7 Platform. This change provides more consistent behavior, reduces maintenance, and reduces the risk of regression issues. As a result, you can no longer customize these rules, and upgrading the Pega 7 Platform requires special considerations if you previously customized these rules.
For more information, see Upgrading with customized pyInvokeRESTConnector and pxDeferenceEndpoint rules.
Deprecation of EAR deployments in Pega Platform 8.6
Valid from Pega Version 8.6
Starting with Pega Platform 8.6, EAR deployments of Pega Platform are deprecated. In the upcoming 8.7 release, EAR deployments will not be supported. The following rules that require EAR deployments will also be deprecated and no longer supported in Pega Platform 8.7:
- Connect EJB
- Connect JCA
- JCA Resource Adapter
- JMS MDB Listener
- Service EJB
With this deprecation, you can use the latest tools and keep your application up to date.
Upgrade impact
In Pega Platform 8.6, you can still create rules that require EAR deployments and update existing rules. However, after an upgrade to Pega Platform 8.7, rules that require EAR deployments are no longer supported.
What steps are required to update an application to be compatible with this change?
To prepare your application for this change well in advance of the Pega Platform 8.7 release, see the following table for a list of alternative rules and for guidance on modernizing your application.
Deprecated rule type | Alternative rule type | Recommended configuration |
Connect EJB | Connect REST | Substitute legacy EJB resources with a REST API, and use REST connectors to interact with them. |
Connect JCA | Connect REST | Substitute legacy JCA resources with a REST API, and use REST connectors to interact with them. |
JCA Resource Adapter | JCA resource adapters are data records that are used within the scope of a Connect JCA rule. If you replaced Connect JCA rules in your application with Connect REST rules, JCA resource adapters are no longer relevant. | No further configuration is necessary. |
JMS MDB Listener | JMS Listener | Replace JMS MDB Listener configurations with standard JMS Listener configurations. |
Service EJB | Service REST | Redefine your EJB services as a set of RESTful service APIs, and invoke them over HTTP/HTTPS. |
For information on the supported platforms that are affected by this deprecation, see Pega Platform 8.6 Support Guide.
Legacy Parse XML rule configurations must be upgraded to edit them
Valid from Pega Version 8.6
If your application has Parse XML rules that use the legacy configuration from Pega Platform™ 5.x, you cannot edit these rules after you upgrade to Pega Platform 8.6 until after you upgrade them to use tree-based parse rule configuration.
You must upgrade a Parse XML rule that you want to edit if it shows the following warning when you open it in Dev Studio.
This type of Parse XML rule is deprecated. An upgrade should be performed.
An option to upgrade also displays below the message.
Upgrade impact
Parse XML rules with the legacy configuration do not map data to the clipboard, and the rule definition is empty. After you upgrade to Pega Platform 8.6, you cannot edit Parse XML rules that you created in Pega Platform 5.x or earlier until you upgrade them to use tree-based parse rule configuration.
What steps are required to update an application to be compatible with this change?
Update legacy Parse XML rules to use tree-based parse rule configuration before you edit them in Pega Platform 8.6. Using tree-based parse rules is considered a best practice.
- Open the legacy Parse XML rule.
- On the Mapping tab, click Upgrade.
Result: The Allow tree editing? check box is displayed and is automatically selected. You can add attributes and elements to the tree structure, or delete them. - Save the upgraded rule configuration.
For more information, see Parse XML rules.
Connect MQ rules configured with alias queue do not work after upgrade
Valid from Pega Version 8.6
Connect MQ rules that you defined with an alias queue in earlier versions of Pega Platform do not work after an upgrade to Pega Platform 8.6.
Upgrade impact
If you defined an alias queue in Connect MQ rules, after an upgrade to Pega Platform 8.6, those Connect MQ rules do not work.
What steps are required to update an application to be compatible with this change?
In the Pega-IntegrationEngine ruleset, create the following dynamic system settings and their default values:
- "mq/pmo" = 0
- "mq/gmo" = 0
- "mq/oo_request" = 1040
- "mq/oo_response" = 16
For more information, see Creating a dynamic system setting.