Understanding Components

Before you proceed with the installation, it is important to understand the product components and prepare your server for it. 

Digital Worker has multiple components that work together to provide an end-to-end solution.

The components are categorized into:

• Server-Side_Components
• Client-Side Components

 

Server-Side Components

Below is the list of server-side components:

• Control Tower: It is a web-based administrative and monitoring server for users, roles, license, robots, and others. It enables the administrator to configure various aspects of Digital Worker such as create and update users, assign role to the users, control, and update server settings and so on.
  
  It enables them to set up and manage robots running on remote machines.
  
  It also enables process SMEs to access Decision Workbench that acts as a bridge between digital and human workforce to support Digital Workers in variety of scenarios such as business decision making, business data review, and exception handling.
• Vanguard: It is a background service that helps to perform various background jobs, monitors the status of the Digital Worker components and sends the notifications to the intended recipients.
• Messaging (RabbitMQ): It is a message-oriented middleware that helps the various components to communicate with each other.
• TxnStore (OpenSearch): It is the search and analytics engine. All the data related to automation processes such as the transactional data are stored in the OpenSearch. 
• Reporting (OpenSearch Dashboards): It is used for reporting of the data stored in OpenSearch. It helps to search, view, analyze and project the data in easy-to-understand formats such as charts, tables, and maps.
• ETL (Logstash): It is a data processing pipeline that sends data to OpenSearch.
• ML: It is the Machine Learning (ML) component that helps in the execution of tasks using algorithms and statistical models. For example, it predicts SLA adherence for all transactions in Digital Worker. It consists of Baked In ML and cognitive services.

 

Client-Side Components

Client-side components are supported only on the Windows machine and should be downloaded by the end user from the Admin module. Robot Farm also forms a part of the client-side component that helps in the execution of automation process.

Below is the list of client-side components:

• Automation Studio:It is designed to create and configure automation process workflow. Automation Studio includes automation configuration capabilities for varied and heterogeneous technology applications.
• Robot Farm: It signifies collection of Robot Agent, Robot and Proctor.
  
  Robot is an automation runtime that runs the automation processes built in Automation Studio. 
  
  Robot Agent is the component that enables your machine to host multiple robots. It also helps in the management of robots such as start a robot, stop a robot and so on.
  
  Proctor enables the creation of robot agents from Control Tower. It also helps to start, stop, and update the robot agent from Control Tower itself. It auto-starts the Robot agents and Robots (that were already in the running state), whenever the server restarts.
  
   

  NOTE:

  Make sure that the time is in sync between the server where the robot is running and the Digital Worker server; else, the server will not work as expected. To sync time between workstations on a network, enter w32tm /resync command. It is recommended to create Robot Agents via Proctor.