Showing posts with label Integration. Show all posts

Home » Posts filed under Integration

What is Synchonous and Asynchronous Processing in Pega?

Synchronous processing occurs when a request has to be fulfilled before a response is generated. For example, when a user makes an API call or a database query, the request must be handled and a response generated before anything else can happen.

What are stateful and stateless processing modes in Service package

Stateful processing mode is where a Service Package remembers data between two requests from a client. This data is stored in its memory and the next request from the client can use the stored data for faster processing.

Exception handling in Pega Connect-REST

Error handling when using Pega Connect-REST involves catching response codes from the server and taking the appropriate action in the application.

By default, a GET or PUT request will return a 200 or 204 for success or a 404 for a note found. The other error codes, such as 401 and 500, should be handled in the application code.

GET, POST, PUT, PATCH and DELETE methods in Pega Integration

•GET: The GET method is used to retrieve information from a specified source. It is one of the most common HTTP methods and is used to retrieve data from an API. GET requests can be cached, remain in the browser history, and can be bookmarked. GET requests should never be used when dealing with sensitive data; as they are passed on the URL they are inherently insecure.

Explain Service REST integration in Pega

REST integration in Pega is a process that allows two different systems to exchange data with each other via a standardized protocol such as REST (Representational State Transfer). This is done by creating an API that the two systems can use to communicate with each other. The API acts as a bridge between the two systems and can move data from one to the other and vice versa. The API is usually accompanied by a couple of web services that need to be invoked in order to complete the integration. These web services may include authentication, authorization, data transfer and other services needed to complete the integration. By leveraging the power of REST, Pega can provide integration to various systems and services, giving users greater flexibility and control over their data.

What is exception handling in pega?

As we know connectors are used to communicate with external systems to fetch data and there is a possibility of something going wrong always exists. We can encounter some exceptions/errors during the communication so we need to be ready with the handling strategies. Errors could be temporary/Transient or permanent. Transient errors are temporary errors, do not last long, and can rectify themselves over time. For example, Connector is unable to connect because the application is temporarily unavailable/restarted.

Permanent errors: Typically due to configuration issues or invalid request, these kinds of error persists until we fix them.

What is the simulation in pega?

Simulating integration connectors to see how the response is coming or when there is no data source is available/external system is not available. We will define our own data source and test the integration. Use simulations to unit test the integration connector. We can simulate any external service as long as we know that "what is the request it is expecting and what is the response it is going to return".

How to simulate an integration in pega?

What is REST?

Nowadays we are using REST integration interface to interact with external systems through web service in Pega, basically to make calls between machines.

REST stands for Representational State Transfer Protocol.

What is REST in Pega?

Pega is proving a service (response) to the external system by processing the request received from an external system.

Basically, we will receive a request from external system/machine to Pega, Pega will process that request and provides a response back to an external system.

Add caption

The request will be in different types XML/JSON. Let’s consider the request type is JSON.

Pages