Build, protect and deploy apps across any platform and mobile device
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate decision processes with a no-code business rules engine
Build mobile apps for iOS, Android and Windows Phone
Deploy automated machine learning to accurately predict machine failures with technology optimized for Industrial IoT.
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
As an IBM consultant for Cognos BI, my project experience is mostly related to the Cognos BI server, as well as TM1 within the Cognos family. However recently, I've been engaged with several shops running IBM Cognos Data Manager on Unix/Linux platforms such as AIX and Solaris SPARC looking for connectivity to SQL Server. I have also consulted on a couple projects running Cognos PowerHouse 4GL applications that required similar connectivity to SQL Server. And with the release of IBM Cognos BI 10.2, life in the Cognos world remains new and exciting for me.
Hopefully, every Cognos shop has seen my tutorial on connecting Cognos and SQL Server from Unix/Linux; and now I want to share what I learned working on a recent project where we engaged IBM support to configure the IBM Cognos Data Manager to integrate SQL Server data.
IBM Cognos Data Manager (formerly DecisionStream) is an ETL tool bundled with the Cognos BI and performance management solutions (including Rational Insight) to create data warehouses and data repositories for which operational SQL Server databases are a common source from Unix/Linux application servers. The Progress DataDirect Connect for ODBC SQL Server driver is recommended by IBM. And with the 7.0 ODBC release, we support the latest versions of SQL Server including 2012; and include native support for Windows Authentication from Unix/Linux against SQL Server without any external dependencies.
1. Download and install 32-bit DataDirect Connect for ODBC SQL Server driver for Unix/Linux.
2. Setup the Unix/Linux environment using the driver's odbc.sh or odbc.csh script in the install directory. In addition, configure the following environment variable:
setenv UDA_SS_DRIVER_MANAGER_LIBRARY libodbc.so:libodbcinst.so
2. Create an IBM Cognos Data Source Connection for Data Manager 10
Note: On the Connection Details tab, make sure to select "ODBC" and DBMS Type "SQL Server".
3. Test the connection using the sqlterm command line, for example:
connect ODBC 'UID=myUser;PWD=myPassword;DSN=mySQLServerODBC;DBMS=SQL Server;COGNOSSQL=FALSE'
4. Create and run a jobstream to access the SQL Server connection.
Call 1-800-876-3101 to speak with a live Solutions Consultant to learn how other organizations are using DataDirect SQL Server ODBC Driver to connect to SQL Server from IBM Cognos Solutions on Unix/Linux.
Sumit Sarkar is a Chief Data Evangelist at Progress, with over 10 years experience working in the data connectivity field. The world's leading consultant on open data standards connectivity with cloud data, Sumit's interests include performance tuning of the data access layer for which he has developed a patent pending technology for its analysis; business intelligence and data warehousing for SaaS platforms; and data connectivity for aPaaS environments, with a focus on standards such as ODBC, JDBC, ADO.NET and ODATA. He is an IBM Certified Consultant for IBM Cognos Business Intelligence and TDWI member. He has presented sessions on data connectivity at various conferences including Dreamforce, Oracle OpenWorld, Strata Hadoop, MongoDB World and SAP Analytics and Business Objects Conference, among many others.
Copyright © 2017 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.