Understanding Components 

Enterprise edition of AssistEdge involves installation and configuration of the components as per the deployment model you choose. Before you proceed with the installation, it is important to understand the product components and prepare your system for it. 


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


The components are categorized into:

 

Server-Side Components

Server-side components can be logically segregated as UI or backend components. 

  • UI Components (Web) are the server-side components with which you directly interact for user management, designing automation processes, creating, and managing Robots and so on.
  • Backend Components (app) are the server-side components that form the transactional backbone of AssistEdge. You do not interact directly with these components. The backend components must be accessible only to the AE components and any other access must be blocked by the firewalls.  

 

Below is the list of server-side components:

  • ControlTower: It is a web-based administrative and monitoring system for users, roles, license, robots, and others.
    It enables the administrator to configure various aspects of AssistEdge such as create and update users, assign role to the user, control, and update system 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 components of AssistEdge and sends the notifications to the intended recipients. For the Linux based system, download libicu Linux package from here and install it.
  • Messaging (Rabbit MQ): It is a message-oriented middleware that helps the various components to communicate with each other.
  • TxnStore (Open Distro): It is the search and analytics engine. All the data related to automation processes such as, the transactional data are stored in the Open Distro.
  • Reporting (Kibana): It is used for reporting of the data that is stored in Open Distro. It helps to search, view, analyze and project the data in an easy-to-understand format such as charts, tables, and maps.
  • ETL (Logstash): It is a data processing pipeline that sends data to the Open Distro.
  • LowCode: It is a web-based system which provides the drag-drop and point-click abilities to build feature rich responsive web applications. LowCode built applications have accessibility over desktop, laptop, tablets and mobile powered by iOS, Android, or Windows OS.
  • AssistEdge Core Cognitive Engine: 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 AssistEdge. It consists of Baked In ML and cognitive services.
  • AssistEdge Premium Cognitive Engine: It is the Advanced Machine Learning component of AssistEdge that helps in building business context specific complex use cases that requires a full-blown Artificial Intelligence ML Platform. Note that, Premium engine is not installed as part of the AE RPA installation.

 

Client-Side Components

Client-side components are supported only on the Windows system and must be distributed to the end user. 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. The Automation Studio includes automation configuration capabilities for varied and heterogeneous technology applications.
  • EnterprisePersonalAssistant: It delivers attended automation capabilities.
  • 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. Robot Agent can be created via Proctor as well as manually.

    Proctor enables the creation of robot agents from ControlTower. It also helps to start, stop, and update the robot agent from ControlTower itself. It auto-starts the Robot agents and Robots (that were already in the running state), whenever the system restarts.

 

NOTE:  
  • Make sure that the time is in sync between the system running the robot and AE servers; else, the instance won’t work as expected. In order to sync time between different workstation in a network refer w32tm /resync command.
  • It is recommended to create Robot Agents via Proctor.

 

  • Engage: It delivers automation driven operational productivity. Its unified dashboard non-intrusively integrates with disparate applications and technologies to provide a relevant and contextual view.