Konzepte

Integrationen interagieren direkt oder indirekt mit mehreren Komponenten in den verschiedenen UiPath-Produkten. Diese Seite soll neuen UiPath-Benutzern (oder solchen, die eine Auffrischung suchen) einen Überblick über die verschiedenen Komponenten geben.

Diese Seite konzentriert sich auf die Produkte und Komponenten, die für Integrationen relevant sind. Sie ist nicht beabsichtigt, alle UiPath-Produkte und -Komponenten abzudecken.

Nachdem Sie diese Seite gelesen haben, haben Sie ein umfassendes Verständnis der verschiedenen UiPath-Produkte und deren Beziehungen zueinander.

Produkte

Wir beginnen mit den Produkten, mit denen Sie bei der Entwicklung Ihrer Integrationen interagieren. Es gibt drei Endbenutzerprodukte, die zum Erstellen, Verwalten und Ausführen Ihrer Automatisierungsprojekte verwendet werden: Studio, Orchestrator und Robot.

Produkt	Beschreibung
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.

Komponenten

Jedes Produkt enthält Komponenten, mit denen Sie direkt oder indirekt interagieren und Ihre eigenen Integrationen entwickeln.

Studio

Die folgenden Studio-Komponenten gelten hauptsächlich für die Entwicklung oder Verwendung einer Aktivitätsintegration.

Komponente	Beschreibung
Aktivität	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.
Abhängigkeit	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.
Projekt	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

Die folgenden Orchestrator-Komponenten gelten hauptsächlich für die Entwicklung oder Verwendung einer Connector-Integration.

Komponente	Beschreibung
Mandant	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.
Prozess	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.
Umgebung	An environment is a grouping of Robots that is used to deploy processes. For more information, see About Environments in the UiPath Orchestrator guide.
Paket	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.
Warteschlange	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.
Assets	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.
Auftrag	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

Die folgenden Robot-Komponenten gelten sowohl für Aktivitäts- als auch für Connector-Integrationen.

Komponente	Beschreibung
Dienst	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.
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.
UiPath Assistant	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

Nachdem wir nun die verschiedenen Komponenten vorgestellt und definiert haben, sehen wir uns nun an, wie sie sich grafisch aufeinander beziehen.

Komponenten

Das folgende Architekturdiagramm bietet einen allgemeinen Überblick über die Beziehungen zwischen den Produktkomponenten, die in den obigen Abschnitten behandelt wurden.

Integrationen

Das folgende Architekturdiagramm zeigt die Beziehung zwischen Connectors und Aktivitäten von der Entwurfszeit bis zur Laufzeit.