DB Link
uniflow.plugin.dblink •
Category: IT & Network •
Version: v1.0.15
DB Link Plugin Reference Manual
1. Overview
Plugin Name: DB Link
Type: IT & Network
Identifier: uniflow.plugin.dblink
Description
Connect to MySQL, PostgreSQL, MSSQL, or Oracle databases. Browse tables and stored procedures, read data as collections, and perform INSERT/UPDATE/DELETE operations from rules.
2. Configuration Parameters
The following configuration fields are available in the User Interface for this plugin:
| Configuration Setting | Description |
|---|---|
| Database Provider | Specifies the database provider. |
| {Binding HostLabel} | Specifies the {binding hostlabel}. |
| Port (Optional) | Numeric value specifying the port (optional). |
| {Binding DatabaseLabel} | Specifies the {binding databaselabel}. |
| Username | Specifies the username. |
| Password | Specifies the password (secure). |
| Additional Parameters (Optional) | Specifies the additional parameters (optional). |
| Schema Filter (Optional) | Specifies the schema filter (optional). |
| Connection Pool Size | Specifies the connection pool size. |
| Max Rows Per Query | Specifies the max rows per query. |
| Command Timeout (Sec) | Numeric value specifying the command timeout (sec). |
| Poll Interval (Sec) | Numeric value specifying the poll interval (sec). |
3. Exposed Routes & Data Types
The following routes are available in the Uniflow catalog for this plugin:
| Display Name | Route ID | Kind | Category | Access | Data Type |
|---|---|---|---|---|---|
| {table.Name} (Row Count) | {table.CatalogItemId}:count | Value | DB Link | Read | Int64 |
| displayName | id | Value | DB Link | ReadWrite | Json |
| displayName | id | Command | DB Link | Execute | String |
Route Parameters: displayName
This route requires the following parameters when executing commands or writes.
| Parameter Name | Display Name | Type | Required |
|---|
4. Usage Examples
Scenario A: Reading/Monitoring Data
To monitor data from DB Link, add the corresponding Input Node in the Rule Editor and select the desired property from the catalog. Link its output to any logical comparison or directly to an Action Node.
Scenario B: Triggering Actions
If the plugin supports writable properties or actions, use an Action Node in the Rule Editor. Configure the Target property to point to the DB Link action, and supply any required parameters mapping from your rule's logic.