Purpose:
WEB Orchestrator is a ROBIN platform component, a service for dispatching and administering robot launches. It allows you to launch robots by schedule/event and track the statuses of task execution, view logs and errors.
Let's consider the main functionalities of Web Orchestrator:
- Access rights differentiation: manage access rights to applications, robot schemes, finished robots, etc.
- Robot and action storage: centralized storage of robot schemes, finished robots and action packages
- Robot versioning: Storing multiple versions of the same scripts or finished robots in remote storage
- Workstation monitoring: Collecting and displaying operational information about the status of remote workstations
- Remote robot launching: launch ready robots on remote workstations
- Maintaining RDP connection to the right accounts to execute UI robots
- Collecting robot data: tracking which robots are currently running, where and who is running them, what their current state is
- Work with resource queues: create your own resource queues and use them in robots' work
Solution components:
The Web version of the Robin platform consists of various modules that are accessible from one common interface. One of the modules is the "Orchestrator" module.
Orchestrator is one of the modules included in the ROBIN platform and is designed to run and control the execution of program robots created with ROBIN Studio. The module is available only to users with the "Orchestrator administrator" role.
The table below summarizes the main services included in Orchestrator and what each service is responsible for.
Service | Service description |
Keycloack | Application for implementing a single point of authentication and authorization, as well as for managing user rights: setting and checking user rights. |
Rabbit | A message queue that provides data transfer from RMS to other components |
WildFly | Application server |
Nginx | WEB interface server |
Elastic | Log storage component. Designed for storing and indexing logs of robots and other Robin components. |
Logstash | Log collection component. Necessary for collecting logs of robots and other Robin components and transferring them to Elastic. |
PostgreSQL | PostgreSQL DBMS server. It is intended for storing information. |
Nexus | Package storage repository manager. Required for storing and managing (including versioning) packages of robot actions available in ROBIN Studio, packages of robot sources and packages of finished robots. |
Rdp | Microsoft RDP (Remote Desktop Manager). A component for establishing and holding an RDP connection to the host on which the robot will run. |
HAProxy | Load Balancer |