How open-rpa/openrpa works
Project type and purpose
• OpenRPA is a full-stack, plugin-driven desktop application for Robotic Process Automation (RPA).
• The core is a WPF/.NET client (“OpenRPA” folder) that provides a visual workflow designer and runtime.
• It dynamically loads many plugin modules (e.g., OpenRPA.Image, OpenRPA.IE, OpenRPA.SAP, etc.) to support different automation targets.
• There are companion services and integration layers:
– OpenRPA.Net (messaging library for backend communication)
– Named-Pipe wrapper and NativeMessaging host for browser integration
– RDService Windows service for unattended robot sessions
– JavaBridge/SAPBridge/TerminalEmulator for specialized app hooks
– PowerShell (OpenRPA.PS) and Node-RED connectors
File structure
• Top-level “OpenRPA” solution (.sln) contains:
– OpenRPA.Interfaces: shared interfaces (IPlugin, IDetector, IActivity, IPC services)
– OpenRPA (core WPF client)
– Per-domain plugin projects (OpenRPA.Image, OpenRPA.Database, OpenRPA.IE, …)
– Infrastructure libraries (OpenRPA.Net, OpenRPA.NamedPipeWrapper)
– External host processes (NativeMessagingHost, RDService, JavaBridge)
– Setup projects (WiX installers under OpenRPA.SetupProject & SetupActions)
– Docs and deployment manifests (docs/, manifests/, winget, chocolatey)
Supplementary README insights
• Emphasizes desktop installer, community docs, and “OpenFlow” backend for multi-robot orchestration.
• Mentions commercial support and links to the OpenFlow service (the server-side orchestration engine).
a. Main components
1. Desktop client (WPF UI + core runtime)
2. Plugin loader & runtime host
3. Plugin modules (Image, IE, SAP, Terminal, Database, Office, Script, Utilities, etc.)
4. Shared interface layer (OpenRPA.Interfaces)
5. IPC & integration layers:
– Named-Pipe wrapper
– NativeMessagingHost (browser extensions)
– JavaBridge and SAPBridge host processes
– RDService (Windows service for unattended mode)
6. Messaging & backend communication (OpenRPA.Net over WebSocket/REST to OpenFlow)
7. Local storage providers (Filesystem, LiteDB)
8. Installer & configuration (WiX projects, SetupActions)
9. Developer tooling (PowerShell modules, Node-RED connectors)
b. Relationships & interactions
• The WPF UI invokes activities which call into plugin modules via the shared interfaces.
• Plugins use detectors/hooks in their host processes to interact with target applications (e.g., SAPBridge.exe for SAP, JavaBridge.exe for Java apps, NativeMessagingHost for Chrome/Firefox).
• Plugins and core send/receive control messages via Named-Pipes and the OpenRPA.Net library to coordinate workflow execution and backend tasks.
• For unattended automation, the WPF client delegates execution to RDService, which runs as a Windows service under another session.
• Workflows and activity results are stored either in local files (Filesystem plugin) or in a local LiteDB database (LiteDB plugin).
• The core and plugins register with OpenFlow (cloud-hosted backend) via WebSocket messages (OpenRPA.Net) for orchestration, queue management, and metrics.
• PowerShell cmdlets and Node-RED nodes connect to the OpenRPA IPC or WebSocket endpoints for external automation control.
c. Architectural patterns & design principles
• Plugin architecture via a central IPlugin/IActivity contract (OpenRPA.Interfaces)
• Host-process isolation for each automation domain (browser, Java, SAP, terminals)
• IPC channels for within-machine communication (Named-Pipes, Native Messaging)
• Messaging bus for backend orchestration (WebSocket + JSON messages)
• Modular installer using WiX to compose plugins and services
d. Key technologies & frameworks
• .NET Framework 4.x / .NET Core (WPF)
• WiX Toolset for MSI installers
• Named-Pipes and Native Messaging for IPC
• WebSocket‐based messaging (OpenRPA.Net)
• PowerShell modules
• Node-RED integration
Detail without over-partitioning
• Distinct process (e.g., separate JavaBridge and SAPBridge)
• Plugin interface layer (OpenRPA.Interfaces) as the glue
• Distinguish local execution vs. remote/backend orchestration