Human-Bot Collaboration Server
The Human-Bot Collaboration Server enables centralized management of its clients--Assistant, Designer, and Launcher.
In the data center, Human-Bot Collaboration is installed on a server and configured to interact with the other data center components. The Human-Bot Collaboration Server can be installed on the same server on which the Control Room is installed.
Important: The Human-Bot Collaboration Server cannot be installed on a machine
(server-level) with IQ Bot.
The Human-Bot Collaboration Server includes services with the following functions:
- Human-Bot Collaboration authentication and authorization
- Human-Bot Collaboration messaging
- Human-Bot Collaboration queuing
- Human-Bot Collaboration data storage
- Human-Bot Collaboration configuration and execution
The required data center components of the Human-Bot Collaboration Server include a Microsoft SQL Server with a Human-Bot Collaboration database.
Human-Bot Collaboration components
- The Human-Bot Collaboration Server acts as the single point of access and control for executing Human-Bot Collaboration features.
- The Launcher, Assistant, and Designer are connected to the Human-Bot Collaboration Server before they can be used.
- Launcher can only execute Human-Bot Collaboration forms (.atmf) and task lists (.atmt) that are associated with a Human-Bot Collaboration Server and a TaskBot (.atmx).
- All forms and task lists are first published to the Human-Bot Collaboration Server from the Designer.
- Every single Human-Bot Collaboration activity is authenticated against the Human-Bot Collaboration Server.
- The Human-Bot Collaboration Server is responsible for publication and delivery of forms and task lists. Built-in version control features facilitate seamless collaboration for end-to-end business process automation by multiple users.
- All the triggers are managed by the Human-Bot Collaboration Server.
- Forms and TaskBots are deployed on the Launcher machine for execution by the Enterprise Client (Bot Runner).
- All historical activity data is stored in the Human-Bot Collaboration Server audit logs.
Centralized access control
- Least privilege and access control user access are implemented in the Human-Bot Collaboration Server role-based access control (RBAC).
- All users are created and assigned roles from the Human-Bot Collaboration Designer.