Articles → AUTOMATION ANYWHERE → Introduction To Workload Management In Automation Anywhere

Introduction To Workload Management In Automation Anywhere

In this article, we will discuss about workload management in automation anywhere.

What Is Workload Management?

Consider an example where you have 100k transaction per day and each transaction would take 5 minutes to complete.

One day is not sufficient to complete all the transactions. One way is to run the process parallelly on different machines. This could be accomplished using workload management feature in automation anywhere.

Workload management is a process of strategically distribute the work to maximize performance.

Workload Management Vs Manually Distributing The Task

Workload management	Manually distributing the task
No custom coding required implementing workload management.	Custom implementation is required for workload management.
Automatic distribution of work items.	Manual distribution of work item.
Centralized console for workload configuration and monitoring.	No centralized console for workload configuration and monitoring.
Automatic failover of BotRunners.	Customized implementation of exception handling.
Based on priority workload pools are flexible.	Customized implementation is required to implement flexibility.
Queues are encrypted so not required to implement data security explicitly.	Customized implementation is required for data security.

Components Of Workload Management

Following are the components

Data queue (container for work items or transactions)
Task bot
Device pool (collection of bot runner)- Device pool can execute work item of one process or task.
Automation that connect the above 3 components.

Advantages Of Workload Management

Multiple tasks run in parallel so that task can be completed within SLA.
Bot runners associated with device pool can be reused.

How Workload Management Works

See the picture below where we have a list of queues (transactions) and list of bot runners. Device pool is responsible to map queue with bot runner.

In this way multiple queues gets executed using bot runner in parallel.

Picture showing the representation of how workload management is done in automation anywhere

Click to Enlarge

Roles

Following are the roles in workload management

System role
1. Pool admin – This is the role to create device pool. Role name is AAE_Pool Admin in control room.
2. Queue admin – This is the role to create queues. Role name is AAE_Queue Admin in control room.
User defined role
1. Bot runner role.
2. Queue participants and consumers.

It is important to note that queue and pool can have multiple owners.

Posted By -	Karan Gupta

Posted On -	Wednesday, January 9, 2019

Query/Feedback

Your Email Id		**

Subject		*

Query/Feedback	Characters remaining 250	**