IC Data Source Configuration

Some components of CIC depend on data stored in a variety of repositories (such as SQL Server databases, Access databases, different Exchange or IBM Domino data sources). Rather than tie CIC components directly to an external data source, these components reference a local CIC data source name, which points to a particular type of data repository. This allows CIC developers and administrators to change a data repository without having to change references to that repository.

For example, CIC report logs are currently stored in SQL Server databases and accessed via a CIC data source (called IC Report Logs in this case). This data source points to a SQL Server database and the ODBC DSN to set up connections to the report logs. Since the report logs and reports point to a CIC data source, they will not have to be reconfigured to support a new data source. Only the CIC data source must be reconfigured.

CIC supports basic data sources, including:

• ODBC - for most relational databases that include an ODBC driver (for example, SQL Server and Oracle)

• JDBC - for Java applications that use JDBC drivers to access ODBC compliant databases (not used in CIC by default)

• JDBC-ODBC - for the JDBC-ODBC bridge to let Java applications access ODBC compliant databases via ODBC drivers.

• MAPI - CIC no longer supports Microsoft Exchange MAPI-based integrations.

• LDAP - for contact directories that use an LDAP-enabled directory server.

• White Pages - for white pages directory data on the IC server.

Click on the above data source types to see help on how to configure that data source.