The ConnectionTypes element has one or more child elements called ConnectionType. Each ConnectionType element specifies how the Integration service connects to a database. You define a name for each connection type using the Name attribute.
The JDBCDriver element contains information used to create JDBC connections. This element has one attribute, DriverName, as shown in
Table 9-1. The JDBCDriver element has three child elements, ConnectionString, ConnectionProperties, and LibraryPath, as shown in
Table 9-2.
The ConnectionString element provides a template for the JDBC connection string. The parameters enclosed in percent signs (%), for example %server%, are placeholders for the values you type on the Data source connection properties page, shown in
Figure 9-1, when you create a data connection definition. These values are retrieved from the data connection definition (DCD) file when the Integration service creates a connection.
You can exclude a portion of a connection string when no value is provided for a connection parameter by enclosing it in double brackets ([[...]]). In the following example, to exclude the IANAAppCodePage parameter from the connection string when the value is left blank, define the ConnectionString element as follows:
[[IANAAppCodePage : CODEPAGE=%IANAAppCodePage%]] is not included in the connection string unless the IANAAppCodePage parameter is set.
The CatalogFilter element filters catalogs returned by the JDBC driver when Information Object Designer displays a list of tables, views, or stored procedures in the New Maps dialog. By default, all catalogs are returned. Like the template for the JDBC connection string, the catalog filter can contain placeholders for the values of connection parameters, for example:
The ConnectionParams element defines the parameters that are used in the ConnectionString element. The ConnectionParams element has a single child element, ConnectionParam. Here is an example of a ConnectionParam element that defines the server parameter: