Multiple robot accounts for running multiple processes but on same machine
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-09-20 09:02 AM
Hi,
Can someone please share me documentation on how to handle multiple robot accounts for running multiple processes (especially if the process belongs to different business units) running on a single prod machine. Need to understand how the blue prism will be configured and run in such scenario.
------------------------------
Ritansh Jatwani
Consultant
EY
Asia/Kolkata
------------------------------
Can someone please share me documentation on how to handle multiple robot accounts for running multiple processes (especially if the process belongs to different business units) running on a single prod machine. Need to understand how the blue prism will be configured and run in such scenario.
------------------------------
Ritansh Jatwani
Consultant
EY
Asia/Kolkata
------------------------------
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-09-20 11:37 AM
Hi Ritansh,
Blueprism has the concept of MTE (multi team environment) by which you could group the process based on business units.
create multiple AD groups for each BU and add robot accounts to them. you could have custom Blueprism roles created in the environment and associate this AD groups to them. once that is done you could restrict the process group access with the created roles.
when it comes to running process on same resources you need to define a windows login credential pattern for the different BUs (default is Windows login <Machine shortname> this needs to be modified along with miner tweaks in login agent object as well to use the pattern.
you will have to logout from the VM every time after the main process run completes and login to the VM with appropriate account that the subsequent process should be using.
All the AD groups we created at the beginning should have logon permission to all the VMs (or you can assign logon permission for the accounts of your choice to target VMs)
since we both work in EY you can reach out to me if you need help setting this up.
------------------------------
Jerin Jose
RPA Product SME
EY
Asia/Kolkata
*"If you find this post helpful, please press the "Recommend" Button.*
------------------------------
Blueprism has the concept of MTE (multi team environment) by which you could group the process based on business units.
create multiple AD groups for each BU and add robot accounts to them. you could have custom Blueprism roles created in the environment and associate this AD groups to them. once that is done you could restrict the process group access with the created roles.
when it comes to running process on same resources you need to define a windows login credential pattern for the different BUs (default is Windows login <Machine shortname> this needs to be modified along with miner tweaks in login agent object as well to use the pattern.
you will have to logout from the VM every time after the main process run completes and login to the VM with appropriate account that the subsequent process should be using.
All the AD groups we created at the beginning should have logon permission to all the VMs (or you can assign logon permission for the accounts of your choice to target VMs)
since we both work in EY you can reach out to me if you need help setting this up.
------------------------------
Jerin Jose
RPA Product SME
EY
Asia/Kolkata
*"If you find this post helpful, please press the "Recommend" Button.*
------------------------------
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-09-20 01:57 PM
Hi
Following links may help.
https://digitalexchange.blueprism.com/dx/entry/9648/solution/remote-desktop-services--blue-prism
------------------------------
Pritam Poojari
Solution Architect
Capgemini
Europe/London
------------------------------
Following links may help.
https://digitalexchange.blueprism.com/dx/entry/9648/solution/remote-desktop-services--blue-prism
http://portal.blueprism.com/customer-support/support-center#/path/1356860182
http://portal.blueprism.com/customer-support/support-center#/path/1140997822
------------------------------
Pritam Poojari
Solution Architect
Capgemini
Europe/London
------------------------------
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
23-02-21 10:44 AM
Hi Jerin,
This is exactly what we are looking to do at the moment. Could you give me some more detail on the required modifications to the windows login credential pattern and to the login agent object to be able to use it?
Many thanks,
------------------------------
Felix Oehl
Belgium
------------------------------
This is exactly what we are looking to do at the moment. Could you give me some more detail on the required modifications to the windows login credential pattern and to the login agent object to be able to use it?
Many thanks,
------------------------------
Felix Oehl
Belgium
------------------------------
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
23-02-21 02:07 PM
The good news is you don't have to edit the Login Agent. The ability to login to the same Runtime with different accounts requires some minor editing to the Login Process.
From there you can choose which account you want to use to login.
Logging into multiple sessions on the same host uses a different methodology. While technically possible it will likely involve rewriting some of your automations to recognize the application in the context of the user session. Not all applications work well with multiple sessions. You will also need to put each user profile on a different port. I would use 8181 to talk to the host to manage the sessions.
That being said Remote Desktop Sessions are being used successfully by some customers. The common denominator is they are running on dedicated hosts and understand RDSH very well. Their automations and environments are optimized for it.
------------------------------
Steve Waters
Platform Consultant
Blue Prism Professional Services
America/Chicago
------------------------------
From there you can choose which account you want to use to login.
Logging into multiple sessions on the same host uses a different methodology. While technically possible it will likely involve rewriting some of your automations to recognize the application in the context of the user session. Not all applications work well with multiple sessions. You will also need to put each user profile on a different port. I would use 8181 to talk to the host to manage the sessions.
That being said Remote Desktop Sessions are being used successfully by some customers. The common denominator is they are running on dedicated hosts and understand RDSH very well. Their automations and environments are optimized for it.
------------------------------
Steve Waters
Platform Consultant
Blue Prism Professional Services
America/Chicago
------------------------------
