Conceptos

Las integraciones interactúan directa o indirectamente con múltiples componentes de los diferentes productos de UiPath. El propósito de esta página es proporcionar a los nuevos usuarios de UiPath (o aquellos que busquen un repaso) una descripción general de los diferentes componentes.

Esta página se centra en los productos y componentes relevantes para las integraciones. No está destinada a cubrir todos los productos y componentes de UiPath.

Después de leer esta página, adquirirá una comprensión de alto nivel de los diferentes productos de UiPath y sus relaciones entre ellos.

Productos

Comenzaremos con los productos con los que interactúa al desarrollar sus integraciones. Hay tres productos de usuario final que se utilizan para crear, administrar y ejecutar tus proyectos de automatización: Studio, Orchestrator y Robot.

Producto	Descripción
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.

Componentes

Cada producto incluye componentes con los que interactuará directa o indirectamente desarrollando sus propias integraciones.

Studio

Los siguientes componentes de Studio se aplican principalmente al desarrollo o uso de una integración de actividad.

Componente	Descripción
Actividades	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.
Dependencia	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.
Proyecto	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

Los siguientes componentes de Orchestrator se aplican principalmente al desarrollo o uso de una integración de conector.

Componente	Descripción
Tenant	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.
Proceso	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.
Entorno	An environment is a grouping of Robots that is used to deploy processes. For more information, see About Environments in the UiPath Orchestrator guide.
Paquete	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.
Cola	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.
Activos	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.
Trabajo	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

Los siguientes componentes de Robot se aplican tanto a las integraciones de actividades como a las de conectores.

Componente	Descripción
Servicio	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.
Ejecutor	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.
Asistente de 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

Ahora que hemos presentado y definido los diferentes componentes, veamos cómo se relacionan entre sí gráficamente.

Componentes

El siguiente diagrama de arquitectura proporciona una descripción general de alto nivel de las relaciones entre los componentes del producto tratados en las secciones anteriores.

Integraciones

El siguiente diagrama de arquitectura muestra la relación entre los conectores y las actividades desde el tiempo de diseño hasta el tiempo de ejecución.