Integrating Pega applications in Pega Cloud with external systems
Integrating Pega Platform and Pega industry applications allows the Pega applications to interact with the applications and your external systems. In order to integrate your Pega applications running in Pega Cloud Services environments with your enterprise systems, use the following rule types:
- Resources maintain the connection properties and other configuration data for your Pega applications integrations. They are used to configure services to accomplish work such as Pega file and email listeners, which establish connectivity and processing work rules, but also allow you to add operational meta-data controlling how and when these services get executed.
- Services are used to expose integration points into the application, such as REST APIs.
- Connectors enable your Pega Cloud application (acting as a client) to request information from external systems (servers).
The following resources, services, and connectors are available for integrating Pega applications running in Pega Cloud Services environments with your enterprise. As with any external system connectivity, ensure that you follow security best practices to mitigate attacks and prevent data loss. These practices include the following items:
- Using strong authentication for all requests
- Ensuring correct authorization of application users
- Securing network connections with TLS 1.2, and, as required, by utilizing a Pega Cloud VPN
Resources and services
Pega applications running in Pega Cloud Services environments support integrating with resources in your enterprise using the following industry-standard protocols.
|Protocols or services||Description||Related information|
|SOAP||Create secure SOAP service connections to your endpoint interfaces in Pega when your Pega application running in a Pega Cloud Services environment needs to act as a web service.||Service SOAP rules|
|HTTP||Create secure HTTP service connections to your web interfaces in
Pega when your Pega application running in a Pega Cloud Services
environment needs to process, including the following types:
||Service HTTP rules|
|REST||Create secure REST service connections to your endpoint
interfaces in Pega when your Pega application running in a Pega
Cloud Services environment needs to supports interactions with
external systems through web services.
As a best practice, use REST connectors instead of HTTP connectors when possible.
|Service REST rules|
|Connect to your enterprise SMTP, IMAP, and POP3 mail server using the Pega Email service to manage your email in Pega applications.||Service email rules|
|SAP||Supports connecting a SAP system to your Pega Cloud application through the use of SOAP web service protocols.||Service SAP rules|
|Java Messaging Service||Supports sending messages using JNDI servers with the Java Messaging Service (JMS) standard. For details about using Pega Platform as a messaging service publisher and receiver, see Configuring enterprise messaging using JMS.||Messaging service overview|
|IBM MQ||Supports interactions with external systems using the IBM WebSphere MQ middleware messaging standard. For details about Pega Platform support for and interoperability with IBM MQ, see Configuring enterprise messaging using IBM MQ.||Service MQ rules|
|Secure File Transfer (SFTP)||The Pega Cloud Services SFTP Service provides Pega Cloud Services
clients with simple, secure file transfers to and from their Pega
Cloud applications. The service supports file exchanges between your
enterprise and your Pega applications powered by Pega Cloud
Services, and uses the Pega Cloud File
Storage repository for reliable and resilient
Pega Cloud Services environments do not support using the SFTP connector rules in Pega Platform, because Pega Cloud Services does not support directly accessing files on the local filesystem of your environment.
|Pega Cloud Services SFTP Service|
Pega applications running in Pega Cloud Services environments can request data or services from another system using the following industry-standard protocols.
|SOAP||Use SOAP connector rules when your Pega Cloud application needs to call an external web service.||Creating SOAP integration|
|HTTP||Use HTTP connector rules when you want your Pega Cloud application to send XML or string data (text) as messages to an external system without the need to comply with messaging standards or protocols such as SOAP.||About Connect HTTP rules|
|REST||Use REST connector rules in Pega Cloud applications to consume information exposed by REST web services (typically presented as JSON or XML). As a best practice, use REST connectors instead of HTTP connectors when possible.||About Connect REST rules|
|SAP||Use Connect SAP rules in your Pega Cloud application to connect to an existing SAP SOAP web service||About Connect SAP rules|
|DocuSign||Use this smart shape in a flow to send documents for electronic signatures by using the DocuSign service.||Flow shapes|
|Java Messaging Service||Use Java Messaging Service (JMS) rules in your Pega Cloud application to configure enterprise messaging while leveraging Pega Platform as a message publisher and receiver. For details about Pega Platform support for JMS, see Configuring enterprise messaging using JMS.||Messaging service overview|
|IBM MQ||Use Connect MQ rules in your Pega Cloud applications to configure enterprise messaging using the IBM MQ messaging standard. For details about Pega Platform support for and interoperability with IBM MQ, see Configuring enterprise messaging using IBM MQ.||About Connect MQ rules|