ROBIN Orchestrator is a client-server application and is deployed on a centralized server.
The application server can be deployed in the three standard variants described below. Individual configurations can be deployed upon agreement.
- Clustered deployment variant
- Typical deployment variant
- Delivered as a virtual machine
In order to realize its functionality, ROBIN Orchestrator also includes services. The following table shows these services and their descriptions
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 |
Обзор
Инструменты контента