Overview
DataBlend offers two ways to connect to Fluence. Via our convenient DataBlend Fluence connector and via the database connector. Both offer a unique solution to users.
Connector Configuration
-png.png?width=688&height=364&name=Screenshot%20(1095)-png.png)
|
Field Name |
Required/ Optional |
Description |
|---|---|---|
|
Type |
Required |
Fluence |
|
Name |
Required |
Provide a unique name for this credential |
|
Base URL |
Required |
Enter the associated base URL. Example: https://fluenceapi-xy.fluence.app |
|
Tenant ID |
Required |
Enter the associated Tenant Id within the User Profile. |
|
API Key |
Required |
Enter the associated Tenant Id within the User Profile. |
Database Configuration
The database connection string must be correct for the server making the database connection. If the DataBlend server will be making the connection, then the database must be available on the internet.
To make a connection to a Fluence database, the following credentials are needed:
|
Field Name |
Required/ Optional |
Description |
|---|---|---|
|
Type |
Required |
Database |
|
Name |
Required |
Provide a unique name for this credential |
|
Connection Type |
Required |
SQL Server |
|
Connection String |
Required |
The connection string should be in the correct format for the Fluence database you are connecting to. String example: Data Source=Server_Name\Instance_Name; Initial Catalog=TestDatabase; Persist Security Info=True; User Id=Username; Password=PW Where: Server_Name\Instance_Name = e.g. us-east-2-np.database.windows.net TestDatabase = database name Username/PW = SQL Server user name/password The entire connection string will be masked to protect server and password details. |
Setting Up DataBlend Connection Within Fluence
First, you need the API Client Id and API Secret keys from within DataBlend.
In DataBlend: click on the account (person) icon to the top right, then Manage Profile. The keys are to the top right (you will have to click the eye icon to see the Secret); note them down.
In Fluence: Configure -> Connection Strings, and add one (note the name for your Fluence workflow), Provider: DataBlend. Paste in the below; replace YourClientId and YourSecret with the values from DataBlend, but leave the quotation marks in:
{
"ClientId":"YourClientId",
"ClientSecret": "YourSecret"
}
You will also need to set up a Fluence workflow that runs a stored procedure to populate the relevant Staging Table – Fluence can assist with this.
Remote SQL Server credential cannot be tested, the test will always fail. Testing can be done and the connection verified through running a collector.