A360 Workload management (WLM)| Multi Bot Deployment | Multi Bot Architecture |

Подписаться 1,6 тыс.

Просмотров 13 тыс.

50% 1

Hi All,
To get the notification for the next video's, Please like, share and subscribe the channel. This video explain the below things.
Work load management & Multi bot Implementation in A2019
1. Creation of work queues
2. Create Task to publish data to work queue
3. Create Task to retrive data from Work Queue
4. Create device pools & Run the bots with work queues.
5. Deploy bot on Multiple Machines

Опубликовано:

2 окт 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 18

@himanshutiwari5712 3 года назад

Amazing explanation

@gopinathsrimatthirumala3092 4 года назад

Good One

@kartik4svpbuilder 3 года назад

Great explanation

@ashwina.k5602 3 года назад

Hi Hithika, Your videos are really amazing and I really appreciate that you are willing to put in the effort to make these tutorials for us. Please continue to make more! Kind Regards, Hsa

@imranazam8071 3 года назад

I am able to understand Queue completely. I have replicated same concept and working like rocket :) Thank you Hithika Productions.

@hithikaproductions 3 года назад

👍

@naveengoud9793 4 года назад

Hi, thanks for making this video. Can u please make a video on Attended & Unattended bots with example.

@hithikaproductions 4 года назад

naveen goud sure

@arshu6869 3 года назад

Well explained. Appreciated

@VenkataBangarusetti 3 года назад

How can we configure multi-devices with multi sessions? for example, device-1 having 2 sessions and device-2 having 1 session, and 3 bot runners consuming 3 sessions?

@hithikaproductions 3 года назад

I guess it's not possible for the same machine twice to run on different session with two different runner licenses

@VenkataBangarusetti 3 года назад

@@hithikaproductions Thank you for your reply, Can you please elaborate as I can't understand. We created one queue and selected run as with 3 bot runners and selected one device pool. The device pool has 2 devices (device-1,device-2). but when running all the runners are trying to deploy in a single device i.e., device-1. Scenario-1: Device-1 having 2 login terminals and Device-2 having 1 login terminal.

@sivajagannadhpotnuru306 4 года назад

Hi This video give more information tome can you explain in detail of how to decide of threshold value of any other than pre-defined

@hithikaproductions 4 года назад

sivajagannadh potnuru threshold was nothing but, it trigger the bot upon the respective threshold reaches the work items in Queue. It is nothing but trigger the bot once the work items reaches the threshold in Queue

@andonii46 3 года назад

Great explanation. However, when each queue item has to be processed in multiple bot runners and we have to do initialization tasks (such as login and so on) before doing the actual process item in each Bot Runner , how can we handle this?

@hithikaproductions 3 года назад

Yeah we can handle it, basically there would be one data feeder bot and the other one was data process bot, let's include this initialisation things in the data process bot and deploy it on queue with different bot runners. There are some other approaches as well. Even you can handle it in single bot as well with necessary "if" conditions ect

@andonii46 3 года назад

@@hithikaproductions But what if one of the bot runners does not handle the init task properly or the item needs to be retried closing/opening apps?wouldn't that be a problem? Doing it with a single bot and a bunch of if statements is a bit annoying...

@hithikaproductions 3 года назад

@@andonii46 It dosen't make any troubles if We implement proper exception & error handling,