Pega Connectors

 

Connector:

A connector defines an outbound request to the service, and a connector establishes a connection to an external system by using common HTTP methods such as SOAP(Simple Object Access Protocol) or REST(Representational State Transfer). Connectors pass application data through a mapping rule with the required and optional parameters, and are in charge of mapping the response from the service to the application.

How to configure the call of the connector:

The connector can be called from an Activity, Data page, etc The most recommended use of a connector is a data page. On the data page, you can set up, through a data transformation, the mapping for the request data responder, and it can be called from anywhere in the application .

Let's get this process through the steps :

  1. Map data to the integration: you can create a data transform to map the data from the clipboard to the service

  2. Invoke the connector: the connector can be invoked from a data page, data transform, or activity. But as a best practice, it's recommended to call it through a data page

    2.1- Initialize the connector

    2.2-map outbound data

    2.3-Invoke the service

    2.4-Map inbound data

    2.5-Complete the connection

  3. Map response back to the application

Supported Connectors:

Pega provides connectors for a wide range of industry-standard protocols and standards. Standard connectors include Cassandra, CMIS, HBase, JMS, MQ, REST, SAP, SOAP, and SQL

Services

a service process inbound request and responds to the requesting service

Consider an order management application for a wholesaler that is implemented in Pega Platform. A retailer configures their inventory management application to access a service provided by the wholesaler to place an order for items that fall below a specified inventory threshold. Each week, the inventory management system sends a list of items and quantities to order. The service provides a response that includes an order total, confirmation number, and expected date and time of delivery.

How a service process a request

  1. Inbound request recieved
  2. Service process the request
  3. Map inbound data
  4. request processing
  5. map outbound data
  6. System return a response

Application settings ,

we use application settings to move the services endpoints and configurations in one rule and we can define all this configurations trough differents enviroments in one place




Comments

Popular posts from this blog

How to save a Page List into data type, Pega Tutorials

Step by step How to create a SOAP Connector in pega

Pega For Beginners - How to create your first application in pega in 5 minutes