Database Connection

  • Updated

A Database Connection endpoint is used to create a globally named connection to a database server that can subsequently be used across any number of Database Tables, SQL Query definitions and Execute SQL Query Actions.


The following is a description of the Database Connection Edit form:


Specifies the logical name of the Database Connection that Database Table, SQL Query definitions and Execute SQL Query Actions will refer to within the rule application


Specifies the provider chosen for the database connection. It can be OLEDB, SqlServer, Oracle, etc. More details for selecting a provider are described below.

Connection String

Specifies the parameters the rule engine should use when connecting to this database such as the type of database server, the computer name or IP address, the database name, the user id, etc. This must be an "OLEDB" format connection string at authoring time. Note that this connection string may be overridden via the SDK at runtime, with any connection string type (OLEDB, Sql Server, Oracle etc.) or an open transaction or connection object.

The mceclip1.png button launches the data provide form shown below to assist with the construction of a valid connection string.



The user can choose the desired provider and click on the mceclip3.png button. The configure button brings up a pop-up which allows the user to key in the settings required to build a valid connection string.

If OLEDB is selected as the provider, the click on Configure button brings up the "Data Link Properties" screen as shown below. The tab "Provider" on the "Data Link Provider" screen gives a detailed list of all the providers the users can choose from.


For "Other" providers, the click on the configure button brings up the "Custom Provider form". Below is an example to configure an ODBC connection, using the Custom provider form.


Was this article helpful?

0 out of 0 found this helpful



Please sign in to leave a comment.