How data from an EDC Datasource integrates into rule output

An EDC connector enables interaction with its connected database, its Datasource, to read and write data from rule executions. Without database connectivity, Decision Service execution takes data in the request payload, modifies it through rules, and then returns the data in the response. When EDC is used, the Datasource can enrich the data in the request, and can store the result in the database. The following sections show separately the effects in read-only and read-update scenarios. Included in these examples are variations that use the Extend to Database feature to further enrich results.

To enable adequate complexity, the scenarios use data provided and the familiar Cargo.ecore Vocabulary:.

The sample Rulesheet is defined as shown:

The Datasource data in this section was established in a Microsoft SQL Server installation as described in the topic Quick Steps for setting up the Cargo sample

Contents

• When Datasource access is Read Only
• When Datasource access is Read/Update