You should work through the procedural style of the Corticon Tutorial: Using Enterprise Data Connector (EDC) to experience configuring and using this new feature.
Note: The functionality described in this chapter is always enabled in Studio; however, Corticon Servers need explicit licensing for EDC, even in evaluation installations. Contact Progress Software technical support or your Progress Software representative for additional details on licensing and RDBMS support.
Note: When using the Vocabulary editor, setting it to show details exposes properties related to database interaction. When you enter data in properties when showing details and then switch to hide those properties, the properties are just hidden, not changed or cleared.
When you create a Vocabulary, you use the properties of the Entities, Attributes, and Associations to define Rulesheets, Ruletests, and Ruleflows. Everything is local -- any data required by the rules is either entered as Ruletest input or is generated by the rules during execution.
Corticon EDC lets you define mappings to a database so that rules can "reach out": to access (query) a database directly, and then retrieve what it needs "on-the-fly" during execution, thus enriching the information available to the rules.
As useful as this capability is to the technical people responsible for Rulesheet deployment and integration, a rule modeler might ask "what's the cost to me?" In designing EDC, Corticon made this capability as transparent to the rule modeler as possible. In other words, we don’t want the rule modeler to worry about where the data "fed" to Corticon Server is stored, how it’s retrieved and assembled, or how it is sent. We want the rule modeler to be concerned with getting the rules right, and let everything else follow from there. This is consistent with our declarative approach to rule modeling – modeling rules that express what to do, not how to do it.
This chapter focuses on the aspects of rule modeling that are affected by the Corticon Enterprise Data Connector.