Question
CSC GLobal
US
Last activity: 18 Jun 2020 8:28 EDT
We are getting below exception log and we have not installed robotic manager
Resource not found;com.pega.pegarules.pub.PRException: Failed to retrieve Rule-Service-Rest instance robotics.v1.register using default rulesets (Data-Admin-ServicePackage robotics doesn't exist)
Pegasystems Inc.
GB
Hello,
Are you trying to connect a RPA to Platform? if so the exception is coming from the RPA calling the registration endpoint and not finding it.
To connect a RPA to Platform you require Robot Manager to be installed.
CSC
US
Hi Herma,
Thanks for your response.
Our implementation is we queue the assignment to Robotic Workbasket and from there the RPA bot will take over. Then provide a handshake once the RPA Bot process is complete. Bot reference the StartupProject for deployable. We are yet to implement Robot Manager and Package Server to manage the RPA bots. We did it in Dev so updated the configuration in the RunTimeConfig XML for PegaServerURL and PackageServer tags under Robotics. This config got copied to Prod but don't have neither Robot Manager nor Package Server setup in Prod. Is there a way to get rid of these exceptions by doing any configuration changes in the RuntimeConfig or CommonConfig XMLs until we implement Robot Manager and Package Server.
Pegasystems Inc.
GB
Hi,
You'll need to at least install Robot Manager and add it to your application stack to get the required APIs. Otherwise the RPA won't be able to register to pull the work in the work queue.
You don't need to leverage Robot Manager to manage the bots or the assignments but it is required to register the bots.
CSC
US
Hi Herma,
Thanks. Yes we will go ahead and move the Robot Manager to all environments. Another question, in Dev we have installed the Robot Manager for Pega 7.2.2 version(PegaRoboticAutomationConsole:01.01.01). But still not able to see the Rule-Service-Rest instance robotics.v1.register or the ServicePackage robotics. Does it need any specific Access Group/Role to be added to view it.
Pegasystems Inc.
GB
Hi,
Which version of Pega Platform and Robot Runtime are you using? Registration service wasn't introduced until RM4 before then it was using the api/v1/case endpoint to register the operator. If you are using a new runtime version. The runtime will attempt to use the latest endpoint and if not found will revert to the old one. That is probably why you're seeing the exception.
CSC
US
Hi Herma,
RunTime version 19.1.18.0
RM Version 1(since our Pega Platform version is 7.2.2)
Will the RunTime revert to api/v1/case endpoint considering the RM version?
Pegasystems Inc.
GB
Hi,
You're using something that it is 3+ years old with something that it is few months old. The solution works but you'll see the exception in the logs which you can ignore. The option to remove the exception would be to use a Runtime which is as old as the Platform but I wouldn't recommend that.
Is it not possible to upgrade the Platform version? at least to 7.3 or 7.4? That way you could run RM 4 or even RM6 which includes remote scheduling control for RPAs.
Angel
CSC
US
Hi Herma,
Thanks. Our upgrade to 8.3 is underway and will happen soon during Q2 or Q3. So we will mostly then install RM Version 8.3.1 which will help avoid this error. Thanks for your response.