Question
Nationwide Building Society
GB
Last activity: 17 Oct 2024 7:25 EDT
REST service replacement challenges for 22.1 runtime & robots
We're currently utilising the REST service for robots on 19.1.102 and 19.1.132 that communinicate with PEGA applications using an SSL certificate (bound to port 9443).
The 22.1 documentation states that the REST service is no longer needed because of infrastructure changes to the way certificates are handled in Robot Studio version 22.1.
We're also packaging the 22.1.34 runtime and upgrading the robots
As part of the upgrade of the robots will we need to remove from the code all REST service ccomponents?
If so what do we replace them with?
Do we still need to deploy the SSL certificate as per the current 19.1 robots?
Are there any other factors we need to take into consideration as part to ensure successfull communication between PEGA applications and 22.1 robots
Accepted Solution
Updated: 17 Oct 2024 7:25 EDT
Pegasystems Inc.
US
@RichardB3397For Robots using 22.1, Pega Platform now uses the Constellation Messaging service to communicate with Robots for your attended RPA. With the Constellation Messaging service, the calls will be made via the service. In terms of the code inside your bots, that does not need to be changed. The Robot Activity event will still fire as expected, and you can retrieve any of the data exposed as fields in the same manner.
The Robot Manager REST Components you are using shouldn't be affected by this change either. If you are using those to call other APIs in your Pega application, you may continue to do so.
You do not need to deploy the SSL cert with 22.1. As long as you are using the Constellation messaging service, you should be OK.