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.

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.

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

Guidelines on Progress Hybrid Data Pipeline usage

When you choose Progress DataDirect Hybrid Data Pipeline (HDP) as a Database Server selection, cloud deployments of Corticon for Java and .NET can talk with an HDP server. The HDP server in turn has the driver to talk to one or more datasources. Where HDP is effectively a proxy to datasources, the semantics of each datasource are exposed to Corticon. Corticon needs the mapping and dialect to map data types and to know what dialect of SQL to speak.

When creating a HDP data source, configure the HDP URL end point by identifying its HDP (DNS) Server name <server> and port <port> address (default port is 8443, but this might be a different port based on the HDP Server configuration).

Use the defined HDP user credentials for accessing the data source and provide its name <datasource_name> in the data source field in the connection URL.

Corticon supports a limited set of data sources which must be selected from when setting up the HDP data source in Corticon. Only the data from these sources are semantically understood by Corticon and proper SQL statements are generated for the target data source.

HDP requires a secure (SSL) connection. Hence, a SSL certificate must be uploaded as described in "Enabling a client to publish to a secure Corticon Server" in the topic Secured deployment on Java web services to enable encrypted data traffic. Upon installation of the HDP Server, a .pem file (certificate) is generated and stored in the /redist directory. Use this file to upload to the Corticon Studio and Corticon Server Java key stores.

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: