Concepts

Les intégrations interagissent directement ou indirectement avec plusieurs composants des différents produits UiPath. Le but de cette page est de fournir aux nouveaux utilisateurs UiPath (ou à ceux qui recherchent une mise à jour) un aperçu des différents composants.

Cette page se concentre sur les produits et composants pertinents pour les intégrations. Il n’est pas destiné à couvrir tous les produits et composants UiPath.

Après avoir lu cette page, vous aurez une compréhension approfondie des différents produits UiPath et de leurs relations entre eux.

Produits

Nous commencerons par les produits avec lesquels vous interagissez lors du développement de vos intégrations. Trois produits pour utilisateurs finaux sont utilisés pour créer, gérer et exécuter vos projets d'automatisation : Studio, Orchestrator et Robot.

Produit	Description
Studio (build)	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 (manage)	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.
Robot (run)	A Robot is an execution host that runs your automation projects. For more information, see the Robot Guide.

Composants

Chaque produit comprend des composants avec lesquels vous interagirez directement ou indirectement en développant vos propres intégrations.

Studio

Les composants Studio suivants s'appliquent principalement au développement ou à l'utilisation d'une intégration d'activité.

Composant (Component)	Description
Activité	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.
Dépendance	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. For more information, see and About Dependencies and Managing Packages in the Studio Guide.
Projet	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.

Orchestrator

Les composants Orchestrator suivants s'appliquent principalement au développement ou à l'utilisation d'une intégration de connecteur.

Composant (Component)	Description
Locataire	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.
Processus (Process)	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.
Environnement (Environment)	An environment is a grouping of Robots that is used to deploy processes. For more information, see About Environments in the UiPath Orchestrator guide.
Paquet (Package)	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.
File d'attente (Queue)	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.
Actifs	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.
Job	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.

Robot

Les composants Robot suivants s'appliquent aux intégrations d'activités et de connecteurs.

Composant (Component)	Description
Service	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.
Exécuteur (Executor)	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.
Assistant UiPath	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 UiPath Assistant in about the UiPath Robot guide.

Putting it all together

Maintenant que nous avons présenté et défini les différents composants, voyons comment ils sont reliés graphiquement.

Composants

Le schéma d'architecture suivant fournit un aperçu de haut niveau des relations entre les composants du produit abordés dans les sections ci-dessus.

Intégrations

Le diagramme d'architecture suivant montre la relation entre les connecteurs et les activités, de la conception à l'exécution.