Integrations directly or indirectly interact with multiple components across the different UiPath products. The purpose of this page is to provide new UiPath users (or those looking for a refresher) an overview of the different components.
This page focuses on the products and components relevant to integrations. It is not intended to cover all UiPath products and components.
After reading this page, you will have a high-level understanding of different UiPath products and their relationships with one another.
We'll start with the products that you interact with when developing your integrations. There are three end-user products that are used to build, manage, and run your automation projects: Studio, Orchestrator, and Robot.
Studio is the desktop application that enables you to build simple to complex automation projects using Studio's built-in and/or your custom activity packages.
For more information, see the Studio Guide.
Orchestrator is a web application to help you create, deploy, execute, and monitor the automation resources that execute repetitive business processes.
For more information, see the Orchestrator Guide.
A Robot is an execution host that runs your automation projects.
For more information, see the Robot Guide.
Each product includes components that you'll directly or indirectly interact with developing your own integrations.
The following Studio components primarily apply to the development or use of an activity integration.
An activity is the building block of process automation. Each activity is an action that you want a robot to perform against a software application, such as as clicking a button, reading a file, or writing to a log panel.
For more information, see the Activities Guide.
A dependency is a package that is linked to a specific project. The package includes existing activities that you want to use in your project. Dependencies are contextual and take into consideration each project's definition, including the activities that it uses, variables, input/output arguments.
An automation project is a graphical representation of a business process. It enables you to automate rule-based processes, by giving you full control of the execution order and the relationship between a custom set of steps.
For more information, see About Automation Projects in the Studio Guide.
The following Orchestrator components primarily apply to the development or use of a connector integration.
A Tenant is an isolated data set (e.g., packages, processes, queues, jobs, etc.) in a single instance of Orchestrator.
Tenants enable multiple teams/departments to orchestrate their own automation processes while sharing the same Orchestrator instance with the rest of the organization.
For more information, see About Tenants in the UiPath Orchestrator guide.
A process represents the association between a package and an environment. Each activities, it's time a package is linked to an environment, it is automatically distributed to the robots that belong to that environment.
For more information, see About Processes in the UiPath Orchestrator guide.
An environment is a grouping of Robots that is used to deploy processes.
For more information, see About Environments in the UiPath Orchestrator guide.
A package represents an automation project that is added to start building your Orchestrator instance.
For more information, see About Packages in the UiPath Orchestrator guide.
A queue is a container that stores multiple types of data you can use in complex automation projects.
For more information, see About Queues and Transactions in the UiPath Orchestrator guide.
Represent shared variables or credentials that can be used in different automation projects. They give you the opportunity to store specific information so that the Robots can easily have access to it.
For more information, see About Assets in the UiPath Orchestrator guide.
A job is the execution of a process on one or multiple robots. After creating process (deploying a Package to an Environment), the next step is to execute it by creating a job.
For more information, see About Jobs in the UiPath Orchestrator guide.
The following Robot components apply to both activity and connector integrations.
The robot service is the brain of all operations. It receives and facilitates the delivery of process information to provide the necessary instructions to the robot executor.
There are two service types, according to deployment: Service Mode (unattanded) and User Mode (attended).
For more information, see Service in the UiPath Robot guide.
The robot executor (UiPath.Executor.exe) is the component that is directly responsible for the execution of a process. Every time a job is own. To get started, an executor instance gets created by the robot service.
For more information, see Executor in the UiPath Robot guide.
The robot agent (UiPath.Agent.exe) is the user interface of the robot. It is a WPF application that displays the available jobs in a system tray window. As a client of the robot service, it can request following links to start or stop jobs, and change settings through an IPC protocol, based on user input.
For learn more information, see Tray in about the UiPath Robot guide.
Now that we've introduced and defined the different components, let's see how they relate to each other graphically.
The following architectural diagram provides a high-level overview of the relationships between the product components covered in the sections above.
The following architectural diagram shows the relationship between connectors and activities from design time to run time.
Updated about a year ago