-
Print
-
DarkLight
Database and Third-Party Integrations
The following databases can be accessed through the Integration Builder:
- EdgeReady Database
- External Database,
- Salesforce Database
- SAP Database
- SnowFlakes Database
The Data can be fetched from their respective platforms through the different lanes. While the EdgeReady Database is our own it can be accessed directly from the On-cloud lane. The others are 3rd party databases and are accessed from the plugin lane. All the data fetched are stored in the EdgeReady Drive.
EdgeReady Database
For the EdgeReady Database, 5 actions can be performed in the Integration builder. These actions are done using variable mapping by inserting necessary input and output variables in the "where" and "to" spaces.
DB Operation | DB Operation on Canvas |
---|---|
Select Data:It is a simple SQL statement block to select data from a database table with or without a where condition. The data can be sorted and stored in a variable(table) The user provides the following details:
Note For more information on input and output variables, refer Input, Output and Local Variables section. | ![]() |
Create Data:It is a SQL statement block to create a new table with the required columns. The user provides the following details:
| ![]() ![]() |
Update Data:It is a SQL statement block to update existing data within a table. The user provides the following details:
| ![]() |
Delete Data:It is a SQL statement block to delete existing data within a table. The user provides the following details:
| ![]() |
Prepared StatementsIt is a feature used to execute same or similar SQL statements repeatedly with high efficiency. Uses:
A SQL query in the Prepared Statement oval box The required Parameters are added. An output variable is added in the "to" oval box. Click the Variable mapping icon to map the columns if required. | wip |
Third Party Servers - (External Database, SAP, and Salesforce):
The Edgeready platform supports the extraction of data from the following third party servers:
- External Database
- Salesforce Database
- SAP database
- Snowflakes Database
The configuration of plugins and adapters for the third party servers with the Edgeready platform is done in the Administration->Integrations tab. Once configured, the data can be accessed through the relevant plugin and adapter in the Integration builder for any logical operations.
For example: The user needs to fetch data from the SAP database, process it and store it in the local Edgeready database. In this scenario, the user inserts the plugin lane block (that holds the Plugin and adaptor information)within the On-cloud lane block, and within the plugin lane fits the required action block for data manipulation that is executed on the SAP data. The output can be stored in the Edgeready database by inserting the required blocks in the On-cloud lane.
External Database:
External database refers to any SQL database that the user can integrate with the Edgeready platform. Currently, the user can access the MySQL, Oracle and MSSQL databases.
- For external databases, the action blocks are added to the Plugin lane. It requests user credentials (selection of plugin name and adapter name) in the Plugin lane.
- When the plugin and adapter are selected by the user, the username is displayed in the first oval box and the user is prompted to enter the password in the second oval box.
- The external database consists of the Select, Create, Update, Delete, and Prepared actions blocks. The action and functionalities are the same as in the EdgeReady DB.
- Similar to EdgeReady DB, these actions are done using variable mapping by inserting necessary input and output variables in the "where" and "to" spaces provided.
Salesforce Database
The Salesforce database does not require a plugin but the salesforce system type is configured in the Administration->Integrations tab by adding a New Adapter. The adapter information is then selected by the user in the Integration builder to access the salesforce data and manipulate it with the action blocksthat are available for salesforce database
- The user selects the adapter from the dropdown list and the username configured for the selection is generated in the first oval box. The user then enters the corresponding password in the second oval box.
- There are 4 actions that can be performed in the Integration Builder. The options are List, Create, Update, & Delete.
- The action and functionalities for Create, Update & Delete are the same as in the EdgeReady DB.
- The List helps to retrieve a list of data items rather than a single file or folder. It is similar to a SELECT query.
- Like in the EdgeReady DB and external DB, these actions are done using variable mapping by inserting necessary input and output variables in the "where" and "to" spaces that are provided.
Salesforce Thumbnail and on Canvas operations | Salesforce All Operations in the on-cloud lane |
---|---|
SAP
The SAP database requires a plugin and adapter to be configured in the Administration->Integrations tab. For servers like Edgeready, Salesforce, the data retrieval is query-related. Whereas, in the SAP server, data is fetched using Functions and not queries.
The data is not retrieved in the form of tables. They are fetched in Key-value pairs that are in the form of transactions.
The SAP action blocks are:
| ![]() |
There is a select plugin option for the SAP block. The plugin is mandatory for SAP blocks. All the SAP operations are carried out in the plugin lane. They are explained below.
SAP action blocks | SAP Operation on canvas |
---|---|
BAPI / RFCIt is a standard application interface that enables the Edgeready server to access the SAP database. The user provides the following details:
| ![]() |
CommitCommit helps to fetch data and perform certain operations to it. It helps to conclude a database and start a new one. | ![]() |
Roll BackRollback helps to restore values to previous values by negating recent changes. It undoes all changes and restores the database and updates. | ![]() |
Start/Stop Transaction:A function call can be started or stopped using the Start/Stop Transaction Blocks. Note Both Start and Stop transactions can be done after either commit or rollback operations. All SAP actions follow a logical destination path. | ![]() |
- Business Application Programming Interface (BAPI) is used in mySAP to achieve business-related functionalities.
- It is a remote-enabled functional module provided by SAP, that enables stable and standardized methods to achieve seamless integration between the R/3 system and external applications (legacy systems and add ons).
- BAPIs are implemented as RFC-enabled function modules and are created in the Function Builder of the ABAP Workbench.
- RFC is the protocol used by SAP for remote communications (between SAP & non SAP) as well as communication between two independent systems(non SAP) or modules of the same system.
EXAMPLE: How does a typical SAP block function in real-time?
| BAPI/RFC: |
SnowFlakes Database
The Snowflakes is a Datawarehousing database that holds structured and semi-structured data. While accessing it from the Edgeready DB it does not require a plugin but the system type is configured in the Administration->Integrations tab by adding a New Adapter. While configuring the adapter, the databases that are available to the user in snowlflakes are listed and the user can choose any one. This database is available for selection in the Integration builder while working with the Snowflakes action blocks
- The data in Snowflakes database are organized into schemas which in turn are organized into tables.
- There are 4 actions that can be performed for snowflakes in the Integration Builder. The options are Select, Create, Update, & Delete.
- The action and functionalities for Create, Update & Delete are the same as in the EdgeReady DB.
FTP Block:
FTP helps transferring files from a particular source to a specified destination. This is done by specifying the URL path.
Service Block & Sharepoint:
These are services provided to the 3rd party servers. They work both in on-cloud and Plugin lanes.
Business Users:
Refers to the users of the App created in the platform. Refer to Users & Roles section for more information.