My ODBC client application would not work with the CIS ODBC driver until I set the the COMPOSITE_DSN_XML variable

Available Languages

Download Options

PDF (3.9 KB)
View with Adobe Reader on a variety of devices
ePub (73.9 KB)
View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle) (73.9 KB)
View on Kindle device or Kindle app on multiple devices

Updated:March 21, 2017

Document ID:201169

Introduction

Why would ODBC client application doesn't work with the CIS ODBC driver until COMPOSITE_DSN_XML variable is set?

Introduction

This document describes why Open Database Connectivity (ODBC) client application doesn't work with Cisco Information Server (CIS) ODBC driver until COMPOSITE_DSN_XML variable is set.

As CIS comes with an ODBC driver. If you are using an ODBC client (e.g. WinSQL), your client can use the driver to connect to a CIS server and subsequently access published resources.

Why would ODBC client application doesn't work with the CIS ODBC driver until COMPOSITE_DSN_XML variable is set?

The CIS ODBC driver has a dependency on the compositeNN.xml file (NN is the version number). This file is located under the $COMPOSITE_HOME directory by default. The ODBC driver relies on the COMPOSITE_DSN_XML variable to find the file.