Posted: 21 Feb 2018 13:54 EST Last activity: 25 Feb 2019 7:56 EST
Best practice Pega Robotics Deployment
We are starting with Pega Robotics within our company and are facing a lot of questions.
We will be using both RPA and RDA and want to have a good deployment strategy.
A Package server will of course be the heart of our infrastructure with Pega Robot Manager(s).
But here is one of the questions.
How to implement a good Pega Robot Manager environment?
We have an infrastructure with DEV/TST/ACC/PRD Pega Clusters with an AES PRPC server monitoring those.
We want use RPA robots fired from Pega Cases, with virtual PC's. Those can be managed by Robot Manager.
But, do we need 1 robot manager then or 1 per PEGA Application, we have about 40 apps on each environment, or can we manage all of those with one Robot Manager.
We are in the assumption that RDA's can be managed by just one Robot Manager, but know that this will only list them out. Managing has to be down through workgroup.
Maybe my question is not completely clear, but, we are planning RDA and RPA, within a multiple divisions company with a lot of workgroups and want to use Robot Manager and Package Server to manage all of them. What is the best practice?
Is there a company who has such an infra running and are you/they willing to help us?
Up till now we did not get a satisfying answer so who can help us?
Lots of questions ... let me try to answer some of them.
You should need only a single Robot Manager per environment.
RPA work is managed by WorkGroup and WorkBasket. Robots are assigned to a WorkGroup and must be able to respond to all case types that are contained in that WorkGroup. Robot Manager will show all WorkBaskets that are set to Robotic type.
RDA work is managed at the department or user level. You assign a deployment package to departments and/or to users and when a user starts runtime the correct package will load.