We need to implement REST Connector in PEGA 6.2 SP1. As PEGA 6.2 doesn’t provide connect-REST rules and capability, we are looking for different approach to implement this. Please let us know if REST connector components can be provided as additional rules with backward compatibility. Even if we get only connect-REST, it will solve our business purpose.
***Updated by Moderator: Marissa to add SR Exists tag***
Agreed: you should be able to use CONNECT-HTTP rules to get at your target system's REST-based API .
What payload format does your target REST-based system provide ? If it is XML, then you already have XML processing mechanisms available in PRPC; it it's JSON then you'll probably have to import a JSON processor (I could be wrong but I don't believe v6 had any JSON libraries available OOTB) of some sort.
I don't think it would be a good idea to port the V7 Rest Features to the older V6 Release: the correct course of action (all things be equal) would be for you to plan an upgrade from V6->V7 in order to get hold of the V7 features; rather than 'bolting-on' the V7 features to the older platform; which would come with it's own set of timelines and complexities etc.
Posted: 7 years ago
Posted: 17 Aug 2016 7:54 EDT
Sujit Kumar Patra (SujitKumarP)
The target REST-based system provides JSON payload format. We are considering the approach of using CONNECT-HTTP rules. However, CONNECT-HTTP provides only GET and PUT functionality. However, we have a requirement also to use DELETE, so not sure how we can handle this.
Any idea how we can achieve this requirement of using DELETE if we are going with the approach of using CONNECT-HTTPS rules.