Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Modernized Integration Patterns

Updated on October 8, 2023


This content applies to On-premises, Client-managed cloud and Pega Cloud environments

Modern integrations should leverage Web Service APIs, like REST or SOAP, over the encrypted internet. Pega recommends replacing integrations like Direct JDBC connections to external systems with modern design patterns.

Pega Cloud uses Java Standard Edition, rather than Java Enterprise Edition.  Several rules are not supported, because they require Enterprise Archive (EAR) deployments.

Additional rules are deprecated due to security, complexity, or performance concerns.  You cannot create new instances of these deprecated rules. However, you can use and modify existing rules.

For more information about changes to integration patterns, see:

How to identify

To identify unsupported, deprecated, or not recommended rules, the rows in the output report from the Pega Cloud Readiness Tool are:
Area:  Legacy Cloud Integration
Rule Type (any of the following):  

  • Data-Admin-DB-Name
  • Data-Admin-Connect-JCAAdapter
  • Data-Admin-Connect-JMSMDBListener
  • Rule-Connect-dotNet
  • Rule-Connect-EJB
  • Rule-Connect-File
  • Rule-Connect-Java
  • Rule-Connect-JCA
  • Rule-Connect-MQ
  • Rule-Connect-SAPJCo
  • Rule-Service-dotNet
  • Rule-Service-EJB
  • Rule-Service-Java
  • Rule-Service-JSR94
  • Rule-Service-SAPJCo

How to modernize

Using Data-Admin-DB-Name rules for direct JDBC connections to external systems are not recommended.  They should be replaced with Web Service APIs, like REST or SOAP.

The rules that are deprecated or no longer supported are listed in the following tables, along with the new rule types to use instead.


Unsupported Rule TypeAlternative Rule TypeRecommended Configuration
Connect JCAConnect RESTSubstitute legacy JCA resources with a REST API and use REST connectors to interact with them.
JCA Resource AdapterJCA 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 ListenerReplace JMS MDB Listener configurations with standard JMS Listener configurations.
Connect EJBConnect RESTSubstitute legacy EJB resources with a REST API and use REST connectors to interact with them.
Service EJBService RESTRedefine your EJB service as a set of RESTful service APIs and invoke them over HTTP/HTTPS.


Deprecated Rule Type


Alternative Rule Type


Connect dotNet

Connect SOAP rules


Connect File

For on-premises systems, use the D_pxNewFile landing page with the defaultstore repository.
For Pega Cloud systems, use the D_pxNewFile landing page with the pegacloudfilestorage repository. For more information, see Repository APIs.

Connect JavaConnect REST
Connect MQ

These are no longer being actively developed.  Use Connect JMS instead.  See Connect MQ rules and Connect JMS rules.

Connect SAPJCoConnect SAP rules
Service dotNetService SOAP rules
Service HTTPService REST rules
Service JavaService REST rules
Service JSR94Service REST rules
Service SAPJCoService SAP rules


On-Prem only:
For information on how specific supported platforms are affected, see the Pega Platform Support Guide.


Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us