You can assign 1 user account as a windows assisted sign on AND you can assign a user account in the windows vault that acts as a user carrying out the automated process. So, 1 account to login and 1 account local to the VDI to carry out tasks. This is not a central configuration. How does this scale? You cannot image this concept and deploy from image. You will have machines all using the same windows login and same accounts to run the applications if you deploy from image. This will be an issue for licensing and session control. Can someone enlighten me how this approach is tackled?I am looking to use Pega on Xendesktop VDI. Is this possible?
Can anyone assist in providing knowledge on scalability from a read only VDI image using Pega Runtime? My understanding is that 1 windows login and 1 account is used for automated process and both accounts are configured on the master machine. You deploy 200 machines from an image then they will al be using the same windows login details and account for automation.
Posted: 3 years ago
Posted: 15 Jan 2019 15:17 EST
Grigory Petrov (Grigory Petrov)
Senior Consulting Manager, Pega Consulting
Hi, Gareth - this is more a of a use case question than Pega technology. Your biggest hurdle is to actually verify that from a business perspective you will have no concurrency conflicts when using the single network ID to automate applications on multiple VDIs. For example, if you are going to have bots pull work from the same queue on multiple machines, will there be conflicts? Do your business applications allow concurrent logins by the same user ID? If you are all clear with that from your business application security and access management, then Pega supports the ability to scale VDIs in the RPA mode. If you use Robot Manager and Enable RPA parameter when installing runtime, then your multiple machines will be automatically registering themselves with RPA console by using a combination of the network ID + machine name. This ensures uniqueness of each VDI for bot work force management purposes, yet allows you to "clone" VDIs with the same network ID. More on this is here: https://community.pega.com/knowledgebase/articles/tutorial-automating-processes-your-pega-platform-application-robotic-process
Posted: 3 years ago
Posted: 25 Jun 2019 5:57 EDT
Gareth Carson (GarethC8)
Thanks for the information. So, we cannot have concurrent logins due to monitoring and licensing requirements. In a very rare case would you ever have systems that you can utilize the same logins. I get from a management perspective the machines can register with unique network Id's, but the goal here is to clone a VDI using Machine Creation Services and have these machines log on with unique unattended accounts. This is RPA, not RDA. Happy to discuss.