Control Compliance Suite v11 can connect to and collect from external data sources to collect data. One such connection can be an ODBC connection to a MySQL database server. It has been noted that using a 32 or 64bit MySQL driver and/or the 32 or 64bit windows "ODBC Data Source Administrator" makes a difference when configuring such a connection within CCS. This article outlines what to watch out for and how it works with the current version of CCS (v11.0.546.10100, PU 2012-1, SCU 2012-3).
No error as such but a previously configured "ODBC data source" using the windows "ODBC data source Administrator" might not show up when configuring the Data location within CCS.
The root cause of the unexpected behaviour is related to ODBC Data Source created DSN. The CCS console expects and only lists 32bit DSN's - the CCS data collector on an x64 (64bit) CCS manager that does the actuall data collection expects and only works with 64bit DSN's.
This scenario is assuming a single CCS system that contains all the components, CCS Application server, Manager and Console, all-in-one, installed on a Windows 2008 R2 (x64) system.
Step 1 - install the 32 and 64 bit MySQL ODBC drivers.
Step 2 - create the 32bit DSN using the 32bit version of "ODBC data source Administrator" - this connection will be seen and used by the CCS console.
Fig 1. This shows the directory and two DSN's - one named "32bit" for illustration purposes only.
Step 3 - create the 64bit DSN using the 32bit version of "ODBC data source Administrator" - this connection will be used by the CCS Manager for data collection.
Fig 2. This shows the directory and two DSN's - one named "64bit" for illustration purposes only.
Step 4 - create a data location in CCS
Fig 2. This shows only two DSN's - only the 32bit DSN's - it does not show the 64bit DSN. Because we named the 32bit and 64bit DSN the same - the console is allowed to select a DSN with the name "MySQL_DSN" but the CCS manager will look for and use the 64bit DSN with the same name i.e. MySQL_DSN.
Step 5. - create a Data System within CCS.
continue with the configuration until finished - further configuation and use of External Data Integration is outside the scope of this knowledgebase article, for more information around External Data Integration please consult the CCS administration guide.
As you're reading this article, you might also be interested in the following articles:
MySQL External Data Integration - Error: The specified DSN contains an architecture mismatch between the Driver and Application. - http://www.symantec.com/docs/TECH199664
Control Compliance Suite - MySQL External Data Integration - Error: You have an error in your SQL syntax. - http://www.symantec.com/docs/TECH199666
Control Compliance Suite v11
Windows 2003, 2008, 2008R2 - x64