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.
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. Both integration with the corporate user directory and organization of internal storage are supported |
Rabbit MQ | A message queue that provides data transfer from the server to the client applications of the ROBIN platform |
WildFly | Application server (back-end) |
Nginx | Application server (front-end) |
ElasticSearch | Component for centralized storage and indexing of execution logs of robots and ROBIN platform components |
Logstash | Component for collecting logs of robot execution and operation of ROBIN platform components |
PostgreSQL | PostgreSQL DBMS server. Can be used by PostgresPro if a license is available |
Nexus | Package storage repository manager. Required for storing and managing (including versioning) packages of robot actions available in ROBIN Studio, packages of robot schematics and packages of finished robots |
RobinRDPmanager | Remote desktop manager. Allows you to create and hold an RDP connection to a host for the duration of a robot that requires a graphical session to run |
HAProxy | Proxy server. Organizes a single point of communication between the ROBIN platform client applications and the server. It also acts as a load balancer in a cluster deployment variant |