skip to main content
Corticon Server: Data Integration Guide : Getting Started with Multiple Database Connectivity : Define multiple database connections
 

Try Corticon Now

Define multiple database connections

Note: Using the sample:Two ADC database connections are defined in the Vocabulary. Just enter their credentials, and then test each connection.
To connect a Vocabulary to a defined database where you will use SQL queries, define the connection as an ADC Datasource. In the project's Vocabulary editor, select the Vocabulary command Add Datasource > Add ADC Datasource, as shown:
An ADC tab is added to the root level of the Vocabulary. The ADC sample renamed the first Datasource to Patient Data which is now the name its tab, as illustrated:
where:
*Data Source Name: The connection name that displays on the Vocabulary tab. This is also its name that will bind this ADC connection to an instance of the service call-out in a Ruleflow. While you can change this name, it is a good idea to do so before you specify it in Ruleflow Service Call-out's Service Name.When you add additional ADC Datasource tabs, the default names will increment n in ADC_n.
*Description: Provide an informative description of the use of the Datasource you are adding.
*Use for Query Service: Indicates that the data source will contain query definitions. As there are two database connections in the sample, it is very important to distinguish which one store queries.
*Database Server: The database product. Click the dropdown menu on the right side of the entry area to list the available database brands. Corticon embeds Progress DataDirect JDBC Drivers for each database. These drivers provide robust, configurable, high-availability functionality to RDBMS brands. The drivers are pre-configured and do not require performance tuning.
*Database URL: The preconfigured URL for the selected database server. You must edit the default entry to replace (1) <server> with the machine's DNS-resolvable hostname or IP address and port , and (2) <database name> with the database name that was set up (typically case-sensitive).
*Username: The user credentials that enable connection to the database. The credentials are encrypted when the database access file is exported for deployment.
*Password: The specified user's password.
*Catalog Filter and Schema Filter: Patterns that refine the metadata that is imported during Import Database Metadata and Create/Update Database Schema.
Note: Filters are a good idea for production databases that might have hundreds or even thousands of schemas. As the Catalog filter value does not support wildcards, distinguishing two metadata import filters enables the use of wildcards in the Schema filter value: Underscore (_) provides a pattern match for a single character. Percent sign (%) provides a pattern match for multiple characters (similar to the SQL LIKE clause.) For example, you could restrict the filter to only schemas that start with DATA by specifying: DATA%. The ability to specify patterns is especially valuable when testing performance on RDBMS brands with applications that use multiple schemas.
Click the CONNECTION Test button. Confirm that you have a valid connection before proceeding.

Another database connection

When another ADC tab is added to the root level of the Vocabulary, you define a separate database connection. In the sample, the second Datasource was renamed to Treatment Data which is now the name on its tab, as illustrated:
Notice that this connection does not state to use it for the sample's query service as only one connection can be so designated. Confirm that you have a valid connection before proceeding.