Product specifications

• DB2 UDB for iSeries V6 with Client Access AS400
• DB2 UDB for i v6.1 with Client Access AS400
• Generic datasource through OLE DB
• MS Access 2010 through ODBC
• MS Excel 2010 through ODBC
• MS SQL Server 2005, 2008, and 2008 R2 through OLE DB
• SAP HANA 1.0 SP3 through ODBC
4.1.2 64-bit Microsoft Windows support
Connection Server comes with the SAP BusinessObjects Business Intelligence platform and then
supports installation on both 32-bit (as in-proc) and 64-bit MS Windows environments (as in-proc and
remote server).
Vendors do not provide 64-bit middleware for the following databases through ODBC on Microsoft
Windows:
• Greenplum 3
• Ingres database 9
• MS Access 2003 and 2007
• MS Excel 2003 and 2007
• PostgreSQL 8
• Progress OpenEdge 10
• text files
• Data Federator XI 3.0 Query Server
• Salesforce.com
64-bit Microsoft Windows also does not support the following OLAP databases and their middleware:
• SAP BW through SAP BAPI
• MS Analysis Services through OLE DB for OLAP
• Oracle Essbase through the Essbase middleware
For all these data sources, the Data Access layer is able to work with 32-bit middleware on 64-bit
versions of Microsoft Windows. This functionality is handled through a specific deployment that consists
of two Connection Servers running simultaneously in server mode. The first one is 32-bit and runs
connections to data sources that cannot handle 64-bit middleware, while the second one is 64-bit and
runs connections to the other data sources. As the cs.cfg file is common to both servers, they share
the same configuration.
Restriction:
This architecture implies you cannot run the same data access driver on both servers. However, you
can establish a generic ODBC connection on either 32-bit Connection Server or 64-bit Connection
Server, but not on both servers at the same time.
2012-03-1526
Learning data access specifics