Deprecation of EAR deployments in Pega Platform 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.
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.