ROBIN Orchestrator is one of the key components of the ROBIN platform for the Enterprise delivery variant.
The main purpose of the Orchestrator is to control the launch of program robots in automatic mode and to provide differentiation of user access to them.
Access to the Orchestrator interface is realized as a web application, and its management is available in the unified Robin web interface, in a separate menu section.
 

 

Queues and resources


Orchestrator provides a number of features:
•    Performs "resource queue" maintenance for complex workflows, using tags, combinations of blocking and item processing priorities, etc.
•    Orchestrator acts as a centralized repository for resources, actions, and IP credentials


•    It performs assignment of conditions and launches on the basis of production calendars (which the user can create and customize independently)


•    Orchestrator provides the ability to share robots with UI and in the background 
•    Compliance with enterprise requirements for information security, management, architecture based on LDAP protocol 

Automatic task allocation


Orchestrator provides a wide range of functionality to automatically allocate and launch tasks

  • Orchestrator provides automatic scheduled launch of digital assistants, for this purpose it selects a virtual machine based on the assistant parameters, on which hosts, and how many assistants need to be launched to process scheduled tasks
  • To ensure continuous operation, the orchestrator builds assistant queues to optimize the time to complete a task based on its parameters for continuous operation
  • The user can create resource queues in Orchestrator to scale the job
  • To prevent the situation when an application or information systems are temporarily unavailable when attempting to execute an assistant, Orchestrator provides the ability to customize the number of attempts to launch workflow tasks and their interval
  • To allow assistants to run on virtual hosts, Orchestrator can be configured to automatically launch an RDP session (when a robotic task needs to work with the interface of the systems the assistant is using
  • Multiple production calendars are available to set up and use for flexible distribution of assistant launches according to enterprise calendars



  • Нет меток