Corticon's ADC and EDC provide access to many different databases. This allows you to enrich the data being processed by your rules as well as persist the results of rule processing to your database. For the list of supported databases and versions, see the Corticon Resource Center.

Common Guidelines on Database Usage

Some Corticon features are not supported in certain supported databases. Data manipulations and database startup functions that might be required to ensure error-free interaction between Corticon EDC and a database are noted.

The mapping of database columns to a Corticon Vocabulary through SQL might experience problems when database columns have hyphens, spaces or other special characters (even though some databases and SQL parsers allow them). The generally accepted valid values are all alphanumeric characters and the underscore character. It is a plus to use all-lowercase names to avoid platform case inconsistencies. For more information on Corticon's accepted names, see the topic Vocabulary node naming restrictions

The feature of importing database metadata will infer associations when the information (foreign keys) is available in the data source's metadata.

Note: For the current list of supported databases and versions, access the web location Corticon Supported Platforms Matrix .

Guidelines on Progress OpenEdge Usage

Because OpenEdge and Corticon are companion products in the Progress portfolio, additional features are provided in both products to simplify their interaction. Corticon typically makes a Progress OpenEdge connection with port 5566 and OpenEdge credentials. Database Access actions let you create a Business Resource Vocabulary Definition (BRVD) file to create the database schema. You can import a .brvd file created in OpenEdge (see Progress OpenEdge documentation for details.) The function of importing into Corticon is described in Import an OpenEdge Business Rules Vocabulary Definition file .

Note: Startup of OE server - It is recommended that you start the OpenEdge database server with the following parameters within the Proenv window, shown here with values used in a test environment:
proserve db_name -n 65 -Mn 20 -Mpb 4 -Ma 20 -Mi 3 -S port_number
where: