Manage Pega V851 API's via Open API Gateway (WSO2)

-
In this post, let us focus on how Pega API's can be managed via any Open API Gateway like WSO2. To work on this exercise, we need the below prerequisites.
1) Create a Service-REST API in Pega [Eg: Create a HR Service case in this context]
2) SwaggerHub tool to import the API's YAML data from the above step
3) WSO2 tool to publish and invoke the above API service

Create a Service-REST API: Follow the below simple steps from Pega using Service-REST

























Capture the YAML data from the above created service and update the server URL with tunneled URL generated by using ngrok.exe [Eg: run the command "ngrok http 8082" from command line prompt] Copy/mark the https URL from command line prompt and update the YAML file in the editor shown in below video.





































SwaggerHub tool editor to import the API's YAML data: A brief idea on this tool before we start using this Opensource at our end. Swagger is a set of rules (in other words, a specification) for a format describing REST APIs. The format is both machine-readable and human-readable. Google it for more details. Here is the site where we need to register and start using for our exercise.
https://app.swaggerhub.com/home
Follow the steps as per the simple video and downloas the json file as mentioned.

WSO2 tool to publish and invoke the above API service: After capturing the file, we need to publish this API using WSO2 tool(trial ver). It is a lightweight, component oriented; Java based enterprise service bus (ESB). WSO2 ESB allows developers to integrate services and applications in an easy, efficient and productive manner. It also provides ease of connecting cloud applications using a wide array of cloud connectors that comes ready to be used.

Use this site to register for a 14 days trail in WSO2:  https://api.cloud.wso2.com/publisher/site/pages/index.jag
Follow these steps from WSO2 API cloud env as per below YouTube video.
After finishing the above process, take the Request URL and is required for testing it from Postman. Before running this API from Postman, we need to generate the token by using the URL:https://gateway.api.cloud.wso2.com/token?grant_type=client_credentials
Check the below screenshot for more details

Follow the below steps from the video and check the Pega case created from the Dev Studio.



References:
1) Google.com
2) Pega Community Site
3) WSO2.com
4) SwaggerHub.com
5) LinedIn.com





Popular posts from this blog

Connecting Claude to Pega Infinity 25.1.3 via MCP — Step-by-Step

-
Image
Enable AI-powered access to your Pega Investigative Case Management data directly from Claude prompts using the Model Context Protocol (MCP) and OAuth 2.0. What is MCP and why connect Pega to Claude? The Model Context Protocol (MCP) is an open standard that lets AI assistants like Claude securely call tools and read data from external systems — all from a natural-language prompt. Think of it as a universal adapter between your enterprise systems and AI. Pega Infinity V25.1.3 ships with a first-class MCP service built on its existing REST framework. Once enabled, Claude can: Query and summarize investigative cases without switching apps Retrieve assignment details and case status on demand Trigger Pega workflows from conversational prompts Version requirement: This guide is based on Pega Infinity V25.1.3 (Community Edition) with the Rule-Service-MCP rule type. Earlier versions may not include native MCP support. Architecture overview The connection uses three layers: Claude as the AI c...
Read more

Build Pega Applications with GitHub Copilot CLI, Pega Infinity AI Plugin & MCP — Branch-Based Agentic Authoring

-
Image
To work on this experiment, we need the Github Copilot CLI, Pega Infinity Instance, and Pega Infinity AI Plugins ( https://github.com/pegasystems/infinity-ai-plugins ) . In my case, I have used the Pega Infinity V26.1 Community Edition and here is the Github repository to upload it in the Github Copilot plugin marketplace. For this entire exercise to work well, we need Java 17 or above.  Windows Command Prompt (Agent-Driven Terminal): Represents the Github Copilot CLI. It shows the active terminal execution where commands like pega-setup, list-skills, list-available-applications etc. MCP (Model Context Protocol) Orchestrator: Acts as the bridge and mediator between the AI terminal environment (GitHub Copilot) and the Pega platform. It translates natural language directives and agent commands into structured operations and API calls to manage application configurations. Here the name of the MCP server is pega--infinity-authoring Workflow Directives: Represents...
Read more

itextpdf API to generate PDF doc from an image file using Pega PE

-
Image
Probably some of the techies might have an idea on an opensource called " itextpdf " (earlier name is lowagie ) to convert an image file(png,jpeg,jpg,tiff,gif etc.) to a PDF file. It is very simple to use this API in Pega function to build the logic using java code. Moreover, this API comes in one single jar file and we need to import it in Pega before we start using it.  I see the conversion comes good in PDF file but not sure if any limitations of this API in terms of conversion is like formatting, font, images etc. So far so good and may be we can keep this API as one of our solutions while working on the requirements accordingly.  Heard that same API can be used to convert the text file to PDF but I didn't explore on it. Those who are interested to work on text -> PDF can take a look at the documentation. Don't hesitate to contact me offline for any further discussion in this context :) :) Prerequisites for doing this exercise: 1) itextpdf 5.4.0 jar file 2) Peg...
Read more