In this blog, we are going to discuss the integration of applications, along with the related services and resources, connectors. Become a Pega professional in developing CRM and BPM applications with this online Pega training course. Experience the design expertise in learning the Pega concepts of decision, process, application, user interface, report, etc.
Pega industry apps and Pega Platform integration enable Pega applications for communicating with other apps and external systems. Use the following rule types for integrating your Pega apps operating in Services of Pega Cloud settings with your corporate systems:
- For your Pega apps integrations, resources keep track of the properties of connection and other data configuration. They’re used to set up services like email listeners and Pega file, which not only establish connections and work rules processing but also let you include meta-data for operational use that controls when and how these services run.
- Services, such as REST APIs, are employed to reveal integration points within the program.
- Connectors allow your application on Pega Cloud (acts like a client) for requesting data from the systems which are external (servers).
For linking Pega applications operating in Environments utilizing Services of Pega Cloud with your company, the following resources, services, and connectors are provided. To limit attacks and minimize data loss, make sure you’re following security best practises. while connecting to other systems. The following are examples of these practices:
- For every request, strong authentication is used.
- Assuring that application users are properly authorized.
- Using “TLS 1.2” to secure network communications and, if necessary, a VPN on the Pega Cloud.
Services and resources
The following standard industry protocols are supported by Pega applications that run in Services of Pega Cloud settings for interfacing with your company’s resources.
When you require to employ your application of Pega as web service in an environment of Services in Pega Cloud, build connections of SOAP service that are secure to your Pega endpoint interfaces.
For more details on service rules, read this link SOAP rules for Services.
If your application of pega runs in an environment of Services of Pega Cloud requires to process, comprising the following categories, build secure connections with HTTP service to your pega web interfaces.
- Data is submitted via an HTML POST form.
- Requests including XML or data from other strings (text) that do not need to adhere to protocols or messaging standards like SOAP.
For more details on service rules, read this link HTTP rules for Services.
If you’re using the environment of Pega Cloud Services to execute your application in pega, it requires interactions with other systems using web services, creating secure connections with REST service to your pega endpoint interfaces.
When possible, use REST connections rather than HTTP connectors as best practice.
For more details on service rules, read this link REST rule for Services.
To handle your email in Pega apps, use the service of Pega Email to connect with your company’s POP3, IMAP, and SMTP mail server.
For more details on service rules, read this link Email rules for Services.
Supports using SOAP web service protocols to connect the SAP system with your application in Pega Cloud.
For more details on service rules, read this link SAP rules for Services.
The standard of JMS allows you to transmit messages via JNDI servers. See Configuring enterprise messaging using JMS for more information on utilizing the platform of pega as a receiver and publisher of messaging services.
For more details about messaging service, read this link Overview of Messaging service.
Uses the Messaging protocol for MQ middleware of IBM WebSphere to interface with systems that are external. See Configuring enterprise messaging with IBM MQ for more information on Pega Platform assistance and IBM MQ interoperability.
For more details on MQ service rules, read this link MQ rules for Services.
Cloud Services provided by clients of Pega can use the SFTP Service to send and receive files across their Pega Cloud apps in an easy and secure manner. The repository for file storage of Pega Cloud is used for secure and reliable file transfers between your company and Services of Pega Cloud powered Pega applications. Because cloud Services from Pega doesn’t allow you to directly access files on your environment’s local filesystem, you can’t utilize the rules of SFTP connection in the Pega Platform.
For more details on SFTP, read this link SFTP Services of Pega Cloud.
To obtain services or data from external systems, Services of Pega Cloud apps can use the standard protocols in the industry as listed below.
When you need to call a web service that is external from your Cloud-based Pega application, use SOAP connector rules.
For more related information on SOAP, read this link Creating integration using SOAP.
When you would like to use your application in Pega Cloud to communicate string data (format of text) or XML as messages for a system that is external without having to follow communications protocols or standards like SOAP, use HTTP connector rules.
For more related information on HTTP rules, read this link About HTTP rules for Connect.
Web services in REST expose information that you may consume using REST connection Pega Cloud application rules (XML or JSON is commonly used). When possible, use REST connections rather than HTTP connectors as a best practice.
For more related information, read this link About REST rules for Connect.
For connecting to an existing web service of SAP SOAP, employ the rules for Connect SAP in your application in Pega Cloud.
For more related information on SAP rules, read this link About SAP rules for Connect.
Using the DocuSign service in a state of flow, employ the smart shape to transmit electronic signature documents
For more related information on flow shape, read this link Shapes of Flow.
To configure corporate messaging while employing Platform of Pega as message receiver and publisher, use these JMS rules in your application of Pega Cloud. See Configuring business messaging with JMS for more information about JMS support on the Pega Platform.
For more related information messaging services, read this link Overview of Messaging service.
To configure corporate communications utilizing the IBM MQ messaging standard, employ rules for Connect MQ in your applications of Pega Cloud. See Configuring enterprise messaging with IBM MQ for more information on Support for the Pega Platform and IBM MQ interoperability.
For more related information on MQ rules, read this link About MQ rules for Connect.
In this article, you now became aware of the integration rule types for Pega applications operating in Pega Cloud Services. We have also discussed the best practices of ensuring security while connecting to other systems. The service and resource protocols and connectors were also explained in detail.